btw, use a vst effect, and you have the hd bouncing/streaming that lots of people have been asking for!


Just did the same, been using this loader for donkeys and never given a penny so consider it gratitude rather then a bugfix bribedouble07 wrote:Yeah good call, donatedmute wrote:everyone should think about clicking on that donate button @ http://www.xlutop.com/buzz/ every once and awhile, i just did ;]
Hi, i checked the n2o plugin, the problem is that the plugin does not return proper information about it's input/output connections. However you can configure the inputs/outputs by hand in the preferences(per-plugin tab). I would say setting up two stereo inputs should work here.Tiadiad wrote:Hello, THANK YOU for the amazing work you've put into this! Love these loaders man! One thing, has anyone been having an issue with the PSP plugs, like N20 for instance? the dry signal only feeds through the left, nothing is coming out of the right speaker, not sure what is happening...
That might happen if you using the vst3 version of this plugin(if there is one). Unfortunately I had to change something which breaks projects using a vst3 plugin. In any case you have to rescan the shell plugins again via preferences->"scan shell". Then you should be able to load the plugin again in a new project, however if you have an old song not loading the plugin you have to replace the vst3shell.core found in your vst folder with the b23 version.Tiadiad wrote:Hello, ok, so I have a new problemWith the b23 loaders the Waves Kramer Master Tape plugin loaded fine, but with b24, it doesn't. Not sure what's happening. The PSP plugs work like a charm. I contacted Waves customer service, and they told me that waves products do not support Buzz hehehe, well, I guess they do, theyre just idiots. Hoping this can be fixed
Hi, thanks for the info, i'll upload an updated loader version this weekend. Works fine here so farShro0m wrote:Hello polac,
I've just noticed that if one add any machine which reports latency > 0 back to buzz, it be will compensated for (global setting in buzz).
This again seems to screws up the midi timing when using midivst.
I tested this with midivst (external gear) and adding joachips Neptune (latest version).
I had a quick chat with Oskari, who now has updated buzz with a new callback "GetTotalLatency callback".
So I'm hoping that perhaps you could update the midivst so the midi timing will be correct when using machines with latency
Anyway, thanx for your great work with PVST :]
Awesome. Thanks a bunch :]polac wrote:Hi, thanks for the info, i'll upload an updated loader version this weekend. Works fine here so farShro0m wrote:Hello polac,
I've just noticed that if one add any machine which reports latency > 0 back to buzz, it be will compensated for (global setting in buzz).
This again seems to screws up the midi timing when using midivst.
I tested this with midivst (external gear) and adding joachips Neptune (latest version).
I had a quick chat with Oskari, who now has updated buzz with a new callback "GetTotalLatency callback".
So I'm hoping that perhaps you could update the midivst so the midi timing will be correct when using machines with latency
Anyway, thanx for your great work with PVST :].
Perhaps it helps to uncheck "Embedded Vst Gui" setting in the bridge options. Btw. you can also access these options while the mouse cursor hovers over the opened vst gui and holding the Ctrl+Shift keys.boombaxx wrote:Hi i am trying to use Kontakt 5 player in buzz every time i load an instrument it just hangs and crashes buzz with vst32.exe left in the process list. When i load a multi it works fine K4 works perfectly but just bought a couple of libs from NI that need K5. I tried them in Reaper and they work fine Latest Buzz build and PVST win 7 64
Sorry, ctrl+alt was meantboombaxx wrote:ctrl shift while hovering over the vst gui does not seem to do anything. Tried various vsts