oscillators that are not in use

jorge · 1 Apr 2005

hi sluggo

Unused oscillators take no processing at all. When you say that you choose between 7 oscs or just 2, I assume you're using a Selector component. The selector causes a re-linking of the machine code each time the selection changes, the state of the memory stays exactly the same, it's just the code that changes to reflect the new selection.

sluggo · 1 Apr 2005

Yes, what I'm doing right now is incorporating 2 osc modules. One module contains 2 ocs, the other module contains 7 osc. A selector is incorporated for the user to pick the supersaw or dual detune osc.

thanks

stefan · 1 Apr 2005

To simplify what jorge said: A selector picks one connection, all the other stuff connected to it stays unconnected. If you have not at any other place connected these to other parts of the schematic they basicly are removed from the schematic (not in your visual schematic, but in what is compiled by SM). It's like just putting an oscillator somewhere in a module and not connecting it to anything.

Tom7777 · 1 Apr 2005

I was wondering this also, its good to know i can have a load of oscs in a schematic and not use all the cpu 🙂

Kitchen Sink · 3 Apr 2005

Interesting. 🙂 I wondered how it works, too. This would make a good addition to the user's manual.

sluggo · 5 Apr 2005

I'm kind of confused here, not sure that we're talking about the same thing. I'm not talking about compiling a synth for different amount of oscillators, I'm talking about a finished synth where the user chooses to use either 2 or 7 oscillators. All 9 oscillators are already compiled into the vst dll.

it's just the code that changes to reflect the new selection

If you have not at any other place connected these to other parts of the schematic they basicly are removed from the schematic (not in your visual schematic, but in what is compiled by SM)

jorge · 5 Apr 2005

sluggo wrote: All 9 oscillators are already compiled into the vst dll.

Compilations are dynamic, not fixed. They happen whenever needed like when you change the choice in a selector or multiplexer. What's saved with the vst dll is not the compiled code but the schematic. When you load your exported vst in a host, it does an initial compilation to make it work at startup but it might do further dynamic, in memory compilations each time you press a switch, selector etc. Basically only the parts of the schematic required for the sound you hear are being used.

Acolmiztli · 6 Apr 2005

So are we saying that oscillators NOT in use do not take any extra CPU? So if you've got a 128 oscillator synth (for sake of argument) but only 2 of them are in use, then 126 do not have any effects what so ever on CPU consumption?

If this is true, then WOW!

stefan · 6 Apr 2005

Acolmiztli wrote: So are we saying that oscillators NOT in use do not take any extra CPU? So if you've got a 128 oscillator synth (for sake of argument) but only 2 of them are in use, then 126 do not have any effects what so ever on CPU consumption?

If this is true, then WOW!

This is true.

bones · 18 Apr 2005

Are you serious!?! That fairly rawks! I am getting quite excited about this now.

BTW - Hi, I'm BONES and I just got onto the early adopters bandwagon. You'll be sick and tired of my stupid questions before long.

stefan · 18 Apr 2005

bones wrote: Are you serious!?! That fairly rawks! I am getting quite excited about this now.

BTW - Hi, I'm BONES and I just got onto the early adopters bandwagon. You'll be sick and tired of my stupid questions before long.

I think most of us already know who you are...

I think you're a funny prick, so just be your ordinary self 🙂

bones · 18 Apr 2005

I don't recognise quite a lot of the nicknames here. i just figured it woudl be the usual suspects but its good to see a fresh batch of minds to corrupt.