Alan Gordon
Forum Replies Created
-
It very well could be the GPU being the bottleneck. In the first scenario there is no scaling going on. It is 1080p straight through. In the second, the GPU must scale the 5k footage to 1080 before playback. And it must do this twice. I would think that 2x 285 should be able to handle a 5k scale each but it is an older card with data lanes being shared with each other AND the rockets.
-
The problem was I was using Red footage in the timeline so going to fcp was impossible. Also I had scaling and positioning information that I didn’t want to have to redo and aaf from premier does not have ptzr information that davinci understands. I just set all the r3ds to redlogfilm and exported as prores 4444 it became basically like grading alexa footage.
-
Nope never figured it out. Not even cs 6 fixes the issue.
Ended up having to export a flattened MOV and use scene cut detection. Worked but not ideal. And it’s real weird because another project xml worked beautifully…
-
I would personally recommend shooting ProRes4444 for this situation. While you probably don’t need ArriRaw, the Alexa can go to 4444 on board so why shoot less quality? The space requirement isn’t that great and it will playback realtime off any drive. If you need Alexa’s slomo, just go down to HQ for those shots. FCP and Premiere Pro can both edit any of the ProRes formats just fine and in realtime.
Cheers,
-AG