Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Media Manager - Error Code 34

I have a large project, and I want to reduce it with Media Manager.

I've selected 1 sequence, opened Media Manager and set it up to copy, deleting un-used media, using 2" handles, duplicating selected items & placing in a new project.

This goes all sweet except 1 clip on the timeline brings up "Error Code 34"

Can anyone help me get around this error?

Quad Core Xeon, Mac OS X (10.6.2), 8Gb RAM, Matrox MX02 Mini

Posted on Feb 28, 2011 2:05 PM

Reply
14 replies

Apr 11, 2012 6:00 PM in response to Studio X

I've been editing, not media managing.


Anyway. Within 20 minutes, I discovered a work-with (not a work-around). I thought I'd enrich the frustrated and curious masses (instead of trolling them, Studio X).


During Manage, if you request that FCP trim your managed clips, the file is copied and the file name is appended. If your filename is lengthy (try to remember the last time you worked with footage that didn't have a camera-generated or footage-log-generated name), Final Cut is unprepared with a solution and sh•ts its ridiculous bed. It will ask you if it should make a second absolutely futile attempt, abort the entire process, or skip ahead to see if it will trip on its lips trying to manage the next clip in the timeline.


If you choose to skip, your file is still copied and trimmed and placed in the Media folder at your specified destination. However, due to the fact that it is nearly as old as the Nirvana Nevermind baby, FCP won't connect the newly created clip to your managed timeline, nor will it add the appropriate .mov file extension in the Finder.


Your only burden now is to root through your Media folder, add the extensions to the skipped files and to manually reconnect the footage in your project.


At this rate I will suggest that it may be easier to become familiar with the following F, ⌘E, return process.


1. Place the playhead on the first clip in your timeline.

2. Press F. This will bring the clip with the current in and out points into the viewer.

3. Press ⌘E and select a location to save the clip.

4. Press Return.

5. Repeat until all clips are accounted for in the save location.

6. Export an XML of your sequence.

7. Import the XML and reconnect the sequence footage to the new clips.


I hope this is helpful to anyone nutty enough to want to use FCP in the future. Thanks.

Jan 18, 2013 5:49 AM in response to Bengt Wärleby

I've always heard that you should keep at least 10% free on every drive and more on your startup drive. The OS uses the startup drive to swap in and out of ram as needed and programs such as compressor by default use the startup drive for temporary storage, so keeping at least 20% free space on your startup drive is probably a good idea. Also, if programs like Compressor lock up/crash while processing a large job, large files may reside on your startup drive indefinitely unless you know where to look and delete them.

Nov 19, 2013 1:30 AM in response to Burning Head

The 34 error is not the same as a OS -34 which is for Disk Full. I had this issue with media menager, and it seems to be with files exported from motion. I am pretty sure that FCP is falling over when trying to truncate H.264 codec files.


Also Studio X, we have noticed that:


1. Unfortunately FCPX is being dropped from most production houses.

2. Many people are actually sticking with FCP Studio or moving to Adobe Creative Suite in its entirety.
(source: BBC)


The work around was to move the whole files - not try and trim them or delete unused.

Nov 19, 2013 7:14 PM in response to camiono

1. Actually, FCPX was never adopted by major production houses as it lacks most of the basic features required to produce projects larger than a youtube video.


2 As the BBC notes, big operations that are using FCP7 will stay with FCP7 until forced to move. When that time comes, they will either move to Adobe Premiere or Avid.


Stability of workflow, consistent output, known entity, etc, are worth A LOT. Apple seems to have had a total brain fart regarding that. I suppose this comes from being a consumer driven company.


x

Dec 10, 2013 1:09 PM in response to camiono

I'll chip in here if I may...


I am also having trouble exporting my latest project using 'Media manager" from FCP7 on my new film for BBC, who are still using (as you may have guessed)...FCP7. According to my Editor at BBC, they do not even have an evalulation copy of FCPX, so investing in that software seems pretty pointless. However, BBC are looking at Premiere Pro (which is pretty simialr to FCP and very good indeed - I just cut a short film on it this week, very impressed) and since they use After Effects and Photoshop extensively for Graphics work, it would seem to make sense. I am not sure they are consdiering Avid again.


I wrote wee blog about PP isf anyone is interested http://is.gd/tdBjFX


FCPX is fine for any independent that does everything in house. But if you are using facilites (or in my case the broadcaster's own facilities) for a final edit, then your NLE next step from FCP& is dictated by others it seems. IN my case, everything seems to be steering me towards Premiere Pro.


But this does not solve my current issue. Why is FCP not making a copy if my project with Media Manager as usual? The first file that it fails on seems to be one of my P2 imports on the scracth disk. Could this be the issue?

Media Manager - Error Code 34

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.