Open toofunkybeats opened 2 years ago
Thanks for reporting @toofunkybeats . ~Are you trying to load VST2.x plug-ins, that is the deprecated format, or VST3?~
EDIT: sorry, missed this one:
0 plugins found - there's quite a few VST2 and VST3 plugins in the directories.
What if you try to scan a directory containing only VST3 plug-ins?
Thanks for the pointer!
Looks like it doesn't eat the folders containing the .dlls - instead I got it scan 1 plugin by pointing at a folder that contains a .vst3 file. Not used to this, as all other VST hosts I know work with the .dll folder, but at least it got me starting
unfortunately trying to load HALion 6 results in a crash:
[mixer::reset] buffers ready - maxFramesInLoop=529200, framesInBuffer=1024
[mixer::enable] enabled
[KA] Start stream - latency = 0
[KM] Device 'Giada MIDI input': 1 MIDI ports found
0) microKEY2 0
[pluginManager::scanDir] requested directories: 'C:\Program Files\Common Files\VST3\Steinberg\HALion 6'
[pluginManager::scanDir] current plug-in types: 0
[pluginManager::scanDir] 1 plugin(s) found
[pluginManager::saveList] unable to save plugin list to .\plugins.xml
[pluginManager::makePlugin] plugin found, uid=VST3-HALion 6-6ddef5-dc766d8e, name=HALion 6...
[pluginManager::makePlugin] plugin instance with pid=VST3-HALion 6-6ddef5-dc766d8e created
[Plugin] plugin initialized and ready. MIDI input params: 9793
I'll see if i have more luck with NI VSTi, but it looks like some of their plugins (like Battery4 ) only exist as vst 2.4 - at least on my system. I'll investigate.
Looks like it doesn't eat the folders containing the .dlls - instead I got it scan 1 plugin by pointing at a folder that contains a .vst3 file.
This is interesting. It might be a limitation in JUCE, the library we are using for VST support. Or maybe it is the correct way to handle VST3 plug-ins, by keeping the dll files in their .vst3
folder.
unfortunately trying to load HALion 6 results in a crash:
Is it 100% reproducible every time you load it?
Also I see this one:
[pluginManager::saveList] unable to save plugin list to .\plugins.xml
it means the list of scanned plug-ins can't be saved. Are you running Giada inside a read-only directory?
No, definitely writable. i started testing with giada 0.20 - it looks like once I made it recognize a VST instrument, it won't save any configuration any more.
I started giada.exe from a terminal to make sure the current working directory is correct. It only saves if I didn't scan for plugins. Once I scan, it won't save settings any more.
Is there a way to get more detailed logs out of the application?
No, definitely writable. i started testing with giada 0.20 - it looks like once I made it recognize a VST instrument, it won't save any configuration any more.
All configuration files? The list of scanned plugins and the giada.conf
file?
Is there a way to get more detailed logs out of the application?
What you see is the current maximum log level. You have to step through a debugger if you want to dig deeper.
No, definitely writable. i started testing with giada 0.20 - it looks like once I made it recognize a VST instrument, it won't save any configuration any more.
All configuration files? The list of scanned plugins and the
giada.conf
file?
yes. I can save any configuration, but only by exiting giada before scanning for plugins. After that, no config gets saved (which also means, plugins.xml can never contain more than just an empty xml node).
Is there a way to get more detailed logs out of the application?
What you see is the current maximum log level. You have to step through a debugger if you want to dig deeper.
Hmm... i don't have devtools installed on my system. I might kindly ask to log exceptions in the future :) that might help troubleshooting without having a debugger (or knowing how to use it).
yes. I can save any configuration, but only by exiting giada before scanning for plugins. After that, no config gets saved (which also means, plugins.xml can never contain more than just an empty xml node).
The configuration file is saved when you quit Giada: if it crashes -> no clean quit and so the configuration file is not saved.
I might kindly ask to log exceptions in the future :) that might help troubleshooting without having a debugger (or knowing how to use it).
This is a good idea! Also we should make plug-in crashes less "damaging" - maybe running them in a separate process? Needs investigation.
Environment
Describe the bug This might be related to #512, the behaviour is very similar - i didn't check with an older version (yet) though.
Basically i can't find a way to get giada to recognize any VST plugins.
To Reproduce Steps to reproduce the behavior:
Expected behavior
Screenshots
Additional context Please advide if you need more information