![]() ![]() If that doesn't help, I notice in your crash log you have considerable external devices connected to your M1 Ultra. Can you check if that is disabled on your machine (as an editor you'd normally want that). We think that was fixed in 10.6.5 but we aren't sure. In the Thomas Grove Carter case, he eventually determined it was a combination of his dual monitors and the MacOS system setting "automatically adjust brightness". If you have multiple monitors on the problem machine, as a troubleshooting step can you try disconnecting that and see if the problem can be reproduced? If so please send me that crash dump. I had the same dual monitor config as him but I could never reproduce it. In his case disconnecting those temporarily was a workaround. We had a previous problem reported by well-known editor Thomas Grove Carter which was related to multiple monitors. ![]() In the concise thread 0 stack there is a call to NS_setFlushesWithDisplayLink which may be associated with using multiple monitors. There are apparently recursive calls in some NS (that means NextStep) methods. The rest of the call stack from frame 127 up to the crash frame 0 are all MacOS frameworks. On frame 128 it references LunaKit which is an FCP UI framework. On the thread 0 application-specific backtrace, with a single exception there are no FCP frameworks or classes listed. Your crash dump is quite complex I haven't seen anything like that before. Anything you do to a large event will crash it, folks at the FCP team told me to reduce the number of items on an earlier OS or downgrade it. If it still hangs or crashes, turn off background rendering, in FCP preferences, delete all render files by selecting the library in the left sidebar, then File>Delete Generated Library Files>Delete Render Files>All.ĭropped you a file in the dropbox. Can you verify you are on the latest versions of those plugins? If you already are on the latest versions, try resetting FCP preferences (item 11 on this page): /en-us/HT203477 That is normally fixed by the plugin developer updating their software. It is unfortunately common for plugins to make FCP crash after updating MacOS or a FCP version. However I don't use Film Nitrate or Color Finale. In general it seems reliable when grading 4k/23.98 Sony XAVC-I and 8k/23.98 RED RAW. I'm running FCP 10.6.5 and Ventura 13.1 on a top-spec M1 Ultra Mac Studio. I use also Film nitrate and Color finale plugins. Every time I try to color grading, even with color correct of FCPX, it crashes. I have Macstudio m1 ultra with 64gb ram, and working videos 4k, that my MacBook Pro intel runs softly. ![]() since I update macosx to Ventura, FCPX is constantly crashing or blocked processing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |