Final Cut Pro X - Interface Corrupted

I have a problem with my FCPX. For some reason when I start the program, the splash screen doesn't go away at all and the interface is somehow corrupted or loads up incomplete. When I select Restore original layout from the menu, I get almost normal view but for example Share menu is empty (and there's still that splash screen).
I already reinstalled the program once and it helped for a while but now the problem is back. Any idea what could cause this?

Try downloading FCS Remover to make sure you get rid of any and all FCP-related files before reinstalling. Wouldn't hurt to repair HD permissions after you reinstall.
Good luck.
Russ

Similar Messages

Final cut pro 7 interface font display problem!

Hello,Every Editor,My final cut pro 7 have wrong font display problem!How to slove?How to resume default font?
I create a new Accounts to slove the wrong font problem!But How to slove the problem in old Admin Accounts?thx for everyone help!
Please forgive my poor english!THX
Wrong font display:
Normal font display:

Tom.I have uncheck the box for chinese and then restart!But it still does not slove the problem.
Please see the Pic:
Wrong:(click to see large)
Normal:(click to see large)

I'm having Final Cut Pro X interface issues

I am a total n00b to FCP, and I have messed up my version seemingly completely and have no idea how. I am currently taking a class (only a couple classes in) and the layout on the class FCP X is totally different, listing the different drives and event libraries, etc. It should look something like this:
But mine looks like this:
I've uninstalled and reinstalled three times, deleting my preferences, etc. and it hasn't reverted back to the original layout. Anyone have any clue how I can get it back to the original layout that lists the different drives and events, etc.? I'm hoping it's something simple that a moron such as myself will be able to fix.

You'd get better answers if you post questions about FCP-X in the appropriate FCP-X forum: https://discussions.apple.com/community/professional_applications/final_cut_pro_ x?view=discussions
This forum is for the legacy versions of FCP (version 7 and below).
-DH

How can you fix corrupt Project Files in Final Cut Pro X?

Hello All,
I have reason to believe that one of my project files in Final Cut Pro X is corrupt.
How may I begin to resolve this issue? Is there a third party software someone could recommend, like Digital Rebellion (if they have software for FCP X, I'm not sure) that may improve, if not hopefully solve this issue?
Many thanks!!
Molly

Had a similar problem.
Follow it here:
http://www.fcp.co/forum/4-final-cut-pro-x-fcpx/11076-freeze-during-export
among other steps taken I used Corrupt Clip Finder to isolate/remove the culprit and all was OK after that
no idea how/why the file ( which I''d been using over 5 previous versions) became corrupted

Which firewire interface for Final Cut Pro on MacPro?

I currently own a Presonus Firepod, and it seems to work pretty well, but may sell this when I upgrade from a MacMini to a MacPro. I use my Mac for Logic Pro currently.
I anticipate running Final Cut Pro in the near future, so I'm wondering about the ability to read/generate SMPTE time code that the MOTU traveller supplies?
There will be no external mixer, so this interface will connect directly to speakers & headphones. (would be nice to be able to mute speakers and control headphone mix using just the firewire interface).
I don't anticipate needing more than 2 Mic inputs - and my current mike is a Rode NT1. (As the NT1 is not a top-of-the-line mic, unsure if I should place a lot of emphasis on worrying about the pre-ams?)
I would like decent mic preamps, and ability to graphically monitor input and output levels (is this graphic monitoring necessary, or is just the single overload indicator sufficient?).
Which interfaces in $600-$1500 range would work best with Final Cut Pro - and Logic Pro?

I saw the Traveller ads in Videography mentioning
time code, so I presumed it had an advantage over
other interfaces.
I found this in some ad copy:
"""The Travler provides on-board SMPTE time code synchronization features that allow you to slave your Traveler system to SMPTE time code without a synchronizer. The Traveler provides a DSP-driven phase-lock engine with sophisticated filtering that provides fast lockup times and sub-frame accuracy. The included MOTU SMPTE Console software provides a complete set of tools to generate SMPTE for striping, regenerating or slaving other devices to the computer."""
So it likely uses an audio port for timecode I/O. However, unless you have external equipment that you want to slave to Logic Pro, (or have Logic slave to) e.g. a timecode DAT, then this really is not necessary. FCP would not see the Travaller as a "controllable" device.
For Final Cut Pro use, I'd probably shoot in HDV.
When shooting a green screen near my computer (or
maybe even on-site), I wondered if there would be an
advantage to recording the audio thru an interface
like the traveller.
The advantage is that you could capture additional mics and audio tracks with your mac while the cameras shoot. Just slate your takes and sync up later.
Do I actually need an interface that provides time
code, or is that only needed for movie work?
I have SMPTE I/O on my Unitor8, directly accessable in Logic Pro. In 8 years I've probably used it twice to capture audio from some modular digital multitracks. So, unless you have some specific need.....
Maybe it is simpler just to connect to the mic
directly to the camera's input?
Indeed. You should always have camera audio available. Anything else is supplemental. Alternatively, you could use the Travaller or RME, etc. as a "live to camera" mixer in a studio situation. Plug your mics into the interface, create a submix and send it to the camera while simultaneously capturing each mic to an individual track in Logic Pro. There are many possibilities.
G5 QuadPPC2.5, Ram:12.5g, Magma PCIe-PCI expansion Mac OS X (10.4.8) 2X Hammerfall DSP Digiface+Multiface, Digi 002r, 4X UAD-1

Interface Sony (Digibeta) DVW-A500 to iMac and final cut pro x

Hello all,
I am looking for a way to import (capture) footage from the DVW -A500 Digibeta deck into an iMac, (OSX mountain lion Final Cut pro x )
with XLR out for two channel audio and component out for the video. I have a Canapous ADVC110 but the problem is, all it has is an S connector in. I can connect the Grass Valley Canapous to the Super BNC connector with and RCA converter but the video quality sufferes to the point it may as well be a composit connection.
I have a firewire out on the Canapous and the audio it no problem but I need the component interface to get the Video quailty I need. Does anybody know where I can get an interface? This is a home edit suite so high end commercial is not an option unless I can rent the interface for a while.
Thanks to all.

Thanks Ben. My issue is not so much SW as it it the physical Link between the Sony DVW-A500 Digibeta deck and the iMac.
I (as you know) have a Firewire connection on the iMac as the channel that feeds the signal to Final Cut Pro X. The deck has BNC connectors out for the component Video signal. I need the hardware interface to take the Component signal to firewire. For audio I have XLR connectors which are eiasly enough converted to the 1/8 audio jack on the Mac. Would be better of course to have both audio and video feed through one interface.
I dont need to control the Digibeta deck, I just need to aquire the content from the deck into Final cut Pro so that can transcode the data into a digital file.
Thanks...

Final cut pro x corruption after combining events

Hi,
I installed the trial of Final Cut Pro X 2 days ago to determine if it will work properly for me. It seems that I am getting sporadic corruption when merging events, which may turn out to be a show stopper.
I am doing small merges - 2-3 events with 2-3 short clips. In general it has been fine, except yesterday I got 2 clips correped during a merge, a crash of the app which corrupted a day, and just today 5 clips from a single merge got corrupted.
Note I using the FCPX event libray and dragging/dropping to move clips around.
Any ideas of why this may be happening and whether this is a known issue?
iMac 2.8 dual core, 4G, plenty if disk (260G free)
all of the latest OS patches as well as the latest FCPX.
Nothing else significant has been running concurrently.
If there are any missing details, please do let me know.
Thanks,
Gary

Hey Andy,
Thanks for the response. To start I am a complete newbie to FCPX and have had very limited exp in iMovie. The importing was terribly slow for iMovie and I never got around to actually editing. I have a pretty lenghty response below so as to provide details.
Workflow:
1) I had done an import of files from an archives as well as my iMovie directory (as I had some clips which were missed from my orginal import into iMovie). For iMovie, I had really just been building an collection of videos which were very disorganized. I had lots of events which were date1_1, date1_2, date1_3, date_2, date_3... So checking out FCPX, I figured I would group clips mostly by an event of MONTH YR, except where there was an actual event such as a birthday.
This really cleaned up my events. As a next step, I plan to further review and break out additional events.
2) workflow going forward (current plan anyhow) - please do let me know if you have a different recommendation
now - import new footage -> either put it into the generic MONTH YR event, or put into a new appropriately labeled grouping -> some time in the future actually do something with all of this video I have taken.
On a side note, it appears that I did not have corruption, but clips that had to be re-linked. I just did a re-import from iMovie or the camera archive and that seemed to do the trick. I understand, in the future I just need to re-link
Codec:
I have the optimized video selected, however, it was just taking too long on my computer so I had stopped the transcode on several occasions..
Location:
all on my primary drive - 4T 7200
Memory:
The cpu seems to be the bottleneck - uses 150% of my dual-core. The memory seemed to be okay, but I have ordered a 4G ram chip to replace one of my 2G to bring me to 6G.
I did have a crash during an import at some point and not sure about the impact on any files, so I have DELETED MY FCPX Events and am performing a new re-import. I will not lose anything significant as I had only been reorganzing the video. I do clearly have a I have updated the prefs to only optimize. The other options I will do adhoc.
After an import from iMovie, I will be importing from my 3 camera archives since not everything is in iMovie...so this will mean dupes. I know that FCPX will prevent dupes from a particular source, but now we are talking about 3 sources which will have duplicates. Any recommendations here?
Thanks,
Gary

Using Tascam US-122mk11 as audio interface in Final Cut Pro 7

Using Tascam US-122mk11 as audio interface in Final Cut Pro 7. Works fine with Garage Band. Final Cut Pro won't use it. It appears in source menu in Voice Over Tools, but FCP won't use it.

This is the Final Cut Pro X forum. You are using a very different application. The Final Cut Studio forum, which is for the application you're using, is here:
https://discussions.apple.com/community/professional_applications/final_cut_stud io
Give exact details of your media and sequence settings. It would also be good to know what kind of drive you're using and how it's connected.

Will Final Cut Pro X recognize Avid Mojo interfacing with Broadcast Pix? If so, how do I accomplish this?

Our church used an HP for 12 years that was refurbished and finally died. We captured Sunday services for broadcast using Avid Express connected to a Broadcast Pix Switcher via an Avid Mojo with a firewire cable. This week, I replaced it the HP with a Mac in hopes of using Final Cut Pro to capture and edit video for broadcast. Will Final Cut Pro X recognize Avid Mojo interfacing with Broadcast Pix? If so, how do I accomplish this? Currently I have the mojo connected to the Mac via a firewire adapter through the thunderbolt port. However, the Mac isn't seeing the mojo or the cameras connected to the switcher.

Just turned off background rendering.
I'm not certain what you mean for specs in a specific point in the video, but here are the specs for the entire edit I initially received:
Dimensions: 1920 X 1080
Codecs: H.264, AAC, Timecode
2 Audio Channels
Total bit rate: 12,083
Size: 951,735,770 bytes (951.7 MB on disk)
Here are the specs for the exported video that has the audio issue:
Dimensions: 1920 X 1080
Codecs: H.264, AAC, Timecode
2 Audio Channels
Total bit rate: 12,274
Size: 966,817,082 bytes (966.8 MB on disk)
The video is 10:28 minutes long and the audio leaves at 5:57.
If that wasn't what you were looking for, just let me know. I'm not very good with technical stuff sometimes so may have misunderstood.
Is there something I should have done to the piece before I began color correcting it, like transcoding?

Corrupt quicktime files in Final Cut Pro

I have several long quicktime files that I used in a Final Cut Pro project. The files were captured to a firewire drive. Because the drive was formated in MS Fat32, the long capture was broken up into 2gig files with the same name and a number added (file, file1, file2, etc.) The movies worked fine for several months but now won't open in Final Cut or Quicktime. All that shows up is player that looks like an audio file but has no sound.
I recently reinstall my OS, but I tried opening the files on another mac and got the same results.
thanks,
Jim Thompson

I tried your tip but it didn't seem to work. The clips have a "v" after the file name if that helps. The first clip in the sequence opens like there's no video and will play, but has no sound. the second clip gets the error "not a movie file"
I have Quicktime Pro but don't know how to join the clips together.
Any additional advice would be appreciated

Why would Final Cut Pro 7 work smoother on one user account over another?

I just purchased a new 27" iMac 3.1 Ghz Intel Core i5, 16GB RAM, AMD Radeon HD 6970M 1024 MB. Just went to Mountain Lion a few days ago. I installed a licensed version of Final Cut Pro 7 on my account (Admin). However, the program immediately started to lag. I click on ANYTHING on the FCP interface (Modify, Sequence, etc), it immediately stalls for about 3 seconds, and then color wheel spins for a few more seconds before the menu finally drops down. Footage logs fine but the same thing happens when I drop a small video snippet on the timeline and try to play. Stall, color wheel, then it needs to "catch up" before the footage starts to play.
I don't think this has anything to do with footage formats or anything like that. I did a little research and someone said to open FCP on a different user account. I did and low and behold, FCP works swimmingly. Very odd. This particular person suggested to uninstall and then reinstall FCP on the main user account. I did. But I still have the same issue with the stalling and lagging of the program on the main user account. Now no footage is logged. It's just an empty project and I'm still having these problems with lagging. So I know it's definitely not a footage issue.
I ran diagnostics on my HD and everything is perfectly fine. Does anybody know of what could be causing this? Thanks!

Possibly corrupted preference files. If you don't have it already, download Digital Rebellion's Preference Manager.
Also, since you just did this fresh install, I'd repair permissions in Disk Utility.
Good luck.
Russ

How do I connect my DSLR camera to Final Cut Pro's Camera Import?

I recently purchased a Canon EOS Rebel T3i. I am trying to get it to record directly into Final Cut Pro, but I can't figure out how.
It does not have a FireWire port, just a USB and HDMI output. I'm thinking it's going to need to output to the HDMI port and have some sort of interface between the Mac and the HDMI cable, but I would prefer to record directly using the USB cable.
I was wondering if anyone knows how to do this and/or has done it before. Any help is greatly appreciated.
Thanks!
Zane

I haven't got a DSLR but I think they probably import like most AVCHD camcorders.
You connect it with a USB cable and switch it on.
You then set FCP X to import the video clips.

My Final Cut Pro unexpectedly quits when I scroll near a certain project in my Project Library (and unable to open said project).

I was working on a project last night and Final Cut Pro would unexptedly quit several times. I eventually got tired of it and decied to go home. Came back today and the problem continued. I turned my Macbook off and turned it back on, same problem. I moved some of my stuff off my Mac HD into my external hard drives, still the same problem. I ran Disk Utility on all my harddrives, used Preference Manager on Final Cut Pro; the problem continues. I'm able to open and work on all my other projects, but when I even scroll near the file I was working on last night, FCP decides to completely close.

I hope it'll work for others.
My version FCPX 10.1.4
After a lot of research it appeared that some of my thumbnails were corrupted and made FCPX freezing while trying to display them.
So here is my solution:
- FCPX is closed
- Go to your library storage
- Explore your Library or just remove the .fcpbundle extension if you have chosen to display the extensions then you'll see that the whole library as a normal folder
- Go to your project folder --> Render Files and move the whole Thumbnail Media folder to the trash
- Don't forget to rename the library folder with the .fcpbundle extension if you have removed it previously
- Launch FCPX again and it'll recreate the media thumbnails while opening your library
Et voila
David

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).

I have AVI files that I need to be MOV files so that I can edit them in Final Cut Pro. I am going to use Quick Time Pro for this....do I have to 'export' it or can I just 'save as', or is there even a difference? Thanks in advance for your help!

I have AVI files that I need to convert to MOV files so that I can edit them in Final Cut Pro. I am going to use Quick Time Pro for this....When I have the files open in QT Pro do I have to 'export' it or can I just 'save as', or is there even a difference? Thanks in advance for your help!

I strongly recommend you use compressor to do the conversion (if it will open the files - since quicktime will open them, it will more than likely do it.
Compressor allows you to customize presets and save them and apply them to multiple files. Although the interface may seem daunting, it's actually pretty simple.
Even if you can edit the avi in fcp, it's not a good idea. Liable to cause problems down the road.

Final Cut Pro X - Interface Corrupted

Similar Messages

Maybe you are looking for