buzz forums

Just a quick update to say that reverting to b40 fixes the load-time issue (both on instantiation and initial load of buzz).

richb wrote: ↑Wed Jun 26, 2024 3:58 pm 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 plugins, but only new shell plugins get scanned, but i have to instantiate the shell once.

polac wrote: ↑Sun Jul 07, 2024 10:02 am

richb wrote: ↑Wed Jun 26, 2024 3:58 pm 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 plugins, but only new shell plugins get scanned, but i have to instantiate the shell once.

Hi polac, thanks for getting back to me & no, I’m using the latest 32bit build of buzz from jeskola.net - I did just give ReBuzz a go & selected all the options to reset config just in case, and it’s similarly slow (or at least it’s been chugging away for an hour and hasn’t finished scanning yet).

Bump, some bugixes this time.

Bump, small update again.

Thank You !!

Cool update again! Thank you.

Is it possible to fix the windows flip issue occuring after closing a VST?

Hi Polac

a request about VST3 implementation:

When you send a kPolyPressureEvent to a VST3, the noteId is always -1, could you send the corresponding noteId please like with other kNoteExpressionValueEvents? Other Hosts like Bitwig handle it this way and i'm pretty sure that's the intent in the VST3 spec.

Bug report: latest f'em (tracktion) vst3 crashes on load. Latest splice instrument crashes on load.

there's v46 of PolacVST at beta dir
https://www.xlutop.com/buzz/zip/beta/

why its not posted here, is it rolled back to v45?

Sorry, I have it linked now on this forum thread. I did post this on Discord channel first to see if it fixes the issue with some vst3's. I seemed to work so it now it is here.

Latest version downloads are getting blocked by chrome for being supposedly "dangerous". I can only assume this is a false flag, but just thought I'd mention it.
ETA: Also tried in Firefox. Says it contains a virus or malware.

Mozart von Robot wrote: ↑Thu Dec 25, 2025 9:55 pm Latest version downloads are getting blocked by chrome for being supposedly "dangerous". I can only assume this is a false flag, but just thought I'd mention it.
ETA: Also tried in Firefox. Says it contains a virus or malware.

i got same with unrelated software (of mine) so it's probably a false positive. firefox said it's bad but windows 11 virus scanner didn't so i'm guessing it's a change in a browser virus scanner thing.

I don't know if this is related or useful at all, but just in case it is, there's this...

Followed by this...

I can't say I know what any of it means.

Must be false positive. Some versions ago windows defender also alarmed me with pvst(and shell2vst). I'm pretty sure i have no malware of virus on my system.

lolokimono wrote: ↑Wed Nov 26, 2025 6:55 pm Bug report: latest f'em (tracktion) vst3 crashes on load. Latest splice instrument crashes on load.

I think i have the f'em working now. Possibly also fixes the splice problem. Will upload a fixed version soon.

Edit: A really stupid old bug in my memorystream class caused the problem. It only works as long as you continously write and not using a seek in between, it messed up the memory. I think a lot of vst3 did not work and crash, arghh.