Quite a few old machines are incompatible with the new multithreading feature and we built up a small list on BC to let everyone know which they are. To stop a machine using multithreading, you need to edit the gear.xml that can be found in jeskola\buzz\gear. The instructions are in the file, and below is my version.

Geonik 2p - typical, glitched output when more than one source connectedAutomaton EQ7 - typical, glitched output when more than one source connected

I know more, but I'll just add em as I come across them. If ppl add to this list, I'd suggest they give a simple two-three word why.

Btw, I use Simple Gain with multithreading a TON (i use all of "kibibu's stereo tools" routinely).. it doesnt have any problems (?)

Can we use wildcards in the machine name like you did for Rymix? That works? If so, I would do Rout*, Geonik*, etc. (pre buzz1.2 stuff). Most (not all) the issues seem to resolve around the input mixing method used...which will mostly affect older machines. A comprehensive list, with some reasons why.. would be very beneficial. Great thread.

EDIT: Actually it seems to affect v1 as well so I guess - <Machine Name="Matilde*" Multithreading="False"/>

Is it also possible to make individual VSTi's to permanently not use multithreading via gear.xml (I know about the 'shift' track as a temporary solution). I've got one that locks midi notes to a specific scale and when using peer machines to talk to it, and that midi VSTi to talk to another VSTi it just gives up - but if multithreading is globally disabled it works fine.

EDIT: Yes there is Pete - right click on the VST/i go to Preferences -> name of vst tab -> Untick Multithreading. Cool thanks Pete !

EDIT: Actually it seems to affect v1 as well so I guess - <Machine Name="Matilde*" Multithreading="False"/>

this file bursts immediately after loading ... no Matilde anywhere ... even without pressing play. i had multithreading disabled globally.i guess it's rather the effect combination that is responsible for this.

Weird, I don't get a burst just a crackly/robot-y noise when the second Matilde is connected. What happens if you manually create the chain - Matilde Tracker 1.9rc7 (aka Matilde Tracker 2) -> FSM Philthy -> Jeskola Raverb -> Master

Originally I did - first the philthy then raverb, then both (I first posted those being at fault before editing, then re-editing, then re-re-editing ! ) as I also thought that those were more likely to be the fault. But it wasn't until I disabled multithreading on Matilde that the problem went when creating that chain.

Weird, I don't get a burst just a crackly/robot-y noise when the second Matilde is connected. What happens if you manually create the chain - Matilde Tracker 1.9rc7 (aka Matilde Tracker 2) -> FSM Philthy -> Jeskola Raverb -> Master

Crap, sorry man I uploaded the wrong bmx last night - that one was meant for this post: viewtopic.php?p=2970#p2970 (glad you also confirm a noise burst, as that was the reason for the upload - in that topic anyway !)

Crap, sorry man I uploaded the wrong bmx last night - that one was meant for this post: viewtopic.php?p=2970#p2970 (glad you also confirm a noise burst, as that was the reason for the upload - in that topic anyway !)

oh .. i guess i mixed them up ... anyway

yes, confirmed ... no noiseburst with multithreading disabled globally, but when i enable it, the sound gets messed up when i connect the second matildeto philthy. i wouldn't call it noise burst though. it's rather a strange click-n-pop noise that replaces the original sound. when i delete raverb from the chain,the original sound reappears and the clicking is gone.

so i thought raverb has the multithreading issue. but adding <Machine Name="Jeskola Raverbdll" Multithreading="False"/> <Machine Name="Jeskola Raverbdll (Stereo)" Multithreading="False"/>to the gear.xml made no difference ... the clicking still appeared when i connected the 2nd MAtilde to philthy ?!?

Last edited by thOke on Tue Mar 20, 2012 4:58 pm, edited 3 times in total.

Cool, cheers for confirming man - the nearest I'd describe it as is being a buffer underrun, like the samples are struggling to get there quite in time so you get this metallic sound.

Edit - looks like you went through exactly the deduction process I went through last night Try disabling the multithreading just for Matilde*, it should now work fine and you can connect the second matilde to philthy.

Last edited by mcbpete on Tue Mar 20, 2012 4:59 pm, edited 1 time in total.

odd... doesn't happen here ever, and mtrk and philthy are my 2 most used machines. what you're talking about is far from a noise burst, but screwed up processing that happens when you connect multiple generators to a effect that can't handle multiprocessing.. a perfect example of this would be automaton eq-7, but most people have that disabled already in gear.xml i think.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum