MDV-YVR wrote:I'm exporting an indie feature for the colorist using the Media Management tool (my first time). I selected used media with trim 24 fr, it says there are 388 clips, old size was 580GB, new size 412GB and showing the progress as a 20+ hours export job! Is this normal? It seems excessive to me. Why would this take so long?
I'm guessing it's very large files. Media Management is limited by the speed of your system and the speed of the connected drives. I just had a 20TB (source) conform that took about 20-22 hours to slice all that footage down to 3TB of 5K R3D originals, and I was fine with it. The client had given us relatively-slow USB3 drives, and the new conformed source media-managed drive was an SSD RAID0. We accept that it takes this long, especially when it's accessing material spread across multiple drives.
Also does anyone know if I click on stop can I resume later and not lose the several hours of what it has already done?
It will not. A bigger problem is, if Media Management encounters an error, it will come to a screeching halt and refuse to go on. I wish it had better error trapping, so it would just finish the entire Media Management process and then pop up a warning that says, "Caution! The following errors were encountered!" and then list whatever files it couldn't find. Dermot above is right in that Resolve Collect will not do this, but Resolve Collect also will not trim footage, so there's that limitation.
Here's some Media Management tips that work for the way we use Resolve:
1) limit your session to just the files actually used in the session (that is, make sure no unnecessary files are sitting in bins)
2) Render-in-Place all H.264, JPG, TIFF, and PNG graphics clips to ProRes or DNxHR so that now the clips have embedded timecode and (preferably) unique file names
3) for camera clips with embedded audio, my opinion is you're better off if you strip the sound out as a WAV file that lives in the session
4) be aware that Titles can be a bit dodgy and don't always survive the changeover with Media Management. (I would say the same thing with Fusion sequences, which I would render out and treat as a separate transcoded element.)
The simpler you make your session, the better the potential for successful Media Management. The moment you have a filename clash or a timecode conflict, it can fail. I wish Resolve had better error trapping so that when it did encounter an error, it just popped up a message with a list of problems, rather than just bailing on the Media Management entirely.
As mentioned earlier, if your file copying is failing for another reason, try Nikolai Waldman's Resolve Collect and I bet it'll get you at least 98% there without errors. His program has been a lifesaver for me over the last 6-7 years.
http://www.niwa.nu/resolve-collect/Another possibility (which I haven't tried) is EditSpy for Windows:
http://edlspy.felixhuesken.de/