Blackmagic Forum

Hi

I am using 12.5.1 on mac , i want to copy all the data in my project to a new destination for back up .
the total size of data is 3.34TB and there are 789 files involved. first time it stopped on the file numbered 2801 wich i checked it is an Alexa files playing normally in resolve .
the first time i checked to preserve the folder hierarchy . there is no problem in the file in itself. i restarted the system and proceeded again.
the second time i didn't check the preserve hierarchy, the process stopped on the file number 19 which is a quicktime file playing normally in resolve.

any suggestions ?? is there a way to continue again from where the backup stopped??

Georges Kolja

I would try a backup utility like SuperDuper and see if it can get through the troublesome file without any problem. It's possible there's an illegal character in the file name, or there's a bad spot on the disk, or there's some corrupted bits within the file itself... there's several reasons why Finder copies fail. Same thing in Windows.

I am using the media management tool of Resolve. My aim is to consolidate my project. I tried copying the whole file and trimming. So far I realized that there are lots of duplicates file in my mediapool . So i don't know if this is the problem....

Sent from my E6883 using Tapatalk

Kolja georges wrote:I am using the media management tool of Resolve. My aim is to consolidate my project. I tried copying the whole file and trimming. So far I realized that there are lots of duplicates file in my mediapool . So i don't know if this is the problem....

You could do it all manually. Another alternative would be to use Nikolai Waldman's Resolve Collect:

http://www.niwa.nu/2013/06/collect-sour ... e-collect/

The only time I have seen Media Management fail is when the system is missing a small file, like a (relatively unimportant) title or audio file in an unused timeline. If it's in the project, Media Management will insist on trying to find it, and if that fails, the whole copy process will fail. I'd like to see better error handling here and have it just put up an error message and keep going. Maybe at the end, provide a report that says, "Warning: XXX out of YYY files were copied, 3 files were missing."

yes , we really look for a more advanced media management tool , a tool that does not stop if an error occurs, but skips the error and continues the process ,and at the end deliver an error log to fix later. But we also think that the media pool should handle the imported files in a way that it doesn't t allow you importing a clip that it is already in the media pool, nor it makes multiple duplicates of the same files .

Resolve finally managed to continue the media management process after doing the following :
first keeping only used shots in the media pool , by flagging all used clip in my timeline i was able to delete all unused files in the media pool.

removing all duplicate files in the media pool , by putting all shots in the master bin and deleting all other bins. and force conforming offline shots to the left video file in the media pool. it was a long process though.

And last after realizing that there are some go-pro files that have the same naming, all over the project , i checked marked the keep hierarchy button just to remove any conflict it might occurs.

I don't know what was the reason behind the media management failing but after doing the above the process of copying all the files succeed.

Bump. I just experienced two "Failed at..." errors, 4 hours into a 5 hour Media Management of a big RED project. The first time it failed, it seemed to be because of clips with special characters in the name. There was an archival clip within the mostly RED project with a "$" in the clip / file name. So I let the editor have it, then renamed the clip.

I started the second media management attempt, only to get a "Failed at A002_C001_01059K.R3D". No special characters there... Who knows why it failed...

The idea of Media Management is such a promising workflow. So many feature projects I work on require copying terabytes and terabytes of client media to my RAID -- only to use a small fraction of it in the project. I just love the idea of copying only what I need and avoiding 5-, 8-, 12-hour transfers, not to mention eating up less of my RAID space.

But Media Management as implemented now feels so finicky. I second the idea that I wish Resolve would just power through the "failed" clips and tell me afterwards which clips failed to copy...I will drag those over manually, I guess.

+1 on fixing the media management function. I find it fails at least 40% of the time.

Ugh... Same issue here. The media Management doesn't know how to manage errors gracefully. Failed imports because of just one tiny single file is corrupt or missing, are a thing of the past.

Gabi

any improvement in resolve 15 ?

While there are other tools for this, I'd say it needs to be either 100% reliable or just disabled.
It's too dangerous if you can't rely on it.

BTW, there is some improvement. Version 15 should be able trim GPO formats now. In my tests it does, but only for .mov or HEVC. It fails with H.264 in a mp4 wrapper. Works after re-wrapping, though.

Careful with overlapping segments, they only make into the trimmed version if they were defined as subclips.

archive will do what you want,
and will do it reliably
i use it - with no failures to date
media manage function is something i avoid

I'm having some trouble with this in Windows 10 as well.
Small project - under 70 files, most of what are jpegs.
There's one mp4 file which I'm using in the project, and it stops at that one every single time.
When it fails on that one file, the entire process fails and nothing is copied to the project folder I've set up.

So, one vote here for at lease to continue with the management process, copy/move everything that can be copied/moved, skip the ones that can't, and just give me an error report at the end instead of the entire process failing because of one file.

+100!

Media Management could be great, but failing because of just one bad apple (no pun intended) is ridiculous. In particular, if you are working in documentary and would like to transcode and slim your stuff down at the same time.

Reviving this as I encountered same issue (on windows 10), for just copying the whole project to a new hdd for transport.

I tried various things to see what worked, and turns out it was 'preserve file hierarchy' that caused the issue. Changed it from 0 to 1 and all worked fine. Perhaps due to having media scattered across hard drives? No idea, but could be worth testing.

Thanks for the hint, changing the folder level from 0 to 1 solved the problem, i.e., the folder hierarchy starts right after the drive name.

Same problem for me. One clip only made the copy failed.
I solved this by rerender the clip, put in place in the edit and then it was OK. Seems the file got something wrong with it, don't know what.

Seems Media Management still has the same issues... Resolve 17.3, copy fails without giving any log whatsoever... this should be rock solid guys...

Please invest some time in these things, is truly fundamental.

This channel offer a solution (I didn't try):
In timeline, locate the clip making the render crash, right click on it and "Render In Place".
then the render in Deilver page should work.

https://www.youtube.com/c/BillyRybka/

Thank you for the reply but this solution is only acceptable on some situations, the workflow to copy media should be rock solid, something we can trust 100% so although I appreciate the note, in my case is not good enough.

I am now forced to write a python script to analyse what is going on and find the offending clips... not fun.

Eddy Juillerat wrote:This channel offer a solution (I didn't try):
In timeline, locate the clip making the render crash, right click on it and "Render In Place".
then the render in Deilver page should work.

https://www.youtube.com/c/BillyRybka/

SOLVED.

So, after crawling thru the edit and replacing by hand every single clip with a traditionally downloaded version of each of those, eliminating any frame.io link, everything seems to work again.

The crashes are now gone, the export and project archival works, the media management works.

This makes me think there is some work to be done in those media handling tools to integrate properly with Frame.Io.

I love the new workflow, please guys fix this ASAP.

thanks.

However many years since this post and this is STILL an issue. I am getting really tired of how Resolve handles files and projects and databases. I just need to deliver the project but I can not because archive automatically fails right at the start. I tried the transcoding route but for some reason, Resolve ridiculously changes the file names so that you can't relink without replaceing... every...single...clip. WTF is the point? Pretty pissed because my client came with a checkbook and left with it after 2 months of work.

Tried just sending the drp and relinking the terabyte of files but client is on free version so of course Resolve watermarked everything as I'm on studio. Come the f on.

Good grief. Simply attempting to use Media Management to test the function of Media Management so I can trim excess useless footage from original source media.

Any time I select "Used media and trim keeping..." one clip is created and then the process fails, leaving what looks like trimmed clips in the destination folder, but they're corrupt.

What other tools can we use to ditch useless video from our source files?

I have just used Media Management for a project with about 300 clips from 3 cameras with different codecs, trimmed. At first try it complained about an offline clip, clearly indicating its name. That was a tiny bit of a leftover which was not easily seen on the timeline. After deleting this it went trough without a hiccup.

I'd only wish you could add just the missing clips in such a case, like an incremental backup.

Unchecking "Preserve Hierarchy" always solves it for me. No idea why. I do have duplicate file names since we forget to advance the scene and shot numbers all the time. So there is a danger in unchecking.