Tim Kolb
Forum Replies Created
-
Sorry…I should have read less hastily…clearly they came from AE.
You said you have a ‘few’…are there others that are coming through fine on export, or are all the PR444 titles in that project messed up?
Have you used this exact workflow in the past without issue?
Not that these are sure fixes, but have you tried importing that project into a new/clean project just to see if it affects the problem? (Just troubleshooting here…nothing jumps out at me…
-
What did the PR444 files come from? AE?
-
Just curious…are any of you on Quadro cards, or are all these GTX cards?
(Not that it should make any difference…just a point of curiosity.)
TimK,
Director, Consultant
Video Producer at I-CAR -
QuickTime remaining 32 bit running under a 64 bit NLE (which Premiere Pro is after v5…FCP7 was still 32 bit), isn’t an ideal scenario. Adobe has a little application frame serving from QuickTime in the background, but adding that process with 4K probably isn’t going to help anything.
Having an I-frame file does help to take some stress off the processor (decoding load decreases) when you go to a mezzanine format like ProRes or even AVC-Intra, but the file size balloons considerably and the disk read speed and data throughput requirements increase…you’re effectively transferring stress from one part of the system to another.
Overall, I’d say do a small scale test and compare the formats’ behavior in the edit system before making a choice on how to proceed. The optimal solution is different for everyone.
TimK,
Director, Consultant
Video Producer at I-CAR -
I think Alex is thinking the same way I am…those two 6 TB drives may be the bottleneck.
RAW will certainly tax a processor, but depending on what the format of the .mov files are, they may be quite large…
TimK,
Director, Consultant
Video Producer at I-CAR -
If you use the motion controls (scale), you can be a bit more flexible…zoom in/out, etc with key frames in an HD sequence. You’ve got some real estate to play with there.
TimK,
Director, Consultant
Video Producer at I-CAR -
Not actually certain what you mean by ‘bin clips’…
I’ve seen proxy workflows that simply name the proxy folder ‘media’ or whatever…do the edit…then change the folder name to ‘proxy’ and relink to the online folder named ‘media’. (or whatever names you want obviously, but the main thing is to begin the process knowing you’ll need to do the folder rename)
Then of course…it works best if no media was trimmed when the proxies were created at the same framerate, etc…
TimK,
Director, Consultant
Video Producer at I-CAR -
Using mixed media in and of itself should not cause crashing…it may cause performance to be less responsive…
Are there particular clips or groups of clips that you tend to be scrubbing/playing when the thing takes a powder?
Do you get an error report? Look through it and check if it indicates what thread crashed.
TimK,
Director, Consultant
Video Producer at I-CAR -
I would edit at 1280x720p 23.976fps…
The 1920×1080 can be scaled down.
I would take the 25 fps material and use ‘interpret footage’ to get it to play at 24 fps. The audio will pitch down by 4%…but depending on the material, it may not be a problem if there is no footage of the same people talking, etc on another clip that isn’t speed-converted.
The 29.97 material will run reasonably well on a 23.976 timeline with no adjustment…but check ‘frame blend’ by right-clicking the clip on the timeline to reduce the ‘gallop’ effect in the frame cadence if the action is causing to many motion artifacts.
While converting everything to a mezzanine format (like ProRes) seems like a good idea…and make no mistake, it would probably run easier that H264 material…it makes gargantuan files and if you aren’t using that step to do some kind of conversion beyond just creating massive files, you won’t gain much beyond a lot of data footprint on your drives.
PPro is designed to deal with mixed format material…you might as well use it if your machine has the power to handle the processing…
TimK,
Director, Consultant
Video Producer at I-CAR -
Are you running McAfee with real-time scanning? If so, turn real-time scanning off and try the install again…
TimK,
Director, Consultant
Video Producer at I-CAR