Export crashing FCP

I had successfully exported my short video to QuickTime to make it a movie. Then I went back and changed one element. I put in scrolling credits at the end. It is all rendered, but now when I attempt to export the material to QuickTime, it takes down FCP. I'm not sure how to troubleshoot the problem. I assume the introduction of scrolling credits is the issue, but I don't know how to uncover the problem. Any suggestions?

There would be several things to try to troubleshoot this however here one suggestion.
Edit (or copy/paste to see if it works) the credits on a completely different/new project with same settings. Export the new credits as QT movie self-contained (or reference), same settings (this way quality will be unchanged).
Finally import the newly exported credits into your original project and export again.
See if that helps,
G.

Similar Messages

Exporting as WMV crashes FCP

Hi there. I'm not sure which part of help this should come under as i'm sure there are lots of issues why its not working.
I'm using FCP HD 4.5 on my MAC OS X version 10.3.9, with QuickTime 7.0.0. I have just installed "Flip4Mac WMV Studio Pro" and when i try to export as a WMV it crashes FCP. I previously had problems with newer versions of QT not working on my FCP, so thats why i use 7.0.0. Any ideas? will newer versions of FCP work on my older system? Thanks

Hi, yep did that one too lol. here is what he said:
Update Quicktime to 7.3.1. Use Flip4Mac 2.1.3.10 rather than 2.2.0.49. FCP 5.1.4 should work on your system.
FCP can only be updated to 5.0.4 unless you have the "universal" 5.1.x discs but 5.0.4 would work.
QT 7.0.0 should not be used at all. 7.1.6 is the lowest most would recommend.
Flip4Mac has an uninstaller in its Applications folder. You can run that and then install 2.1.3.10
ALWAY run Repair Disk Permissions before/after ALL updates of any software.
All Apple updates (that are recommended) are on Apple's support site.

File Crashing FCP - Can import from different tape brand be at fault?

I always use Sony Premium mini DV tapes and import my video through my Sony DSR-11 miniDV deck into FCP.
I was recently handed a Fujifilm miniDV tape. The video imported fine. But once I dragged it to the timeline, rendering any transitions or filters caused big gray boxes to appear on the video. Sound also fell. I was able to make it work - but the exported file retained the boxes at different places each time I exported.
Now the file doesn't open at all and it crashes FCP. All other files on my system still open and export fine except for this one.
My question is 1. whether the change of tape brand can cause the import to go haywire.
and 2. Is there any way I can open this file? I trashed preferences and restarted with no luck.
Any suggestions ar emuch appreciated. Thanks!
Dual 1.8 GHz G5 Mac OS X (10.4.8) 4 GB DDR SDRAM

I've never had the same experience, so this is purely speculation.
Changing brands used in the same camcorder has been reported as the cause of recording & playback problems. But, since the playback from the DSR was okay, I'm guessing the brand isn't the problem.
Could be the camcorder settings don't match your FCP settings?
What if you copied the Fuji tape to Sony tape in your camcorder. That way you would have control of both the tape and the camcorder settings.

XML Crashing FCP while importing. Magic Bullet Looks could be the problem

Hi All,
Need a little help here.
I am using FCP 6.0.5 on a power mac G-5.
I am trying to open an XML which was exported out of FCP 7 as a version 4 XML.
Magic Bullet Looks is being used on the project, and I think this is were the problem is.
when importing the XML it crashes FCP when I select the Include Video/Audio Effects.
When I import the XML without this option selected it opens fine.
I have MB Looks Installed on machine, so the Plugins are there.
Just wanted to see if anyone has dealt with this issue or might have any insight to the problem.
I can post the Crash info on the specific thread if that can help.
Thanks!

Couldn't agree more Jim - hence why I'm not using Snow Leopard yet as I had a nightmare in the early adoption of an older operating system. As for MBL, there seem to be many using it without problems so I don't think it's an issue with the product per say and it really is a very good plug-in. (That view will change to excellent once the problems go away) I just need to get to the bottom of which square peg is destined for which round hole and I'm hopeful that all will be well. I've also submitted a support question to Magic Bullet so will update if I get a solution. I like the CleanApp idea. I'll try that as well. (and I may even give Snow Leopard a go!)
R

HUGE JPEGs crashing FCP

Ok, I'll start off by admitting I made a nubie mistake scanning photos in at exorbitant PPIs resulting in TIFFs that were hovering around 1GB, yes that GIG, and the largest file being 1.58GB. I've since gone through, and exported them to JPEGs resulting in file sizes about 10% the originals. However, that largest file is still giving FCP problems. Most other jpegs, from 2.7MB to 65.7MB results in a green render bar under Unlimited RT on my 2.16 Core Duo MBP with 2GB of RAM. Now when I go over that, with the 3 files that are 77.3, 86.6, and 115.8MB, the images get an orange render bar and result in crashing FCP. I read in a previous thread that it was a memory issue, and that was confirmed when I went to play one of the images in the Viewer and I get Error:Out of Memory. So I jacked the memory, all of it. Application was always listed as 100%, but now I have Still Cache also set to 100% and Disk set to 10,000K and RAM at 1,000K, but this still hasn't fixed my issue. I've tried every way I know of to render this image, and they all quit FCP. Before I raised the memory, just placing the file in the timeline would cause a crash, so at least now it gets past that. If I let it auto render, crash. If I do it manually, crash. If I make a new sequence like David suggest in a previous thread, you better believe it crashes. The interesting thing is despite raising FCP's memory usage, Activity Monitor still shows 1.04GB of free RAM, so if FCP is Out of Memory, why doesn't it just use up that 1+GB? Does anyone know why FCP can't play with such large files?
I guess I'll just need to recompress the few images again, but it's VERY annoying. At least I'm not trying to work with the 1.5GB image.
-Brian
By the way, I am on Final Cut 5.1.4.

You can reduce the cache levels and history states in Photoshop's memory preferences. This will buy back some memory. You should quit and restart Photoshop after each major image resize. This will also keep the app from building up too much cache.
I'll assume these are PSB format, rather than PSD. PSB's don't work the same as PSD's with scratch disk. You may need a separate scratch disk if you keep getting errors. Designate your fastest largest drive to do this.
You really need to get them down to around 1000x1000 pixels to be truly fast in FCP.
Don't forget that Photoshop has a new tool called Image Processor under File/Scripts/ that can size documents without really having to rasterize them. It works much faster than opening the file then running a resize. But be careful to just run 1 or 2 at a time, since I've found that it doesn't do a great job at purging the memory after each image. You will run out of memory quickly if you have too many files at once.
Remember to quit and restart Photoshop, or even you machine if it really slows to a crawl. These are signs your hard drive is full and relaunch and reboot will clear all the temp files from Photoshop's scratch disk.

QT plugins that crash FCP 5.1.2

OK... here are the known QT codecs that crash FCP 5.1.2 at startup:
These are found in /Library/Quicktime/
On2V3
TSCC
X_Vid
Avid codecs

These are the plugins I have currently sitting in my /Library/Quicktime/ folder and FCP DOES work with these installed:
3ivx D4 4.5.1. for OSX
AC3MovieImport.component
AppleHDVCodec.component
AppleIntermediateCodec.component
AvidAVDJCodec.component (05/01/02-version 9.4.2)
AvidAVUICodec.component (05/01/02-version 9.4.2)
Blackmagic Codec.component
Blackmagic RT Color Correction.component
Blackmagic RT Dissolves.component
Blackmagic RT Image Control.component
CanonMJPEGAVI
DesktopVideoOut.component
DivX 6 Decoder.component
DivX Encoder.component
DVCPROHDCodec.component
DVCPROHDMuxer.component
DVCPROHDVideoDigitizer.component
DVCPROHDVideoOutput.component
DVCPROHDVideoOutputClock.component
DVCPROHDVideoOutputCodec.component
FCP Uncompressed 422.component
Flip4Mac WMV Export.component
Flip4Mac WMV Import.component
Flix Flv.component
Flix Swf.component
IMXCodec.component
KinomaExporter.component
lame 3.92.shlb
LAMEEncoder.component
LiveType.component
Media 100 Transcoder.component
Microcosm Decode.component
Microcosm Encode.component
Motion.component
MP3.component
OsirX Broadcasting.component
RealMediaExporter.component
SheerVideo™ HD Pro.component
Sorenson Video Pro OSX.qtx
Now.... on two of our machines we were unable to get FCP 5.1.2 to run with the same version of Sheer codec installed.
I also want to note that I did restart FCP once after it running without problems and I had to remove all my codecs... restart FCP.... kill FCP... move my codecs back into the Quicktime folder and then it worked fine.
I put the dates on the Avid codecs to let you know which ones I know are working.
As far as I know all other codecs listed are up to date.

Substandard renders and .motn projects that crash FCP.

On rendering out video from Motion (first version) I am warned that almost every object on my timeline is 'too large to render and will be cropped'. I'm working on anamorphic D1 projects and some of the objects it is telling me are too large are things like 720x576 video clips and even 16 pixel high caveats with no effects. I can get a render using the 'export' command in Motion but for some reason these are exceptionally jagged and have no sub-pixel supersampling (I've got anti-aliasing turned on but this doesn't help a great deal and the jagged edge are far too obvious to use for broadcast purposes). I'm rendering Uncompressed 4:2:2 and both project and render settings are upper-field first.
I have tried simply importing the .motn projects into FCP which for some reason manages to render objects much smoother than Motion's native renderer - but unfortunately all of the projects contain particle effects which seem to crash FCP every time it comes across them. Going back to Motion to render these sections is no good as it seems to render particle effects with random jumps and missing frames in them.
Any tips for getting decent quality smooth anti-aliased renders from Motion into Final Cut Pro as I'm not having any luck so far and I've got nine television commercials due for delivery Monday morning - yikes!
Any suggestions most welcome!
Cheers,
Tom

Though I realize Motion 2 isn't available as a separate item anymore, it is absolutely worth getting as far as speed and performance.
I remember thinking that on the same hardware it felt like it was 2x as fast.
Definitely check out the linked Motion Smarts article - it's a great explanation or introduction to the specific problems you can have working with a GPU-based FX program like Motion. This stuff matters - if you can master optimizing your projects by design Motion will be a nice addition to your toolbox.

PDF Export Crash (follow-up)

There was a thread a while back titled "PDF Export Crash." Because it was archived, I was unable to post my findings there. This issue recently became front and center for me within the last 24 hours. For those unaware, I am referring to an issue where Pages crashes every single time you try to export to PDF on certain documents (even through the print dialog). Using a different computer only produces the same results!
After some investigation and testing, I was able to discover that the presence of footnotes was directly tied to the problem. Once removed, seamless exporting followed. However, not all footnotes were responsible. I found the third page of my document, when isolated, exported just fine along with its footnote; while the fourth page of my document, when isolated, did not export (crashed). Footnote along are there NOT directly responsible.
Although I am still unable to determine the exact problem, I would like to make these observations available along with another workaround I discovered. It is a little tedious, but absolutely guaranteed to work for someone who is desparate.
1. Copy and paste your entire document into TextEdit.
2. Create a new blank Pages document and past it back in.
3. Manually add your footnote back in one at a time.
4. Make any minor formatting corrections from the transfer.
After using this method to recreate the original document, while visibly symmetrical, the recreation process somehow eliminated the "quirks" that were causing Pages to crash during a PDF export.
If anyone is still having this issue, I'd be interested to hear from you. Especially if you have discovered exactly what causes certain footnotes to disrupt the PDF export process.
iMac G4 Mac OS X (10.4.2)

In order to isolate the problem as much as possible, you may want to delete parts of the document, step by step, and see how small it can be and still crash.
If you are lucky, that may tell us exactly what causes the crash.
If you are unlucky, the reason is an exceptional corruption of the document, which happened some time in the past, and which cannot be isolated this way.
Good luck!

Thumbnail view crashing FCP -- Kona3 the problem?

For larger projects, running bins in thumbnail view crashes FCP.
Most of the time, I'm editing 6 to 8 min. stories for a news magazine format show. We shoot on Sony XDCAM, so usually 2 or 3 disks per project (roughly 44 mins of HD viddy per disk, with anywhere from 20 to 120 individual clips on the disk).
However, for our documentaries (either 26 mins or 56mins) we shoot between 30 to 45 disks full of content. When importing the disks into FCP7, we use a bin per disc, translating into an average of 80 clips per bin. Whenever a project is this big, I can only open 3 or so bins in thumbnail view. After that, the system crashes. Even if I only keep one bin open at a time, by that fourth bin, the system crashes.
We are using a KONA3 card configuration.
Anyone else seen this?

PROBLEM IDENTIFIED (NOT SOLVED):
I've had this problem with thumbnail images crashing FCP after opening bins for over a year now and when going back using footage from old projects it happens more frequently. I can open 2-4 bins before it will crash FCP completely.
TROUBLESHOOTING IN THE PAST:
- Dumped Prefs
- Re-installed FCP
- Formatted & Re-installed EVERYTHING (OSX included)
- Increased thumbnail cache size
- Created new projects & bins, etc.
CONCLUSION:
None of the above troubleshooting strategies worked. Increasing the thumbnail cache size may appear to work a little but problem persists with little improvement.
HOW I IDENTIFIED THE PROBLEM:
Only recently have I been working with other formats aside from XDCAM. I've recently incorporated more ProRes files into my most recent project of T2i footage from the Canon DSLR camera. If I open a bin and display thumbnails of the ProRes video clips everything works without a problem. Loading thumbnail bins with the raw .mp4 files also works fine. Only loading XDCAM files will cause FCP to crash. The problem has nothing to do with the Kona card. If you read the posts carefully here and elsewhere you will see the common denominator is the XDCAM encoded video files being displayed as thumbnail icons.
I am using XDCAM EX files at 1080p 30fps. To further isolate this problem as something having to do with the XDCAM files, another user posted on another thread:
*"I am having similar issues with two separate projects. The only commonality between them is XDCam.*
*To possibly isolate it I reinstalled FCP on one system, and installed latest Blackmagic driver on the the same. Both systems are up to date visa vi OS, FCP, and QT.*
*Both still crash with the same regularity as described here."*
Apple, this problem has persisted for more than two years and is a major problem. Just search the forums including this one. Any further upgrades of Final Cut Studio or OS X are worthless until this problem is fixed. A brand new body and interior won't fix a car with a broken engine. Please help!! Please solve this issue with the XDCAM footage in FCP!
If anyone has any solutions or work arounds please notify me. I need it!
[email protected]
/\/\ichael
Message was edited by: MichaelRev1412
Message was edited by: MichaelRev1412

Everytime I export from FCP using comressor I am lose my audio, any ideas as to why this is happening. Or do I have somthing turned off and I am just missing it? Dual 2.7 Ghz PowerPC G5 1.5 GB DDR SDRAM, Mac OS X (10.4.6)

Everytime I export from FCP using comressor I am lose my audio, any ideas as to why this is happening. Or do I have somthing turned off and I am just missing it? Dual 2.7 Ghz PowerPC G5 1.5 GB DDR SDRAM, Mac OS X (10.4.6)

Exporting via Compressor may be recommended but it is slow and doesn't fully support all available filters, etc.
Try exporting the timeline as a QT Movie (the "normal" export) using Current Settings and them submit the resultant clip to Compression. Works for me...

Export from FCP directly into DVD studio pro?

Is it possible to export from FCP directly into DVD studio pro? If not, what is the preferred file format because my exported quicktime files come up as "incompatible format" when I try to add them into my DVD project. Any help is appreciated.

You need to encode audio as well from Compressor. You'll have 2 files - audio and video.
Here's a tutorial:
http://www.youtube.com/watch?v=wFgJpd7DEWw
Message was edited by: Eric Pautsch1

Exporting from FCP to DVD

Hey
Just wondering if I can get some advise. I need to export my project from final cut pro to DVD but just wondering what the best way to do this would be to get the best quality DVD. (This is for a company to take out to potential clients to sell what the company does - so it needs to look good!)
My project is no longer than 5 mins
1920 x 1080 - 1080i (16:9)
Field Dominance: None
frame rate 25
I have Final Cut Studio latest version.
I'm trying out a few options at the moment using compressor - best quality - so we'll see what these look like, but I'm not sure what all the settings should be set at.
Any advise on what you think will be best would be great.
Thanks

Wouldn't use Quicktime conversion - no need. Just export from FCP as Quicktime Movie at current settings.
In my experience, changing the field dominance from interlaced to progressive can cause stuttering particularly in motion graphics - this might not be an issue if you're laying to tape for broadcast but when you convert back to interlaced for SD DVD it can look very ugly.
In any case, at the very least, you need to be using a Kona card or IOHD to do this type of conversion properly - and really, if you want progressive you should shoot progressive.
Message was edited by: Dynamicworm
Message was edited by: Dynamicworm

Rendering Sequence with Motion 3 Template Crashes FCP

I am using a template with 8 drop zones from Motion 3 in FCP 6.0.2. The template is used about 10 times end to end with a slight overlap. As FCP renders the sequence about 23% of the way through it crashes FCP. The templates contain still images - no video.
Any thoughts? (Besides don't use templates)
Thanks!

Joe,
You might want to post this in the Motion forum
http://discussions.apple.com/forum.jspa?forumID=656

AVCHD files crashing FCP using Perian

Hi everyone, I'm wondering if anyone can help with a rather hard to pin down issue.
AVCHD files on a SD card recorded on a Panasonic broadcast camera have started crashing FCP on random file transfers (log and transfer window), say I have 30 clips to transfer, it'll freeze then crash the system on clip 22 but the other clips will be fine.
I have had a look at the report window and it says' Perian has unexpectedly quit' (why the **** are apple using third party software to do the job) and the log is just code to me.
I first suspected the camera an AG HMC151 (150) because I have two so it was easy to just test the other one, but it does it on both.
Then I suspected the cards, it does it on all of them.
So I can only assume it's the macs, of which I have two, both have 10.6.6 and I'm running FCP 6.0.6. they are both about a year old.
Because this is a random problem it's actually rather stressful as this is my living.
If anyone has any good ideas or has experienced this please let me know, I think I have mentioned everything I know and apologise if I have left out some piece of vital info.
Thanks

I've been having the same issue with importing AVCHCD footage from my Sony NXCAM. Through some major digging, I discovered someone else in another forum recommend the program Clip Wrap 2 (which I see someone also recommended above). I downloaded it just now and it works GREAT for creating useable clips. Highlight recommend.
http://www.divergentmedia.com/clipwrap

AVCCam Crashing FCP

Hi,
Just back from Cannes where my latest short film was picked up by a distributor...aside from that great news, back to reality:
I'm just trying to load in some footage from the new HMC151 panasonic AVCCam.
However, everytime I try log and transfer it crashes FCP saying there's a problem with Perian. I've tried different Macs, card readers, using the camera as the reader etc, but the clips won't load in.
I tried shooting in 720/25p and the clips came in fine, but that doesn't help the fact I have a card full of 720/50p clips I need to get in and edit.
Any ideas? How do I remove Perian to get that out of the equation?
Help as always appreciated.
Kenny.

It has an uninstaller.
Look in the system preferences.

Export crashing FCP

Similar Messages

Maybe you are looking for