buzz forums

Great news!!!! :dance: :dance: :dance: Is it working with buzz machines ? Thanks a lot :D it works with 64 bit buzz machines and some 32 bit ones. i started to test the old 32 bit machines on a build about 6 months ago to see which ones worked, and i was making a spreadsheet with the results. afaik...

Might just be me, but experienced it with two interfaces (steinberg UR44 and a midiface 4x4 midi usb thing) and while using loopmidi and midi ox.

Not sure if it's intentional, but I have just spent a couple of days wondering why i couldn't get MIDI out through your midi out, and found out the problem was I had 2+2 buffers (ASYNC) set in Polac ASIO. Worked as soon as I switched back to 2 buffers (SYNC). (And by 'wondering' I mean going insane ...

There's no portable version of the latest builds, your best bet is probably to install it on another computer and copy the install directory to your work computer but I doubt it will work. Also make sure to use the 32 bit version even though you are on 64 bit windows. The latest vst wrapper (pvst) w...

The vst version works great with buzz now, takes midi inputs, and parameter learning is just as normal. Don't need the clock trick i was using as you just put the notes and parameter changes in the pattern as normal. BSP also removed the limitation of having only an instrument or an effect, both wor...

Whats the advantage compared to using the normal version and VST bridge ? not tried the bridge yet, but from the git site, its mainly that you can save patches in the daw and have multiple instances. (and put them on different cpus) i'm getting pretty frustrated i cant get the midi to work, so will...

theres a 32 bit version too now. still stuck on the midi input, but will upload a bmx with a clock buzz->vcv hack tomorrow if anyone wants it.

It's a lot of fun :) I can't manage to get it to see note and midi stuff from PVST yet, so if anyone cracks that, please let me know! By Lucky Chance I stumbled along an article in a german MusicMag. Perhaps it helps. They say for the Exchange of midi-data they used a driver called LoopMIDI by Tobi...

I've been using the VST version of this the past couple of days. https://github.com/bsp2/VeeSeeVSTRack has about 350 of the opensource modules baked into the VST, and its being (very) actively developed. You can have multiple instances, but the dev warns you shouldn't have the instrument and effect ...

I hope he answers soon, I am having trouble not making puns here.

hi, theres a few old threads on making themes in the dev section, i found http://forums.jeskola.net/viewtopic.php?f=3&t=186 and http://forums.jeskola.net/viewtopic.php?f=3&t=217 after a quick look. those might help, but i think the first thing to do is copy the folder of one of the existing ...

majkol freebase, my favourite machine to use with the preset morphing/randomization Killer machine! Shame majkol never succumbed to my constant pestering for virtual channels. That would have made it perfect. Get the sounds you want, clone freebase 7 times, solo the track you want for each machine ...

that top25 download list got reset a few years ago, just as i started releasing machines... made for a lot of fun watching my effects become the most downloaded :) anyway, dont take it too seriously because of that. as for gems gens: rymix kyriespecter, it can get stuck with some parameter combinati...

I like how no one noticed I posted a different thread requesting AM 3000 yesterday Oskari pointed this thread out to me, with code already in it!

already on it.

definitely unfinished, the parameters are ignored. anyway, working version of the above code: https://dl.dropboxusercontent.com/u/12332475/Jeskola%20AM%203000.dll edit: oh and the updated code to use the newer machineinterface.h and stereo, in case anyone is interested. https://dl.dropboxusercontent...

create a new directory in the solution folder called "Fody", move the contents of the current directory buzzgui\packages\Fody.1.YourVersionHere into it, and they edit the project's Fody.targets file from AssemblyFile="$(FodyPath)\Fody.dll" to AssemblyFile="$(SolutionDir)Fody...

good to hear

thanks!

i needed to restart visual studio to get it to work after editting the file.

edit: and i was using 1.25