[Request] OS-Compatible Files For Multi-disciplined Users

Hi There,

Multi-disciplined users need to group assets from multiple apps into a single source of project truth:
THE JOB FOLDER

For example, we do a lot of movie advertising for one of the larger studios, here's a typical job folder:

Code: Select all

|_7865 STUDIO Title
  |_7865 STUDIO Title Media Schedule.xlxs
  |_MOTION POSTERS
    |_9865 STUDIO Title Motion Posters 6.prproj
    |_ASSETS
    |_OPTIMISED
    |_RENDERS
    |_WORKING
      |_9865 STUDIO Title Motion Posters 1.prproj
      |_9865 STUDIO Title Motion Posters 2.prproj
      |_9865 STUDIO Title Motion Posters 3.prproj
      |_9865 STUDIO Title Motion Posters 4.prproj
      |_9865 STUDIO Title Motion Posters 5.prproj
  |_SOCIAL
  |_YOUTUBE
  |_ONLINE
  |_INVITES
  |_PRESS
  |_EMAIL
  |_WORKING


As you can see, we do a huge amount of video plus online and print which requires the use of at least 7 major video, compositing and graphics apps/disciplines each day.

REQUEST
In addition to the facility-focused database workflow, we need support for the tried and true graphics workflow:
- An option to save Resolve projects to the OS
- Relative asset links (relative to the project file) so moving projects minimises re-linking
- A default folder (like 'Assets') Resolve looks to first, if links get lost


BENEFITS FOR MULTI-DISCIPLINED USERS
Although the pro movie world often dismisses the graphics workflow, the simplicity, consistency and portability of OS-compatible project files is something the graphics workflow gets right for multi-disciplined users:

1.
Job assets from multiple apps are grouped into a single source of project truth. Life changing.

2.
Move a complete project in one step with auto-asset linking. No importing, no exporting, no extra steps for different apps.

3.
Basic multi-app version control: option-drag project files to 'Working' before opening. Instantly restore by moving back with auto-asset linking. Stupid simple, no additional software, no versioning databases, and consistent across all apps.

4.
Sync projects to and from portable drives via the OS, or your preferred sync app. OS compatible project files integrate with any current or future sync/backup app that can manage files, and it's the same process for all apps/assets.

5.
One-step archiving and backup. No additional steps for different apps/assets, everything is archived in one peace-of-mind step.

6.
Disk corruption doesn't create a single point of failure because multiple projects are not corrupted in a single file (the database). Plus there's a consistent recovery process for all apps with no additional database wrangling. Obviously YMMV, have experienced this and seen it several times with other users/companies/apps. And while we use on-site/off-site daily/nightly/weekly/monthly backups, sometimes you get a comedy of errors.

7.
Upgrade files on a case-by-case basis instead of upgrading an entire database of projects. Instantly revert individual files, and get a single, consistent process across all apps.


DIFFERENT STROKES
This isn't an EITHER/OR request, it's an AND request.

Yes, the prevailing tone lately seems to be 'go somewhere else'. But since FP7, many of us have been using different editors and Resolve has come into focus for many amazing reasons. And if BM aren't embracing more kinds of users, why add Editing, Fusion, Fairlight, the new cut page, and make it all free?

I hope people can see how vital OS-compatible project files are for multi-disciplined users and isn't taken the wrong way. I'm not trying to offend anyone - where I come from, OS-compatible project files are the opposite of crazy-talk.

Cheers

I suspect you're going to have to change your method of working to conform to the way Resolve functions, because it's not going to work the way you're accustomed. Resolve isn't Premiere, and it also doesn't necessarily function the same way Avid or Baselight or Lustre or FCPX or any number of other programs work.

What I do is I create a folder structure similar to this:

Client Name
--Project_Name_Date
---Color
---Camera Files
---Delivery Files
---EDLs & XMLs
---Fixes
---Graphics
---Notes
---Reference
---Scans [for film projects only]
---Sound
---Titles
---Trailers
---Transcodes
---VFX

This is what we use for final color & conform; no doubt an editor would use a different structure (no less valid, but not applicable to what we need for final color). There are cases where we get the Premiere or Avid session as well in rare cases where something has to be checked and verified.

The "Color" folder is really just for backups of the current color session as a DRP. The actual Resolve sessions live in a Project Database on a PosgreSQL server, which is shareable among different colorists and editors working in Resolve. It is possible to use network storage for all the source files. [You can also use a local Project Database, but it would not be shareable per se.] Cache files & Gallery files are local (on an SSD), but it would be tricky to share those across a network (but not impossible to copy them). The Reference files include stills provided by the DP, temp edits from the editor, and possibly look files intended for inspiration.

You can drill down and make the folder structure as simple or as complex as you want: for example, Delivery Files could include social media, theatrical DCPs, preview versions, temp versions, final versions, home video files, broadcast versions, foreign versions, whatever. Every facility has a different approach, and a lot depends on the vendors you deal with and their specific requirements. This will work across Linux, Mac, and Windows, assuming you have the codecs to play the file formats in all three OS's.

Workflow is not a simple area, and it's fair to say that there are a lot of approaches and philosophies that can work. Dailies requires one approach; Editing requires another; Sound goes in a different direction; VFX has different needs; and Color has different requirements as well. The only thing that's important is that you cover all your bases and document your workflow in detail so that every co-worker has a thorough understanding of how to maintain order to avoid chaos. I would point to Scott Arundale's book Modern Post: Workflows & Techniques for Digital Filmmakers as a source of further information.

Thanks for the reply, and for info on how you work.

Is there a practical way to create and manage multiple disk databases so there’s a job database (and therefore a Resolve project) which lives with the rest of the assets? I tested this idea several versions ago but it was painful - maybe v16 is simplified in this regard?

Did I understand you correctly that you export a backup of the Resolve project to the job (the Color folder) after each session?

Did I understand you correctly that you export a backup of the Resolve project to the job (the Color folder) after each session?

Wether you do it each time or not depends on the level of positive paranoia you show in your work...
Exporting a drp is really a handy way to be sure you can collect all necessary info about your ongoing project in case of unexpected OS or hardware issue. Among different ways of backup, you may want to choose this one regardless to the organization/WF you choose...

Wether you do it each time or not depends on the level of positive paranoia you show in your work...
Exporting a drp is really a handy way to be sure you can collect all necessary info about your ongoing project in case of unexpected OS or hardware issue. Among different ways of backup, you may want to choose this one regardless to the organization/WF you choose...

Thanks for the reply. I've experimented with databases saved into job folders but you can tell Resolve doesn't love it (plus it's convoluted). Judging by the comments, it seems people perform extra steps just to have a single source of project truth.

It's worth it for color, and while I prefer editing in Resolve, non-OS compatible project files are unnecessarily painful compared to FCP7/Premiere/AE.

Data management is ugly enough without proprietary data workflows so it's a shame Resolve doesn't support OS-compatible project files - the database doesn't integrate, backups and archiving can't be done in a single step, and it's the opposite of grab 'n go portability.

Everything else is about Resolve is awesome though, it's a shame we can't have both (it's certainly possible).

Disk databases are still painful if you're are a multi-disciplined (multiple apps) motion graphics artist or work in short-form video, especially online advertising.

OS-compatible project files offer...

• Simplicity
• Consistency
• Flexibility
• Portability
• Unified multi-app asset and job management
• Unified multi-app version control
• Unified multi-app backups
• Unified multi-app archiving and retrieval

I've used many apps that relied on disk databases over the past 30 years and without exception, a disk database always created unwanted extra overhead and inflexibility. And Resolve is no exception.

This isn't an either/or feature request - it's an AND feature request...
Keep database workflows for those who benefit but allow OS-Compatible project files for graphics users.

The graphics workflow is legit, tried and tested and is better in every respect for multi-disciplined motion graphics artists. We evenly split our time between multiple apps all day (e.g. Photoshop, Illustrator, Substance, Cinema4D, Modo, AE, Resolve, Fusion etc) and need to manage everything as a single job.

OS-compatible project files would fully integrate Resolve into the rest of the job folder.
Cheers