When will Apple resolve the FCPX Crashes when Effects are added to a clip in timeline.

I have tried every route to get answers from Apple regarding system crashes when applying an Effect to a clip in the timeline. I am now getting more aware from posts in all sorts of Forum / Communities that this is causing VERY MANY users a problem.
It would only take 30 seconds for Apple to post a statement to let their users know what they intend or are doing to resolve together with an estimated fix time.
Come on Apple please SAY something at least.
F. Jackson

Here we go - I have another thread that I started the other day, but thought I'd continue this here. I just did an extensive test. Fred, you may be on to something here. I'm beginning to think some of this is only happening if you are:
(a) running the Trial version
(b) Motion is NOT installed
(c) and it may be that the 10.0.1 update has created this problem, although surely Tom and Andy are running that update...
...or some combination of the above. Anyway...
New iMac i5 quad-core 12mb RAM - new machine with total stock config - only Apple software except for Office 2011.
FCP X Trial version, Motion is not installed
I've tried a variety of clips, but to eliminate variables, for this test I just used clips from a Canon 60D. They were imported from the card and converted to ProRes by FCP X.
Again, these crashes only relate to using the Inspector with certain Effects. If the Inspector is closed, I can apply these Effects and they play back flawlessly. However, once I've applied them and selected the clip, clicking the Inspector button causes an immediate Quit of FCP. And, if the Inspector is already open, just applying the Effect to any clip causes an immediate Quit.
These are the Effects that cause the crash (for me) by category:
Blur - Radial, Zoom
Distortion - Earthquake, Fisheye, Fun House, Glass Block, Mirror, Scrape, Water Pane
Keying - Image Mask
Lighting - Highlights, Side Lights, Spot
Looks - amazingly enough, all work except for Glory
Stylize - Censor, Halftone, Line Screen, Photo Recall, Pixellate, Vignette
Tiling - Kaleidoscope, Kaleidotile, Perspective Tile (but strangely just plain "Tile" DOES work)
So, this is approximately half of the supplied Effects. Interestingly, there is not a single category in which ALL of them work, nor one in which NONE of them work. And, by the way, doing this gave me a chance to check out every Effect - wow are there some cool ones I can't wait to work with. And, I got into this routine of highlight clip, make sure Inspector was open, double-click Effect, if no crash just CMD-z and repeat. I threw a lot of changes at it in quick succession and it handled it beautifully, except for the list above.
There is also a third party free effect from Alex4D called Smooth Move. It looks fantastic! It allows Ken Burns-like scaling which somewhat alleviates the weird animation that results if you scale and move at the same time with keyframes, BUT it allows the flexibility to NOT have the move span the entire clip like Ken Burns does. Oops, sorry, that Effect ALSO crashes the Inspector, so I can't access the controls. And, to keep this test pristine, I didn't try the Alex4D Effect on this test iMac, just on my Mac Pro on a clean system install.
Now, if Apple said (or says later) oh, wait, in the Trial version some of the Effects are not adjustable, but they are flawless in the paid version, I'd be fine with that. And, if you guys with the paid version and/or Motion installed say it works fine for you, I believe you :-). It's just that several of us were excited to get the Trial. I've been using FCP since 2003 and LOVE this new version. But, until you figure out that you can't use the Inspector with half of the Effects if you are using the Trial version, it just seems like the thing is unusable and crashes constantly - because it does.
Now that I know this, I don't think I've had a SINGLE crash otherwise - even on my "wrong" install on my MacPro with FCP7 and FCPX both on the boot drive.
David

Similar Messages

  • When will Apple resolve the lost album artwork saga for Mac/Windows Users?

    Hello,
    I'm running Windows XP, although this problem appears to be both OS- and platform-independent. I've read several forums within and outside the Apple Support site that describe issues around lost album artwork.
    In a nutshell, iTunes loses artwork that was manually obtained/added (and also iTunes-downloaded). I know I can right-click lost albums for downloaded music, but this is annoying because I have thousands of albums (or single songs from albums) and I don't want to constantly reload the information. It's even more aggravating because a large portion of my music collection consists of rare albums, and it's not unusual for me to spend significant time finding a single cover.
    I've tried some tips described in the forums, but it really comes down to users asking: Can Apple please acknowledge that this is a broad v8.x.x issue and commit to resolving it in an official release?
    Artwork coverflow-style viewing is a huge part of the music experience to me. I LOVE iTunes, but not if using it means that I'll constantly be frustrated and worried about data loss. I'm loyal to iTunes and don't want to leave, but I'm already looking at other players.
    Apple - We're begging you. Can you please fix this?
    Thanks
    -B

    Hello ! This is a user chat board - you can provide feedback to Apple via itunes menu > Help > Provide iTunes Feedback.
    My artwork doesn't get lost, so I wonder what is different on your PC? I've embedded the artwork in the MP3 tags, and they are ID3 v2.3.
    You might check your Windows Media Player settings. The default settings get info from the internet and can change things without you ever 'running' WMP. Then the next time you look at a file in iTunes, it is changed - so it seems iTunes did it.
    It's in 3 places in WMP - general, privacy, and library tabs.
    If you are talking about itunes store downloaded artwork going missing, that's a different matter. I think not, since you mentioned rare albums - presumably not sold in iTS, so therefore not downloaded from iTS.

  • When will Apple bring the urgently needed Aperture 3.4-Repair-Update?

    After installing the Aperture-Update to Version 3.4 the App crashes unexpectedly by start and cannot restart after Database-Repair.
    When will Apple bring the urgently needed Aperture 3.4-Repair-Update?

    I am having the same problem. Here is the crash log.
    rocess:         Aperture [2285]
    Path:            /Applications/Aperture.app/Contents/MacOS/Aperture
    Identifier:      com.apple.Aperture
    Version:         3.4 (3.4)
    Build Info:      Aperture-301036000000000~1
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [179]
    User ID:         504
    Date/Time:       2012-09-22 21:43:52.503 -0500
    OS Version:      Mac OS X 10.8.2 (12C54)
    Report Version:  10
    Interval Since Last Report:          153586 sec
    Crashes Since Last Report:           11
    Per-App Interval Since Last Report:  194 sec
    Per-App Crashes Since Last Report:   10
    Anonymous UUID:                      E2C0D557-6915-DF12-D27D-22B6575C8BF3
    Crashed Thread:  3  Dispatch queue: com.apple.root.default-priority
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSURL initWithScheme:host:path:]: path 1282424674 is not absolute.'
    terminate called throwing an exception
    abort() called
    Application Specific Backtrace 1:
    0   CoreFoundation                      0x00007fff919c90a6 __exceptionPreprocess + 198
    1   libobjc.A.dylib                     0x00007fff975fc3f0 objc_exception_throw + 43
    2   CoreFoundation                      0x00007fff919c8e7c +[NSException raise:format:] + 204
    3   Foundation                          0x00007fff8c05ede8 -[NSURL(NSURL) initWithScheme:host:path:] + 112
    4   PrintServices                       0x0000000105463c6d +[NSURL(ISNSURLExtensions) URLWithScheme:host:path:] + 61
    5   PrintServices                       0x0000000105463bef -[NSURL(ISNSURLExtensions) URLByAppendingPathComponent:] + 127
    6   FacebookPublisher                   0x0000000112ff27f2 -[ILFacebookAPIRequest graphURLRequest] + 215
    7   FacebookPublisher                   0x0000000112ff2fb5 -[ILFacebookAPIRequest send] + 33
    8   FacebookPublisher                   0x0000000112fe44da -[IPHFacebookPlugin displayNameForUsername:] + 88
    9   AccountConfigurationPlugin          0x0000000104974fa5 -[AccountConfigurationProfileInformationDownloadOperation main] + 174
    10  Foundation                          0x00007fff8c0b5986 -[__NSOperationInternal start] + 684
    11  Foundation                          0x00007fff8c0bd1a1 __block_global_6 + 129
    12  libdispatch.dylib                   0x00007fff91361f01 _dispatch_call_block_and_release + 15
    13  libdispatch.dylib                   0x00007fff9135e0b6 _dispatch_client_callout + 8
    14  libdispatch.dylib                   0x00007fff9135f1fa _dispatch_worker_thread2 + 304
    15  libsystem_c.dylib                   0x00007fff963bbcab _pthread_wqthread + 404
    16  libsystem_c.dylib                   0x00007fff963a6171 start_wqthread + 13
    Thread 0:: Dispatch queue: com.apple.main-thread
    0   com.apple.Foundation                    0x00007fff8c0a9087 NSKeyValuePropertyForIsaAndKeyPath + 1
    1   com.apple.Foundation                    0x00007fff8c0a8ede -[NSObject(NSKeyValueObserverRegistration) addObserver:forKeyPath:options:context:] + 80
    2   com.apple.Aperture                      0x00000001038ebea4 0x103601000 + 3059364
    3   com.apple.Aperture                      0x00000001038edd9c 0x103601000 + 3067292
    4   com.apple.Aperture                      0x00000001038edd31 0x103601000 + 3067185
    5   com.apple.Aperture                      0x000000010388ce6b 0x103601000 + 2670187
    6   com.apple.Aperture                      0x000000010388874a 0x103601000 + 2651978
    7   com.apple.Aperture                      0x0000000103888cd3 0x103601000 + 2653395
    8   com.apple.Aperture                      0x00000001038ca4ad 0x103601000 + 2921645
    9   com.apple.Aperture                      0x000000010365cda5 0x103601000 + 376229
    10  com.apple.CoreFoundation                0x00007fff9197b47a _CFXNotificationPost + 2554
    11  com.apple.Foundation                    0x00007fff8c06f846 -[NSNotificationCenter postNotificationName:object:userInfo:] + 64
    12  com.apple.AppKit                        0x00007fff96a8d60d -[NSApplication _postDidFinishNotification] + 292
    13  com.apple.AppKit                        0x00007fff96a8d346 -[NSApplication _sendFinishLaunchingNotification] + 216
    14  com.apple.AppKit                        0x00007fff96a8a532 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 566
    15  com.apple.AppKit                        0x00007fff96a8a12c -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 351
    16  com.apple.Foundation                    0x00007fff8c08912b -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 308
    17  com.apple.Foundation                    0x00007fff8c088f8d _NSAppleEventManagerGenericHandler + 106
    18  com.apple.AE                            0x00007fff94c50b48 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 307
    19  com.apple.AE                            0x00007fff94c509a9 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 37
    20  com.apple.AE                            0x00007fff94c50869 aeProcessAppleEvent + 318
    21  com.apple.HIToolbox                     0x00007fff91cf68e9 AEProcessAppleEvent + 100
    22  com.apple.AppKit                        0x00007fff96a86916 _DPSNextEvent + 1456
    23  com.apple.AppKit                        0x00007fff96a85ed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
    24  com.apple.Aperture                      0x0000000103a7500d 0x103601000 + 4669453
    25  com.apple.AppKit                        0x00007fff96a7d283 -[NSApplication run] + 517
    26  com.apple.prokit                        0x0000000104b16324 NSProApplicationMain + 378
    27  com.apple.Aperture                      0x00000001036109c2 0x103601000 + 63938
    28  com.apple.Aperture                      0x0000000103610314 0x103601000 + 62228
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib                  0x00007fff90a23d16 kevent + 10
    1   libdispatch.dylib                       0x00007fff91360dea _dispatch_mgr_invoke + 883
    2   libdispatch.dylib                       0x00007fff913609ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib                  0x00007fff90a236d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff963bbeec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff963bbcb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff963a6171 start_wqthread + 13
    Thread 3 Crashed:: Dispatch queue: com.apple.root.default-priority
    0   libsystem_kernel.dylib                  0x00007fff90a23212 __pthread_kill + 10
    1   libsystem_c.dylib                       0x00007fff963baaf4 pthread_kill + 90
    2   libsystem_c.dylib                       0x00007fff963fedce abort + 143
    3   libc++abi.dylib                         0x00007fff8e97ca17 abort_message + 257
    4   libc++abi.dylib                         0x00007fff8e97a3c6 default_terminate() + 28
    5   libobjc.A.dylib                         0x00007fff975fc873 _objc_terminate() + 91
    6   libc++.1.dylib                          0x00007fff915aa8fe std::terminate() + 20
    7   libobjc.A.dylib                         0x00007fff975fc5de objc_terminate + 9
    8   libdispatch.dylib                       0x00007fff9135e0ca _dispatch_client_callout + 28
    9   libdispatch.dylib                       0x00007fff9135f1fa _dispatch_worker_thread2 + 304
    10  libsystem_c.dylib                       0x00007fff963bbcab _pthread_wqthread + 404
    11  libsystem_c.dylib                       0x00007fff963a6171 start_wqthread + 13
    Thread 4:
    0   libsystem_kernel.dylib                  0x00007fff90a236d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff963bbeec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff963bbcb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff963a6171 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib                  0x00007fff90a236d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff963bbeec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff963bbcb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff963a6171 start_wqthread + 13
    Thread 6:
    0   libsystem_kernel.dylib                  0x00007fff90a236d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff963bbeec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff963bbcb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff963a6171 start_wqthread + 13
    Thread 7:
    0   libsystem_kernel.dylib                  0x00007fff90a230fa __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff963bdfc3 _pthread_cond_wait + 927
    2   com.apple.Foundation                    0x00007fff8c0e7933 -[NSCondition waitUntilDate:] + 357
    3   com.apple.Foundation                    0x00007fff8c0e7789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
    4   com.apple.proxtcore                     0x00000001057ea03a -[XTMsgQueue waitForMessage] + 47
    5   com.apple.proxtcore                     0x00000001057e9282 -[XTThread run:] + 329
    6   com.apple.Foundation                    0x00007fff8c0bc612 __NSThread__main__ + 1345
    7   libsystem_c.dylib                       0x00007fff963b9742 _pthread_start + 327
    8   libsystem_c.dylib                       0x00007fff963a6181 thread_start + 13
    Thread 8:
    0   libsystem_kernel.dylib                  0x00007fff90a230fa __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff963bdfc3 _pthread_cond_wait + 927
    2   com.apple.Foundation                    0x00007fff8c0e7933 -[NSCondition waitUntilDate:] + 357
    3   com.apple.Foundation                    0x00007fff8c0e7789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
    4   com.apple.proxtcore                     0x00000001057ea03a -[XTMsgQueue waitForMessage] + 47
    5   com.apple.proxtcore                     0x00000001057e9282 -[XTThread run:] + 329
    6   com.apple.Foundation                    0x00007fff8c0bc612 __NSThread__main__ + 1345
    7   libsystem_c.dylib                       0x00007fff963b9742 _pthread_start + 327
    8   libsystem_c.dylib                       0x00007fff963a6181 thread_start + 13

  • Music, Photos, Videos... I can't sync anything for iPhone 4. When will Apple release the new version of iTunes?

    I tried every methods up online trying to sync the music, photo, and videos. Nothing is working right now ever since I updated my ios to 7.
    This is happening to most of people who owns iPhone 4, 4S, and 5. Does anyone know when will Apple release the new version of iTunes which will fix the sync problem?
    What's the point of having a smartphone when you can't sync anything?

    Welcome to the Apple Support Communities
    See if your computer is supported > http://support.apple.com/kb/sp575 Buy Snow Leopard > http://store.apple.com/us/product/MC573/mac-os-x-106-snow-leopard Then, make a backup, insert the DVD and upgrade. Finally, go to  > Software Update and update to the latest version.
    If your computer is compatible, you can use Mountain Lion. Open App Store and purchase Mountain Lion. Check if your programs are supported > http://www.roaringapps.com

  • HT201071 When will Apple support the Olympus E-M10?

    When will Apple support the new Olympus E-M10? Frustrating that the last Camera RAW update did not include it.

    We're just users like yourself. Try: http://www.apple.com/feedback/
    When will Olympus provide the data to Apple? That could be the question.

  • When will Apple give the Battery Percentage option for the iPod?

    When will Apple give the Battery Percentage option for the iPod?

    It's hard to tell since Apple has never included it in all generations of the iPod and I assume you mean the iPod Touch.
    Apple could place it in the sixth generation iPod Touch but Apple has been pretty tight lipped on the possiblity of one coming. It's been since 2012 when the fifth generation arrived in the fall so the iPod lineup is due for an upgrade. Some reports say it won't come this year and others say different. But with the new iPhone expected to debut with larger screen it is still possible the new iPod will come with a larger screen alongside the new iPhone. It happened back in 2012.
    But no one really knows. Until then download an app to measure your battery percentage. I have battery doctor and it's really useful to determine how much battery my iPod has left and it also can clean up your memory and any junk files.

  • When will Apple have the programmes for 'Samsung Scanners' updated please?

    When will Apple have the programmes for 'Samsung Scanners' updated please?

    It's up to Samsung to do that, not Apple. You need to ask them.

  • The 9.2.1. of iPhoto seems to be a risk to purchase. When will Apple release the fix 9.2.2 or 9.3.1?

    The 9.2.1. of iPhoto seems to be a risk to purchase. When will Apple release the fix 9.2.2 or 9.3.1?
    I would like it with Photostream, but do not want to risk the issues other users have.
    And with these reviews it is crazy of Apple not to update or communicate about it.

    Huh?
    9.2.1 is as stable as every other version of iPhoto. Look back through this forum or any other. There are always people who have issues, always. There are no more nor no less with this version. When the next one comes out - be it 9.2.2 or 9.3 or whatever there'll be more posts from other people.
    Remember, the people who don't have issues don't post to forums on the Internet.
    This is not only true of iPhoto but just about every single piece of software on every OS and the OSes as well
    Welcome to the real world.
    Regards
    TD

  • When will Apple resolve its issue with Adobe so iPad users can use flash?

    When will Apple resolve its issue with Adobe so iPad users can access flash?

    That isn't going to happen. Adobe has not only given up on iOS, they have given up on all mobile device now.
    Why do you think you need Flash?
    Allan

  • When will Apple put the Adobe Flash version on the iPads?

    When will Apple put the MS Adobe Flash version on the iPads?  The iMac desktop has Quick Time, but there's nothing for the iPads that I know of.

    Guess you haven't seen the analysts reports and sales numbers for Android tablets lately... Or heard that the tablet optimized version of IE in Windows 8 will be plug in free... Or heard that Adobe is now pushing a server product that will convert Flash video to HTML 5 for use on mobile devices.
    A 1980 Chevy Chevette will do the same thing as a 2011 Mustang. I guess Ford is going to go out of business when everyone starts driving Chevettes.

  • When will Apple have the audio driver problems repaired?

    Cannot find Audio Devices !!!!!!?????
    No Cuebase ???? No Presonus hardware interface !!!
    Now that all new macs ship with OSX Lion when Will Apple solve the problem I would have thought the engineers would have seen this coming and thought this through.
    I had to downgrade back to Snow Leopard!! The whole incedent cost me valuable time and money
    I loved the Lion interface but c'mon guys ...!!! did you hire a bunch of laid off microsoft windows Vista programmers or something? 
    I can't believe you all made such an obvious mistake "not making OSX Lion backwards compatible with Snow leopard proven third party drivers"
    I did not expct this from Apple ..What a disapointment ......

    It's up to Samsung to do that, not Apple. You need to ask them.

  • When will Apple correct the CD insert printing problem with 11.02.26?

    When will Apple correct the CD insert printing error in itunes 11.02.26?

    Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
    ORA-00942: table or view does not exist

  • Will apple update the applemaps for UAE?

    does anyone know when will apple update the applemaps for UAE?

    IF you have the latest version, the Maps app has a feedback button for reporting errors and inaccuracies. Given the debacle that the initial Maps release turned out to be, it appears that reports are taken very seriously and resolved, so you may be in luck. That's the best we have.

  • Will apple replace the L shape MagSafe Adapter the pins are sticking causing late 2011 macbook not to receive charge.

    Will apple replace the L shape MagSafe Adapter? The pins are sticking causing my late 2011 macbook not to receive charge.

    Yes, Apple will replace it if you are still under warranty. Otherwise, as in my case, you will have to buy a new one.
    I purchased my MacBook Air July of 2011.  Approximately four months later the adapter stopped working. I brought my MacBook and the adapter to the Genius bar. The adapter was replaced because it was under warranty. To make sure the problem was not something I did as I didn’t want to duplicate, I inquired and was told some adapters just have problems.  After two weeks, I noticed the rubber coating to the wire bunched up on the L end that connects to the MacBook Air on the replacement adapter. I returned to the store and was assured that my concern was unwarranted and that since the adapter was working fine I was fine and that if it stopped working I could just return it. On 11/22/12 it was not getting power. I returned to the store. After being asked where I returned the adapter when I originally had the problem (same store) I was informed that the replacement adapter was only covered for three months, to be happy it lasted as long as it did, and I would need to buy a new one for $61. However, the store didn’t have the adapter I needed and could buy the 60W adapter for $79. I was told I could go up, just not down. Before leaving, however, I asked if I was doing something wrong with the adapter and how long the new one was covered for. He inspected the nonworking adapter, pointed at the where the wire connects to the base and said no, usually people have their cords pulled from here but yours looks fine. On the plus side, the rubber coating around the wire of the new adapter appears thicker with no chance of sliding and bunching up. Glad Apple fixed this issue.

  • Will apple supply the OS X lion on the new iMAC's,or do we have to buy it

    I plan to buy a new iMAC. Will apple supply the OSX Lion as a default with it or will I have to pay to upgarde from the snow leopard?

    After Lion is released it will be pre-installed on new computers. Some inventory will remain with Snow Leopard pre-installed. In that case the purchased will get a drop-in upgrade redemption coupon enabling them to install Lion. See
    The Mac OS X Lion Up-To-Date upgrade is available at no additional charge via the Mac App Store to all customers who purchased a qualifying new Mac system from Apple or an Apple Authorized Reseller on or after June 6, 2011. Users must request their Up-To-Date upgrade within 30 days of purchase of their Mac computer. Customers who purchase a qualifying Mac between June 6, 2011 and the date when Lion is available in the Mac App Store will have 30 days from Lion’s official release date to make a request.

Maybe you are looking for