FILM OUTPUT FINAL crashes FCP
After two 31 hour sessions outputting my final 2hours movie, it has crashed with only two hours left.
So I have a sequence which is my final movie of 2hours. Im exporting quicktime with Uncompressed 10bit NTSC. vs choosing the dv compression, I was trying to get an uncompressed final to have as final. Can someone please check my crash log and tell me what would be causing this? Im at wits end trying to fiqure out why in the last two hours it would crash. I starting exporting snippets from the last part to see if I can find the area where its crashing. Does Final Cut export from begaining to end or does it export backwards?
To clarify I choose Export as quicktime, instead of using current settings Im choosing Uncompressed 10bit NTSC just to get the highest resolution. I guess I could try the current settings but I fear there is a resolution loss. If anyone can look over my crash file and or give me some support for exporting a 2hour film, my final goal is to encode as Mpeg2 for DVD. So would love some support
Date/Time: 2010-10-03 10:21:07.419 -0700
OS Version: 10.4.11 (Build 8S165)
Report Version: 4
Command: Final Cut Pro
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Parent: WindowServer [74]
Version: 5.0.4 (5.0.4)
Build Version: 2
Project Name: FCPApp
Source Version: 512141418
PID: 802
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00005000
Thread 0 Crashed:
0 <Unknown disk fragment> 0x47ccb968 copyfrom_8bit_integer_world_simd_12MBFloatWorldFllUlPCUc + 296
1 <Unknown disk fragment> 0x47ccb4f0 copyfrom_8bit_integer_world_12MBFloatWorldFllUlPCUc + 112
2 <Unknown disk fragment> 0x47ccb318 copyfrom_PF_World__12MBFloatWorldFRC11PFLayerDefPC4Rect + 152
3 <Unknown disk fragment> 0x47ccb01c ct__12MBFloatWorldFRC11PFLayerDef + 92
4 <Unknown disk fragment> 0x47ce16f4 renderframe__FP9PF_InDataP11PF_LayerDefRC9tSettingsP11PFLayerDef + 116
5 <Unknown disk fragment> 0x47cca800 Render_FP9PF_InDataP10PF_OutDataPP11PF_ParamDefP11PFLayerDef + 576
6 <Unknown disk fragment> 0x47ccaab4 main + 180
7 ...CutPro.Plugins.AfterEffects 0x063a13d8 CALLPLUG_INPROC + 184
8 ...CutPro.Plugins.AfterEffects 0x063aadfc AEFXRenderFrameRequest(tagAEFXStateMachine*) + 168
9 ...CutPro.Plugins.AfterEffects 0x063ab720 ProcessAEFXStateRequest + 1488
10 ...CutPro.Plugins.AfterEffects 0x063c3b44 PluginMainEntry(long, long, KGDictInt*, void*) + 2216
11 com.apple.FinalCutPro 0x002fd918 pKGRunTransition(KGDictInt*) + 984
12 com.apple.FinalCutPro 0x0025bf20 ProcessFilters(KGDictInt*, KGDictInt*, long, unsigned char, WhenRec*, double, KGRect*, long, KGCanvasRec*, KGCanvasRec*, KGCanvasRec*, double, double, renderStackInfo*, unsigned char*, BufferInfoRec*) + 2448
13 com.apple.FinalCutPro 0x0025c4b0 GetFilterFrame(KGDictInt*, KGClipItemType, long, unsigned char, WhenRec*, double, BufferInfoRec*, KGCanvasRec*, KGRect*, renderStackInfo*, unsigned char*) + 816
14 com.apple.FinalCutPro 0x00260344 GetMotionFrame(KGDictInt*, KGClipItemType, WhenRec*, double, BufferInfoRec*, KGCanvasRec*, KGRect*, renderStackInfo*, unsigned char*) + 8556
15 com.apple.FinalCutPro 0x00260d78 GetBlurFrame(KGDictInt*, KGClipItemType, WhenRec*, double, BufferInfoRec*, KGCanvasRec*, KGRect*, renderStackInfo*, unsigned char*) + 1228
16 com.apple.FinalCutPro 0x00262428 GetTrackItemFrame(KGDictInt*, TrackInfoRec*, BufferInfoRec*, KGCanvasRec*, KGRect*, renderStackInfo*) + 5124
17 com.apple.FinalCutPro 0x00263a6c CompositeLoop(KGDictInt*, WhenRec*, KGCanvasRec*, KGRect*, BufferInfoRec*, renderStackInfo*, unsigned char*, TrackItemAtTimeCache*) + 876
18 com.apple.FinalCutPro 0x002662fc pKGGetClipVideoWithAlpha(double, long, KGCanvasRec*, KGRect*, long, KGDictInt*, AlphaType*, unsigned long long) + 3536
19 com.apple.FinalCutPro 0x00266958 pKGGetClipVideo(double, long, KGCanvasRec*, KGRect*, long, KGDictInt*, unsigned long long) + 64
20 ...alCutPro.Plugins.QTM Reader 0x06b102fc CompressClip(KGDictInt*, KGFileRec*, unsigned char, KGDictInt*, long, double, double, long, KGDictInt*, char*, double, unsigned char, KGCanvasRec*, unsigned long long, unsigned long, KGCanvasRec*, KGRect*, KGDictInt**, CompressClipFlags, LongGopConformParameters const*) + 9980
21 ...alCutPro.Plugins.QTM Reader 0x06b1226c CompressToQT(KGDictInt*) + 3072
22 ...alCutPro.Plugins.QTM Reader 0x06b2b00c PluginMainEntry(long, long, KGDictInt*, void*) + 5072
23 com.apple.FinalCutPro 0x0024e780 ExportClipCore(KGDictInt*, long, KGDictInt*, KGDictInt*, KGFileSpec*, long) + 2924
24 com.apple.FinalCutPro 0x0024ee54 pKGExportClip(KGDictInt*, long) + 864
25 com.apple.FinalCutPro 0x001c106c pKGMenuPerformExport(KGDictInt*, long) + 144
26 com.apple.FinalCutPro 0x000b7080 pKGClipHandleDefaultMenu(KGDictInt*, long, unsigned char) + 892
27 com.apple.FinalCutPro 0x001ee468 pKGClipDefaultMessage(long, long, KGDictInt*, KGDictInt*, long) + 980
28 ...Pro.Plugins.Timeline Editor 0x06bd6a48 TimelineViewMessage(long, long, KGDictInt*, KGViewRecord*) + 9188
29 com.apple.FinalCutPro 0x002cb08c pKGPanelMessage(long, long, KGDictInt*, KGViewRecord*) + 6792
30 com.apple.FinalCutPro 0x0026dce8 ServicesPanelsMessageProc(long, long, KGDictInt*, KGPanelRecord*) + 3096
31 com.apple.FinalCutPro 0x0026e718 TimelineMessageProc(long, long, KGDictInt*, KGPanelRecord*) + 104
32 com.apple.FinalCutPro 0x002c7ff4 pKGPanelWindowProc(long, long, KGDictInt*, void*) + 104
33 com.apple.FinalCutPro 0x002d9688 pKGSendWindowMessage(KGWindowRec*, long, long, KGDictInt*) + 172
34 com.apple.FinalCutPro 0x0015f830 HandleMenuCommand(long, unsigned char, unsigned char, unsigned char, KGErrorCode (*)(long, long, KGDictInt*, void*), void*) + 440
35 com.apple.FinalCutPro 0x0015f9a0 HandleCommand(long, unsigned char, unsigned char, unsigned char) + 240
36 com.apple.FinalCutPro 0x003f5ff8 CommandProcess(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 344
37 com.apple.HIToolbox 0x9329b934 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 692
38 com.apple.HIToolbox 0x9329b08c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
39 com.apple.HIToolbox 0x932a1e90 SendEventToEventTarget + 40
40 com.apple.HIToolbox 0x9331a7e8 SendHICommandEvent(unsigned long, HICommand const*, unsigned long, unsigned long, unsigned char, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 380
41 com.apple.HIToolbox 0x9334a6a0 SendMenuItemSelectedEvent + 136
42 com.apple.HIToolbox 0x9334a5a8 FinishMenuSelection(MenuData*, MenuData*, MenuResult*, MenuResult*, unsigned long, unsigned long, unsigned long, unsigned char) + 144
43 com.apple.HIToolbox 0x93331a54 MenuSelectCore(MenuData*, Point, double, unsigned long, OpaqueMenuRef**, unsigned short*) + 404
44 com.apple.HIToolbox 0x9333153c MenuSelect + 100
45 com.apple.HIToolbox 0x9332d7b0 HandleMouseEvent(OpaqueEventRef*) + 84
46 com.apple.HIToolbox 0x933314c4 StandardMenuBarEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 56
47 com.apple.HIToolbox 0x9329b934 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 692
48 com.apple.HIToolbox 0x9329b08c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
49 com.apple.HIToolbox 0x932a1e90 SendEventToEventTarget + 40
50 com.apple.HIToolbox 0x934913fc HandleMouseEvent(OpaqueEventRef*) + 388
51 com.apple.HIToolbox 0x932a21fc ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 496
52 com.apple.HIToolbox 0x9329bb84 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1284
53 com.apple.HIToolbox 0x9329b08c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
54 com.apple.HIToolbox 0x932a1e90 SendEventToEventTarget + 40
55 com.apple.HIToolbox 0x932e2c04 ToolboxEventDispatcher + 92
56 com.apple.HIToolbox 0x932e2b90 HLTBEventDispatcher + 16
57 com.apple.HIToolbox 0x932e1148 RunApplicationEventLoop + 148
58 com.apple.FinalCutPro 0x00167598 KGMainEvent(void*) + 64
59 com.apple.FinalCutPro 0x002dde40 main + 100
60 com.apple.FinalCutPro 0x0000d83c _start + 392
61 dyld 0x8fe01048 dyldstart + 60
Thread 1:
0 libSystem.B.dylib 0x9000b348 machmsgtrap + 8
1 libSystem.B.dylib 0x9000b29c mach_msg + 60
2 com.unsanity.ape 0xc0001b54 _apeagent + 296
3 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 2:
0 libSystem.B.dylib 0x9002c3c8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x90030eac pthreadcondwait + 480
2 com.apple.FinalCutPro 0x0041626c Synchronizable::Wait() + 60
3 com.apple.FinalCutPro 0x00406fe0 DisplayQueue::Run() + 744
4 com.apple.FinalCutPro 0x0043e460 Thread::RunHelper(void*) + 32
5 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 3:
0 libSystem.B.dylib 0x9002c3c8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x90030eac pthreadcondwait + 480
2 com.apple.FinalCutPro 0x0041626c Synchronizable::Wait() + 60
3 com.apple.FinalCutPro 0x004b75f8 WorkUnitPerformer::Run() + 84
4 com.apple.FinalCutPro 0x0043e460 Thread::RunHelper(void*) + 32
5 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 4:
0 libSystem.B.dylib 0x9000b348 machmsgtrap + 8
1 libSystem.B.dylib 0x9000b29c mach_msg + 60
2 com.apple.CoreFoundation 0x907de9b8 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x907de2bc CFRunLoopRunSpecific + 268
4 com.apple.CoreFoundation 0x907ed71c CFRunLoopRun + 52
5 com.apple.DVCPROHDMuxer 0x09e4e1ac AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*) + 404
6 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 5:
0 libSystem.B.dylib 0x9000b348 machmsgtrap + 8
1 libSystem.B.dylib 0x9000b29c mach_msg + 60
2 com.apple.CoreFoundation 0x907de9b8 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x907de2bc CFRunLoopRunSpecific + 268
4 com.apple.audio.CoreAudio 0x91459524 HALRunLoop::OwnThread(void*) + 264
5 com.apple.audio.CoreAudio 0x914592c4 CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 6:
0 libSystem.B.dylib 0x9000b348 machmsgtrap + 8
1 libSystem.B.dylib 0x9000b29c mach_msg + 60
2 com.apple.CoreFoundation 0x907de9b8 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x907de2bc CFRunLoopRunSpecific + 268
4 com.apple.CoreFoundation 0x907ed71c CFRunLoopRun + 52
5 com.apple.AVCVideoServices 0x00c6bd94 AVS::AVCVideoServicesThreadStart(AVS::AVCVideoServicesThreadParams*) + 168
6 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 7:
0 libSystem.B.dylib 0x90054388 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90070be8 pthreadcond_timedwait_relativenp + 556
2 ...ple.CoreServices.CarbonCore 0x90bf93f4 TSWaitOnSemaphoreCommon + 176
3 ...ickTimeComponents.component 0x991c2174 ReadSchedulerThreadEntryPoint + 5316
4 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 8:
0 libSystem.B.dylib 0x9002c3c8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x90030eac pthreadcondwait + 480
2 com.apple.vImage 0x91f2e1ac vImageQueue_DequeueJob + 60
3 com.apple.vImage 0x91f2e538 vImageWorkerThreadFunc + 120
4 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 9:
0 libSystem.B.dylib 0x9002f08c kevent + 12
1 com.apple.DesktopServices 0x92af8e50 TFSNotificationTask::FSNotificationTaskProc(void*) + 56
2 ...ple.CoreServices.CarbonCore 0x90bc6794 PrivateMPEntryPoint + 76
3 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 10:
0 libSystem.B.dylib 0x9002c3c8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x90030eac pthreadcondwait + 480
2 ...ple.CoreServices.CarbonCore 0x90bc6984 MPWaitOnQueue + 224
3 com.apple.DesktopServices 0x92af94cc TNodeSyncTask::SyncTaskProc(void*) + 116
4 ...ple.CoreServices.CarbonCore 0x90bc6794 PrivateMPEntryPoint + 76
5 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 11:
0 libSystem.B.dylib 0x90054388 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90070be8 pthreadcond_timedwait_relativenp + 556
2 com.apple.audio.CoreAudio 0x9146a6ac CAGuard::WaitFor(unsigned long long) + 204
3 com.apple.audio.CoreAudio 0x9146a5bc CAGuard::WaitUntil(unsigned long long) + 304
4 com.apple.audio.CoreAudio 0x91468800 HP_IOThread::WorkLoop() + 852
5 com.apple.audio.CoreAudio 0x91468498 HPIOThread::ThreadEntry(HPIOThread*) + 16
6 com.apple.audio.CoreAudio 0x914592c4 CAPThread::Entry(CAPThread*) + 96
7 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 12:
0 libSystem.B.dylib 0x90054388 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90070be8 pthreadcond_timedwait_relativenp + 556
2 ...ple.CoreServices.CarbonCore 0x90bf93f4 TSWaitOnSemaphoreCommon + 176
3 ...ple.CoreServices.CarbonCore 0x90c03e9c AIOFileThread(void*) + 520
4 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 13:
0 libSystem.B.dylib 0x9002c4b8 semaphorewaittrap + 8
1 ...ickTimeComponents.component 0x996d8d94 QTThreadWaitSignal + 100
2 ...ickTimeComponents.component 0x99245b70 audioprepThreadEntry + 96
3 ...ickTimeComponents.component 0x996d8a54 start_thread + 84
4 libSystem.B.dylib 0x9002bd08 pthreadbody + 96
Thread 0 crashed with PPC Thread State 64:
srr0: 0x0000000047ccb968 srr1: 0x100000000200f030 vrsave: 0x00000000ff000000
cr: 0x44822218 xer: 0x0000000020000000 lr: 0x0000000047ccb4f0 ctr: 0x000000000000005a
r0: 0x0000000000000b40 r1: 0x00000000bfffa250 r2: 0x0000000008804000 r3: 0x00000000bfffa390
r4: 0x0000000000000b40 r5: 0x00000000000001e0 r6: 0x0000000000000b40 r7: 0x0000000073a05b80
r8: 0x0000000047cee6e8 r9: 0x0000000047cee710 r10: 0x0000000000005000 r11: 0x0000000000000000
r12: 0x0000000073a05b90 r13: 0x0000000000000005 r14: 0x00000000bfffb350 r15: 0x0000000035fdf69c
r16: 0x0000000000000000 r17: 0x000000003547b674 r18: 0x0000000000000000 r19: 0x00000000bfffb360
r20: 0x00000000bfffbdb0 r21: 0x0000000000000002 r22: 0x0000000000000000 r23: 0x0000000001935b10
r24: 0x0000000000000010 r25: 0x0000000000005010 r26: 0x0000000000005020 r27: 0x0000000043300000
r28: 0x00000000000000b4 r29: 0x0000000000005030 r30: 0xfffffffffffff4c0 r31: 0x0000000000000000
Rather than export the entire two hours, try exporting into segments. This has worked for me in what sounds like the same situation.
For example:
1. In your Timeline window mark an In at the beginning and an Out one frame before the tenth minute (if you're using drop frame time code at a 30 fps base, this would be 1:09:59;29).
2. Chose File > Export > QuickTime Movie; Current Settings, Make movie Self-Contained.
If this works, continue to the next step.
3. In your Timeline window, mark an In at the first frame of the tenth minute and an Out at the frame before the twentieth minute.
4. Chose File > Export > QuickTime Movie; Current Settings, Make movie Self-Contained.
If this works, repeat in ten minute segments until you have enough segments to complete the duration of your Timeline.
You might be able to export in fifteen or twenty minute segments rather than every ten minutes. Or, you might have to try five minute segments.
As you export, name the files such that the order is obvious (like "segment 01", "segment 02", etc.).
Once you have each segment, turn them into either a referencing movie or a self-contained movie (recommended in this case) which can then serve as your edited master. I'd import them into a new project file to do this.
This should work if it's just something going on within FCP. However, there is always the chance that it's a source file that isn't getting in the way with editing but is getting in the way with exporting. With the approach outlined above, you'll be able to isolate where it is in your Timeline if that's the case.
Another thing worth mentioning is that I dealt with this same issue from FCP 4.5, 5 and 6 for a documentary project (www.thehoopinglife.com, if you have time to check it out). Exporting a 90 minute cut always had to be done in segments until upgrading to version FCP 7.
"Current Settings" is the way to go. DV-NTSC will hold up well enough.
Plan B: if your Sequence will play from start to finish in the Timeline (and that's a big "IF"), you could record to a DV deck or camcorder and then recapture that.
-Warren
Similar Messages
-
Final Film output differs from the film in timeline!!!! :
This is frustrating. I am working on a film and when I want to export it when it is finished the final output does not match some parts of the project in the timeline. I look at the film within Final Cut Pro and everything look good. But on some part (the end of the film) when I look at the exported Quicktime movie in the Quictime applicationm the saturation and lightness has changed! The end of the film (just about 4 frames before I start to play around with a few flying cows ( yes it is true) the picture becomes pale and unsaturated for the rest of the film?
I did try the color corrector 3 way on some of the clips.... not all. But that should not have anything to do with it?
Message was edited by: Simen MyrbergetWhen I have tried to export or save final art (finished films) with File -> Export -> Quicktime Movie the results have been far from reliable. Things has been looking good in the timeline when after exporting the film changed a lot at some parts. This was especially often when I did include graphics which were cut out using alpha channels. The end product looked like it was bleached on those parts involving moving graphics with alpha channels.
But after I tried Compressor things changed. This seems to be much more consistent. The best quality for this specific project was with Output for DVD (Best Quality), but then there were no sound...... and this is the ".m2v" format which I am not familiar with.
http://fotofikling.com/ftp/temp/exportqualitydiffersfcp.jpg
I did also try the 10 bit uncompressed, that was ok too, but slightly paler and less saturated than what I worked out in the timeline (what I wanted for end result).
This was an old film I shot 10 years ago on SD format. I am quiet new to FCP, but I surely hope that one could work in a way that enables to get more reliable results.
Any suggestions how to get a better end result in compressor? Something more like the ".m2v" version..... (see the attached link)... -
Final Image Quality in Film, Avid vs. FCP
Hello all,
I'm heading up post-production and editorial for an independent feature film in pre-production. There are some potential producers that are interested in the film, but they're saying that (from their experience) the films they've cut on Avid have turned out to be visually superior than those cut on Final Cut Pro.
Now, I have no specifics as to the exact post-production workflow for either of the films, but I feel as though this statement is incorrect, as it is my assumption that give the same post-production workflows, the image quality would be the exact same.
I, for one (as the editor attached to the project), am for using a Final Cut Pro workflow, specifically because I already have a system set up:
Mac Pro 2.66 GHz Quad
5.0 GBs RAM
Final Cut Pro 5.1.4
Kona LHe
Cal Digit HD444 6 TB RAID
Toshiba 26" HD Client Monitor
1402 Mackie Mixer
DSR-1500 DVCAM Deck via SDI and 422 machine control
Personally, I have no issue with editing on either system, as I am well versed in both Avid and Final Cut Pro. However, this is an independent feature, and saving money is key. So why cut on Avid and have to rent a bay when we could cut on mine for free?
As far as finishing is concerned, we're planning on cutting back to the original negative (using Cinema Tools as our aide).
Can anyone give me a possible reason for why cutting a feature-length on film in Final Cut Pro would not look as good if it were cut on Avid, assuming the post workflow is the EXACT same?
Thanks!
Mac Pro Quad 2.66 GHz / 5.0 Gigs RAM / GeForce 7300 GT / 2.0 TBs internal SATA Mac OS X (10.4.9)Specifically, the producer in question noted that in
the past, when using FCP to cut a feature, they had
issues in the sound mix.
In my experience, I've never encountered a sound
mixer that's had a problem with an OMF export from a
FCP sequence when they create their ProTools
session.
Additionally, they pointed out that only Avid offline
projects would translate to a Da Vinci DI suite, and
FCP wouldn't work as well. Is there any truth to
this? I find this hard to believe...
It sounds as if your Producers don't truly understand the details of a post-production workflow for a professional film. They either only know the brands that they paid for, or they tried to unrealistically accomplish too much with too little resources and facilities on prior films, and hung their hats on the lesser of two evils. If the sound was edited, mixed, and somehow mastered on AVID or Final Cut only...without going into sound design/final mix/mastering in their respective stages and facilities...either one has an equal chance of sounding crappy...and that's a good chance. As long as the editor knows what he/she is doing and how to prepare their work for the next steps, a final mix/design can be just as good coming from a film edited on FCP as from AVID.
FCP offlines can translate just fine for AVID online/correction and what have you as long as this is planned for, researched, and understood from the outset. Basic things like knowing not to repeat frames if you're going back to film negative unless someone's willing to pay for the interpositives/dupes and such...apply if you're preparing for onlining. Same goes for sound and knowing that the final mix is where things will really take shape. the post supervisor needs to make sure that the editor and online/color correction facility (if different) are in perfect communication with eachother, and that the editor will know how to prepare and export their project to be compatable with the Davinci or whatever. The people who perform this work should generally be very open to your questions and attention, because it makes their job easier and more accurate when they're getting things well-prepared, rather than having to redo things that should be in place already. I've prepared simple EDL's which have worked fine for onlining and correction...but I made sure, step by step, that I was delivering what they needed, rather than just making it and shipping it out, and I was there with them for the whole process in case something was missing or confusing. Went without a hitch.
For sound design, I only do a basic edit during picture edit for sync work and music selection/editing/matching, or a rought mix that will approximate the final results, but I won't use that for the actual design except for perhaps a scratch reference. The rest...EFX, ambiences, foley, etc. is done in Pro Tools, and I can simply bring the project in to a mix house and open it on their system.
I guess you could hypothesize that there's a smaller, younger, and less-experienced pool of talent using primarily FCP than those using AVID, since AVID's been around longer and is still the "standard''. And a well-established, fully AVID-based in-the-can to on-the-screen facility will be more capable than a single FCP suite. But that's not FCP's fault. As long as we know the steps that have to be taken, FCP is fully capable of performing perfectly in its step on the ladder, and moving the project to the next.
So again, it seems like the producers are inaccurately attributing their disappointments to machines, instead of workflow and compatability that can and should be controlled by people who understand it. It's ususally the Post Supervisor's job to make sure of that. Of course, not every production will have the right budget for this, but the producers need to understand where the money for post goes and what things (along with the people, of course) need to be paid for in order to get the quality deserving of a professional feature film. That's the producer's job...at least one them. -
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 -
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. -
Master Templates is crashing FCP 7, In Maverick
I just updated my iMac from Lion to Maveric. I was very disapointed that all the Master Templates HD are crashing FCP 7. Its amazing that Apple did not fix this issue with FCP7 upgrade. To get FCP X is out of the question.
Is there a solution thanks.Have you tried trashing your FCP Preferences? This is a common first step when you get unexpected performance from Final Cut Studio components.
You can download Preference Manager from Digital Rebellion (free) and it will do it for you:
http://www.digitalrebellion.com/prefman/
Your preferences will be reset to default settings the nest time you launch the applications.
MtD -
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. -
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,
TomThough 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. -
I was editing last night saved the project and now it crashes FCP on launch on all our editor, and it's autosaves do the same thing. Other projects open fine. I have tried taking the media offline, restarting etc.
Ok,
Here is the log
Date/Time: 2006-12-15 16:26:35.558 -0700
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Final Cut Pro
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Parent: WindowServer [60]
Version: 5.1.2 (5.1.2)
Build Version: 3
Project Name: FCPApp
Source Version: 609211640
PID: 606
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000001
Thread 0 Crashed:
0 libSystem.B.dylib 0x9000ff50 __sfvwrite + 752
1 com.apple.FinalCutPro 0x0047fbf8 SegmentStartEnd(KGDictInt**, long, long, double*, double*) + 172
2 com.apple.FinalCutPro 0x00469728 GetNextClipInfo(PlayerSegmenter*, trackInfo*, double) + 232
3 com.apple.FinalCutPro 0x00469be4 InitTracks(PlayerSegmenter*, KGListRecord*, long, unsigned char, KGDictInt*, trackInfo**, long*) + 428
Model: PowerMac7,3, BootROM 5.1.8f7, 2 processors, PowerPC G5 (3.0), 2.5 GHz, 2.5 GB
Graphics: ATI Radeon 9600 XT, ATY,RV360, AGP, 128 MB
Memory Module: DIMM0/J11, 256 MB, DDR SDRAM, PC3200U-30330
Memory Module: DIMM1/J12, 256 MB, DDR SDRAM, PC3200U-30330
Memory Module: DIMM2/J13, 1 GB, DDR SDRAM, PC3200U-30330
Memory Module: DIMM3/J14, 1 GB, DDR SDRAM, PC3200U-30330
Modem: Jump, , V.92, Version 1.0,
Network Service: Built-in Ethernet, Ethernet, en0
PCI Card: firewire, ieee1394, SLOT-3
PCI Card: ATTO ExpressPCI UL4D, scsi-2, SLOT-4
PCI Card: ATTO ExpressPCI UL4D, scsi-2, SLOT-4
Serial ATA Device: ST3160023AS, 149.05 GB
Parallel ATA Device: SONY DVD RW DW-U21A,
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: Sentinel SuperPro 6.3.0, Rainbow Technologies Inc., Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Optical USB Mouse, Logitech, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
USB Device: Keyspan USA-28Xb, Keyspan, a division of InnoSys Inc., Up to 12 Mb/sec, 500 mA
FireWire Device: LaCie Big Disk Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
FireWire Device: LaCie Big Disk Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
FireWire Device: LaCie FW800 Bigger Disk drive LUN 0, LaCie Group SA, Up to 800 Mb/sec
FireWire Device: LaCie Big Disk Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
FireWire Device: LaCie Big Disk Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
FireWire Device: LaCie d2 Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
FireWire Device: LaCie Big Disk Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
FireWire Device: AJ-SD93, Panasonic, Up to 800 Mb/sec -
Boris Red 3.05 Transition Crashes FCP 5.12
I never had problems with Boris FX, but after upgrading FCP to 5.12 nothing shows in the browser. I reinstalled Boris Red and Applied the patches from Boris site, it works when I applied the filter, but when I apply transition and double click on it than it crashes.
I called Boris Support for weeks, and finally they have sent me an email that made no improvement what so ever.
Does anyone know the solution?
Thanks,I recently crossgraded from FCP5.0.4 to 5.1.2 on my Quad core G5 and my 17 G4 powerbook. Botis Title 3D completely crashes FCP on the G5 when attemting to create text. It works fine, though, on the G4 (???) I have trashed prefs, repaired permissions, reinstalled Boris only, reinstalled FCP. Apple tech support doesn't care! The Boris tech guy got so flustered with me he dropped his little headset on the floor. I have researched every applicable forum on the net and see that I am not alone. Notice that the first post in this thread is from early November. It is now almost February. No real solution. I love the "sibling" style behavior between the host app. co. (Apple) and the 3rd party co. (Boris) ..."It's not MY fault its HIS!!" "Is NOT" "Is TOO!"
I guess my problem is that I just need to pony up that $700.00 for Apple's "Pro applications technical support"
...maybe I should have purchased Edius Broadcast...
G4 17" Powerbook Mac OS X (10.4.6) -
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 SDRAMI'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. -
I am using only one Apple ID. The problem, since iOS 6, is the App Store purchased items screen just shows loading screen it finally crashes or gives the error message 'can not connect to Apple store'
I am using only one Apple ID. The problem, since iOS 6, is the App Store purchased items screen just shows loading screen it finally crashes or gives the error message 'can not connect to Apple store'
-
I have been creating a film on Final Cut Express and half of my film has disappeared! What can I do to retrieve it?! Furthermore, command Z doesn't appear to be working! Any help would be much appreciated!
Check the capture/scratch disc to make sure the media is still there. If it isn't your hard drive may be going bad. If it is, then you may have inadvertently cut part of the video from the Timeline or deleted it from the Browser.
As for the Command z issue, see how many levels of undo you have set in FCE preferences. Also keep in mind that Command z will not work if you close the project and reopen it.
-DH -
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 -
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
Maybe you are looking for
-
*** Using HTTP port 7101 *** *** Using SSL port 7102 *** C:\Users\Administrator\AppData\Roaming\JDeveloper\system11.1.2.4.39.64.36.1\DefaultDomain\bin\startWebLogic.cmd [waiting for the server to complete its initialization...] JAVA Memory arguments:
-
OfficeJet 7000 Wide Format - network install problem
Hello to all. I get a call to install this printer in a small network of three computers. All of them are Windows XP 32bit. Install process is fine till one point. Printer is recognized on the network. Address is given by DHCP server on ADSL router.
-
Using a FAT32-formatted drive as backup disk with Time Machine
For strange and perverse reasons of my own, I'd like to use a FAT32-formatted external hard drive with Time Machine. Is this possible?
-
AirPlay is available on iMac & iPhone 5, but not on iPhone 5S or 6
I have a Time Capsule, and 2 AirPort Express units, 1 of which is in my kitchen hooked up to a standard set of laptop speakers. Usually I stream music or radio through the kitchen Express via AirPlay, and have never had an issue until today. I tried
-
SQL*PLUS: Setting a concrete RETURN CODE
I don't know how to force a concrete EXIT CODE for in a SQL*PLUS process. I use "WHENEVER SQLerror EXIT SQL.SQLCODE" and a "EXIT SQL.SQLCODE;" at the end of the process. But I need to be able to exit the process with a sqlcode "54" or "23" or whateve