The major benefit to this plugin is that you don't have to leave FCPX to grade your footage, which is great news for filmmakers who are not only editing their own work, but are doing the final grade as well. Has announced their new Final Cut Pro X plugin, Color Finale, which gives users tools that are typically reserved for completely separate grading programs, like 3-way color wheels, RGB curves, vector based secondaries, and 3D LUTs all within the FCPX timeline.Ĭheck out the video below to see what Color Finale can do for your footage:Īnd here's a demo to see how the plugin works in real-time: Been waiting (for forever!) for 10.6.2 to come out and just hoping that it’s fixed.DISCLOSURE: This is a sponsored post by Color Grading Central. mp4 container, so that might or might not be relevant. I also saw that some people on the FCPX forum were talking about a bug with 10.6.1 and the. mov instead, I feel an improvement but not complete resolution. I work with a lot of 4K60 video game footage produced by OBS and subjectively I felt that FCP was crashing more often with. I’ve looked around in Reddit and the FCPX forums but no solution. ![]() Happening on both an M1 Air and an M1 Pro 14”. I’m on 12.3 but it was happening on 12.2 as well. Right down to the same:Ĭrashed Thread: 109 Dispatch queue: .flatten Exception Type: EXC_BAD_ACCESS (SIGSEGV)Įrror message. Man, I’ve been getting this error heaps on 10.6.1, on two different M1 machines. See comment 'QoS NOTE' where compressionSession is created! (sfrc->expectedQOS = qos_class_self()) :: void compressionOutputCallback(void *, void *, OSStatus, VTEncodeInfoFlags, CMSampleBufferRef) (file: /Library/Caches//Sources/Flexo/Flexo-40100.141.14/framework/utilities/FFSegmentStore/FFSegmentStoreInfo.mm, line: 1188) May result in self-throttling performance issues. Last ProCore Log: assertion failed: FFSegmentStore compressionOutputCallback did not run at the expected QOS level. ![]() REGION TYPE START - END PRT/MAX SHRMOD REGION DETAIL Bytes before following region: 4367794160 VM Region Info: 0x10 is not in any region. Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Here's a copy/paste of the top part of the error log: I'm wondering if this an indication that something is wrong with the SoC on my machine, or if the frequent crashing is a problem with Color Finale running on Apple Silicon? My system seems stable in every other aspect, with the except of TextEdit which sometimes crashes randomly while moving the cursor with the arrow keys, but I chalked that up to a Monterey bug. I've also noticed that every time the error log says something to the effect of "ProCore QoS did not perform at the expected level". My first thought was that it might be related to the known memory leak in Monterey, but every time the crash happens I've checked Activity Monitor and haven't seen any indication that I'm getting close to running out of RAM. I also have 2019 Intel iMac and have seen none of the crashing I do on my MBP. It's actually caused me to lose quite a bit of work over the past few weeks, even with FCP's auto-save feature. I've noticed that anytime I have something in the timeline that's color corrected I experience frequent crashes, up to several per hour. ![]() I have a 14" MBP with a 10-core M1 Pro chip (14-core GPU) and use Color Finale 2.0 regularly in my workflow. I've been scouring the internet trying to find anything about the issue I'm having, and not having any luck so I figured I'd post here and see if anyone else is having the same problem or if it's just me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |