Export error

Guys, I have a serious problem.
The 10.0.3 solved many bugs here, and in general, the program became fully functional, finally ready.
But .....
Since I updated, I can not export anything bigger, anything longer than 15 min. gives error, an error-rated 5000 and something. I've tried everything, saving in all forms but the error persists, and in more than a different job.
Unfortunately, this error prevents me from working, because all my jobs have more than 1 hour.

Hi Uk,
what format(s) are you trying to export, and by which means: using Compressor or directly from FCPX?

I tried "current settings" and also H264, tried directly and via the compressor with the same results. However, in the same jobs (event), other project, a video of 14 min. was exported smoothly.

Using a Macbook pro 13, core 2 duo, 8gb ram.

No other app open.

Now here I tried again, with 37 min video. The error number 5000 is not actually an error whenever he thinks the frame around 50,000 this time was 48,500.
The error is -108.

Always the same thing. Unfortunately, I have to reinstall 7 and leave the X.
Sadly, I was enjoying the X!

Did you go to the File menu and delete the render files for that Project, and for the related Events?

I did not happen. But I'll try.
I got the XDCAM export as needed to deliver the job right, I'll try it after exporting everything .

I exported a file of 37 min., Now I'll try a 57. If I can, I'll be saved, for now ...

List the capacity of each drive on your system.
List how much of it is free space.
I assume all of your media is on an external FW800, 7200rpm drive?

List the capacity of each drive on your system.
External 1 - 1T
External 2 - 2T
Internal - 250gb

List how much of it is free space.
External 1 - 200 gb
External 2 - 560 gb
Internal - 90gb

I assume all of your media is on an external FW800, 7200rpm drive?
yes

The problem is that I've been with them more fuller, and it worked.

It is recommended to leave at least 10% to 15% of free drive space available on all drives for the drive to properly function. You are above this level with the info you provided so should be OK there.

Assuming you don't have a corrupt project or event, your problems may be a result of trying to edit directly from FW800 drives. These will often work but struggle with large HD projects. I use them only for archiving media. Faster drives will improve preformance.

But I had no problems with the same units before 10.0.3.
Even a file that you exported without problems in 0.2, crashed in the 0.3 export
Apple may have created a standard where the TB would be needed?

TB is still too expensive!!

When edited with external HD, if not using them would have to move tons of files on the internal hard drive, which would have to have a 5TB

Well, on a MBP the only option, if it's a newer one, is a T'bolt drive. But drive speed only really effects actual editing operations.

More RAM would help. I think that MBP should hold 16 GB RAM, or is it's limit 8?

As for the error being during an Export operation, drive speed has very little bearing on this.

I'm assuming you export with Cmd-E, Current Settings, Video and Audio?

Here's what I'd recommend at this point just to clear out a host of possible problems in one fell swoop?

1. Download the free "Final Cut Remover" app from Digital Rebellion, and use it to wipe FCP X from your drive.
2. In the App Store, the Purchased tab, click to install FCP X.
3. Use Disk Utility to Repair Permissions on the system drive, and Repair Drive to all other dirves.
4. If you leave your computer off or in sleep mode at night, get the app Cocktail to run the Daily, Weekly, and Monthly UNIX maintenance routines, but do NOT run any of it's other functions!
5. Inside FCP X, delete Render files for all Events and Folders.
6. Turn off background rendering in preferences.
7. Try again.

These will knock out a lot of possible causes at one time.

Yes, dirves should have 15% free space. External 1 only has 50GB left until it's technically filled. External 2 has 260GB left. Internal has 53GB left. You're good, but close to filling them.

Also, I wonder if you have tried to set up any clusters with QMaster?

Don't put your media on your system drive, either.
There's nothing in FCP X that forces you to use a T'bolt drive, computers just don't work that way.
What OS version are you on?

BenB wrote: If you leave your computer off or in sleep mode at night, get the app Cocktail to run the Daily, Weekly, and Monthly UNIX maintenance routines, but do NOT run any of it's other functions

I use Cocktail routinely and I am wondering what other functions you recommend NOT to run with it and why.

Localization will destroy foreign language dictionaries, menus, etc, that you may need. I've seen that happen to a few clients. All the caches it clears are a waste of time, since they are limited capacity caches and are self maintaining, and you may clear out stuff you won't want cleared out. Defraging a drive today is simply an outdated joke. It's better than it used to be, it used to have functions that folks unknowingly destroyed their whole systems with at one time way back when. 90% of what it does is unnecessary and should be left alone. Based on my over 20 years as and IT engineer.

OK...I just usually let it run the scripts, repair permissions and occasionally I manually drag a folder into it to let it search for corrupted preference files. I have been letting it clear caches from time to time, but I'll stop that and see how it goes.

I installed 10.7.3 Lion. When I installed, I repaired permissions etc.. All clear, cleaned HD.
The strange thing is that to install the Lion, I bought RAM, so before they were 4gb of Ram, and Snow. FCX 10.0.2 and exported all right.

The time now is 8GB of Ram, Lion, and not exports. Theoretically the situation was better now than before, so even if it is 8 bit, it's still better than 4.

As spoke my grandfather, where they eat four, eat eight!

What I mean is that if the problem was performance, but it sure was not this happen before and not now.

The 0.3 is working much better for me than others. I would say that it was not for export, it would have reached the point where we can say that the program is ready, only making minor point releases.

But if the problem of export is not resolved, the program unfeasible.

I've seen in forums here in Brazil that the problem is recurring, many people complaining about the same problem.

I'll test the "Final Cut Remove".

The export problem you're having is rare among my clients, students, and the forums I moderate and watch. Did you update Compressor and Motion when you updated FCP X?

Someone suggested to me to reset the PRAM when this happens. Worked for me. But be careful - you might want to look into your system preferences afterwards.