Final Cut Pro X - Clicking off of the film strip on the clip isn't deselecting the clip
Final Cut Pro X 10.0.8
Why?
If I click on the name of the clip name just under the clip in list mode then it deselects. But it's suppose to deselect by clicking anywhere outside the clip in the clip window. I don't know if there is a system slowness problem on my machine or some parameter is causing the interface to not deselect. I tried clicking with both the cursor as the arrow and the hand icons but neither works.
Any ideas?
Dave
Ok thanks for such quick response.
I wonder why his video tutorial shows otherwise?
I don't know if he is using an older OS X op system or FCP Pro X version however. Well I'm sure he did since this is not very new anymore. 2007,8 or 9?
I tried it in non list (filmstrip) view (clicking off of the clip to see if it works like you said and it does.
Thank you.
Similar Messages
-
Would I still be able to fun Final Cut Pro with no problem with the new 13"
My old MBP has "NVIDIA GeForce 860M GT with 128MB" and the new 13-inch MBP has "NVIDIA GeForce 9400M graphics" I don't really know what "GT" means, but the more expensive MBP's listed have it, so I'm guessing it's pretty good. I was wondering if I'd still be able to fun Final Cut Pro quickly if I got the new 13-inch MBP.
Back in 2007, the guy at the Apple store said I'd have to get a MBP instead of a MB if I wanted to fun FCP correctly, and now both the MB and MBP use the same graphics chip, so I'm wondering if FCP will still function correctly on the new 13-inch MBP?Eric wrote:
Incorrect about what? I never made any statements, just questions. According to the Apple store, the Macbook and 13-inch Macbook Pro both use the same chip, which is the only statement I made. And which is why I'm wondering if the new 13-inch MBP can even handle FCP since the MB can't (according to the guy in the Apple store).
Actually, your original question was formed as part of a statement:
now both the MB and MBP use the same graphics chip, so I'm wondering if FCP will still function >correctly on the new 13-inch MBP?
And that's the part that BoyHowdy pointed out that you are "a little incorrect" about. While it's true that they both have an onboard 9400M graphics chip, you are overlooking the fact that the 15" & 17" MBPs also have the much more powerful and dedicated 9600M GT graphics card. This is not an insignificant difference. Final Cut Pro, not to be confused with Final Cut Express (not you, others have confused the two), requires a dedicated card which the 15" & 17" MBPs have in the form of the additional 9600M GT, but the 13" still lacks.
The specs on the Final Cut Pro page are a little confusing because while it says it *will not work* with integrated graphics, it specifically refers to Intel, and does not mention Nvidia. However, it still says it requires an AGP or PCI Express card, which the 9400M is not.
My feeling is that even if it runs, the performance of Final Cut Pro on that system will be unacceptable, and will ultimately drive you mad. It really pushes the graphics systems hard, and despite their vast improvement over the pathetic Intel onboard graphics systems, the 9400M is still pretty anemic for high end work. You're better off saving a little more money and getting the low end 15" model. Not to mention, the extra screen real estate makes a huge difference with the very crowded Final Cut Pro UI. -
Are the sound clips from Final Cut Pro Fair Use?, Are the sound clips from Final Cut Pro Fair Use?
I recently found YouTube had flaged a video for containing a "third party" sound clip. All clips I've used in videos for YouTube have come directly from Final Cut Pro X. Any idea if the sound clips are Fair Use? I'm not sure how to repsond to YouTube and don't want to get a mark against my account due to this.
You can pretty much forget about monetizing that specific video.
[Okay... I'm going to ramble now...]
To avoid problems with youtube, you need to post a copyright (like this: @2013 by Your Name) on the video (I recommend within the first 10 seconds) -- and you better have it *right*. If you use other audio and video, as long as you have secured the proper permissions for use, you can still claim a copyright to the video you post on YouTube -- it is your creation (but it better not be a single clip of somebody else's work being passed off as something you did -- just to be clear -- your videos need to have original content that you created in order to justify the © you put on it. If you use *other stuff* as long as it's *with* permissions, it's still your video.) [If your video is going to be monetized -- make absolutely sure you have that permission for *commercial* use! Quite a lot of sources will specify that their materials *cannot* be used for any commercial use without further permissions, if at all. With Apple Loops (pro apps music and sound) you do have that express permission to be used in commercial works as long as it follows the EULA. More below.)]
You also need to specify the music and/or sound effects are "licensed from Apple Computer and used with permission" and you might as well state they are "made with Apple Loops". YouTube understands the EULA of the Apple Pro software (Logic, STP, FCP/FCPX, etc...) -- but even Apple licensed all that stuff from outside sources. Apple just takes care of paying "them" for it in advance so you don't have to (you buy it with the cost of the software license.)
You cannot use any of the "music beds" by themselves, in their entirety (all those nice long demo pieces everybody likes so much and you hear several times a day on [local] TV commercials). The EULA actually specifically states this (although you might have to read it two or three times until it becomes clear...LOL). Even loops are not to be released "as is", in their entirety, in any "derivative work". So, basically, make sure some other sound is mixed in with it (if it's music, add drums or other percussion, harmony, or duck it under talking, etc...)
The point is, no matter what audio source you have, if it is *music* (or foley) and EVEN IF you are the creator of that music or sound effect, you need to specifically put it in writing IN the video (not in the description). You need to reference the source (e.g.: stock footage by BottledVideo.com) and state it's being used with (or by) permission. [According to YouTube: I have copyright infringed MYSELF!!! just for leaving out all this *stuff* from my subsequent videos (music that I composed and performed myself on guitar... I was livid... but it stuck!).]
I can pretty much guarantee that within minutes of posting your video (if it is monetized) -- some real live person at youtube puts eyes on that video to make sure it is properly "signed". I can tell by how long it takes for the monetize checkmark to go from dark to light green -- usually less than 10 minutes.
If your video is not monetized, and it's not a blatant violation, they probably will let you off with a warning, tell you that you don't need to do anything "right now" and it won't count as a mark against you... If it IS monetized, it won't be - they'll turn it right off and your chances of winning a challenge are almost 0 (unless you can PROVE you own the material -- and I have won a challenge -- see * below); and you will probably see a "Copyright Notices" (or similar) item in the menu on your channel settings. If you can redo the video - pull the old one, put in the new info and re-up it. It's a royal PITA, but in this day and age, it's a necessity.
All videos destined for youtube should be treated as mini motion pictures and be prepared as such with full "disclosures" in titling... Welcome to 21st Century Pox [This statement is not meant to be derogatory to 21st Century Fox or imply any association or criticism or slander, and is only to be intended to be received as a parody on a common phrase that is currently still in use... No words were harmed in the formation of this pun.]
Get the point? YouTube tries to tell everybody -- but they've done a pretty lousy job of doing it. It's taken me, oh, I guess a year or so to learn to "behave" after wandering through a mire of confusing information from too many different sources -- and even if I am the sole producer of 100% of all the content in the video, I *still* have to place that © and "commit" it; it is *not* taken on faith. I actually had to go back and reread all my licenses and interpret the legalese to figure it out. It would have been simpler if they just put it: Your video is a miniature professional production. Make sure it includes all titling to reflect all participants -- *just like you'd see in a modern major motion picture or a major broadcast television series* -- I think everyone would pretty much understand what that involves. You don't have to get quite that extreme, just cover you bases and your a©©.
I tried to cover it all... but I'm pretty sure I haven't... so... good luck!
*How I won my challenge with an Apple Loops composition:
1) the music, even though using "canned" loops, was an original complex composition (I'll argue theory with anyone about this... it will be based on limited sets and recombinants as well as the theory of instrumentation and timing. In other words - I massage the heck out of loops until they don't sound anything like the originals. I almost never use audio loops -- always MIDI.) [BTW - this was another instance of copyright infringing myself - I had used the same music in a previous video I produced a year or so earlier... when I, like you, thought I was "free" to use the clips as I saw fit.]
2) the music I used in the video was originally created in Logic and I made sure the ID3 tags were filled in with my name and copyright information
3) I have a YouTube Associated Website (think this is a "partner" thing... and google "sanctioned") but if you see it, make sure you associate your domain. [I think you might be able to create a Google+ account and associate a domain that way if it's not part of your YouTube settings.]
4) I uploaded the original mp3 with the ID3 tags to my associated domain.
5) in the challenge, I 1) attached the original mp3 (w/ID3 tags); 2) gave youtube a link to the copy on my associated website for *verification* that the files belonged to ME; (and they already had the URL to the video in question -- a basic 3 point verify.)
It worked. They accepted the verifcation. (And this was the first challenge I've been able to win.) [This was very recent. What about the others? I might get a chance to complete the verifications, but I know for some, I've used up my challenges. The only other option is to pull them and redo them...]
One last word of advice: It does not pay to get "huffy", indignant, or righteous with YouTube in a challenge. They don't care. <-- read that again a lot more slowly... They have their own behinds to take care of — and your video (and/or account) lives (or dies) by their grace. If you read that and infer that I have been those things, then yes, I have... to absolutely no avail... even though I thought I was right (to the best understanding I had at the time) — they have rules. Be respectful. In general, they're pretty relaxed about all this even though it might not look that way to many users. Once you get the rules down, everything goes a lot easier... even if it is a little more work. You have to take responsibility for your own work. -
can you help me, i try to import video from my gopro to final cut pro but when i play the video he become very slow and i lose qualiter ???
Right click one of yur clips in the event browser and choose Transcode Media. Make a test project and playthat clip. See whether that solves your lag.
Russ -
"Error: Final Cut Pro was unable to read the movie file just captured"
Hello everyone!
We had a computer crash while we were working on Final Cut Pro and backing up some media to a hard drive.
Since then, whenever we "capture' video footage and hit the escape key to stop capturing - we get -
"Error: Final Cut Pro was unable to read the movie file just captured"
We reinstalled the Final Cut Pro software all over again thinking that maybe the software got corrupted and we also rectified any disk permissions for the hard drives.
Any ideas?
Thanks
Efrain
G 5 Mac OS X (10.4.8)We had a computer crash while we were working on Final Cut Pro and backing up some media to a hard drive.< </div>
You eventually want to figure out how that happened and make sure you fix it.
Since then, whenever we "capture' video footage and hit the escape key to stop capturing - we get -
"Error: Final Cut Pro was unable to read the movie file just captured"
<
You reformatted the external drive, yes? You might not have used the correct initialization setting. Should be Macintosh HFS, journalling is optional. Or you have a drive formatted for Winderz.
Aside from incorrect drive formatting, we have seen this error if the capture is incomplete or improperly terminated.
It's not an FCP issue, it's hardware.
bogiesan -
Final cut pro quit unexpectedly while using the CUDA plug-in?
Hello,
FCP 7 quits on Quicktime conversion export every single time.
Just to give some information as to how this issue started, we recently had to send our Mac early 2009 OSX 10.8.5 to get repaired because of permissions issues with the start-up drive. We had been running 10.8.5 and Final Cut Pro 7.0.3 for a while without any major issues. We also have a 3rd party graphics card installed, the Sapphire HD 7950 for mac which has been running for about six months and still seems to operate correctly. As part of the repair the Apple certified shop re-installed our OSX.
After they re-installed our OS, I ran Final Cut Pro 7 and realized that I was unable to export using Quicktime Conversion. Every time I try to export using Quicktime Conversion, Final Cut Pro instantly crashes saying "Final Cut Pro Quit Unexpectedly while using the CUDA plug-in". I asked Sapphire/AMD Radeon support what the problem was and they said this is a Final cut pro problem and not related to their card. Their response was "CUDA isn't supported by AMD hardware in MacOSX. My best guess is that either an option was turned on in Final Cut Pro to use CUDA, or the program is doing some sort of detection (possibly on installed NVIDIA Drivers). Without the NVIDIA hardware, the drivers would be running and hence the active but unsupported CUDA would fail."
Below is the log from the error that happens when I try to export using quicktime conversion. Any help would be greatly appreciated. Thank you.
Process: Final Cut Pro [17868]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCutPro
Version: 7.0.3 (7.0.3)
Build Info: FCPApp-1008261348~8
Code Type: X86 (Native)
Parent Process: launchd [195]
User ID: 503
PlugIn Path: /Library/FrameWorks/CUDA.framework/CUDA
PlugIn Identifier: com.nvidia.CUDA
PlugIn Version: 5.5.47 (5.5.47)
Date/Time: 2014-04-08 15:39:14.289 -0500
OS Version: Mac OS X 10.8.5 (12F45)
Report Version: 10
Interval Since Last Report: 100749 sec
Crashes Since Last Report: 12
Per-App Interval Since Last Report: 104765 sec
Per-App Crashes Since Last Report: 5
Anonymous UUID: A7DB7158-63B1-6A05-6194-B48755ED702E
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
VM Regions Near 0:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
__TEXT 0000000000001000-0000000000871000 [ 8640K] r-x/rwx SM=COW /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Application Specific Information:
/Library/FrameWorks/CUDA.framework/CUDA
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x90c99c12 CFStringCompare + 18
1 com.nvidia.CUDA 0x31d02f13 GetNVDADriverModelString + 371
2 com.nvidia.CUDA 0x31d067f0 cuda_driver_initializer + 112
3 dyld 0x8fe9bcda ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 230
4 dyld 0x8fe9bfde ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 64
5 dyld 0x8fe98268 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 356
6 dyld 0x8fe980ba ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 62
7 dyld 0x8fe8ce0b dyld::runInitializers(ImageLoader*) + 88
8 dyld 0x8fe92605 dlopen + 718
9 libdyld.dylib 0x91d5adbe dlopen + 68
10 com.apple.CoreFoundation 0x90d13c42 _CFBundleDlfcnLoadFramework + 210
11 com.apple.CoreFoundation 0x90cd9196 _CFBundleLoadExecutableAndReturnError + 822
12 com.apple.CoreFoundation 0x90cd8de6 CFBundleGetFunctionPointerForName + 70
13 com.apple.carbonframeworktemplate 0x6f1b7161 SMCudaInfo::SMCudaInfo() + 325
14 com.apple.carbonframeworktemplate 0x6f13a2c1 CPluginCollection::LoadPlugins(char const*) + 35
15 com.apple.carbonframeworktemplate 0x6f13a55b CPluginCollection::Initialize(std::string const&, char const*) + 55
16 SMIQTExporter 0x6eacafde CAceCompressionEngine::Initialize(char const*, char const*, char const*, char const*) + 752
17 SMIQTExporter 0x6e9f9597 SMUIData::Initialize(std::string) + 135
18 SMIQTExporter 0x6e9f8e4b MaybeInitUiData() + 123
19 SMIQTExporter 0x6e9f9204 GetUserOptionsHelper(std::string&, std::string&, bool) + 36
20 SMIQTExporter 0x6e9f93a0 GetUserOptionsFromUI + 96
21 com.apple.sorensonmedia 0x0e41411c GetUserOptions(std::string&, std::string&, bool) + 176
22 com.apple.sorensonmedia 0x0e4143c1 LoadUserOptions + 151
23 com.apple.sorensonmedia 0x0e41531a SMIMovieExportGetFileNameExtension + 140
24 com.apple.CoreServices.CarbonCore 0x955b5adb callComponentStorage_44 + 25
25 com.apple.CoreServices.CarbonCore 0x955a6abf CallComponentFunctionCommonWithStorage(char**, ComponentParameters*, long (*)(), unsigned long) + 45
26 com.apple.CoreServices.CarbonCore 0x955a6aff CallComponentFunctionWithStorageProcInfo + 30
27 com.apple.sorensonmedia 0x0e414311 SMIMovieExportComponentDispatch + 137
28 com.apple.CoreServices.CarbonCore 0x95520ade CallComponent + 151
29 com.apple.CoreServices.CarbonCore 0x95520b38 CallComponentDispatch + 29
30 com.apple.QuickTime 0x9407f269 MovieExportGetFileNameExtension + 43
31 com.apple.FinalCutPro.Plugins.QTM Reader 0x23df470e LongGOPChunkWriter::receiveSample(unsigned char const*, long long, unsigned long, long long, long long, SampleDescription**, unsigned long, unsigned long, long long, bool) + 12524
32 com.apple.FinalCutPro 0x0015e371 GetQTExportCompSubType(KGMessageableRec*, unsigned long*, unsigned long*) + 79
33 com.apple.FinalCutPro 0x001620a5 pKGExportQuickTimeDialog(KGDictInt*, long*, KGFileSpec*, KGMessageableRec**, void**, KGFileSpec*, long) + 543
34 com.apple.FinalCutPro.Plugins.QTM Reader 0x23df22ae LongGOPChunkWriter::receiveSample(unsigned char const*, long long, unsigned long, long long, long long, SampleDescription**, unsigned long, unsigned long, long long, bool) + 3212
35 com.apple.FinalCutPro 0x0015093f HandleMenuCommand(long, unsigned char, unsigned char, unsigned char, KGErrorCode (*)(long, long, KGDictInt*, void*), void*) + 325
36 com.apple.FinalCutPro 0x00150b11 HandleCommand(long, unsigned char, unsigned char, unsigned char) + 263
37 com.apple.FinalCutPro 0x004149db CommandProcess(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 369
38 com.apple.HIToolbox 0x96eb99bb _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
39 com.apple.HIToolbox 0x96d41394 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
40 com.apple.HIToolbox 0x96d40780 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
41 com.apple.HIToolbox 0x96d54655 SendEventToEventTarget + 88
42 com.apple.HIToolbox 0x96eb986a SendHICommandEvent(unsigned long, HICommand const*, unsigned long, unsigned long, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 498
43 com.apple.HIToolbox 0x96d30984 SendMenuCommandWithContextAndModifiers + 70
44 com.apple.HIToolbox 0x96d30931 SendMenuItemSelectedEvent + 268
45 com.apple.HIToolbox 0x96d307b6 FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 134
46 com.apple.HIToolbox 0x96f05e7e MenuSelectCore(MenuData*, Point, double, unsigned long, OpaqueMenuRef**, unsigned short*) + 623
47 com.apple.HIToolbox 0x96f06dc6 MenuSelect + 171
48 com.apple.HIToolbox 0x96ebcc16 HIMenuBar::HandleMouseEvent(OpaqueEventRef*) + 102
49 com.apple.HIToolbox 0x96ebca65 HIMenuBar::HandleEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 165
50 com.apple.HIToolbox 0x96d419bf HIObject::EventHook(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 163
51 com.apple.HIToolbox 0x96eb99bb _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
52 com.apple.HIToolbox 0x96d41394 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
53 com.apple.HIToolbox 0x96d40780 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
54 com.apple.HIToolbox 0x96d54655 SendEventToEventTarget + 88
55 com.apple.HIToolbox 0x96d745f6 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2188
56 com.apple.HIToolbox 0x96d4183f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2538
57 com.apple.HIToolbox 0x96d40780 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
58 com.apple.HIToolbox 0x96d54655 SendEventToEventTarget + 88
59 com.apple.HIToolbox 0x96eb90b7 ToolboxEventDispatcher + 82
60 com.apple.HIToolbox 0x96eb8f79 RunApplicationEventLoop + 240
61 com.apple.FinalCutPro 0x001539d1 KGMainEvent(void*) + 51
62 com.apple.FinalCutPro 0x002c1278 main + 54
63 com.apple.FinalCutPro 0x00002d5b _start + 209
64 com.apple.FinalCutPro 0x00002c89 start + 41
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x957fc9ae kevent + 10
1 libdispatch.dylib 0x97156c71 _dispatch_mgr_invoke + 993
2 libdispatch.dylib 0x971567a9 _dispatch_mgr_thread + 53
Thread 2:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x957fbbe6 __select + 10
1 com.apple.CoreFoundation 0x90cf5650 __CFSocketManager + 1632
2 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
3 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x0042911f DisplayQueue::Run() + 681
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 4:
0 libsystem_kernel.dylib 0x957fbc02 __select_nocancel + 10
1 libsystem_kernel.dylib 0x957fa67b select + 92
2 com.genarts.SapphireAE.plugins 0x27685721 DFTI_SET_VALUE_SGLVAL + 33127
3 com.genarts.SapphireAE.plugins 0x27677501 jpeg_stdio_src + 1793
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 5:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 6:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 11:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 12:
0 libsystem_kernel.dylib 0x957f98e2 mach_wait_until + 10
1 com.apple.CoreServices.CarbonCore 0x95559592 MPDelayUntil + 29
2 com.apple.CoreServices.CarbonCore 0x9556a8bd Delay + 90
3 com.redgiantsoftware.trapcode.Starglow 0x2eb634e0 RGS::SerialServer::ThreadProcess() + 54
4 com.apple.CoreServices.CarbonCore 0x95558a7b PrivateMPEntryPoint + 68
5 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
6 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 13:
0 libsystem_kernel.dylib 0x957f97ce mach_msg_trap + 10
1 libsystem_kernel.dylib 0x957f8cac mach_msg + 68
2 com.apple.CoreFoundation 0x90cabf79 __CFRunLoopServiceMachPort + 185
3 com.apple.CoreFoundation 0x90cb195f __CFRunLoopRun + 1247
4 com.apple.CoreFoundation 0x90cb101a CFRunLoopRunSpecific + 378
5 com.apple.CoreFoundation 0x90cc0ab1 CFRunLoopRun + 129
6 com.apple.DVCPROHDMuxer 0x2ecb998f AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*) + 317
7 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
8 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 14:
0 libsystem_kernel.dylib 0x957f97ce mach_msg_trap + 10
1 libsystem_kernel.dylib 0x957f8cac mach_msg + 68
2 com.apple.CoreFoundation 0x90cabf79 __CFRunLoopServiceMachPort + 185
3 com.apple.CoreFoundation 0x90cb195f __CFRunLoopRun + 1247
4 com.apple.CoreFoundation 0x90cb101a CFRunLoopRunSpecific + 378
5 com.apple.CoreFoundation 0x90cb0e8b CFRunLoopRunInMode + 123
6 com.apple.CoreMediaIOServicesPrivate 0x0110eb76 MIO::DAL::RunLoop::OwnThread(void*) + 146
7 com.apple.CoreMediaIOServicesPrivate 0x0111106f CAPThread::Entry(CAPThread*) + 151
8 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
9 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 15:
0 libsystem_kernel.dylib 0x957f97ce mach_msg_trap + 10
1 libsystem_kernel.dylib 0x957f8cac mach_msg + 68
2 com.apple.CoreFoundation 0x90cabf79 __CFRunLoopServiceMachPort + 185
3 com.apple.CoreFoundation 0x90cb195f __CFRunLoopRun + 1247
4 com.apple.CoreFoundation 0x90cb101a CFRunLoopRunSpecific + 378
5 com.apple.CoreFoundation 0x90cc0ab1 CFRunLoopRun + 129
6 com.apple.qmaster.do 0x32cce460 swamp::CRAdReceiver2::ReceivingThread::runOnce() + 234
7 com.apple.AECore 0x3281a022 aecore::CThread::runThread() + 34
8 com.apple.AECore 0x32817fb9 threadProc(void*) + 17
9 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
10 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 16:
0 libsystem_kernel.dylib 0x957fbbe6 __select + 10
1 com.apple.AECore 0x3281a067 aecore::CThread::runThread() + 103
2 com.apple.AECore 0x32817fb9 threadProc(void*) + 17
3 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
4 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 17:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d09572 pthread_cond_timedwait_relative_np + 47
3 com.apple.CoreServices.CarbonCore 0x955856ad TSWaitOnConditionTimedRelative + 177
4 com.apple.CoreServices.CarbonCore 0x95585184 TSWaitOnSemaphoreCommon + 272
5 com.apple.CoreServices.CarbonCore 0x9558540d TSWaitOnSemaphoreRelative + 24
6 com.apple.QuickTimeComponents.component 0x979b823c 0x973c2000 + 6251068
7 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
8 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 18:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 19:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 20:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 21:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 22:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 23:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 24:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 25:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 26:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 27:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 28:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 29:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 30:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 31:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 32:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 33:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 34:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 35:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 36:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 37:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 38:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 39:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 40:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 41:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10Thank you Michael.
I was exporting a QT Movie and bringing into compressor but there was a further problem of Compressor greying out the "submit" button, so that option wasn't available when I posted.
Your solution led me in the right direction to fix my problem. The Digital Rebellion application is very good and when I ran the crash analyzer, it still said the CUDA plugin was the culprit. But when I tried looking at the available plugins, it didn't show up. I ran a search for the plugin and found that there was a folder under Library>Frameworks>CUDA.framework. I copied that folder into a folder I made on the desktop (because I didn't want to delete something that the computer needed to run) and then deleted it from the Framework folder. I knew that our third party graphics card we installed didn't support CUDA, so I thought I'd be okay risking this; I could also replace that folder from the desktop if something major happened. I restarted and then tried exporting using QT Conversion. It worked!
Next problem then was Compressor. I needed to find out why compressor's submit button was greyed out. The application seemed to work fine, the version of compressor and Q master were the same, 3.5.3, but it didn't allow me to submit anything. I ran compressor repair from the Digital Rebellion application and it didn't change things. I read up a while on why this was happening and found on a support community that had similar issues. Many people on it said this update for Pro Applications fixed their problems:
http://support.apple.com/kb/dl949
So I think, now my computer is running the same way as it was before (except for Sorenson Squeeze which I need to fix). Thanks for the help! -
During the installing the FCP the massage are came "Final cut pro faild to download use the purchuses page to try again"what mean by this i have pruchuse again?
Hey Hamidpetra!
That message is referring to your past purchases page for the Mac App Store. More information on this can be found here:
Download past purchases
http://support.apple.com/kb/ht2519
Use the information in this article to find your past purchases and re-download your copy of Final Cut Pro. Thanks for using the Apple Support Communities. Have a good one!
-Braden -
Can Final Cut Pro 7 be run on the New MacBook Air
Can Final Cut Pro 7 be run on the New MacBook Air (just for looking at footage and assembling a rough cut) or is the graphics processing inadequate? Also wondering the same about Photoshop CS5 and Aperture 3.1.3.
Thanks,
KevinYou can install on (1) Tower and (1) Laptop, as long as they are both used by you, and NOT at the same time. This is for when you edit on your tower, but then need to edit at home, or on the road. You cannot use one copy of FCP on multiple machines at the same time. You need one copy for each machine you intend to use at the same time.
-
Missing all export options in Adobe Premiere (can only export to final cut pro xml). Where are the options?
There never was a trial version of FCP7. The application was only ever sold as part of the Final Cut Studio suite of applications. You might still find copies on eBay.
-
Lost my Final Cut Pro disc, but I have the serial/license number
So basically I want to take my final cut pro off of one computer and put it on another. But I don't have my disc, I do have the serial/license number so is there anyway I can install it on my other computer without the disc? Or is there anyway to get a replacement disc? Thanks for your help.
Nick Holmes wrote:
A few weeks ago, I suggested to someone here who was in the same predicament that they contact Apple with proof of purchase to see if they could get replacement discs. They were told that this was not an option.
So how do you lose $1300 worth of software discs in the first place? Doesn't something kick in that says "these have to be put in a safe place" ?
Mine are in a deposit box at the bank along with my Adobe stuff and Cinema4D discs -afterall, I invested several thousands of dollars in them.
This must be something new.
I unfortunately lost my disks 3 years ago and Apple, with proof of purchase replaced them. -
Where is my text box in final cut pro? I cannot change the default text at all?
Hi, as the title says, I use a default final cut pro title or ending for a video and I cannot change the text, all youtube tutorials just show that you click on the text box, the boxes appear, and then to the right in the text window you literally just type and change it, which ive done several times before, but I just got a new mac, and now that is impossible to do, what can I do? I dont want to upload videos that say, TEXT GOES HERE
hey andy,
i think what you're gonna have to do is just hit command 4!
That should bring up the inspector where you can change the font!
From Kelly -
Is there a way to export a final cut pro 10 project without updating the software to 10.1
I need help exporting a project i created on final cut pro 10, but it keeps saying i need to update to 10.1. To update the software, i need 4GB but my mac book pro only has 2GB
Well it's probably time to do some house/computer cleaning.
You need to clear space and maybe get a large fast external drive for media storage.
Try turning off auto updating in System Preferenses>Software Update.
Al -
Send to Final Cut Pro in Color off an external Hard Drive, causes Color to Crash
Okay, so I'm having some Color issues guys...
I'm color correcting a feature right now, and just completed the CC with Color. I did the entire color correct on an internal hard drive on a Mac Pro. My client wanted to take a look at the CC on a different machine, so I transferred all of the FCP files, Color Projects, footage, etc. (the ENTIRE directory from my machine) onto an external hard drive....
...When I opened the color project from the external drive on his machine, all of my media was gone, so of course I reconnected the media (directly from the source, the same source files I edited with in FCP), and everything was fine. My grades were there, and everything looked great....
....I rendered my Color sequence and tried to Send To Final Cut Pro, and color crashed on me. It continued to do this....
....I went back to my machine and tried to Send To Final Cut Pro, and everything worked just fine. What went wrong with the data transfer? Is that the reason Color keeps crashing? Is it because I relinked the footage in Color to the original source files? It doesn't make sense to me. All of the data from the original drive was moved to an external and relinked.
I'm pretty new to Color so any help would be appreciated. Thanks so much!
-ChrisCopy the original project and media to the external drive using Media Manager. It will maintain the links.
x -
The document "-" could not be opened. Final Cut Pro cannot open files in the "package" format.
Hello.
I have been trying to open a Final Cut Pro project but I keep getting this notification (title). The internet does not seem to have any solutions (maybe because of how simple it is).
I have had in on an external hard drive for a while.
I am using FCP 10.0.9
Is there anything I can do?
Thanks,
Jimmy FoxIt sounds like you're trying to open an FCP library. FCP files are never backwards compatible. The library structure was first created in version 10.1, so 10.0.9 will not open it. You'd need to find out which version created the library.
-
My Final Cut Pro keeps crashing and restarting the computer what could be the problem?
My computer keeps crashing and then restarting whenever I try to use my Final Cut Pro X. I have an iMac with OSX 10.9.2 and 12GB of memory
there is an ATI Radeon Hd 5750 1024 MB Graphics Card, I just don't understand why things are not working at all.
What can I do to ensure everything is compatible and there is nothing I am missing.Whatever the cause, please return to this forum and tell us what you did or had done to get your system working again.
There is no direct connection between FCPX and restarting the Macintosh that I am aware of. You haven't said if you can actually launch FCPX and then something initiates a restart. And you haven't said what error you see, if any. Nor have you actually said if FCPX has ever worked on that machine. Vital information.
If you search this FCPX forum, you will see that other users who have had restarting issues have not reported back to tell us about their solutions. ON other Apple forums, perhaps those related to your specific hardware and version of Mavericks, you will find several obscure and seemingly unrelated restart issues.
I have not had andy Macintosh restart issues for many, many years. My experience with Macs is that restarts are almost always hardware-based, usually incompatibility with some weird third party rig like a USB repeater, firewire adapter, cereal box keyboard, cheap monitor, ancient card reader, or even an oddball sound system. Start by disconnecting everything.
Hope you get it figured out.
Maybe you are looking for
-
On my old computer if i respond to an ad on craigslist a new tab will open to yahoo mail on my new computer this will not happen. it goes to yahoo in the same tab and does not automatically populate the email address in the yahoo to field.
-
Photosmart 8750 banner printing on 13 x 19
I've got 2 big landscape panorama images that I want to print on, say, 2 side by side 13 x 19 sheets to make a big 12 x 36 pano. The only banner option is 2x2 pages, which I tried with the images justified to the top in the hopes that it would print
-
Question about Sun Sparc T5220 server
Hi all, I have a Sun Sparc T5220 server with solaris 10 attached to another sun solaris server through its SER port. I can manage the T5220 server by the command "tip" from the other server. There is not any display device attached to the T5220. I wo
-
How to get OIM workflow waiting for a task successfully completed?
The requirement is to get OIM provisiong workflow pending and wait for a external status ready. When the external status not ready, I return "REJECTED" which mapped to "P" in "Task->Reponse" tab. Meanwhile, in the "Task->General" tab, I set the "Retr
-
Dear All Redo logs are not applying to Physical standby database SQL> select process,sequence#,thread#,status from v$managed_standby; PROCESS SEQUENCE# THREAD# STATUS ARCH 0 0 CONNECTED ARCH 0 0 CON