Glenn Camhi
Forum Replies Created
-
Interesting. We only had the problem on a single PC. They never figured it out, but we’ve since tested it on another PC running Windows 7, and all the files played just fine. So there must be some odd conflict on some computers. We’re going to a different finishing house, we’ll see what happens there.
-
They’re finishing on the DS. Hm, not positive what you mean by “Make sure your finisher under stands the file size issue”… do you mean the issue I’ve been describing? If so, yeah, that’s where the issue is happening, at their facility. They’re at least as baffled as I am.
Thank you Gary for checking your file. It’s got to be something odd going on with their system. I’ll post here if it gets solved.
-
Jeremy: Right, I gave them an HFS+ drive. I don’t know if they have MacDrive, I’ll ask.
Michael: Yeah, that’s what I’m thinking. We may have to go to a different finishing house. This place hasn’t dealt with Alexa/PR4444 footage yet. They’ve never had a problem with anything else, though. They are considerably more affordable than the big post houses around, which makes this a particular bummer.
-
…And again, it wasn’t just the one file. It was every single QT Pro Res 4444 file we tried that was >1.4GB. And it didn’t matter whether the files had been exported from FCP or were ARRI Alexa camera originals that had never even seen a computer. Same results for both. All the files have played fine on Macs.
-
Not silly at all, Jeremy! We thought the same thing, and tested it on their Mac. Worked just fine.
At this point, no thought or suggestion shy of voodoo is silly.
-
Yep, QuickTime is up to date on the PC, they double-checked. No Pro Res 4444 movie file over ~1.4GB would open in QuickTime on their system — we tried over a dozen different file sizes from under 1 GB up to 58GB.
Thanks, I’ll post on an AVID forum as well. So far I’ve found nothing there or on Apple’s forums that proved useful.
-
Hi Michael. Thanks. The drive we brought to the finishing place is HFS+. The computer they transferred it to is running Windows 7 so I assume their drive is NTFS. It didn’t get split up.
Yeah, when I saw that a 1.2 GB test movie worked but that our 58 GB movie failed, first thing I assumed was that we were dealing with FAT32 and expected a 4 gig cutoff. Alas, nope.
Why there’d be a ~1.4GB cutoff is beyond me. They’ve had no problems with any QuickTime files in various other codecs. But again, we want to try to solve this without transcoding to another codec.
The software on the PC is the latest updated version of QuickTime for Windows, and Avid DS. (Though I don’t even know if they got as far as Avid, it may just have been QuickTime.)
-
Grazie Mark! That exhausts my questions.
Sounds like they might want the Lt/Rt tracks separately as well, and just want to use the QT audio for verifying sync. Not sure, but I’ll bring them too just in case.
-
Ah, see, perhaps you should write the documentation for all this that I can’t find anywhere. You’re a great help.
So that makes sense, I just give the house the QT file. And the six 5.1 AIFFs, which they can connect to the video from that QT file as well. Right?
In the General tab of Sequence Settings, does it matter if Discrete Channels, Channel Grouped or Stereo Downmix is selected (for the Lt/Rt)?
Yeah, the hard panning was my problem before. I thought they were panned as a stereo pair, but they weren’t. Doh!
-
One more question yet, re the Lt/Rt mix:
In Final Cut, should I set Audio Outputs in Sequence Settings to Stereo or Dual Mono? And should I export AIFFs? Assuming so, should I choose Channel Grouped or Stereo Mix under Congif?