Just an FYI (or if you have an answer). I’ve upgraded from 3.11.0 to 3.21.1 and found that the mouse position is broken in the plugin - e.g. if I position the mouse halfway along the window, a click is actually registered to the far right of the window.
By various combinations of Cantabile (and Windows 11) DPI settings I can get this to behave better, but find that other plugins have issues.
I’ve raised as a ticket with audiomodelling.
I’m aware of this issue, as is Audio Modeling and I’m in correspondence with their QA team however since I’m in the middle of a rather large update to Cantabile I haven’t had a chance to look into it yet.
I plan to address this (see here: RFC: Removing Plugin GUI upscaling) as part of next major update and depending on what I find, I may retrofit any low-risk bug fixes back into the current series.
As a temporary work around try experimenting with Cantabile’s HiDPI modes → Tools → Options → General → User Interface → HiDPI User Interface as I believe this can help. If you find a combination that works, please post back here to help others.
Thanks Brad, had spotted that RFC and was wondering/hoping if related. I can get this right for Swam by changing those DPI settings, but always found it made other plugins unusable. Ticket is 4557 in case people their side haven’t joined the dots.
What exactly do you mean by “other plugins unusable” - do you mean they just appeared too small with upscaling disabled or something else?
Exactly that - but apologies didn’t take any notes, just tried combinations of everything. I can’t even remember what other plugins were affected.
Happy to test any early builds with the scaling code removed.
Update: I did some testing with SWAM Saxophone this morning.
This is a critical issue with the plugin that I’ve reported to SWAM. I won’t be fixing this in Cantabile (because I can’t).
I asked Claude what it thought about what I discovered:
This is absolutely terrible practice. This is a serious violation of plugin responsibility principles
Currently the only fix is to use HiDPI Mode → Enabled and Upscale Plugins.
SWAM have released an update for their sax plugin that seems to work fine in Cantabile now. Get it here.
For other plugins with the same problem, they said:
if anyone needs beta versions of any of our other products, just have them email us at support@audiomodeling.com and we’ll be happy to provide them with the latest builds.
Thanks @brad, appreciate your work on this. As keen as I am I won’t have time to check this out till next week, likewise the new show notes build (couple of shows to be ready for).
Based on a quick test all seems to be fine with the beta version.
Ugh, there’s another issue with 3.12.1 - and it also persists into 3.12.2 beta:
whenever I load a configuration of the SWAM sax (no matter if alto or tenor) using “Entire Bank”, its master volume resets to -oo and the pan resets to “full left” - that’s a nasty one!
And to add to this: this also happens when loading the rack - so it is initially completely silent for me. Something seems to be wrong with their loading a full “blob”.
@brad - maybe you can also raise this with SWAM, since you seem to have a working relationship with them?
For the moment, I’ve just deactivated my “entire bank” behavior and am fiddling with just using individual VST params, plus “rack load” bindings to initialize volume and pan, but that’s a biggie…
OK, quick addendum: I reverted back to build 4357 and re-initialized the state of the SWAM racks - now things seem to behave.
The reason for my reverting back to 4357 was initially that I had some issues with a number of my songs, with some of the racks suddenly being note-shifted, even though they received the correct notes - extreeeemely funky. Audio-Engine re-start didn’t help in these scenarios; I had to revert the song from its file, then typically it behaved.
Since reverting back to 4357, I haven’t had any such note-shifting, but I’ll be on the look-out.
So overall, my feeling is that 4359 may be a bit tooo experimental for the moment…
Ugh, this seems to be related to the fix for issues with Gateway that you reported. I’ll need to dig into this to try and understand what’s going on. Leave it with me.
Hey @Torsten
I’ve just put up 4360 which seems to fix this and Gateway still seems to work correctly. Please give it a good test on your setup with both plugins and let me know if I’ve missed anything.
Brad