Final Cut Pro X & ProRes Major but Funny BUG

This must be the weirdest BUG I have ever experienced... And the most difficult to find. I found it via coincidence ;-)
I playback and use ProRes 4444 inside of FCPx. And generally there is NO problem doing so. Until yesterday...
In After Effects I converted a bunch of H.264 Canon 5DMKii movies, after denoising them, to ProRes4444.
I imported the movies into Final Cut X and immediately noticed that they were jerky in playback. So I loaded the original files and wanted to see whether they were jerky as well. They were not... Here comes the funny part...
The Original H.264 had AUDIO on them the ProRes version I had stripped the audio from as I did not need it. To better compare the two files (Don't know why I did it but I did) in the timeline I just copied the audio from H.264 file over underneath the ProRes4444-jerky file. Then I compared again. This time the ProRes was playing smooth as silk. I could NOT believe my eyes. I was cursing at the Mac but after smoking a cigarette and contemplating, I went back an deleted the audio from underneath the Prores 4444 file. Back to jerky. I put the audio back - jerkiness GONE...
So I did some more testing...
I took a completely different clip and imported that into After Effects.
I did the same denoising to it and exported TWO versions to PRORES 4444.
1 with Audio and 1 without it...
Then imported the two into FCPx...
We are talking TWO identical files here expect one has audio to it.
The one with audio played back silky while the one without was jerky.
I copied the audio (any audio will do) underneath the jerky one and it stopped jerking around.
I opened the two test files in QuickTime 7 and 10 and NONE of them were Jerky... This issue seems to pertain to FCPx only....
So if any of you export from AE to ProRes4444 and the guy on the FCPx station gets agitated because of the jerkiness,
before you blame adobe (like I did) tell him to just copy some sound underneath the sound-less video clip. That will take care of the problem,
untill Apple fixes the problem ;-)

Glad you found a solution, AtonMusic! Did you bring the issue up to Apple?

Similar Messages

Final Cut Pro X & ProRes Major Funny BUG - Pertains to AE also !!!

This must be the weirdest BUG I have ever experienced... And the most difficult to find. I found it via coincidence ;-)
I playback and use ProRes 4444 inside of FCPx. And generally there is NO problem doing so. Until yesterday...
In After Effects I converted a bunch of H.264 Canon 5DMKii movies, after denoising them, to ProRes4444.
I imported the movies into Final Cut X and immediately noticed that they were jerky in playback. So I loaded the original files and wanted to see whether they were jerky as well. They were not... Here comes the funny part...
The Original H.264 had AUDIO on them the ProRes version I had stripped the audio from as I did not need it. To better compare the two files (Don't know why I did it but I did) in the timeline I just copied the audio from H.264 file over underneath the ProRes4444-jerky file. Then I compared again. This time the ProRes was playing smooth as silk. I could NOT believe my eyes. I was cursing at the Mac but after smoking a cigarette and contemplating, I went back an deleted the audio from underneath the Prores 4444 file. Back to jerky. I put the audio back - jerkiness GONE...
So I did some more testing...
I took a completely different clip and imported that into After Effects.
I did the same denoising to it and exported TWO versions to PRORES 4444.
1 with Audio and 1 without it...
Then imported the two into FCPx...
We are talking TWO identical files here expect one has audio to it.
The one with audio played back silky while the one without was jerky.
I copied the audio (any audio will do) underneath the jerky one and it stopped jerking around.
I opened the two test files in QuickTime 7 and 10 and NONE of them were Jerky... This issue seems to pertain to FCPx only....
So if any of you export from AE to ProRes4444 and the guy on the FCPx station gets agitated because of the jerkiness,
before you blame adobe (like I did) tell him to just copy some sound underneath the sound-less video clip. That will take care of the problem,
untill Apple fixes the problem ;-)

Glad you found a solution, AtonMusic! Did you bring the issue up to Apple?

Final cut pro 10 forced quit but last edited version not their

how do i recover my last version of editing in final cut pro? wdorked on it 6 hours and then crash ad it didnt. save ?

So restoring from a back up works quite differently in 10.0.9 than in 10.1.
You go to your project folder and open Backups to reveal the Time-stamped BU file. Hide the CurrentVersion. fcpproject file and promote the BU file to the same folder hierarchy level prviously occupied by Current Version. Rename the BU file Currentversion.fcpproject. Open FCP X.
Russ

Final cut pro x is open, but cannot see browser, timeline or canvas?

Basically, when I open final cut it acts as if it is opening and then nothing happens. However it is definately open as I can click on the toolbar to do stuff like 'new project' under file etc but when I do, nothing happens again. It's almost like it's working, but everything is invisible. I've seen stuff that only talk about the timeline or canvas being closed, however the solution to these is fixed through going to the browser, which in my case is also missing. I do not have it under another desktop and I've tried deleteing the system preferences etc. I feel like it's something really stupid that I'm not picking up on. Can someone please help?

Im having the same problem and this is what it looks like. I can see the tool bar at top but thats about it.

My Final Cut Pro program starts fine but it closes and says Final Cut closed unexpectedly. Can someone help?

When I try to move anything or edit inside of the program it simply shuts down. I have no idea why or how to fix it.

For a start try trashing the preferences.
Many weird things happen as a result of corrupt preferences which can create a vast range of different symptoms, so whenever FCP X stops working properly in any way, trashing the preferences should be the first thing you do using this free app.
http://www.digitalrebellion.com/prefman/
Shut down FCP X, open PreferenceManager and in the window that appears:-
1. Ensure that only FCP X is selected.
2. Click Trash
The job is done instantly and you can re-open FCP X.
There is absolutely no danger in trashing preferences and you can do it as often as you like.
The preferences are kept separately from FCP X and if there aren't any when FCP X opens it automatically creates new ones . . . instantly.

Final Cut Pro 5 Won't Open

Hi i am having a major problem!
well for starters i must say that a few months ago my macbook crashed and i called apple care and my computer was repaired over the phone(a folder was corrupted)
I was told that my applications were saved and shall run like normal but that was not the case..
I had to re install my internet browser and recently i figured my Final cut pro would work fine but when i went to open it it failed to open! it said a error occurred and asked if i would like to report to apple and i did several times..
Then i decided to look up the problem in online forums and i deleted final cut and re installed it and even deleted old preferences (was suggested in forums ) but when i go to open it it dosen't load ... It crashes
i'm really upset and frustrated and i hope i can be helped because my efforts have gave me no sucess!
please do help me soon!
here below is my error crash report
if that helps
thanks
Process: Final Cut Pro [160]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCutPro
Version: 5.0.1 (5.0.1)
Build Info: FCPApp-504271547~7
Code Type: PPC (Translated)
Parent Process: launchd [64]
Interval Since Last Report: 1152 sec
Crashes Since Last Report: 2
Per-App Interval Since Last Report: 72 sec
Per-App Crashes Since Last Report: 2
Date/Time: 2009-11-17 18:40:46.895 -0500
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: C7CDDB0E-9E9E-4668-84B6-C22A7BA1F69E
Exception Type: EXCBADACCESS (SIGSEGV)
Exception Codes: KERNINVALIDADDRESS at 0x0000000055dde9e4
Crashed Thread: 0
Thread 0 Crashed:
0 translate 0xb80cc909 0xb8000000 + 837897
1 translate 0xb80b7007 0xb8000000 + 749575
2 translate 0xb80d49c0 0xb8000000 + 870848
3 translate 0xb813ce79 spinlockwrapper + 1981
4 translate 0xb8011b64 0xb8000000 + 72548
Thread 1:
0 ??? 0x800bc286 0 + 2148254342
1 ??? 0x800c3a7c 0 + 2148285052
2 translate 0xb818b6ea CallPPCFunctionAtAddressInt + 202886
3 ??? 0x800ed155 0 + 2148454741
4 ??? 0x800ed012 0 + 2148454418
Thread 2:
0 translate 0xb8152be5 spinlockwrapper + 91433
1 translate 0xb8162cb9 CallPPCFunctionAtAddressInt + 36437
2 translate 0xb80bdb8b 0xb8000000 + 777099
3 translate 0xb80b7007 0xb8000000 + 749575
4 translate 0xb80d49c0 0xb8000000 + 870848
5 translate 0xb813d75f spinlockwrapper + 4259
6 translate 0xb8011b64 0xb8000000 + 72548
Thread 3:
0 translate 0xb815282c spinlockwrapper + 90480
1 translate 0xb816e6a1 CallPPCFunctionAtAddressInt + 84029
2 translate 0xb80bdb8b 0xb8000000 + 777099
3 translate 0xb80b7007 0xb8000000 + 749575
4 translate 0xb80d49c0 0xb8000000 + 870848
5 translate 0xb813d75f spinlockwrapper + 4259
6 translate 0xb8011b64 0xb8000000 + 72548
Thread 4:
0 translate 0xb815282c spinlockwrapper + 90480
1 translate 0xb816e6a1 CallPPCFunctionAtAddressInt + 84029
2 translate 0xb80bdb8b 0xb8000000 + 777099
3 translate 0xb80b7007 0xb8000000 + 749575
4 translate 0xb80d49c0 0xb8000000 + 870848
5 translate 0xb813d75f spinlockwrapper + 4259
6 translate 0xb8011b64 0xb8000000 + 72548
Thread 5:
0 translate 0xb81529ef spinlockwrapper + 90931
1 translate 0xb8183633 CallPPCFunctionAtAddressInt + 169935
2 translate 0xb81861e2 CallPPCFunctionAtAddressInt + 181118
3 translate 0xb80dfb0b 0xb8000000 + 916235
4 ??? 0x812f1c96 0 + 2167348374
Thread 6:
0 translate 0xb81529ef spinlockwrapper + 90931
1 translate 0xb8183633 CallPPCFunctionAtAddressInt + 169935
2 translate 0xb81861e2 CallPPCFunctionAtAddressInt + 181118
3 translate 0xb80dfb0b 0xb8000000 + 916235
4 ??? 0x812f1c96 0 + 2167348374
Thread 7:
0 translate 0xb815289e spinlockwrapper + 90594
1 translate 0xb816e8a7 CallPPCFunctionAtAddressInt + 84547
2 translate 0xb80bdb8b 0xb8000000 + 777099
3 translate 0xb80b7007 0xb8000000 + 749575
4 translate 0xb80d49c0 0xb8000000 + 870848
5 translate 0xb813d75f spinlockwrapper + 4259
6 translate 0xb8011b64 0xb8000000 + 72548
Thread 8:
0 translate 0xb815289e spinlockwrapper + 90594
1 translate 0xb816e8a7 CallPPCFunctionAtAddressInt + 84547
2 translate 0xb80bdb8b 0xb8000000 + 777099
3 translate 0xb80b7007 0xb8000000 + 749575
4 translate 0xb80d49c0 0xb8000000 + 870848
5 translate 0xb813d75f spinlockwrapper + 4259
6 translate 0xb8011b64 0xb8000000 + 72548
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x55dde9e4 ebx: 0xb80b6c78 ecx: 0x7798697a edx: 0x00000004
edi: 0xb8208980 esi: 0x55dde9e0 ebp: 0xb7fffa08 esp: 0xb7fffa04
ss: 0x0000001f efl: 0x00010206 eip: 0xb80cc909 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x55dde9e4
Binary Images:
0xb8000000 - 0xb81d7fe7 translate ??? (???) /usr/libexec/oah/translate
Translated Code Information:
Rosetta Version: 21.03
Args: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro -psn0122910
Exception: EXCBADACCESS (0x0001)
Thread 0: (0xb022083c, 0xb81529ef)
0x00000002: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : + 2
0x90c03398: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopRunSpecific + 1816
0x90f27fac: /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio : HALRunLoop::OwnThread(void*) + 216
0x90f27de8: /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio : CAPThread::Entry(CAPThread*) + 108
0x94baa1d4: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
0x00000000: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x94b20120 ctr: 0x94b191f0
r00: 0xffffffe1 r01: 0xf0192550 r02: 0xa01d2c88 r03: 0xf0192930
r04: 0x03000006 r05: 0x00000000 r06: 0x00000450 r07: 0x0000a603
r08: 0x00000000 r09: 0x00000000 r10: 0x00000004 r11: 0xa077068c
r12: 0x94b191f0 r13: 0x00000000 r14: 0xa01c0478 r15: 0x7fffffff
r16: 0xffffffff r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0xf0192930 r23: 0x00000000
r24: 0xf0192930 r25: 0x00000450 r26: 0x0000a603 r27: 0x00000000
r28: 0x00000000 r29: 0x03000006 r30: 0x03000006 r31: 0x90c02c88
Thread 1: (0xb019ed68, 0xb815282c)
0x94b5c32c: /usr/lib/libSystem.B.dylib : _pthread_condwait + 1260
0x00411b5c: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : Synchronizable::Wait() + 60
0x004b14f0: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : WorkUnitPerformer::Run() + 84
0x00438d9c: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : Thread::RunHelper(void*) + 32
0x94baa1d4: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
0x00000000: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x94b5c37c ctr: 0x94b19250
r00: 0xffffffdb r01: 0xf0111cf0 r02: 0xa076b53c r03: 0x00006103
r04: 0x00005f03 r05: 0x00000000 r06: 0x00000000 r07: 0x00000000
r08: 0x0000006a r09: 0x00000001 r10: 0x00000066 r11: 0xa0770a84
r12: 0x94b19250 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0x00000000 r27: 0xa076be54
r28: 0x096d25e8 r29: 0xa076b53c r30: 0x096d261c r31: 0x94b5be54
Thread 2: (0xb009abbc, 0xb8152be5)
0x90c0e7a4: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFSocketManager + 664
0x94baa1d4: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
0x00000000: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x90c0e80c ctr: 0x94b7cd68
r00: 0x0000005d r01: 0xf000fca0 r02: 0x00000000 r03: 0x00000020
r04: 0x03c83980 r05: 0x03c866d0 r06: 0x00000000 r07: 0x00000000
r08: 0x00000000 r09: 0x00000000 r10: 0x90c0aa7c r11: 0xa01c12d4
r12: 0x94b7cd68 r13: 0xa01ce514 r14: 0xa01ce514 r15: 0xa01ce514
r16: 0xa01d5a44 r17: 0xa01ce514 r18: 0x00000001 r19: 0x00000000
r20: 0x03c866d0 r21: 0x03c83960 r22: 0x00000000 r23: 0x00000000
r24: 0x03c83980 r25: 0x03c857a0 r26: 0x00000001 r27: 0x00000020
r28: 0x00000004 r29: 0x03c81fe0 r30: 0x00000000 r31: 0x90c0e514
Thread 3: (0xb02a283c, 0xb81529ef)
0x00000000: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : + 0
0x90c03398: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopRunSpecific + 1816
0x90c03c20: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopRun + 64
0x00e81d94: @executable_path/../Frameworks/AVCVideoServices.framework/Versions/A/AVCVideoSe rvices : AVS::AVCVideoServicesThreadStart(AVS::AVCVideoServicesThreadParams*) + 168
0x94baa1d4: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x94b20120 ctr: 0x94b191f0
r00: 0xffffffe1 r01: 0xf0213550 r02: 0xa01d2c88 r03: 0xf0213930
r04: 0x03000006 r05: 0x00000000 r06: 0x00000450 r07: 0x0000ac03
r08: 0x00000000 r09: 0x00000000 r10: 0x00000008 r11: 0xa077068c
r12: 0x94b191f0 r13: 0x00000000 r14: 0xa01c0478 r15: 0x7fffffff
r16: 0xffffffff r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0xf0213930 r23: 0x00000000
r24: 0xf0213930 r25: 0x00000450 r26: 0x0000ac03 r27: 0x00000000
r28: 0x00000000 r29: 0x03000006 r30: 0x03000006 r31: 0x90c02c88
Thread 4: (0xb03a6d60, 0xb815289e)
0x94b5c32c: /usr/lib/libSystem.B.dylib : _pthread_condwait + 1260
0x92d119e8: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _TSWaitOnConditionTimedRelative + 244
0x92d117bc: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _TSWaitOnSemaphoreCommon + 432
0x92d3ac88: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : AIOFileThread(void*) + 1072
0x94baa1d4: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
0x00000000: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x94b5c36c ctr: 0x94b19270
r00: 0xffffffd9 r01: 0xf0315c90 r02: 0xa076b53c r03: 0x00006303
r04: 0x00006503 r05: 0x0000003c r06: 0x00000000 r07: 0x00000000
r08: 0x09bfc080 r09: 0x00000001 r10: 0xf0315e48 r11: 0xa0770a74
r12: 0x94b19270 r13: 0x00000000 r14: 0x00000000 r15: 0xa04aa864
r16: 0xa04aa864 r17: 0x00000000 r18: 0xa04aa864 r19: 0xa04a78a8
r20: 0xa04aa864 r21: 0x92df1614 r22: 0x92df1614 r23: 0x00000000
r24: 0x00000000 r25: 0x00000001 r26: 0xf0315e48 r27: 0xa076be54
r28: 0xa04a78dc r29: 0xa076b53c r30: 0xa04a7910 r31: 0x94b5be54
Thread 5: (0xb0324d60, 0xb815289e)
0x94b5c32c: /usr/lib/libSystem.B.dylib : _pthread_condwait + 1260
0x92d119e8: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _TSWaitOnConditionTimedRelative + 244
0x92d117bc: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _TSWaitOnSemaphoreCommon + 432
0x91527354: /System/Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTim eComponents : _ReadSchedulerThreadEntryPoint + 5316
0x94baa1d4: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
0x00000000: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x94b5c36c ctr: 0x94b19270
r00: 0xffffffd9 r01: 0xf0294c60 r02: 0xa076b53c r03: 0x00006203
r04: 0x00006603 r05: 0x47868c00 r06: 0x00000000 r07: 0x00000000
r08: 0x626d2220 r09: 0x00000001 r10: 0x00000000 r11: 0xa0770a74
r12: 0x94b19270 r13: 0x91525ea8 r14: 0x91525ea8 r15: 0x91bf5ea8
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x09b3e0ec
r20: 0xa0325ea8 r21: 0x92df1614 r22: 0x92df1614 r23: 0x00000000
r24: 0x00000000 r25: 0x00000001 r26: 0xf0294e58 r27: 0xa076be54
r28: 0x09b3e060 r29: 0xa076b53c r30: 0x09b3e094 r31: 0x94b5be54
Thread 6: Crashed (0xb7fffa04, 0xb80cc909)
0x94b23244: /usr/lib/libSystem.B.dylib : small_free_list_removeptr + 100
0x94b1f6a0: /usr/lib/libSystem.B.dylib : szonefree + 2416
0x92d05fe0: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _DisposePtr + 52
0x7ae81cf8: @executable_path/../Frameworks/KGCore.framework/Versions/A/KGCore : DisposePlatformPtr(char*) + 16
0x7ae82ee0: @executable_path/../Frameworks/KGCore.framework/Versions/A/KGCore : InternalReleasePtr(void*, KGPtrHeader*) + 140
0x7ae83000: @executable_path/../Frameworks/KGCore.framework/Versions/A/KGCore : _KGMemoryPtrRelease + 100
0x00136c58: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : FreeRefs(KGListRecord*) + 120
0x00136cd4: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : FreeRefTable(void*) + 76
0x7ae82e9c: @executable_path/../Frameworks/KGCore.framework/Versions/A/KGCore : InternalReleasePtr(void*, KGPtrHeader*) + 72
0x7ae83000: @executable_path/../Frameworks/KGCore.framework/Versions/A/KGCore : _KGMemoryPtrRelease + 100
0x001264ac: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : pKGDictReadWithFlags(KGDictInt**, KGStreamRecord*, KGMessageableRec*, unsigned long) + 508
0x0012629c: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : pKGDictRead(KGDictInt**, KGStreamRecord*, KGMessageableRec*) + 52
0x0024eeac: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : InitThumbnailCache() + 1444
0x00252b00: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : _KGReaderLibAction + 316
0x00253aa4: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : CallLibs(KGLibActionCode, unsigned char) + 268
0x00253d24: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : _KGFinishLibraries + 136
0x0025380c: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : KGInit() + 180
0x003f03c8: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : OpenApplication(AEDesc const*, AEDesc*, long) + 80
0x94960ce4: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE : aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 168
0x94960bec: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE : dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 44
0x949609f0: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE : _aeProcessAppleEvent + 216
0x93385410: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _AEProcessAppleEvent + 56
0x933e47cc: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _AEProcessEvent + 152
0x933e4718: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : HIStdAppHandler::HandleEvent(OpaqueEventHandlerCallRef*, TCarbonEvent&) + 228
0x933e16b8: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : TEventHandler::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 68
0x93359c4c: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1488
0x93358de4: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 468
0x93358c00: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _SendEventToEventTargetWithOptions + 56
0x93388b8c: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 312
0x9335a0a0: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2596
0x93358de4: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 468
0x93375d08: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _SendEventToEventTarget + 56
0x933e44ac: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _ToolboxEventDispatcher + 88
0x933e09e8: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _RunApplicationEventLoop + 168
0x001662c4: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : KGMainEvent(void*) + 64
0x002db860: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : _main + 100
0x0000d83c: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : _CVPixelFormatDescriptionRegisterDescriptionWithPixelFormatType + 40
0x8fc01048: /usr/lib/dyld : _dyldstart + 60
0x00000000: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x94b23244 ctr: 0x94b191f0
r00: 0x94b23244 r01: 0xbfffda00 r02: 0x7a699877 r03: 0x00000000
r04: 0x00000003 r05: 0x00000028 r06: 0x0000002c r07: 0x00001a03
r08: 0x00000000 r09: 0x95777a7a r10: 0x55dde9e0 r11: 0xe9a661d0
r12: 0x94b191f0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00002a00
r20: 0x01e37400 r21: 0x000031ba r22: 0xa076ed40 r23: 0x000031a5
r24: 0x01ffe340 r25: 0x00006374 r26: 0x01e34000 r27: 0x0000001a
r28: 0x0108c000 r29: 0x0000000c r30: 0x01e37400 r31: 0x94b231f0
Thread 7: (0xb011cd68, 0xb815282c)
0x94b5c32c: /usr/lib/libSystem.B.dylib : _pthread_condwait + 1260
0x00411b5c: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : Synchronizable::Wait() + 60
0x00402968: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : DisplayQueue::Run() + 744
0x00438d9c: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : Thread::RunHelper(void*) + 32
0x94baa1d4: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
0x00000000: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x94b5c37c ctr: 0x94b19250
r00: 0xffffffdb r01: 0xf0090c90 r02: 0xa076b53c r03: 0x00005d03
r04: 0x00005e03 r05: 0x00000028 r06: 0x00000030 r07: 0x00005c03
r08: 0x00000000 r09: 0x00000001 r10: 0xffffffe3 r11: 0xa0770a84
r12: 0x94b19250 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0x00000000 r27: 0xa076be54
r28: 0x06dac568 r29: 0xa076b53c r30: 0x06dac59c r31: 0x94b5be54

Fcd1 wrote:
Version: 5.0.1 (5.0.1)
Code Type: PPC (Translated)
Not only is Final Cut Pro 5.0.1 incompatible with Intel Macs, it's also incompatible with Leopard. The reason it used to work was pure luck. When you run an outdated version of Final Cut Pro you live on borrowed time because any future operating system or QuickTime update can break it.
The solution is to purchase a newer version of Final Cut Pro that is compatible with your processor and operating system. As you have a prior version of Final Cut Studio you can upgrade for $299 (even less if you shop around).

How to import MXF files to Final Cut Pro with smooth editing

Summary: Follow this tutorial to learn how to import and edit MXF files in Final Cut Pro by converting MTS to FCP native format.
If you have a Panasonic P2, Canon XF or Sony XDCAM series camcorder,
you may be familiar with Material eXchange Format (MXF). Though MXF is a
great video format to record high-definition videos, it is not easy to
use in that they are not natively supported by most NLE systems like
Final Cut Pro. In order to import MXF to FCP for editing, the easy workaround is to transcode MXF files to FCP compatible video formats.
Along with some help from a top MXF Converter, it can be done. To
help those who wanna edit MXF files in FCP without problems, here I
share with you a simple guide on how to convert MXF files to edit in
Final Cut Pro 6/7 or FCP X.
First of all, downloading the App- Brorsoft MXF Converter for Mac
Overall, the program is a professional yet easy-to-use MXF Converter
on Mac (Mavericks included) which can not only convert XF100, Canon
C300, XF105 and XF305, Panasonic P2 recorded MXF files, but also provide
simple video editing functions for you. The MXF to FCP Converter not
only can convert MXF to ProRes for FCP, but also can transcode MXF
videos for editing in Avid MC, Adobe Premiere Pro, iMovie, FCE, etc.
Just download it and follow the tutorial below to get the work done.
Transcoding (P2) MXF files to ProRes for Final Cut Pro 6/7/X
1. Import MXF files to the converter
Launch the best MXF to FCP Converter, and then click the “add files” button to browse and import MXF videos from your camcorder or hard drive.
2. Select FCP editable format
Click the Format bar, and move mouse cursor to choose “Final Cut Pro > Apple ProRes 422 (*.mov)” as output format.
Tips:
a. Settings- click to set video
resolution(1920×1080/1440×1080/1280×720/720×480), bitrate (from 1Mbps to
20Mbps), frame rate (24p/30p)
b. Editor (next to “Add” icon)- click to set deinterlace, trim, crop, add effect, attach subtitles, etc
3. Start transcoding MXF video to FCP
Click “Convert” button to start converting MXF files to Apple ProRes
MOV for FCP 6/7/X under Mac OS. Once the MXF to ProRes 422 conversion
is done, you can transfer MXF footage into Final Cut Pro (X) for editing
smoothly on Mac with ease.
Source:How to import MXF files to Final Cut Pro with smooth editing
[quote] jacknjchn.tumblr.com/post/76914947404/cant-import-mxf-footage-to-fcp-transcoding-mxf-to-fcp [/quote]

You may refer to this step by step guide on how to convert MXF to Final Cut Pro more supported Apple ProRes or DV at http://www.idealshare.net/imovie-fcp/mxf-final-cut-pro.html
It also applies to convert MXF to other video or audio format. It even applies to convert other videos like AVCHD, MOD, TOD, AVI, and MPEG etc to FCP format.

MPG to Final Cut Pro , convert mpg files to FCP freely

Why need to convert/import MPG files to Final Cut Pro?
Final Cut Pro is the premium choice for any Mac video editing, and it is widely used by Mac users now. These MPEG standard files can be these different codes and cause failure in importing to Final Cut Pro. If anyone comes across the situation, the best solution is to get aids from MPEG/MPG to FCP converter for Mac, which can help you to convert MPEG group files to FCP compatible video format and then files can be easily imported for editing job.
As we know that Final Cut Pro don't natively support MPG, MPEG, MPEG-1, MPEG-2 files, it can import MPEG-4 files (but need to be rendered once you place them on your timeline) and MOV files (without rendering). Therefore, to import MPG to Final Cut Pro directly, the best way is to convert MPG to Final Cut Pro supported Apple ProRes MOV files.
How to convert MPG to Final Cut Pro(fcp)
Step 1: Import MPG files
Download the latest version of MPG to Final Cut Pro Converter, install and run. And then, click Add Files to import MPG files to FCP, or you can also drag MPG files directly to MPG to Final Cut Pro directly.
Step 2: Choose output format and directory
You can click the drop-down list of Convert Toto select output format as "Final Cut Pro"-> "Apple ProRes MOV ". After that, click "…" of Save Toto designate a directory to save your converted files.
Step 3: Convert MPG to Final Cut Pro (X)
Click Convert to transcode MPG to MOV for editing in Final Cut Pro.
MPG to Final Cut Pro Converter is a practical tool for you to convert MPG, MPEG files to Final Cut Pro supported MOV files in order to free import MPG to Final Cut Pro (X) , FCE, iMovie on Mac OS X Mountain Lion . Besides, it is also able to convert MPG to other video files AVI, WMV, MP4, MKV FLV, DV, 3GP, ASF, RM etc.
Related Article:
MOV to FCP: How to convert MOV to FCP
How to convert mp4 files to fcp freely

Import unsupported MPEG-1 or MPEG-2 to Final Cut Pro 7/X, Final Cut Express
Summary:If you are looking for the best way to transcode MPEG-1 or MPEG-2 videos to ProRes MOV for FCP 7/X and FCE, you can follow this post, it has offered best solutions for editing MPEG videos on Mac in Final Cut Pro 7/X, Final Cut Express.
Cases:
The following are two problems when some users import MPEG-1/MPEG-2 to Final Cut:
"I am trying to import MPEG-2 files into Final Cut Pro X. I have the raw files from a Sony Handicam HDR-SR5 as well as raw files from an Sony Handicam MDR-CX560. These files were recorded as MPEG-2 files and copied from the camera hard drives (entire folders were copied containind the MPEG-2 fies) to a local hard drive on my computer. Final Cut Pro X does not recognize the files and will not import them. I have tried to use Compressor to conver the fies. I am using the very latest version that touts being able to export to Final Cut X format. I don't see that option anywhere in the settings."
Question:
Is there a way to get MPEG-1 or MPEG-2 files into Final Cut Pro X without having to convert them?
Answer:
Don't try to work with (highly compressed) MPEG 2 in FCP X. Use software to convert to ProRes 422 first, it's best codec for final cut pro or final cut express. Life will be much easier for you if you do. ProRes 422 is roughly between 5 and 8 times bigger than native camera footage - sometimes as much as 10 times, I believe, but it's well worth it for editing, effects and playback quality. The time required depends largely on your processor power but 30 mins sounds realistic.
Software you need:
Pavtube HD Video Converter for Mac
This software can convert MPEG-1 or MPEG-2 to Apple ProRes 422 codec for Final Cut Pro, Final Cut Pro 7, Final Cut Pro X or Final Cut Expr editing without rendering.
Step by step guide:
1. Download and install the best MPEG1/MPEG2 to ProRes Converter and launch it to add your videos to it.
2. Choose output format. Click on the “Format”> Final Cut Pro, Apple PreRes 422(HQ), Apple PreRes 422, Apple ProRes 422(LT), etc are all the proper choice for you.
3. Click "Settings" to adjust the parameters as you want, like Video Codec, bit rate, frame rate, Audio codec, sample rate, bit rate, channels. Set the video frame rate as 30fps, video size as 1920*1080 will be better.
4. Click Convert button to start MPEG-1 or MPEG-2 to Final Cut friendly Apple ProRes 422 for native editing on Mac OS X.
5. When the conversion ends, you can run the Final Cut Pro and click File --> Import --> Files to import the resulted MOV files and edit them in FCP easily, you can follow this import video to fcp guide.
From the steps above, I think you got the point to convert and import MPEG-1 or MPEG-2 files to Apple ProRes 422 for Final Cut editing, please have a try, this software will solve you MPEG-1 or MPEG-2 importing and editing problems, and then you can import and use your MPEG-1 or MPEG-2 in Final Cut Pro 7, Final Cut Pro X or Final Cut Express on Mac without any problems.
Now you can get DVD Creator which can help you easily burn video to DVD disc/ISO files.
Buy One Get Another Free?! Yes, just join Pavtube's Special Offers to get the promotion.
PS. If you have any problem, pls contact with [email protected] to get more information. You also can leave a message on Pavtube Community or Pavtube Facebook, we will answer your questions as soon as possilble.
Learn more Cameras/Camcorders related tutorial, pls view our FCP Column, etc. on http://www.pavtube.com/hot-topics/

FCE4 to Final Cut Pro with HD Video

I currently use Final Cut Express 4 and was thinking about upgrading to Final Cut Pro (Studio 3). In the past I wasn't using HD video but I will be soon, will FCE4 fully support HD video and are there any advantages to working with FCP instead of FCE for HD? Any input would be helpful.

Hi(Bonjour)!
What is your camcorder model?
FCE 4 support MiniDV NTSC, miniDV PAL for standard def, HDV AND AVCHD for HD.
HDV and AVCHD are transcoded to Apple intermediate codec when imported in FCE.
Final Cut Pro handle HDV natively but not AVCHD that is transcoded to Apple ProRes codec.
If you do not need to work with native HDV, there is no reason to buy FC3 regarding the editing aspect (Final Cut Pro) as FCE support around 90% of FCP features for basic editing.
But FC3 come with other applications that give better tools to handle tasks like audio sweetening (Soundtrack Pro), DVD authoring (DVD studio Pro), compositing and graphic motion (Motion), HD sharing (Compressor) over the net, on BR DVD, etc.
Go with FCE 4 and keep your money to buy external hard drive(s) for a dedicated media storage solution, a must for HD editing and a better HD camcorder.
Michel Boissonneault

Formatting a La Cie Rugged 1TB Esatadisk for Final Cut Pro and partitions?

I have a brand new La Cie Rugged Xl 1TB hardisk and a La Cie Sata II Esata 34 Expresscardadapter.
1.) How to format the drive to work best with Final Cut Pro and Prores HQ?
2.) How many partitions is best for this 1TB disk?
3.) Which tool to use for formatting and partitioning?

Disk Utility's Repair Permissions only works on drives where all of the following circumstances apply:
•The drive has a Mac OS X operating system installed.
•The files to have their permissions repaired were placed there by the *Apple Installer* application.
•A .pkg file or .bom folder was placed in the Library/Receipts directory by the Apple Installer application, containing permissions information pertaining to the file on the drive.
Repair Permissions does not work on secondary drives or on files created by the user on any drive -including, but not limited to documents, video, photos and music.
To avoid permissions issues on the drives that you will be using for video, do the following:
•Right click the drive's icon on the Desktop or in the Finder's sidebar and choose *Get Info*.
•Go to the bottom of the Get Info window and click the triangle next to *Sharing and Permissions* to open that section.
•Click the lock and authenticate with an Administrator User name and password.
•Activate the checkbox for *Ignore ownership on this volume*.
Do not partition media drives, as already mentioned. There is absolutely no need to format a drive using anything other than Apple's Disk Utility application. You do not need to use LaCie's proprietary software to format a drive.

Preview out in Final Cut Pro 6, doesnt seem to be working

I have a cilent coming over in a few hours and im having some issues getting the preview out from my computer to my TV to work. I refreshed everything, and its set to "All Frames" but all i seem to be getting is a black screen.

its DV format, We are running it though a JVC Deck VIA Firewire. It has worked with Final Cut Pro 5 and up but 6 seems to be an issue, Nothing has changed but the software

Changing language of Final Cut Pro

A friend gave me a computer that has Final Cut Pro 3 on it, but it is operating in French. Is there any way to change this? Thanks.

Unfortunately, that doesn't work. It's not the computer, but that application. As if it was installed in French somehow, or bought there. Maybe it was...
Thanks, though.

Can you burn multible movies on one bluray dvd disc with final cut pro

how to burn two completed quick time movies to blu ray dvd with final cut pro? Ive tried but wont play

Mark,
Welcome to the wild and wacky world of DVD's and Mpeg2!
Here are a few things that might help.
it seems to want everything as a QT. This presents size limitations.
Not really, iDVD simply takes the QT files that you feed it and uses its own compressor to encode them to mpeg2 files. As long as your source material is not over 2 hours iDVD can handle it.
I'm planning to export from fcp using Compressor in the hope of fitting everything onto one disc
You can do this, but you might find it simpler to simply export a QT reference movie from FCP and drag that into DVDSP. DVDSP will then use compressor to create the mpeg2 files that you need. I say this because some find compressor a little intimidating at first. (I know that I still do.)
Now, go find the manuals that came with your software and start reading, DVDSP is a powerful program and the manuals are the best place to start.
Good luck!
K

Changing serial number Final Cut Pro 7

Hi there,
I was wondering how I can change a serial number for FCP 7. I saw a bunch of older topics about a Final Cut Pro System ID folder, but I can't find it in the Library.
Thx in advance for the help!

You should be able to use FCS Remover to remove only the registration info:
From the Preset popup, choose "None"
Then scroll down the window and click on the disclosure triangle to the left of where it says "Shared Files" and then tick the checkbox next to "Registration"
Hope it helps
Andy

Trouble burning DVD in Final Cut Pro X (stops at 66%)

I have been trying to burn a DVD on Final Cut Pro 10.1.4, but I find that it always stops the burning process at 66%. An error does not pop up; it just simply stops at the same place every time. I have tried burning different projects of different lengths, I have tried updating Final Cut, I've restarted the computer, and multiple other things that I've seen others have said worked for them, but every time it always stops at 66%. I have been able to burn about 6 or 7 DVDs successfully before this problem started happening, but now I can't get a single one to work.
I seen where some said that this was a common problem in Final Cut when FCP X will hand the job to Create Disc to actually start the burn process, but I don't know how to fix it.
I've tried so many different processes to make it work; could someone please help!

Thank you for the reply! I've been trying to burn each disk without an image for the menu, but I actually even seen where someone had said just to go into it and add a small picture for the background and then delete it and then hit share and that might get it to work. I've tried doing that multiple times, and it hasn't made a difference. It still stops at 66%. I didn't know if there was anything else I could try that might fix it.

Final Cut Pro X & ProRes Major but Funny BUG

Similar Messages

Maybe you are looking for