what does it mean mux vsti isnt multicore compliant?

[AstralExistence]

i always loved mulab or rather, the mux but i just don't like the mulab sequencer as it has no tool icons and is sorta of barren and im not a very good typer. so im considering buying mux to use in studio one but im put off by the what i heard. that mux cant utilize multicore which is something that every vst/vsti can do as far as i know. if it cant do that, that is a huge show stopper and one might wonder why this is left out. so what is the real truth about the mux vsti.

that said, in studio one it uses hardly any cpu even on deep pads but im worried the cpu will start to become an issue as more muxes are added. if this really isnt an issue it should be made clear because, (if the developer isnt aware of this) a lot of people think mux is problematic with multicore pcs and because of this, that's why they don't buy what is a very good value for money plug.

[EvilDragon]

that mux cant utilize multicore which is something that every vst/vsti can do as far as i know

That is not quite true - there's more VST/VSTi plugins that don't utilize multicores than there are those that do.


BTW nobody prevents you from utilizing more MUX instances - depending on how your DAW handles multicores, they will be evenly spread out on the cores. So let's say you have 4 MUX instances loaded on 4 tracks - they probably won't tax only one core of the CPU, but will rather spread out to 4 cores instead.

[AstralExistence]

but i want to make sure. so need to hear that from joe.

[MuTools]

i always loved mulab or rather, the mux but i just don't like the mulab sequencer as it has no tool icons

FYI: That may change in a future version. For you're not the only one requesting this, i have been thinking of something: i could keep the current multifunctional mouse tool (the arrow) which is a single tool to do everything (and which works very well imho), but at the same time i could add a pencil, eraser, ... so users can choose what they want.

im not a very good typer.

Why would you have to be a good typer?

so im considering buying mux to use in studio one but im put off by the what i heard. that mux cant utilize multicore which is something that every vst/vsti can do as far as i know. if it cant do that, that is a huge show stopper and one might wonder why this is left out. so what is the real truth about the mux vsti. im worried the cpu will start to become an issue as more muxes are added.

MUX Vst indeed is using a single core, as many (most?) other VSTs. But i agree with EvilDragon, I don't think that's problematic as a multi-core host will automatically spread the different plugins (i.e. also multiple MUX Vst instances) to different cores. And it's especially the combination of plugins that starts putting load on modern cpu, much more than just a single plugin.

Also note that if as well the host as well many plugins (any plugins, not only MUX) are all fighting for attention of the limited cores, this 'fight' will also have a litlle bit of impact on your cpu, as there is a sub-system that has to manage all the switching between the cores and that takes cpu too!

a lot of people think mux is problematic with multicore pcs and because of this, that's why they don't buy what is a very good value for money plug.

Where are these "lot of people"? You mean here on Kvr or also on other fora? I'm surprised to read this as i don't get this MUX multi-core question a lot.

Hope this helps.

[VariKusBrainZ]

Take the OP comments with a pinch of salt, seems he has a very unstable computer and doesnt know much about working with the various software he uses and bases his comments on what hes read on the net

[AstralExistence]

edit. sorry joe.

[MuTools]

@VariKusBrainZ & @AstralExistence :

No fights here pls!
Anything insulting or too off topic will be removed.
Only constructive posts!

Thanks,

Jo