Clip FX GUI not responding

[lesbrunn]

Originally Posted by noiseboyuk

A mysterious but close-to-definitive end to an utterly bizarre bug.

Good riddance! So are you going back to 23.3?

[noiseboyuk]

Originally Posted by lesbrunn

Good riddance! So are you going back to 23.3?

Not yet - to help with the testing support graciously gave me a year's support plan. There's nothing I need in 23.3 or 6 and I see there's a lot of issues with 6 so I'm going to wait for the next reported stable release.

I also have a feeling (could be wrong) they're looking at that Windows installer which is definitely poor, there's whole massive areas it doesn't uninstall. The whole thing has made me generally a bit more wary of uninstalling and installing, so will only do it when there's a real benefit.

[lesbrunn]

Originally Posted by noiseboyuk

Not yet - to help with the testing support graciously gave me a year's support plan.

Lucky you.

There's nothing I need in 23.3 or 6 and I see there's a lot of issues with 6 so I'm going to wait for the next reported stable release.

Same here. With the exception of the Clip FX bug I've found 22.12 stable, and will be sticking with it till the next groundbreaking release.

[take77]

I installed 2022.12 last night on W10 and experienced the Clip FX bug right off with a single monitor setup.

Selected a clip and tried clicking on the GUI with no response.
After I toggled to mix view & back I was able to see the changes.
Reopening the session helped. Then I opened a different session and it happened again.

I've experienced it 4 times so far after opening a couple different sessions but don't know an exact way to repro.

Just confirming that it happens on a single monitor setup.

[noiseboyuk]

Interesting, thanks take77 - if you can bear it, let support know.

Being as lesbrun and I both made ours go away by taking it down to one monitor and back again, I don't quite know what to suggest in your case... plug in another, run PT, then go back to one?

[take77]

Yes, support has been very helpful and a case has been created.

So far it's only happened when selecting clips on a mono track. But I just installed 2022.12 and it may happen on stereo clips too.
I was thinking of you guys after I installed and thought I'd do a few quick tests.
I don't think mono as opposed to stereo clips would have anything to do with it and might just be coincidence.
But hopefully a good lead.

My main thought is that my system has integrated Intel graphics as opposed to a dedicated one.
Not sure if that's the right terminology. But things work fine in 2022.7.

Graphics drivers are kept update with the Intel driver & support assistant.

[noiseboyuk]

Originally Posted by take77

Yes, support has been very helpful and a case has been created.

So far it's only happened when selecting clips on a mono track. But I just installed 2022.12 and it may happen on stereo clips too.
I was thinking of you guys after I installed and thought I'd do a few quick tests.
I don't think mono as opposed to stereo clips would have anything to do with it and might just be coincidence.
But hopefully a good lead.

My main thought is that my system has integrated Intel graphics as opposed to a dedicated one.
Not sure if that's the right terminology. But things work fine in 2022.7.

Graphics drivers are kept update with the Intel driver & support assistant.

FWIW I have a separate graphics card and had the problem, and it definitely manifest on both stereo and mono clips. It's such a bugger to track down.

Still not come back here though since I changed the number of monitors and back again, hurray. The cure every bit as inexplicable as the bug.

[lesbrunn]

Originally Posted by noiseboyuk

FWIW I have a separate graphics card and had the problem, and it definitely manifest on both stereo and mono clips. It's such a bugger to track down.

Still not come back here though since I changed the number of monitors and back again, hurray. The cure every bit as inexplicable as the bug.

+1 for both stereo and mono. Integrated CPU graphics here. I had problems with Windows recently, so recalled a system backup, and it reappeared. I used Guy's monitor trick and everything's good again. New sessions seem to open with the bug, but resizing PT windows clears it instantly without restarting.

[take77]

Thanks for confirming it's happens on dedicated graphics & stereo clips.
I opened a session with stereo clips that worked fine last night and the bug happened right off.

Thanks for the tip on resizing the window.
Minimizing and maximizing the window solves the problem for the session.

The GUI freeze happens as soon as I open a session so maybe I can train myself to quickly minimize & maximize the edit window after opening the Clip FX tab and before clicking on the GUI.

[take77]

Here's a couple things I noticed just before the bug occurs on my system:

1. When opening the Clip FX tab the processor order is changed to Filters first.

2. If I hover over a filter type my cursor turns into a up/down blue arrow (only in the filter section). This lets me know things are not going to respond.

Then after doing the min/max window workaround the GUI goes back to the default processor order.

Originally Posted by noiseboyuk

AH-HA!

Now we know what this bug is like - a tricky blighter.

Tricky Blighter...

Band Name or track title for sure.