DV Info Net

DV Info Net (https://www.dvinfo.net/forum/)
-   CineForm Software Showcase (https://www.dvinfo.net/forum/cineform-software-showcase/)
-   -   HDLink -- various questions (https://www.dvinfo.net/forum/cineform-software-showcase/43083-hdlink-various-questions.html)

Dave Campbell June 2nd, 2007 08:13 AM

HDlink fails 25u, works hc1
 
Okay, not sure what is going on. If I hook my hc1 to my system,
and run hdlink, sees the unit fine and I can control it. But, when I hook my 25u deck, all I get is no capure devices available. I am using Vista, and when I turn on the 25u, the system sees it just fine.

Any ideas?

Dave

Dave Campbell June 2nd, 2007 08:51 AM

Same thing happens in PPro2 also. HC1 works, m25u no seen.

Dave

Dave Campbell June 2nd, 2007 09:00 AM

Okay, found the issue. I have the unit set to convert hdv-dv.
Once I turned this off, works fine.

Dave

Salah Baker June 11th, 2007 06:55 PM

HDLink Camera-Specific Capture Settings
 
http://www.cineform.com/products/Tec...apSettings.htm

I assume this was for HDV and not for HD-SDI or Hdmi to Hdsdi for a couple of the cams?

David Newman June 11th, 2007 07:07 PM

Yes, for HDV tape capture. The only difference is Canon 24F over HDSDI does require pulldown removal checked.

Salah Baker June 11th, 2007 07:24 PM

Figured so, but it may be a good idea to break it down from just HDV to other capture options..

You Know at first, I spent some time with the Box Varicam to figure out the HD-SDI from it,,,

Terry McGregor June 21st, 2007 02:58 PM

HDLink conversion degrades video sample size
 
Does anyone know why NEO HDV HDLink downgrades the Video Sample Size from 32 bit to 16 bit, when converting HDV to AVI? It also changes something else (from 25 to 19 - see results below), but I'm not sure what it is. Is there any way I can fix these problems?

I also used Sony Vegas Render As to do the same thing and I compared the results. The above mentioned problems to not occur in Vegas.

Here's what I did
Step 1: Downloaded source file (millard.m2t) from http://www.vasst2.com/HDV/FX-1_images.htm
Step 2: Used HDLink to convert millard.m2t file to .avi (Quality = High)
Step 3: Used Sony Vegas to render millard.mt2 file to .avi (Quality = Best)
Step 4: Compared these files in the Sony Vegas Project Media window.

Here are the results

Source file (millart.m2t)
Video: 1440x1080x32, 25.000fps, 00:00:14;25, Alpha=None, Field Order=Upper field first, MPEG-2
Audio: 48,000 Hz, Stereo, 00:00:14;25, MPEG Layer 2
Size: 47MB

Cineform HDLink - Converted file (millart-001.avi)
Video: 1440x1080x16, 25.000fps, 00:00:14;19, Alpha=None, Field Order=Upper field first, Cineform HD Codec 3.11
Audio: 48,000 Hz, 16 bit, Stereo, 00:00:14;19, Uncompressed
Size: 130MB

Sony Vegas - Rendered file (millart-002.avi)
Video: 1440x1080x32, 25.000fps, 00:00:14;25, Alpha=None, Field Order=Upper field first, Cineform HD Codec 3.11
Audio: 48,000 Hz, 16 bit, Stereo, 00:00:14;25, Uncompressed
Size: 126MB

David Newman June 21st, 2007 06:12 PM

16 or 32-bit of almost meaningless information.

It is doesn't make any difference to the file. You even use a hex editor to could 16 to 32, same file will play. 16 is really the correct value for 4:2:2 YUV data, the MPEG could even be considered to have only 12-bits per pixel.

Dan Robinson June 22nd, 2007 06:24 PM

HDLink randomly stopping captures/playback/seeking
 
I've been having an issue with HDLink quietly and randomly stopping captures and playback from my FX1. I'm capturing the m2t file only (no AVI conversion) from my FX1. There is no error message, the program just stops the capture anywhere from 20 seconds to 4 minutes or more in.

At this point I can't do any long captures (over 4 minutes or so) because the software is always stopping it at some point. On shorter captures, I have to watch the program like a hawk, because it often stops the capture prematurely without me knowing it.

HDLink will also send random 'stop' signals to the camera while I'm seeking or playing back video on the camera while it is connected via firewire. I'll be watching footage on the LCD and all of a sudden the camera will stop playing. I have to keep re-starting playback.

I have plenty of disk space and no other programs running.

Has anyone else seen this?

David Newman June 22nd, 2007 06:50 PM

Try another Firewire port, as M2T only capture is very easy. That should not be happening.

Dan Robinson June 23rd, 2007 05:17 PM

Thanks for the reply. Unfortunately my laptop only has one firewire port. I can capture in downconverted SD (AVIs) from the camera into Premiere 1.5.1 without the problem happening. The spontaneous stops only happen in HDLink when capturing HDV.

Wayne Johnson June 24th, 2007 06:42 AM

I had the same problem on my old system. If I used msconfig to stop all startup services, HDLink worked fine. I never tracked down which startup function was causing the problem. Later versions of HDLink reduced, but did not eliminate, the problem.

Terry McGregor June 25th, 2007 05:49 PM

HDLink with the Smart Rendering option enabled, solves the first problem. The Video Sample Size remains at 32 bits.

Does anyone know the answer to my second question? What does the below number "19" represents and why was it change from 25 to 19 by HDLink?

Cineform HDLink - Converted file (millart-001.avi)
Video: 1440x1080x32, 25.000fps, 00:00:14;19, Alpha=None, Field Order=Upper field first, Cineform HD Codec 3.11
Audio: 48,000 Hz, 16 bit, Stereo, 00:00:14;19, Uncompressed

NOTE: This information was taken directly from the Sony Vegas Project Media Window.

David Newman June 25th, 2007 06:20 PM

It is not a "problem" we hardwire the number to 32-bit for Vegas for smart rendering, because Vegas likes not becuase it has any significant meaning. You are looking too hard for data that has no meaning. :)

The 25 vs 19 are the number of frames in the duration field. Often the frame at the beginning or more commonly the end of an M2T are not decodable, we don't put those frames in the AVI. If you into numerology, ask Sony why they they have counted to 25 frames on a 25 fps clip, which should only show frame numbers from 0 to 24, (as NTSC shows frames 0 to 29.)

Marc Colemont August 19th, 2007 10:04 AM

Propect HDLink Stops converting after 250Kb
 
I recently upgraded from AspectHD to ProspectHD. So I don't know if it's related to that...
M2T Clips captured with my DR-HD100 I cannot get to convert properly to AVI through HDlink. Any file which I take (even old M2T-clips which were still on my system were I know for 100% that they work) doesn't want to convert. When it starts on the first file it stops after 250Kbyte and the progressbar goes back to zero. No errors in the Log-window.
All M2T-files play fine in VLC-player.
Does the ProspectHD compared to AspectHD needs more resources from the computer? Currently I'm still running on a P4, 3GHz, 1024MB machine.
I had originally Build 129, upgraded to build 135, but the same result.

David Newman August 19th, 2007 10:41 AM

There is no difference in the M2T handling for Prospect HD and Aspect HD, so more likely there was an install issue. I just tested my PHD M2T conversion, and its working fine. Uninstall Prospect HD, and re-install again. If the problem continues, work with support tomorrow -- file a trouble ticket today.

Marc Colemont August 19th, 2007 01:25 PM

Thank you David,
I will do that.

Dean Gough September 8th, 2007 04:48 PM

HDLink File conversion
 
Easy question, when converting .m2t, avi files etc using HDLink does the process convert them from 8 bit to 10/12 bit Cineform avi files or do you have to render them out within AE or PPro to increase the bit depth?

I've searched the forum and can't find a definitive answer.

David Newman September 8th, 2007 10:45 PM

YUV 4:2:2 is always stored with 10-bit precision (even for 8-bit sources.)
RGB 4:4:4 and RGBA 4:4:4:4 is always stored with 12-bit precision.

Dean Gough September 8th, 2007 11:23 PM

Thanks for the answer David.

Just to be absolutely clear, this is for both live captured and manually converted files?

Within HDLink there doesn't seem to be a facility to choose to convert YUV material to 4:4:4. Does it choose the output bit depth based on the colour space of the incoming video file?

I'm using the demo at the moment and I've converted a few files. When I bring them back into AE7 they only show up as "millions of colours" which Iwould presume is only an 8 bit depth. The demo Viper footage all imports with "trillions of colours"




Quote:

Originally Posted by David Newman (Post 741433)
YUV 4:2:2 is always stored with 10-bit precision (even for 8-bit sources.)
RGB 4:4:4 and RGBA 4:4:4:4 is always stored with 12-bit precision.


David Newman September 9th, 2007 10:09 AM

In AE7 are use the CineForm importer or the default AVI importer? The AE AVI importer is only 8-bit.

For 4:4:4:(4) file creation you will need to use AE or PPro, HDLink link needs some upgrades for DPX file input.

Dean Gough September 9th, 2007 04:21 PM

I assume it uses the Cineform importer as the demo Viper footage interprets as "trillions of colours". When footage is rendered out in AE7 as 444 and then reimported it also displays the high bit depth.

Just to be sure it is not the AE importer I will force the Cineform importer with the Shift/Ctrl key and post the results.

Thanks for your help.

Quote:

Originally Posted by David Newman (Post 741568)
In AE7 are use the CineForm importer or the default AVI importer? The AE AVI importer is only 8-bit.

For 4:4:4:(4) file creation you will need to use AE or PPro, HDLink link needs some upgrades for DPX file input.


Dean Gough September 10th, 2007 12:57 AM

Forcing the Cineform importer seemed to cure the problem. Files converted by HDlink appear as "trillions of colours".

Highly likely we would convert all files to 444 anyway for compositing. So guess we have to run through AE anyway.

Interestingly these show up correctly even when Cineform importer is not forced.

Thanks for the help.

Bruce Findleton September 13th, 2007 10:36 AM

Missing HDLink in build 91
 
I just installed Aspect HD build 91 and it doesn't install HDLink. In Start>Programs>Cineform there is only the Tools folder, no Aspect folder.

And while on the topic of Tools, what is the Register Components script for?

David Newman September 13th, 2007 11:15 AM

It should be there, and no other reports of is missing. un-install and re-install.

"Register Components" -- used under tech support directive if certain errors occur -- can fix installation issues.

Bruce Findleton September 13th, 2007 11:55 AM

Uninstalling manually instead of letting the installer do it did the trick. Thanks.

Nick Williams October 10th, 2007 12:07 PM

HDLink m2t converting problems
 
I recently purchased Neo2k to see it would improve my workflow with the V1u, DR-60 and FCP (on a dual 2.66 MacPro). But I haven't been successful yet in converting an m2t file into the cineform intermediate codec. I'm trying to run HDLink in parallels, but I get an error message in the log and nothing happens.
Log:
pSinkFilter->SetFileName(T2CW(pOutputFilename), NULL) (0x80004005 - Unspecified error) in (ConvertGraph.cpp at 2099)

Anyone seen anything similar?

-Nick

David Newman October 10th, 2007 12:25 PM

Would I repeat myself and say try support, however it this case I know what it is, and it is funny one. You haven't installed QuickTime on the XP side of you Mac, a tad ironic, and you are trying to create an MOV file under XP which requires QuickTime.

Nick Williams October 10th, 2007 04:33 PM

Hi David, thanks for the response. I'm a little windows challenged, that makes total sense. I'll try it out! thanks!

David Taylor October 10th, 2007 06:54 PM

Nick, it is counter-intuitive until it sinks in. In fact when we installed Parallels the first time we scratched our head on the same issue until we had the "Doh!" realization....

Nick Williams October 10th, 2007 09:49 PM

Looks like we're good to go. I hear you on the "Doh!" feeling. ;)

thanks guys.

Nick Williams October 13th, 2007 03:39 PM

more parallels and hdlink issues
 
I seem to have an interesting snag using hdlink to convert my m2t files on a shared .psf drive.

Within parallels, using HDLink I can select an m2t file that resides on a shared .psf drive folder, and successfully convert that file to cineform intermediate to any destination on the C: drive.
But, when I change the hdlink prefs to have the 'output destination' be one of my shared drive folders, the completed converted file is corrupt and won't open.

Has anyone else using parallels with hdlink run into this?

-thanks

David Newman October 13th, 2007 08:15 PM

What is a .psf drive?

Nick Williams October 13th, 2007 08:55 PM

well, I guess .psf drive is not the right lingo. It's a parallels shared folder. So in parallels you can map a link to another one of your local hard drives outside of your main c: drive.

David Newman October 13th, 2007 09:11 PM

Please file a trouble ticket with support so they can test that on Monday.

Carl Middleton October 17th, 2007 02:32 PM

HDLink Compatibility?
 
If I compile I movie using the AME encoder instead of Cineform M2T, will HDLink still properly send it to tape?

It controls the camera, and successfully threw the master copy to tape. However, I rendered the air copy using AME because I was getting a 'failed to allocate video buffer' error repeatedly while halfway thru compiling the air copy in the odd hours of last night (only difference is added QT Animation w/ alpha tags and some cineform intros/outros)

When I try to throw to tape, it just sends a blue screen. Camera turns on and records nothingness. Dohp!

Anyone know of a quick fix for either of those two issues? Any tricky settings I may have missed in AME, or something? The video file does play fine, and I've tried reboot and reinstalling aspectHD.

Thanks!
Carl

PS - I had this problem before with the trial for Cineform before I purchased, and my workaround was to create the m2t, uninstall cineform, create a new project, import m2t, and render and record from premiere, then reinstall cineform for the next go-round. Meep. Looots of work. It had been working fine since then, on a clean install of windows, cineform and premiere.

Tim Bucklin October 17th, 2007 05:48 PM

Hi Carl,

We have not been able to successfully use AME to create an M2T that HDLink will send to tape.

I'm currently working on integrating another MPEG encoder into our Aspect and Prospect families that will allow users to once again export M2Ts compatible with HD Link's export function.

A current solution to get your project out to tape is for you is:
1. Export your finished CineForm project/timeline into a CineForm AVI.
2. Create a new Adobe HDV (not CineForm!) project that matches you desired output (1080 60i, 720 30p, etc.).
3. Import your single CineForm clip into that project
4. Drop your CineForm AVI onto the timeline.
5. File->Export->Export to Tape
6. Click "Render and record"

You do not need to uninstall CineForm for this. You can have it installed and this will work just fine.

This will transcode your clip into HDV and export it to tape. While I don't beleive you get the keep the M2T, you will have successfully archived your project to tape.

Carl Middleton October 17th, 2007 06:59 PM

thanks again!
 
For some odd reason, I did have to uninstall it before to get premiere to render and record properly. I never quite figured out why, but I never saw it again after a much-needed hard drive wipe.

Rebooted, uninstalled & reinstalled aspect, tried to make the cineform M2T again, still didn't work. Decided to do it in pieces, changed my work area, tried again for the M2T, but forgot to set it to work area only. Lo and Behold, it worked.

Just goes to show! Computers like to be spontaneous, sadistic, and generally enjoy the misery of fleshbags. :D The only difference was this time, I was in the room glaring at my screen.

Glad to know now that the AME settings were probably right, at least. Air copy is on tape now, Premiere & HDLink worked flawlessly this time, with no changes since the last few attempts. I wouldn't mind trying repeatedly if it was smaller renders, 27 min with heavy compositing hurts. :D

Once again : Turned out not to be a Cineform problem. You guys are on a roll. And though I've ran into quite a few problems I've asked about on this board since installing Cineform, it's really not indicative of my overall satisfaction. I've had less problems than just working with premiere by itself, honestly. Now I just have found a great online group to help and be helped by. :D And I'm overjoyed to now be a part of the DVInfo.net community. Between this board and Cineform's responsiveness, even when I've had trouble, I've had a long list of workarounds, fixes, and alternate methods I've tried, enough to keep the network off of my back, along the lines of "he tried it how many different ways? He's talking to the CTO of the software company?!"

It all started when I purchased Cineform and mentioned I was going to try a workaround for the nvidia 8800 series cards on the comments section of the order, sometime around midnight EST.

I got an e-mail from David about 5 minutes later. My roommate saw me run out of the room saying "Oh my god, I've never seen customer service like this before!!!" =D

Carl

Marty Baggen October 17th, 2007 07:53 PM

The Cineform folks that respond here are unsurpassed. It has practically redefined user-support and is truly one of the greatest values, second only to the function of their product.

Add to that, the immense resource pool of experience and intelligence of the many participants on this board, and you have a wealth of responsive and helpful knowledge that money literally cannot buy.

Graham Hickling October 17th, 2007 08:10 PM

AME m2t files are not exportable back to tape, in my experience.

However Procoder 2 and TMPGEnc XPress 4 can both produce m2t's that I and others have been able to successfully export back to tape using the HDLink utility.


All times are GMT -6. The time now is 11:01 PM.

DV Info Net -- Real Names, Real People, Real Info!
1998-2025 The Digital Video Information Network