Rohit Gupta
Forum Replies Created
-
Do you see the playback issue with Prores or DNxHD?
-
What format are you rendering to, and what’s your Mac OS version?
-
Just to clarify, most characters other than “/” and “:”, should work ok.
These characters are special characters used as directory separators, and hence now allowed/handled in Resolve.
-
Hi Chris,
You should have to re-process the R3D file at all. Just click the “Mute” icon next to the color page controls. This will avoid the overhead of reading audio embedded with the R3D.
If you don’t care about audio at all, you can just disable audio from the project settings, and this will disable audio everywhere.
We are looking at this right now, and will see how we can improve it for Epic clips with Audio.
Regards,
Rohit -
Do you have any audio on these files? If yes, Can you mute resolve and see if it makes any difference.
What’s the exact resolution of these Epic files?
What bit depth are you decoding at?
-
It should be build 57. The public beta 1 was build 50.
-
Try rendering to full-range data levels? H.264 by default (auto mode) will render to video-range.
-
You need to set the conform rate to 25 before adding any clips to media pool.
If you already have a project set at 24, make a new project and use color trace to copy over your grades.
-
Did you update the firmware on the card, and did you reboot after that?
-
I think you are just running into the limits of your Mac Pro 3,1, memory bandwidth and CPU speeds. Given the fact you see the same speeds whether you use only the GT120 or both the GT120 and Q4000 kind of confirms the same.
You should be able to confirm this by running the Activity Monitor and see how busy your CPUs are during the render.