AZSlow

Quote from: azslow3 on June 04, 2025, 04:08:54 PMSorry, I can't reproduce. Unknown pane info message is usual, so not indicate the problem.

My apologies, I've just found the reason of this error: it was just one NVDA-addon which allows to change the roles of specified controls. So, there's no SIBIAC error.

Quote from: azslow3 on June 04, 2025, 04:08:54 PMPS. I have no plans for Ableton Live

That's sad because Ableton Live 12.2 now is competing DAW with REAPER and might be supported too... I am planning to start using this.

How can I sent you the .cwp file ?

Yes, with .cwp I can find from where that comes and fix.
Note it can take a while.

Hi,
I loaded some projects with reacwp in reaper correctly.
But for another projects nothing are loaded in reaper. Nothing is loaded. The reaper screen is empty. This is strange because with these projects the azslow popup which indicates if there are any errors not appears.
I think there is a bug. Do you want the .cwp to debug ?

Sorry, I can't reproduce. Unknown pane info message is usual, so not indicate the problem.

Which version of NVDA you use?

PS. I have no plans for Ableton Live

Hello!

SIBIAC again broke down. Unfortunately, I don't catched the version of both OSARA and REAPER when this occured, because I was making only the mixing at last six months. Now I have REAPER v7.39, OSARA V2025.5.20.1936,a0bc1415 and SIBIAC V0.23p2b16. No one known plugin window not recognizes by SIBIAC. Log info contains the following:

QuoteINFO - external:appModules.reaper.AppModule.chooseNVDAObjectOverlayClasses (12:31:40.583) - MainThread (18192):
Unknown pane: 3672900 3 reaperPluginHostWrapProc

P.S.: Are you planning to connect SIBIAC to Ableton Live?

Thanks Alexey

I have Windows 11 on my primary computer, since long time.

Thanks Alexey.
The latest version is running fine and I have no problems during latest testing.

By the way, I am planning to update from Windows 10 to Windows 11 next week.  Is AZ Controller running okay with Windows 11?

Regards
Robert

There can be some processing speed "degradation" with new checks added. I re-enumerate strips FXes/sends two times instead of one (the first time when "a problem" is spotted, the second time when Cakewalk inform me something is changed). But in practice that can only happened when parameter "disappear", so not during usual operations.

I will keep in mind "integer IDs" for the next time I update the code.