View Full Version : CineForm and Sony XDCAM EX
Michael Stewart February 9th, 2008, 03:01 AM Can Prospect convert the MXF file to cineform intermediate? If not, how do I convert spanned mp4 clips as one cineform clip in HD link? When I convert an 8GB mxf file in hdlink, it comes out as only 600mb and is green screen. The clips are 1080 24p HQ.
Thanks
Mike
Nelson Maldonado February 9th, 2008, 10:40 AM thanks guys.
LH it is.
I take it that even though Adobe's site still totes the HS card, it appears that the card is on its way out even though aja updated the drivers to support Premiere CS3. Your thoughts?
David Newman February 9th, 2008, 10:49 AM We support MXFs, you systems seems to after an install issue. Try the CineForm->Tools->Register components. If that does fix it, please file a trouble ticket www.cineform.com/support
Michael Stewart February 9th, 2008, 11:03 AM thanks David, just tried the 8gb mxf file to completion, it shows a green check mark for completed but is only 3 gb in size and is green screen when played back. I'll try your fix.
Mike
Michael Stewart February 9th, 2008, 11:21 AM registered componets, but it still gives the exact result. It converts small files, mp4 or mxf, but large ones have problems. Also David, I am testing out Prospect with my EX-1 to see if it meets my needs, so I cannot submit a ticket.
Mike
David Taylor February 9th, 2008, 11:36 AM Adobe specifically wrote drivers (their own) to support the HS card for PPro 2 (if I recall correctly) release. Adobe never wrote drivers to support the LH and LHe. For LH and LHe support driver support comes from AJA or CineForm. Because of this, Adobe doesn't specifically endorse the LH or LHe card.
David Taylor February 9th, 2008, 11:37 AM Michael, you can always submit a ticket, even when using Trial versions....
Michael Stewart February 9th, 2008, 11:48 AM It asks for a serial number
Mike
David Newman February 9th, 2008, 11:52 AM Ignore that, the ticket goes through anyway.
Michael Stewart February 9th, 2008, 12:03 PM Thanks
Mike
Nelson Maldonado February 9th, 2008, 12:05 PM Ok...
So aja updated the HS drivers to support Premiere CS3. The LH card is the recommended card but not offically supported by Adobe.
Both the HS and LH cards offer 10bit digital HD SDI. I have looked at the Xena overview page and can see that the LH card has some extra features like genlock, a few more i/o channels, 12 bit HS SD analog component/composite i/o and 8-channel SDI embedded audio I/O.
What other advantages does the LH have over the HS?
Does the HS have embedded SDI i/o?
Michael Stewart February 9th, 2008, 12:51 PM another test, tried a 2.3 gb mp4 file and get this error in the log
Error: GetPin(pUpStream,PINDIR_OUTPUT, &outputPin)(0x80004005-Unspecified error) in (DirectShowGraph.cpp at 377)
Error: ConnectPin(AudioDecoder, pin)(0x80004005-Unspecified error) in (ConvertGraph.cpp at 2275)
just converted a 1 GB mp4 file, it converted it fine.
Mike
Michael Stewart February 9th, 2008, 02:39 PM I took the 3 clips that spanned together, dropped all three mp4's on the timeline (PPRO3) and rendered out to cineform avi, of course no audio, but at least I can edit the files in a timeline now. Final Cineform file was 22 gb's.
Mike
Michael Stewart February 10th, 2008, 12:55 PM Tried Prospect 4k still the same error
Error: GetPin(pUpStream,PINDIR_OUTPUT, &outputPin)(0x80004005-Unspecified error) in (DirectShowGraph.cpp at 377)
Error: ConnectPin(AudioDecoder, pin)(0x80004005-Unspecified error) in (ConvertGraph.cpp at 2275)
the file was 2.3 gb mp4 Sony EX1 file, it appears anything under 2 gb's works fine.
tried Prospect HD, 2k, 4k, all with the same error (although Prospect hd was (ConvertGraph.cpp at 2258) instead of (ConvertGraph.cpp at 2275)
Aspect Hd, same error, I have tried several different mp4 files over 2gb's, all do the same thing.
Mike
Michael Stewart February 10th, 2008, 03:41 PM Hi David, do these errors sound like an install problem? Or a bug? I would hate to do a fresh install of windows to find out it was a bug.
Mike
David Newman February 10th, 2008, 04:59 PM Please go through support, only they can get the information to determine what the issue is. There never a reason for CineForm functionality to reinstall your OS, everything else much be failing before taking that step. If there is an issue with > 2GB MXF files, maybe you could send us one. Unfortunately Sony only sent us data files, not the camera, so we can't test very large MPEG media from the EX1. We maybe get fewer reports as from the indie film guys (most of our customers) as 2GB is a long take. So while I have heardn't of this one, it could be a real bug. With sample data we should be able to fix it.
Michael Stewart February 10th, 2008, 05:43 PM Thanks David, I did report to Cineform support earlier, I post in hopes of others trying it out to help verify problems, if I send a ticket to cineform, it bipasses others here who can check also. I would be glad to send one, how can I get it to you?
Mike
Marty Hudzik March 2nd, 2008, 07:20 AM what exactly is needed to use cineform with the ex1? I own aspect hd and I am wondering what limitations I would have with it? Is prospect absolutely necessary? What is thecworkflow currently like? If I move to a tapeless workflow it sure would be nice to not have to do a ton converting that would negate some of the timesaving features that tapeless normally provides.
Thanks
Chris Hurd March 2nd, 2008, 10:25 AM Frequently asked (please search first before posting new topics). Have now merged about a dozen CineForm / Sony EX1 threads into one single large discussion. Hope this helps,
Michael H. Stevens March 2nd, 2008, 12:27 PM Hi Guys:
Just to say file size does not seem to be the issue as my problems are with clips no longer than 12 seconds. The big problem with this issue is it is very random in how the thing goes wrong. Sometimes Vegas will stop working just by adding some files to the timeline, but sometimes it does not stop working until you play the files. I note the cinform converted files DO PLAY well in a media player. Only in Vegas is there a problem so some inconpatability there.
Marty Hudzik March 2nd, 2008, 12:33 PM Frequently asked (please search first before posting new topics).
Sorry Chris! I usually do a good job on finding this stuff. I was away from my PC and browsing on my iphone......didn't think to search deeper. I had just been reading all the threads and hadn't gone that far back. This thread has helped immensely.
Thanks.
David Newman March 2nd, 2008, 12:48 PM Hi Guys:
Just to say file size does not seem to be the issue as my problems are with clips no longer than 12 seconds. The big problem with this issue is it is very random in how the thing goes wrong. Sometimes Vegas will stop working just by adding some files to the timeline, but sometimes it does not stop working until you play the files. I note the cinform converted files DO PLAY well in a media player. Only in Vegas is there a problem so some inconpatability there.
This not a EX issue, it is a Vegas. Vegas 8 (likely) some install old CineForm components are using them in favor of the new ones installed with NEO or Aspect/Prospect. There are many post on the easy fix. Basically delete or rename the Program Files/Sony/Vegas 8.0/CFHD.dll file -- it is old and unnecesary if you have a new CineForm license.
Michael H. Stevens March 4th, 2008, 02:57 PM David: Support thinks 157 resolves this issue. I will inform them it does not. This may be a clue. I put my mxf files on the Veags timeline and used the Cineform 3.2 codex to render them to a new track as this was a work-around Serena has used, but for me that stopped Vegas working also. Any other work-arouns to try? I'm really dead in the water here.
David Newman March 4th, 2008, 03:22 PM David: Support thinks 157 resolves this issue. I will inform them it does not. This may be a clue. I put my mxf files on the Veags timeline and used the Cineform 3.2 codex to render them to a new track as this was a work-around Serena has used, but for me that stopped Vegas working also. Any other work-arouns to try? I'm really dead in the water here.
3.2 is not the current codec. You don't seem to have got 157 installed correctly, which would explain you not seeing what support is reporting. Build 157 has VfW codec video V3.6.1.
Michael H. Stevens March 5th, 2008, 05:44 PM 3.2 is not the current codec. You don't seem to have got 157 installed correctly, which would explain you not seeing what support is reporting. Build 157 has VfW codec video V3.6.1.
David: v3.6.1 IS what I have. I quoted wrong, but this is what I have and still no conversioons work. I'll wait for 158 before I post to support again.
Mike
David Newman March 5th, 2008, 06:18 PM It doesn't seem related to the build, Build 158 don't impact anything related to your experience, as it is all working here. Sounds more like an system or Vegas issue. As you have mentioned clips over 12-second fail for you, however our decoder has do concept of time, you (the NLE) gives a compressed frame, we get back an uncompressed one. So any file length issue is more likely an issue with the calling application, particularly if the same files work elsewhere, MediaPlayer, VirtualDub, AE, etc.
P.S. Try put your media a different drive under a different controller, even try the system drive. Just in case. More than once weird stuff like this has been due to a flaky RAID controller.
Michael H. Stevens March 5th, 2008, 07:15 PM It doesn't seem related to the build, Build 158 don't impact anything related to your experience, as it is all working here. Sounds more like an system or Vegas issue. As you have mentioned clips over 12-second fail for you, however our decoder has do concept of time, you (the NLE) gives a compressed frame, we get back an uncompressed one. So any file length issue is more likely an issue with the calling application, particularly if the same files work elsewhere, MediaPlayer, VirtualDub, AE, etc.
P.S. Try put your media a different drive under a different controller, even try the system drive. Just in case. More than once weird stuff like this has been due to a flaky RAID controller.
On my edit machine now I only have one drive. Maybe I should partition it? ALSO I did NOT say long clips were prone to the error. I said it was random. Putting the clips on the time-line one at a time causes Vegas to stop at different places each time. My symptoms are the same as Bill's and Serena's but for them the work-around seems to work.
Anmol Mishra March 28th, 2008, 09:40 AM Maybe this is a bit offtopic. Does Cineform allow capture via the EX1 HD-SDI port and Blackmagic Decklink card ?
I want to see if we can use Neo 4K to record the 4:4:4 signal from the HD-SDI port..
David Newman March 28th, 2008, 09:54 AM Maybe this is a bit offtopic. Does Cineform allow capture via the EX1 HD-SDI port and Blackmagic Decklink card ?
I want to see if we can use Neo 4K to record the 4:4:4 signal from the HD-SDI port..
Yes, HDLink support HDSDI capture through Decklink cards. HDSDI is only 4:2:2, dual link can be 4:4:4.
Anmol Mishra March 28th, 2008, 06:12 PM Cool. So its a choice of Prospect2K or NeoHD. Is that right ?
Yes, HDLink support HDSDI capture through Decklink cards. HDSDI is only 4:2:2, dual link can be 4:4:4.
David Newman March 28th, 2008, 06:20 PM Cool. So its a choice of Prospect2K or NeoHD. Is that right ?
Prospect HD is also a fine choice, it will support full raster 1920x1080 4:2:2 10-bit captures from HDSDI .
Michael H. Stevens March 29th, 2008, 07:09 PM Yes, HDLink support HDSDI capture through Decklink cards. HDSDI is only 4:2:2, dual link can be 4:4:4.
What practical benifit will be see with the 4:2:2 over the 4:2:0? i KNOW THERE IS MORE EFFECTICE RESOLUTION BUT IS IT VISUALLY SIGNIFICAT?
David Newman March 29th, 2008, 07:16 PM What practical benifit will be see with the 4:2:2 over the 4:2:0? i KNOW THERE IS MORE EFFECTICE RESOLUTION BUT IS IT VISUALLY SIGNIFICAT?
This is significant. Keying particularly but even just red objects look much better in 422.
Raul Rooma November 16th, 2008, 03:23 PM Hi All!
what is the best way to convert EX1's files to cineform?IF i input BPAV folder then Hd link makes all copies in the same folder where original file is..if i have lots of clips then it takes lots of time move avi's somewhere else.I tryed also export from clipbrowser mxf files..and converting then avis.its like better ,because all of them in one folder after conversion.But requies one additional conversion..or do i miss something??
Best Regards
Raul
Alex Raskin November 16th, 2008, 03:47 PM Raul, I actually had the same workflow question!
But I think it'd be better to open a new thread for it, here:
http://www.dvinfo.net/conf/cineform-software-showcase/137865-ex1-cineform-workflow-avoid-moving-mp4-files.html#post964528
Robert Bobson November 28th, 2008, 11:21 AM can HDlink convert the long GOP MPEG-2 format files directly from a camera memory card into MP4 files on a computer harddrive?
Or do you always transfer and convert into .MFX files on the hard drive, and then do a batch convert to MP4? I thought I read somewhere that this double conversion loses resolution?
David Newman November 28th, 2008, 11:35 AM We never convert to "MP4" we can convert directly from. The CineForm outputs are AVIs or MOVs for post.
Robert Bobson November 28th, 2008, 01:19 PM Then I guess my question should have been - Is it better (or even possible) to transfer and convert the long GOP MPEG-2 format files directly from the EX1 camera memory card onto the computer hard drive as AVI files all in one step, without converting to .mxp files first?
Or am I missing something here??
David Newman November 28th, 2008, 01:39 PM Quality will be the same, yet the direct MP4 conversion bypasses a step, so I would think that is preferred.
Robert Bobson November 29th, 2008, 06:27 AM good to hear that the quality is the same. easier for the field producer to transfer to his Hard Drive as .mxf, then I can convert to avi in-house.
another question - can "Prospect HD created avi files" be edited from a single firewire connected hard drive? is the speed enough??
thanks for the reply -
Giroud Francois January 23rd, 2009, 09:58 AM I have done a clip browser conversion to MXF of several files, then HDlink conversion to Cineform AVi (HD quality) , all files are 1080i50 from EX1.
Then just dropped them on the CS3 timeline and exported (File/Export movie).
Stangely the export is very slow, like if the video is recompiled.
quality of export is the same setting (hd quality) as capture (in that case likely a conversion)
another question is that capture prefs of HDlink do not show the HD Quality optimized setting that is available in premiere export setting. Why ?
|
|