- Posts: 28
- Joined: Wed Apr 20, 2022 6:01 pm
- Real Name: Chris Hunt
When collaborating in Resolve 18 we are having major issues with proxies. We often shoot mixed frame rates and conform footage to a single frame rate (primarily for slow motion).
When collaborating using the cloud, we have tried to all share the same proxies, which obviously would be the best workflow (and how we always worked in Premiere team projects). But in Blackmagic, every user that tries to connect to those central proxies has original media and the proxies out of sync. It seems an issue with how Resolve is reading the timecodes of the media.
We have resorted to each user needing to create their own local proxies. But the problem continues, once one editor is finished working on the timeline and hands off to any other editor, now the locally generated proxies do not sync again. So we must generate NEW local proxies any time an editor opens a project. It's ridiculous!
This actually doesn't seem to a specifically a problem with Resolve 18 as we experienced some out of sync proxies even with 16 and 17. But now that Resolve has launched the Cloud specifically for collaborating, the bug is very obvious. It just seems to be a problem with how resolve interprets the timecode for any footage that has used clip attributes to conform to a different frame rate.
I can't be the only one that conforms high frame rate footage, uses proxies, and collaborates with other editors.. but I am surprised I can't find any information on this problem. Am I missing something? Is there some hidden option somewhere that tells Resolve to ignore timecode of the clips and sync at frame zero instead?
On a side note, we can not use Proxy Generator since BM did not include the option to change clip attributes in the app. Seems like a huge oversight.
When collaborating using the cloud, we have tried to all share the same proxies, which obviously would be the best workflow (and how we always worked in Premiere team projects). But in Blackmagic, every user that tries to connect to those central proxies has original media and the proxies out of sync. It seems an issue with how Resolve is reading the timecodes of the media.
We have resorted to each user needing to create their own local proxies. But the problem continues, once one editor is finished working on the timeline and hands off to any other editor, now the locally generated proxies do not sync again. So we must generate NEW local proxies any time an editor opens a project. It's ridiculous!
This actually doesn't seem to a specifically a problem with Resolve 18 as we experienced some out of sync proxies even with 16 and 17. But now that Resolve has launched the Cloud specifically for collaborating, the bug is very obvious. It just seems to be a problem with how resolve interprets the timecode for any footage that has used clip attributes to conform to a different frame rate.
I can't be the only one that conforms high frame rate footage, uses proxies, and collaborates with other editors.. but I am surprised I can't find any information on this problem. Am I missing something? Is there some hidden option somewhere that tells Resolve to ignore timecode of the clips and sync at frame zero instead?
On a side note, we can not use Proxy Generator since BM did not include the option to change clip attributes in the app. Seems like a huge oversight.