Channel EQ and Limiter broken after 10.6.6 update?

I'm experiencing a weird problem with audio units. (they all validate, btw) but stock audio units like Channel EQ and Limiter which were applied to projects before the 10.6.6 update are now very broken.


They have odd settings like -18.2 dB which was not what they were set to prior to the 10.6.6 update and when they are active they silence that audio track. I can toggle them off and audio returns.


Even stranger, if I open a project, open the GUI for say a Limiter, and change one of the dials, when I cursor back to the Timeline, that dial snaps back to it's previous (incorrect) location or like with Output Level it'll go to -9.9 dB. If I cursor into the Viewer after changing dials it does not change. The Lookahead dial is especially messed up.


It's like things like Channel EQ and Limiter when applied in the prior version of FCPX got reset or stuck in 10.6.6.


Applying a new Channel EQ or Limiter works as expected. The problem is only with ones added and adjusted prior to the 10.6.6 update. I've sent Apple feedback about this. (btw, these are the Logic units, not the "Final Cut" ones.)


Luckily, I updated between projects but man, if I had to fix all this manually it'd be a HUGE amount of work. As of now, any old project I have which has things like this applied to it is silent and I'd have to re-do (reapply new audio units) all that audio work. Has anyone else noticed this? Is it just me?


Usually, FCPX is largely problem free for me. I just updated to 10.6.6 this morning and just now noticed this odd behavior this afternoon.


I can't think of anything that would have caused this and I've never seen this before. I did do a safe boot after the 10.6.6 update trying to fix an issue with Safari Developer Preview, other than that I didn't do anything else.

Posted on May 24, 2023 12:39 PM

Reply
Question marked as Top-ranking reply

Posted on Jul 20, 2023 10:43 AM

I managed to open some old projects (never opened in 10.6.6) and yup, it appears that 10.6.7 successfully handles limiters and some other audio units if the project was never opened in 10.6.6.


However, for me at least, in projects (could be entire Libraries actually, I'm noticing) that were opened in 10.6.6 that have say, an Adaptive Limiter or Limiter, it is NOT fixed and the buggy behavior remains.


So, it looks like the bug is fixed, in quick testing, in 10.6.7 if the project was not opened in 10.6.6, but possibly if it was opened in 10.6.6, then the bug remains even in 10.6.7. So 10.6.7 "addresses" the "issue" but it is not a complete fix in my limited testing.

Similar questions

26 replies
Question marked as Top-ranking reply

Jul 20, 2023 10:43 AM in response to Tom Wolsky

I managed to open some old projects (never opened in 10.6.6) and yup, it appears that 10.6.7 successfully handles limiters and some other audio units if the project was never opened in 10.6.6.


However, for me at least, in projects (could be entire Libraries actually, I'm noticing) that were opened in 10.6.6 that have say, an Adaptive Limiter or Limiter, it is NOT fixed and the buggy behavior remains.


So, it looks like the bug is fixed, in quick testing, in 10.6.7 if the project was not opened in 10.6.6, but possibly if it was opened in 10.6.6, then the bug remains even in 10.6.7. So 10.6.7 "addresses" the "issue" but it is not a complete fix in my limited testing.

Jun 26, 2023 5:51 PM in response to W. Raider

This does work to a certain extent. This just bit us with a project we have been working on for the past 12 months or so. It's a multi-year project so not updating is really not an option. We have several custom audio chains built to make it simple drag and drop. Updated our editing machine to Ventura and FCP 10.6.6. Opening this project killed our audio chains that were simply EQ, Compressor, Limiter and Multi-Meter.


I sent an Auto Save to another Machine with 10.6.5, along with the Audio Chain. Exported an XML and reimported into 10.6.6... This surprisingly fixed the audio, but all of the Motion Drop Templates we created no longer had content. This was easier to fix than all of the audio that needed to be redone.


Surprisingly this is not happening to everyone, as one of our other editors was able to open the project with no problem. We have some Waves plug ins along with Isotope RX Suite... so I'm wondering if one of those is messing with things.

Jun 16, 2023 6:25 AM in response to angellolly

I have not had time to try this but if you have an XML export of a project from the previous version of FCP you could try importing that into a new 10.6.6 library. I see the audio units data is saved in the XML (obviously) but I haven't tried if this is a workaround yet. Right now, where I am, I don't have access to an older XML to test with.


What I've been doing to repair a project that was updated after it was finished (for the season) but now needs contemporary updates is just manually deleting and redoing the audio effects.


So, my thinking is if you have a backup save of the library (meaning it's not been updated to 10.6.6), and the previous version of FCP, you can restore both, then generate an XML then import it in to FCP 10.6.6 and see how they fare. My guess is they'll still be messed up but no way to know until it's tested. I'm pretty curious about this but I have no way to try it out here on location.

May 26, 2023 9:38 PM in response to W. Raider

I am using 10.6.6, the new Pro Video download, and Ventura 13.4 (though this was happening before the Ventura update)


Any audio track with built-in Loudness filter is muted; any audio track with built-in Compressor is muted. If either of these effects are turned on then the track is muted.


And I was just about to render an extremely complex half-hour project...

May 27, 2023 11:52 PM in response to W. Raider

Same here man! I just posted about it. This happened to me right before my video was about to go up and I had to "rough" adjust the audio. I had to spend almost two days to rebuilt the same audio effect that I built for my microphone and it's still not the same.

As you mentioned the update completely wrecked the limiter as well as Channel Eq and everything else you talked about in your post. Looking forward to speedy apple response to this critical/crucial issue. Looks like someone didn't do 'regression testing'

Jun 16, 2023 7:25 AM in response to W. Raider

I just posted a question about this before seeing your post. Thank you. The same thing is happening for me since the update, and I've had multiple interviews where I had to totally redo the audio because all the limiter levels are wrong. It's costing me money because freelance projects I've almost finished, I'm now having to totally redo the sound levels. And I called Apple Care and they were absolutely no help. I'm so annoyed.

Jul 8, 2023 5:23 AM in response to W. Raider

I'm glad I'm not alone with this issue. Here is my story:

I've had a preset (EQ, multipressor, limiter) which I applied to all the audio and then just made micro adjustments. So after I upgraded to 10.6.6 the preset was ruined, it was painful but ok, I had to remake all the effects and save a new preset. I though it was over but...


now I've applied my new preset and it started glitching again. It is super annoying. I have to do so much extra work now.

Jul 20, 2023 7:54 AM in response to zachfmn

I haven't heard anything back from Apple on this and it's a bit surprising given how serious this bug is. Maybe someone should bring it to the attention of a few popular Mac(something) websites.


It's grown into a pain for me because, like some others, long projects or projects that get periodically updated are suffering from this issue and causing LOTS of extra work, now. I thought about giving Apple a call but last time (for another FCP issue) it was a long series of hand-offs to other people, techs, experts, tiers, that ultimately ended with a "Thanks for bringing this to our attention" kind of generic good-bye response.


Try feedback again at Feedback - Final Cut Pro - Apple because they actually do look at them.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Channel EQ and Limiter broken after 10.6.6 update?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.