Lounge Lizard/Chromaphone (AAS) stopped working with wine

[FeedTheCat]

Hi guys,

The 32-bit versions used to work really well with Linvst, but recently they started crashing. Spent the last few hours trying to fix them, no luck though. Does anybody here have them running?

[4duhwinnn]

I got the 'lite' bundle as a freebie from Plugin Boutique
awhile back, but hadn't installed it yet. So I installed it
in Ubuntu Studio 19.10 in wine-staging 5.12 and to make a long story short, terminal output showed that AAS didn't like something about the path to it's support data:

/home/you/.wine/drive_c/users/you/Application Data/Applied Acoustics Systems

If there are older versions in there, it may be a problem, so move them out.
And of all the weird things, the AAS plugin .dll's had their permissions
for 'execute' set to 'nobody'. (maybe that was my fault for using the
all-root Puppy linux for file transfers at times, but I can't confirm that,
as the other permissions would also have been root, if affected by Puppy)

So I made sure the data folder permissions were OK, they were, and changed permissions on the plugins to allow useage, and then they all opened up ready for action. That is in reaper 5.9.
Good luck!

[FeedTheCat]

Originally Posted by 4duhwinnn

I got the 'lite' bundle as a freebie from Plugin Boutique
awhile back, but hadn't installed it yet. So I installed it
in Ubuntu Studio 19.10 in wine-staging 5.12 and to make a long story short, terminal output showed that AAS didn't like something about the path to it's support data:

/home/you/.wine/drive_c/users/you/Application Data/Applied Acoustics Systems

If there are older versions in there, it may be a problem, so move them out.
And of all the weird things, the AAS plugin .dll's had their permissions
for 'execute' set to 'nobody'. (maybe that was my fault for using the
all-root Puppy linux for file transfers at times, but I can't confirm that,
as the other permissions would also have been root, if affected by Puppy)

So I made sure the data folder permissions were OK, they were, and changed permissions on the plugins to allow useage, and then they all opened up ready for action. That is in reaper 5.9.
Good luck!

Thx for the answer, tried going back to wine 5.12 (from 5.22) and it works again. Hasn't really happened to me yet that a wine update makes a plugin stop working. Wonder if I should report this somewhere...