Work-Offline / Local-Cache Mode for Blackmagic Cloud Project
Posted: Tue May 06, 2025 7:44 pmPlease add a “Work-Offline” toggle that lets an editor open and modify a Blackmagic Cloud project without an active internet connection, then transparently sync changes back when the connection returns.
Main issue: Can't open cloud project without internet. Need a way to download it locally for times in spotty internet and able to re-upload it.
**Does any one else have this issue? Would love to hear how you are currently working around it?**
⸻
Why it matters (real-world pain points)
• Travel & spotty connections – Our three-person YouTube channel edits on planes, in cars and at a rural cottage with flaky LTE. If the connection drops, the Cloud project will not open or save, halting work.
• Workflow with blackmagic cloud - If you export the project to local database then re-upload, all the proxies uploaded to black magic cloud will not be linked to the new project and will have to be re-uploaded?
• Local fall-back saves – If Resolve could keep writing changes to a local cache while the link is down, the app wouldn’t freeze; we’d just continue cutting and the sync would catch up when online again.
• Lost productive time – We currently duplicate the project to a local library before every trip, then export / import timelines later. It’s manual, error-prone and often produces version sprawl.
• Other systems – Google Docs, Notion and many NLE collaboration systems (Avid bin locking, Adobe Productions) already cache locally and merge on reconnection.
⸻
Desired potential behaviour
1. “Make Available Offline” / “Work Offline” button in the Project Manager or Workspace menu, or when right clicking a specific project.
2. Resolve syncs the latest revision of the project to a local cache, then flips the Cloud copy to read-only / locked for other users.
3. While offline, the editor can open, tweak and save as usual; Resolve stores deltas locally.
4. When internet returns or when the user unchecks the 'offline' box, Resolve reconnects, unlocks the Cloud copy and pushes the changes (with conflict-resolution if another user touched the same item).
5. If the editor never reconnects, they can still export a normal .drp backup.
This keeps the current collaboration model intact while giving single editors the reliability they need on the road.
⸻
Repro steps for the issue today
1. Create a project in a Blackmagic Cloud library.
2. Open the project, disable Wi-Fi / pull the Ethernet cable.
3. Try to save or reopen the project → Resolve freezes, then shows “Project library connection lost.”
4. No editing possible until internet is restored.
⸻
Business value for BMD
• Makes Blackmagic Cloud viable for freelancers and indie teams who often work away from stable broadband.
• Reduces support tickets from users who assume projects are locally cached.
• Encourages more Studio licence sales as teams fully commit to the Cloud workflow.
Thank you for considering this—happy to provide logs, demo videos or further testing if it helps flesh out an implementation path.
— Dylan Gitalis (three-person YouTube channel, Montreal)
Main issue: Can't open cloud project without internet. Need a way to download it locally for times in spotty internet and able to re-upload it.
**Does any one else have this issue? Would love to hear how you are currently working around it?**
⸻
Why it matters (real-world pain points)
• Travel & spotty connections – Our three-person YouTube channel edits on planes, in cars and at a rural cottage with flaky LTE. If the connection drops, the Cloud project will not open or save, halting work.
• Workflow with blackmagic cloud - If you export the project to local database then re-upload, all the proxies uploaded to black magic cloud will not be linked to the new project and will have to be re-uploaded?
• Local fall-back saves – If Resolve could keep writing changes to a local cache while the link is down, the app wouldn’t freeze; we’d just continue cutting and the sync would catch up when online again.
• Lost productive time – We currently duplicate the project to a local library before every trip, then export / import timelines later. It’s manual, error-prone and often produces version sprawl.
• Other systems – Google Docs, Notion and many NLE collaboration systems (Avid bin locking, Adobe Productions) already cache locally and merge on reconnection.
⸻
Desired potential behaviour
1. “Make Available Offline” / “Work Offline” button in the Project Manager or Workspace menu, or when right clicking a specific project.
2. Resolve syncs the latest revision of the project to a local cache, then flips the Cloud copy to read-only / locked for other users.
3. While offline, the editor can open, tweak and save as usual; Resolve stores deltas locally.
4. When internet returns or when the user unchecks the 'offline' box, Resolve reconnects, unlocks the Cloud copy and pushes the changes (with conflict-resolution if another user touched the same item).
5. If the editor never reconnects, they can still export a normal .drp backup.
This keeps the current collaboration model intact while giving single editors the reliability they need on the road.
⸻
Repro steps for the issue today
1. Create a project in a Blackmagic Cloud library.
2. Open the project, disable Wi-Fi / pull the Ethernet cable.
3. Try to save or reopen the project → Resolve freezes, then shows “Project library connection lost.”
4. No editing possible until internet is restored.
⸻
Business value for BMD
• Makes Blackmagic Cloud viable for freelancers and indie teams who often work away from stable broadband.
• Reduces support tickets from users who assume projects are locally cached.
• Encourages more Studio licence sales as teams fully commit to the Cloud workflow.
Thank you for considering this—happy to provide logs, demo videos or further testing if it helps flesh out an implementation path.
— Dylan Gitalis (three-person YouTube channel, Montreal)