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.