Andy Mees
Forum Replies Created
-
No worries Gary, perhaps I was waiting a little too keenly for the soapboxes to come out!
Firstly then, apologies. You note that the OP was specifically looking for guidance on a laptop based solution and you are of course correct. I had thought that my original response ( in which I had wholeheartedly endorsed the IoHD ) had already made the point that the IoHD was hardware ProRes capable but perhaps that had got lost in the telling! I jumped in, as until your post the MXO2 had already been very specifically precluded by the OP and was not being discussed. Ah well, thats my bad as they say, I should have let it go. Again apologies if my comment was unfair.
Fwiw, I stand by my original recommendation to the Chris, which was for the IoHD (unless he’s looking for advanced audio handling capabilities at which point the V4HD does indeed look more enticing).
You ask if 10 bit uncompressed capture is working fine with the MXO2 … yes, to the best of my knowledge there are no current issues with that workflow. As an industry commentator you might also be interested to note that a soon to be released MXO2 driver update is slated to bring a “possibility” for 24p (and 25p?) ProRes HD capture on a current MBP laptop. That’s all very “may” and “might” of course but something to keep an eye on perhaps.
Thanks also for the note regarding your success with Uncompressed HD playback through the IoHD. I do have some questions on the point though as I had understood that the IoHD (and V4HD) FW800 connection was not simply not technically / practically capable of handling the data rate of Uncompressed 10 bit HD sources (with the exception of 720p24 perhaps?). With a maximum theoretical bandwidth of 100 MB/s it would seem that even 8 bit Uncompressed HD streams would be pushing that limit? What I had previously been given to understand was that when working with any HD format the IoHD required the signals be passed through a ProRes compression cycle (in order to pass across the FW bus). Is this no longer the case, or perhaps it never was the case, or maybe its format specific? I would appreciate if you could clarify on that point as it does have me puzzling.
Thanks again for the shared wisdom
Andy -
C’mon Gary, do we really need to go there every single time? FWIW then, the MXO2 is the only unit that can capture and work with Uncompressed HD.
-
at 1080 the resolution is 1280×1080
only for NTSC Shane, in PAL DVCPRO HD is 1440×1080 … still not full raster tho and I think thats you point, no?
-
…but there is currently no QuickTime XDCAM codec for Windows.
Ah, but there is. Your client needs to buy (or you need to provide them with) the Calibrated Q XDDecode quicktime component for Windows. That, together with Apple’s ProRes Decode component for Windows should let the Avid work with any of these pre-imported quicktime movie files
https://www.calibratedsoftware.com/QXD.asp
-
The IoHD would be my personal choice …. quite apart from the pedigree of AJA’s video hardware and support and the long list of features the box offers, its superior in hardware ProRes codec support would be the main selling point for me. The V4HD seems to be a nice I/O box with great audio capabilities (not surprising coming from MOTU) and its the only box to my knowledge that is platform agnostic, but its in hardware codec support is for DVCProHD, a nice compressed HD codec but not one thats on a par with ProRes. That said, if you do a lot of audio work, or have any potential need to use the box to interface with a PC, then MOTU box would likely be your better choice.
Note, as both units are firewire based, neither support an Uncompressed HD workflow. -
Assuming the deck supports it, you’ll need to switch the System settings to 50 Hz before you can properly playback/capture a PAL source from it …
-
LOL. I had imagined you would be installing the AVID trial on your Mac so the first condition wouldn’t have occurred … as for the apparent field order issue that you are seeing, its probably/possibly just a incorrect interpretation during the AVID import.
-
>The earliest version I knew of was 2.1 or so
Craig, Its been a while but I might still have a copy of the 0.5 version somewhere if you’re interested!
-
Phil
You have a simple source/sequence format mismatch. You just need to set your sequence timeline to the same format as the source footage.You note that you’re working with FCP5 so this format matching won’t happen automatically, you have to do it for yourself.
You also note that you’re shooting a standard def XDCAM format so that means either DVCAM or IMX 30, 40 or 50. You probably already know which format it is, if so, simply go to your Easy Setup menu and select that format from the list and click OK. Then create a New Sequence and test to see if you still need to render.
If you don’t know the format then a quick trick is to select one of your source clips in the Browser and choose Modify menu > Make Multiclip Sequence. A sequence will be created for you automagically that matches that source clip format.
Failing that, just post back with the source clip Item Properties (select a clip and press Cmd 9) and also with the sequence Item Properties (select a sequence and press Cmd 9, or select the Timeline window and press Cmd- Zero)
Best
Andy -
Niklas
Does this 300 MB file pay back correctly? Is your target hard drive full?
If you are convinced that you’ve got all the settings correct (and choosing Export > Quicktime Movie w. Current Settings and Make Movie Self Contained ticked is all there is to it, you should not have to use any other method) and if its definitely not working correctly then you’ve probably got some hosed preferences. Trash them and try again.
You can trash preferences manually, but using a simple tool to do the job makes it easy and offers some other advantages too (like backup and restore). One of the best FCP preference managers available is Jon Chappell’s excellent Preference Manager … and its free!
Quit FCP, trash the prefs, relaunch FCP and try the export again .. post back
Andy