Hi @rorywalsh, thanks for your time. looking forward. So far all my generated plugins got blacklisted, although there is pvsBlur from mentioned kxstudio package, could make it somehow
Cabbage vst2 plugins get blacklisted in Ardour/Mixbus
Just looking into it now. You don’t happen to know if there is a way to run Ardour directly, without having to run the Ardour5 script? I need to attach a debugger to the Ardour process, but all attempt to run it outside the startup script are failing…
[edit] I’m going to install the version linked to kxstudio and see if that is easier to work with…
[edit] not much better there. I can attach gdb to Ardour once it’s running but the plugins seem to be already blacklisted at that stage. Hmm…
there was a discussion with tech support on Mixbus forum about how plugins get blacklisted :
RE: What happens with a blacklisted plugin?
Normal operation is:
- Mixbus creates an entry for a plugin in the “blacklist”.
- Mixbus scans the plugin.
- If the plugin completes normally without crashing or timing-out, then Mixbus removes the entry in the “blacklist” and adds an entry to the plugin cache list.
If step 2 fails ( the plugin crashes the scanner app, and/or doesn’t respond ) then Mixbus leaves the entry in the blacklist and moves to the next plugin.
As kmsaudio showed, you can clear the “blacklist” and try to re-scan plugins if you’d like to try again ( for example if you’ve downloaded a newer or older version of the plugin that might work )
Also there is a debug version of ardour on their site, although I can’t seem yet to find it there
Thank for that. I think I have it sorted now. There were some conflicts between a library Cabbage doesn’t actually need, and Ardour. Simply removing the linking of said library in Cabbage seems to have done the trick. I also fixed the issue with the examples menu not showing correctly.
Can you pull from the dev branch again and try runing the buildCabbage and installCabbage scripts? I think it should work fine now.
ok will try and message back
compiled latest commit, and now plugins don’t get blacklisted
But no sound no gui
Same was with previous version, I did the trick mentioned in Linux VST export, no GUI/no sound and it worked back then
But now it doesn’t somehow
That’s odd, in my tests yesterday the GUI was showing without any issues. I didn’t check the audio as I assumed it was working. I will try again now with a different Linux machine and see if it works for me there. I’ll let you know. Thanks for your patience!
[edit] I’m seeing the same thing are you on this machine. Let me dig a little deeper…
Hi @alikthename. Can you try again when you get a chance. It looks like I forgot to commit a change to the build script. That explains why it ran on my home PC but not my work one. I just tested and Iain McCurdy’s LoFi bit cruncher has never sounded so good 
Hi @rorywalsh, sounds nice indeed. But here’s another interesting thing. Ardour likes it so much that it won’t allow any other cabbage plugin to be found in plugin manager. It kind of “thinks” other plugins are duplicates of it. Somehow it finds out similarity in binaries. Now if I remove Lo-Fi with it’s .csd from plugins folder and put Compressor.so with corresponding .csd there, then reopen session with Lo-Fi on certain channel. In this situation Ardour/Mixbus should tell me it didn’t find the plugin, disable and grey it out. Instead DAW now puts Compressor in its place while still calling it Lo-Fi. Reaper does the same
Oh dear. That doesn’t sound good. Thanks for reporting. The thing is, they basically are the same binary, apart from their name. I’ll take a look.
I’m going to have to ask on the Ardour list. While plugin binaries are similar, they are certainly not the exact same.
what I see in carla there is an ID for every plugin and they`re different for different plugins. in case of cabbage they’re same
Hello,
with Ardour (and qtractor) from debian 10 repository and Cabbage 2.3.0 from source I had not this kind of problem (I’ve removed the “standalone” checkbox in projucer when compiling cabbage) with the plugin I’m developing (involves filters, compressors and image update on the gui from csound).
Did notice instead that with bypassed plugin (from the daw) or with csound doing nothing (basically passing input to output) there is a change in sound but I’ve a suspect that there is something in my code (not so flat bandpasses filters).
But I didn’t notice vst pluging in the black list, it’s either working or not showing gui (see projucer checkbox solution).
Ciao
Thanks @vallste. Looks like you’re right @alikthename, I just did a check here and the plugin ID is not being set. Should be a simple fix. I’ll let you know…
Should be all good now 
If anyone has a chance to try it out please let me know.
I ran into the same problem but even with the cabbage devel branch, the synths (ToneZ & my June-21) I scan with ardour and end up in the blacklist.
The thing that solved the problem was to use Ubuntu Ardour build (1:5.12.0-3) from disco repository, instead of kxstudio version.
I now can load my cabbage plugins (even without a latest cabbage build)
Shoot, so my fix only works for some version of Ardour and not others? That’s frustrating, I thought it was resolved. It’s working for me on two different Linux machines, both running Ubuntu distros and a version of Ardour I downloaded directly from their own servers.
I’m glad that you got it working, but I would rather it works Ok with all versions of Ardour. Did you try it with Reaper or Bitwig? The problem appeared there too, before I fixed the plugin ID issue. Maybe you can try them it if you get a moment. If not don’t worry about it. I don’t blame you if you prefer to have some fun with ToneZ instead
I tried with Reaper, alas both old Cabbage VST (June-21 & ToneZ with 2.1.05b Cabbage) and new (ToneZ with devel Cabbage) are loading and working fine…
No need for tears, that’s good news 