-
Media Manage Copy fails due to lack of disk space
So I’m onlining / color correcting a feature. I’ve been working on the Producer’s system, but seeing how:
a) I’m longing for the speed and stability of my G4 PB, and
b) The producer is not available often enough for me to get through this project (and isn’t
keen on giving me keys to his home)I am trying to take my work home with me. The producer is unwilling to let me take his drives, but since I just got a shiny new 500GB for cheap, I figure I can make this work. I’ll just Media Manage my way on to the new drive. I know, I know, one must be careful and welcome failure when trying to use any of the sub- or side- apps in FCS, but I’m being optimistic here.
What’s that? The producer’s machine predates USB 2? No problem, I get my powerbook over here, network ’em together, and we’re ready to take files from firewire drives to the G4 desktop to the USB drive via the G4 laptop. Okay. Networking accomplished. Drives all mounted, FCP open and hasn’t crashed yet. Media Manage launched. “File [of your choice] can not be copied due to lack of disk space.”
So I wonder if I’ve formatted or partitioned badly. Nope, showing 460GB of free space left. Check the original file – it’s a big one, at 3.2G. Double check the USB drive, and it’s formatted OSX extended, not FAT32 or some such thing. I find it, copy it manually, and choose ‘skip file.’ I keep doing this, and sometimes it’s multiple GB files that don’t go through, sometimes its 100MB files. Eventually, the entire process stops with the disk space warning.
Now I’ve worked around this, or I’m in the process of doing so right now, but I’m curious if anyone else has seen this erroneous error, or has any idea what the real culprit is, because this producer has all his footage scattered across a variety of drives, in unique but ambiguously named folders, and since FCP knows where everything is I wish it wasn’t making me and spotlight here do all the work.
Sorry for the long post, but I’m occupying myself waiting on the current 70GB to transfer. Thanks in advance.
-
7 Replies
-
Rob,
I’ve seen big problems occur when nonconforming file names have been used, but other than that copy has always worked. But then, I’ve never used media manager over a network. That could be your problem.
David Roth Weiss
Director/Editor/Post-production Supervisor
David Weiss Productions, Inc.
Los Angeles -
This just happened to me as well. Tried to copy 60GB to a 3TB network and received a “low disk space” message. Any workarounds?
-
a couple of things make me suspect:
“just got a shiny new 500GB for cheap”
“What’s that? The producer’s machine predates USB 2?”USB 2 is not great for video.
some people have luck with it,
but on the whole it is NOT for video work.the media may not play back properly, even on your powerbook
(may not be such a problem for simple colour correction)also your new drive may not be formatted for Mac.
should be Mac OS Extended
otherwise i suspect you could have real problems with an Media Manager operation.nick
-
Okay, so it’s matte black.
Truly though, what would cause USB to be a less effective means of transfer? The 2.0 spec does allow for greater throughput than FW400, no? (The real goal I have for this WD Book is to ease the load on a FW800 lacie drive, but in the interests of time I decided to give this a shot today) And yes, it is formatted for OSX extended (non journaling, at that).
-
Rob
Media Manager cannot “manage” files larger than 2GB .. its a bug/limitation, call it what you will, but it doesn’t work.
on the USB issue. USB2 has “peak” transfer speeds that exceed FW400, but “peak” is not what is needed for video work, Video requires “sustained” transfer speeds, and USB2 is just not able to handle these “sustained” data rates.
Sorry its not better news all round
Cheers
Andy -
appologies for not being clearer. the MM / 2GB limitation is specifically a network connected drive limitation and not a local connected drive limitation so if you connect your drive directly to your producers Mac, and MM from there, then you may have more success
-
Interesting news all around, really. Even though as it progressed it was failing to move the 100MB files, that may well be the stem of the trouble.
Sounds like the correct course of action would have been to just go home, put the new USB drive to work storing the non-working files (as in ‘not called upon,’ they work just fine), and then return another day with the FW800 lacie drive. …which is something I’ll be doing anyway.
Thanks for addressing my curiousity.
Reply to this Discussion! Login or Sign Up