MAC OS 14.1 (23B74) fairlight effects

DaVinci Resolve Studio 18.6.2 when I go to Fairlight and you add effect the popup windows of the effect have a bug you can't move them or close them it started happening after the latest Mac OS I installed a previous version of DaVinci and I'm still having the issue I open different projects same bug anyone has seen this issue?

This is a known issue with macOS Sonoma 14.1

If possible macOS users should remain on 14.0 until this issue is fixed.

I wonder if we will see a fix from Apple sooner than later - it may not be high on their priority list, but that would be hard to believe given that if affects several high-profile applications (including Photoshop and Excel, apparently).

Is there any workaround? This makes Farlight total unusable, and annoying to do anything. Cannot reinstall the whole system right now, and also is it possible to install macOS without the last update?

Fix using DaVinci version 18.0 The problem occurs since 18.1

Of course... the fact is that the DaVinci catalog version 18.6 is not compatible with version 18.0... but to work in the meantime you can do so.

Is there any workaround? This makes Farlight total unusable, and annoying to do anything. Cannot reinstall the whole system right now, and also is it possible to install macOS without the last update?

there is a workaround it only affects exiting the effect box but you can still adjust the parameter so when your are done adjusting switch to the edit page and go back to Fairlight and it will exit the effect window if you are a full-time editor that's the only way and hopefully they get this resolve

Click on the lower part of the effects box and hit the ESC key on your keyboard and the dialog should close. You need to click on the lower part of the dialog first to ensure it has keyboard focus.

Click on the lower part of the effects box and hit the ESC key on your keyboard and the dialog should close. You need to click on the lower part of the dialog first to ensure it has keyboard focus.

THX. It'S works!

This has been resolved for me in macOS Sonoma 14.1.1 released today.

Sonoma 14.1.1 released today seems to have fixed this.