-
Editing issues with Apple ProRes422 files
Hi Creative Cows(if you don’t mind me saying so),
I am attempting to cut some promotional material recorded by the broadcast suite in our performing arts facility.
We use four remote control Panasonic Cameras, which are each recorded on a pipeline as well the the program output, which the what is recorded through our vision mixer.Each file is recorded as an Apple ProRes 422 (HQ) file in 1920x1080x24,
Pixel Aspect = 1.00
Audio is 48k, 32bit with 40 channels(yes, forty!)
The plugin used by Vegas is the qt7plug.dllI have fortunately not experienced the glitching issues that other files have when using the qt7plug.dll.
The file sizes are huge, the only one I can get to work is a 35 minute track that is 57Gb in size.
There are 7 other files that I need to use that are between 100-200Gb in size. They simply do not open. Vegas greys out the options to add the file to Trimmer, Project Media etc.The 57gb file works, but it took Vegas about 4 hours to import. And as I said earlier, the larger ones won’t open at all.
Is there a way to cut out certain chunks of the footage in a separate program and just use those without having to import an enormous file into Vegas? My video only needs to be 2 minutes, but it needs a variety of sources.
I do potentially have access to a Mac with FCP7 and a computer with Media Composer on it(not that I know how to use it), so that might be helpful. I may just need to hack though it on FCP7, but I’d really rather not.
What can I do? this video was due yesterday…..
Help greatly appreciated.
Asus G73jh Notebook
Win7 64Bit
AMD ATI Radeon HD5870
12Gb RAM
Vegas Pro 13 -
3 Replies
-
I’m guessing that you are running up against the 32-bit addressability limits of QuickTime on Windows which Vegas Pro uses to manipulate Quicktime files. This is a known limitation. My advice is to use FCP 7 on the Mac that you have available to you. QuickTime files are native to Mac so they preform best on that platform.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Thankyou John.
I am well aware of the issues with .MOV files that are played in Vegas using the qt7plugin.dll, however for some reason, these particular files seem completely immune to this.
Nonetheless, I discovered that my work had another editing machine that had a direct connection to the hard drive that contained these files, and when I used this machine(which runs Vegas Pro 10) it worked quite well.(with some bizarre issues with some of the audio files attached to some video files)
It actually really surprised just how well it dealt with these enormous files; I could playback a 162Gb file in full resolution on the timeline, and only needed to lower the preview quality when I added some crossfades and blended 3 tracks with opacity.
I am pretty sure the issues I faced were to do with the bandwidth available to the computer in relation to the files size.
I am annoyed that Vegas doesn’t have an error screen explaining this. Simply greying out the options of putting the file in Project Media or Trimmer doesn’t help the end user solve the problems they are facing.Thanks for your help.
Asus G73jh Notebook
Win7 64Bit
AMD ATI Radeon HD5870
12Gb RAM
Vegas Pro 13 -
It’s really strange that Vegas Pro would grey out files due to bandwidth constraints but I’m glad you figure it out. I never thought to ask if they were local or remote. Good to know.
~jr
http://www.johnrofrano.com
http://www.vasst.com
Reply to this Discussion! Login or Sign Up