(02-07-2021, 05:58 PM)Dingo Wrote: (02-07-2021, 09:17 AM)Valve Wrote: I am having the same issue - 3rd party VST plugins are detected and load, Harrison's own AVA plugins don't!
I've reinstalled several times, including an entire OS reinstall, same result; everything but AVA plugins are detected and work. I've tried a manual install of the plugins in their own folder, as well as the install script, same result. Every other plugin in my VST folder is detected and loads properly.
Hi Valve and welcome to the Mixbus Forum...
Are you running the latest build of Mixbus? v6.2.270 is the latest MB/32C release.
Also have you tried downloading the AVA package again, it was updated about Jan 16th 2021 ?
As Tassy said earlier, it really helps if you mention what OS version you are running.
(02-07-2021, 09:17 AM)Valve Wrote: No reply from Harrison support, no replies here either!
It is Sunday in Nashville... you should hear back from them real soon.
Hi!
I'm sorry to say this is quite a grim situation for me. Some more more information:
Yes, it's MB 32C 6.2.270 and I have tried several downloads of it as well as transferring the installer over from known working machine.
1) I tried Fedora 33, 3 or 4 fresh installs. It seems one problem here is that a library required for AVA Plugins doesn't exist in the Fedora 33 repos, therefore MB blacklists all the AVA plugins. To overcome that, I did a little bit of tweaking (symlinking the nonexistent libcurl-gnutls.so.4 to libcurl.so.4, look up online), and MB now finds AVA plugins.
Problem is, the plugin GUI corrupted and unsable.
2) I tried a fresh install of Ubuntu Studio.
MB here finds the plugins, problem is, the GUI is corrupted and unusable.
3) Now I tried a fresh install of Manjaro, which is based on Arch Linux. Same problem here as 1) plugins not detected, and I had to give up because it was 1am and I was really starting to go from frustration to anger.
Yes, I tried fresh downloads of the plugins too.
All the while, the majority of both the free and paid for 3rd party plugins are found and work as intended. Only the AVA plugins do not work.
In my experimentation, I therefore tried three major branches of Linux, the Fedora/Red Hat branch, Ubuntu/Debian and Manjaro/Arch, same result each time - no working AVA.
So, that leaves two common elements; MB and AVA plugins, and the hardware.
The hardware in this case isn't exactly esoteric, being a Thinkpad X230, the kind of thing Linux developers are known to use which makes it a known good choice for a portable Linux install. I need portability in this case as I have to work, using MB, on a hardware prototype, get it working well, and then use the whole setup for a technology demonstration next week.
If I don't do the demo, I could lose the contract, and myself, and my partner in this project will be in trouble, and so will the client.
Overall, I now regret my decision to use MB, or, more specifically, to weigh in for the AVA plugins as, it seems to me, and by logical deduction, they aren't ready for what would be called pro, or critical, use, possibly due to a lack of experience with LXVST.
I tried communicating with Harrison via support, no real help there, and almost like 'it works here, so you're on your own mate' and, furthermore, it was very obvious that these issues are well known already, both the licurl-gnutls.so.4 issue, and the corrupted GUI issue if you can actually get past that.
Now, what am I left to think. You will have to agree that, if MB and AVA plugins consistently don't work out of the box, on three of the most popular distros in the Linux ecosphere, including the most popular one for music production, there is a problem somewhere.
My advice is: Be Warned. Do not trust anything important to AVA plugins, at least on Linux, because you may well find yourself in trouble.
UR22, Dynaudio BM5A MKII, Pc all SSD,
