Workflow issue with BMD Cloud and CineDNG files
Posted: Tue Jul 30, 2024 8:00 amThis isn't uniquely a 19beta problem, however it hasn't been addressed in 19beta and I'm hoping to get the attention of the engineers.
tl;dr -- there's no remote proxy workflow for cineDNG files; the originals will sync with BMD Cloud regardless.
Normally in a BMD Cloud / proxy workflow, you can choose to have proxies-only or proxies-and-originals synced to BMD cloud. And even if you choose to have proxies and originals, a remote editor can choose to only download the proxies. Proxies are generated automatically, and it's about as seamless as it can be. Stellar.
However if you are using CineDNG RAW files (i.e. converted from ProRes RAW), this system breaks.
The CineDNG files are image files, not video files. Resolve itself recognizes them as an image sequence and automatically presents them as a movie file. However the proxy engine does not. This means that (a) the original and very large DNG files are synced to the cloud even if you have proxy-only-sync selected, and therefore (b) a remote editor will have to download them even if they too choose proxy-only. It also means that an actual proxy file will not be automatically generated, although that's easy to overcome by right-clicking and forcing a proxy to render. But, that doesn't remove the original DNG files from the cloud, so again, the remote editor has no choice but to download them. And considering that even a small project shot in RAW can be hundreds of GB, that's a problem.
tl;dr -- there's no remote proxy workflow for cineDNG files; the originals will sync with BMD Cloud regardless.
Normally in a BMD Cloud / proxy workflow, you can choose to have proxies-only or proxies-and-originals synced to BMD cloud. And even if you choose to have proxies and originals, a remote editor can choose to only download the proxies. Proxies are generated automatically, and it's about as seamless as it can be. Stellar.
However if you are using CineDNG RAW files (i.e. converted from ProRes RAW), this system breaks.
The CineDNG files are image files, not video files. Resolve itself recognizes them as an image sequence and automatically presents them as a movie file. However the proxy engine does not. This means that (a) the original and very large DNG files are synced to the cloud even if you have proxy-only-sync selected, and therefore (b) a remote editor will have to download them even if they too choose proxy-only. It also means that an actual proxy file will not be automatically generated, although that's easy to overcome by right-clicking and forcing a proxy to render. But, that doesn't remove the original DNG files from the cloud, so again, the remote editor has no choice but to download them. And considering that even a small project shot in RAW can be hundreds of GB, that's a problem.
