buzz forums

Bump, some bugixes this time.

Just a quick update to say that reverting to b40 fixes the load-time issue (both on instantiation and initial load of buzz). Odd, no probs here, do you use Rebuzz, there it could be take a longer time to scan but not much? It coulnd take a bit longer because i have to scan the so called shell plugi...

hi polac, is there a way i can get PVST to call effGetParameterProperties? it would be nice to get parameter names with more than 8 chars in a safe way. it doesn't feel right to just write more than 8 chars on a call to effGetParamName, but apparently many plugins do this? Anyway, VstParameterPrope...

Polac, i just wanted to say THANK YOU for implementing Note Expressions in PVST. i just discovered this on accident while trying to debug this midi stuff. it doesn't seem documented yet, but if a VST3 exposes note expressions, you can actually send them using pvst: note_expressions.png this is awes...

VST3 plugins don't show up

Hmm, here they show up,at least in pvst's own vst menu.

Hi UNZ, i'll take a look.

I tested some demo stuff I created in the former build, triggering some Polac VSTi via midi send and I had to activate "All" instead of the default "active editor" to get sound with the editor closed, but everything loaded fine. (I totally forgot that I once did it in the old ne...

In case of shell2vst, i would move the vst3shell files out of the vst2 folder at first, then use shell2vst on it and put the small stub dlls back to your vst2 folder. That way you only have one entry for each vst in you menus.

hey frank... food for thought... since vst3 is all fucking ruthless about the way plugins are installed (programfiles/commonfiles/vst3) without path installation options and what not... is the possibility you could setup like a txt or config file or some other thing where if we wanted (but not need...

Bump, new version online.

It seems Ohmforce did set their older plugins free now, just for those who are interested.

https://www.ohmforce.com/plugins

Nice, no problems yet.

Thank you Polac (EDIT 26 May 2023): working very good here in buzz x64,scanning improoved much better indeed 8-) A little bit seconds more,when loading buzz , but it is absolutely OK :!: patient... I had issues with DrumNet VSTi for example, before update in buzz64. Now the VST3 plugin running flaw...

New version online. New VST3's are detected automatically now, no more "scan shell" necessary and some bugfixes too.

Would be cool to have also a x64 vst2 version of Oatmeal, shouldn't be too much work for Fuzzpilz. No idea how to contact him though,

Tha oatmeal.dll is still from 2008, but some files in the package got updated. Didn't have some of the banks on my hd it seems, so thanks for info.

Don't know if he still sells the license, and then we had to raise enough money. My wrappers should be more stable and more comfortable than the old wrappers from Arguru(i think it was coded by him). They already can be run inside of Buzz through the vst loaders if you want to test.

Hmm well at least the rightclick popup as working then, however leftclick menu not. A preset popup is still popping up on releasing the rightclick, odd. Workareound is disabling embedded gui in the settings. Don't like it this way too. Edit: Also other leftclick popups(eg filter type) only show up i...

so i found another one of those strange GUI issues: https://dsp56300.wordpress.com/downloads/ with this, the patch browser does not open (you should be able to click on the patch name on the left and a popup menu should open, but it doesn't) also the right click menu anywhere in the GUI opens and i...

Ok, here the reliability monitor shows errors on dfx plugins too. Also some Waldorf plugins show up here. All plugins seem to get scanned successfully however. Perhaps they crash on closing or something like this.

Edit: Geometer indeed crashes on close(FreeLibrary), might be a bug in the plugin.