Clip FX GUI not responding

[lesbrunn]

Originally Posted by noiseboyuk

I've tried it a few more times, and so far ClipFX is behaving.

lesbrunn - maybe 2 things to try. First is plausible, second is nuts.

FIRST - since it could be that my first launch loaded a project already in a strange state and I haven't had it since. try uninstalling PT, then removing the folder

C:/Program Files / Avid / Pro Tools

manually. Then restart, reinstall, restart.

SECOND - this is a very long shot. I noticed over the past week I'd keep highlighting all of the timeline by accident. Sometimes the rename file dialog would come up unprompted. Happened in both versions of PT, was driving me nuts. When I launched something twice in the OS, the penny dropped - my mouse was misbehaving, firing double clicks instead of single. I replaced it and now all is well.

It did occur to me that since then, everything has been behaving properly. It seems a stretch that it could cause the ClipFX to misbehave, but stranger things have happened. I once had a rig where massive CPU-spikes would occur, breaking real time audio, unless A DISC WAS PHYSICALLY IN THE BLU-RAY DRIVE. Bonkers. So thought I'd mention it in the unlikely event that you'd noticed any other behaviour that might be attributable to a misbehaving mouse.

Thanks, noiseboyuk. I've done that a few times, but it always comes back. I actually go as far as also deleting AppData\Roaming\Avid\Pro Tools and AppData\Roaming\Local\Avid whenever I uninstall PT. Mouse-wise, the Kensington trackball hasn't shown any signs of misbehavior as far as I can tell. But there are two other strange things that happen only in PT and no other program.

1. There's a GUI glitch in PT that once in a while causes both windows to flash uncontrollably for 2 or 3 seconds before returning to normal. It doesn't happen in any other program or anywhere else in Windows 11.

2. Some pop-up windows such as the import audio and the import session dialogues don't respond to double clicks. This happens only within PT and nowhere else in Windows, so it's not a mouse thing.

I've checked for viruses; my PC is clean.

[noiseboyuk]

Nope, scratch those above, while the CPU spikes do seem to have gone, ClipFX is still buggy after the reinstall and mouse fixes.

Question for lesbrunn - are the sessions where you get this originated on your own rig? Just had the thought that the project I'm on now was tracklayed elsewhere, and they used ClipFX. Just wondering if it could be a compatibility glitch between 2 different rigs.

[lesbrunn]

Originally Posted by noiseboyuk

Nope, scratch those above, while the CPU spikes do seem to have gone, ClipFX is still buggy after the reinstall and mouse fixes.

Question for lesbrunn - are the sessions where you get this originated on your own rig? Just had the thought that the project I'm on now was tracklayed elsewhere, and they used ClipFX. Just wondering if it could be a compatibility glitch between 2 different rigs.

Yes, this is a session I started, though it contains a bunch of imported wav files that were recorded elsewhere.

[noiseboyuk]

Originally Posted by lesbrunn

Yes, this is a session I started, though it contains a bunch of imported wav files that were recorded elsewhere.

Hmm, unlikely to be that then.

Grasping at straws really. If this was a widespread problem we'd know about it.

[lesbrunn]

Originally Posted by noiseboyuk

Hmm, unlikely to be that then.

Grasping at straws really. If this was a widespread problem we'd know about it.

It's an extremely annoying bug, especially now that I need to fix some very uneven frequencies in lead vocals that were not properly recorded. Multiband compression doesn't do it smoothly enough. I suppose I could automate Pro Q3, but that could be tedious given the fact that no two lines seem to be alike frequency-wise. Obviously, there were drop-ins almost on a per-phrase basis and the singer couldn't maintain a consistent tone.
Do you think this could be plugin-related?

[noiseboyuk]

Originally Posted by lesbrunn

Do you think this could be plugin-related?

It seems unlikely to me, but anything’s possible and we’re running out of plausible theories. Graphics card, even?

BTW, the symptoms I get vary a bit. Often the whole ClipFX is greyed out and power states of the modules are off. Other times it all looks normal, but the UI is unresponsive. I’ve found that it does remember what you changed in this locked-in state, and next time I launch the EQ is all over the place from my blind fumbling.

[lesbrunn]

Originally Posted by noiseboyuk

It seems unlikely to me, but anything’s possible and we’re running out of plausible theories. Graphics card, even?

BTW, the symptoms I get vary a bit. Often the whole ClipFX is greyed out and power states of the modules are off. Other times it all looks normal, but the UI is unresponsive. I’ve found that it does remember what you changed in this locked-in state, and next time I launch the EQ is all over the place from my blind fumbling.

Exactly the same symptoms here. Also, because of the other UI glitches I see from time to time, I was suspecting graphics drivers, but I'm not using a dedicated graphics card. I use the onboard processor graphics, which has served me very well for the past year or so. The drivers are up to date.

[take77]

Not sure if the solution provided in comments #11 & #13 of a related thread will work for you guys but it seems to have solved some other related clip fx issues for a couple people.

https://duc.avid.com/showthread.php?t=423215&page=2

Can't say I've experienced it here since I rolled back to 2022.7 for other reasons.

[lesbrunn]

Originally Posted by take77

Not sure if the solution provided in comments #11 & #13 of a related thread will work for you guys but it seems to have solved some other related clip fx issues.

https://duc.avid.com/showthread.php?t=423215&page=2

Can't say I've experienced it here since I rolled back to 2022.7 for other reasons.

Thanks, take77. I can see I posted in that thread (long before I had this issue). Melodyne is already active here, so that's not going to work for me. Obviously, something has changed in my system since then to cause the ClipFX issue. It's difficult to tell because many things have changed.

[noiseboyuk]

Thank you Take77 - this post from DanPimm caught my eye:

It wasn't Melodyne but the Avid Complete Plugin Bundle that I activated to my iLok cloud, and it fixed the clip effects lag.

My bundle expired end of March, when 2023.3 was released - and this is when my issues started.

Lesbrunn, do you have lapsed support that co-insides with your symptoms by any chance?