thank you for the new version

Hi Mute,mute wrote: ↑Wed Oct 04, 2023 11:03 pm 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 needed), we could define the organization the way we want to? since we can't do it via folders, n whatnot anymore?
vst3 is so annoying because of these forced directories/install paths that most devs even still doing vst2 as an option....and thats what i normally grab, but it's not always an option.
Ho-Ho-Ho! ... Ja, ist denn heut' schon Weihnachten?!?Bump, new version online.![]()
![]()
![]()
polac wrote: ↑Sun Dec 03, 2023 11:13 amHi Mute,mute wrote: ↑Wed Oct 04, 2023 11:03 pm 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 needed), we could define the organization the way we want to? since we can't do it via folders, n whatnot anymore?
vst3 is so annoying because of these forced directories/install paths that most devs even still doing vst2 as an option....and thats what i normally grab, but it's not always an option.
sorry for late reply. You could use my shell2vst tool to create small regular vst2 .dlls instead of having them in all vst3 submenu. You can move them in your vst2 folders as you wish. It's to much fiddling around to have an additional submenu structure in the vst3 menu(and other shell vsts like Waveshell).
https://www.xlutop.com/buzz/zip/shell2vst.zip
Code: Select all
mklink /J vst3folder vst2folder
To narrow this down a bit:
Also instantiation of VST3 plugins seems very slow for me. Buzz startup is ~1 minute, instantiation is 30 seconds or so. Possible that's a pace/ilok thing or something, although they're fast in REAPER.
It's just cumbersome to use note expressions thoughUNZ wrote: ↑Sat Apr 27, 2024 10:01 pm 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 awesome for testing my VST3 and saves me from having to buy cubase or bitwig
one question:
the note expression "track command value" has to be 0002, it doesn't work with 0000 or 0001, is there a particular reason for this?
what is the meaning of the 0002? does it maybe mean "kNoteExpressionValueEvent" ?
hey, speculation on my part but what i know is this: IIRC, if you delete the pvst machine in machine view, the destructors are not called, because the vst is kept alive for undo purposes. i'm guessing this is why your card never frees any resources, the vst doesn't really know that anything happened, to the vst it looks like nothing happened at all. as opposed to when you switch presets, the freeing of used resources is handled internally.
Is it really often used by vsts, and can you tell a vst that use it so that i can test?UNZ wrote: ↑Tue Apr 02, 2024 1:02 am 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, VstParameterProperties label allows 64 chars, but it looks like PVST never calls this.
probably not used very often, i just assumed naively that it can't be that an entire industry ignores the limit and stomps all over host memory in the pursuit of causing buffer overflows and exploits everywhere. no matter how big you make the buffer, there's always a bigger idiot out there...i guess i was wrong and people accept all kinds of crap.polac wrote: ↑Mon Jun 10, 2024 10:42 amIs it really often used by vsts, and can you tell a vst that use it so that i can test?UNZ wrote: ↑Tue Apr 02, 2024 1:02 am 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, VstParameterProperties label allows 64 chars, but it looks like PVST never calls this.
I would say it is safe to use effGetParamName with more than 8 chars, I doubt there are hosts that do not offer larger buffers for safety. In pvst i have a buffer of 256 chars. Also most plugins don't care about the 8 chars limit either.