SynthMaker

Compiling synths

Archive · 2005 19 old posts

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

Nu Audio Science ·

Does SM compile the synth as it is being loaded by the host ? It just seems to tak a long time to load SMplugs ?

stefan ·

Nu Audio Science wrote: Does SM compile the synth as it is being loaded by the host ? It just seems to tak a long time to load SMplugs ?

The exported vst is basicly synthmaker without the editing features automatically loading one specific schematic, so the answer is yes 🙂

Nu Audio Science ·

Aaaah so its exactly the same as SE in this instance, Anybody know why the load times are so high ?

stefan ·

Nu Audio Science wrote: Aaaah so its exactly the same as SE in this instance, Anybody know why the load times are so high ?

Might be due to the tested schematic? What kind of schematic did you try? Something with lots and lots of stuff or with very little stuff? 🙂

Nu Audio Science ·

The example synth 🙂 Iguess this is something that will get faster with later versins 😉

Shifrin ·

Could be due to the time needed to calculate the wavetables for the oscs (they are DSF based aren't they?).

Shif.

stefan ·

Shifrin wrote: Could be due to the time needed to calculate the wavetables for the oscs (they are DSF based aren't they?).

Shif.

I don't know what DSF is, but they do calculate the wavetables upon loading, yes.

Tom7777 ·

It seems like SM probably includeds lots of things from the program, i think when it reaches version 1 a lot of work should be made on making it use as less stuff as possible making the exported vsti/vst smaller in file size and memory use ect.

Sk ·

I noticed the same thing too. I exported the example synth and a simple synth I made up (with 3 oscillators and the 4wheel drive organ; actually not so light 🙂 ). Both take lots of time to load in Cubase. More specifically: the first run after compiling them, the loading of cubase was slower itself; next openings were faster. But when I actually use the synth (open it in VST instruments), it takes again a tenth of seconds or so.

Shifrin ·

stefancrs wrote: I don't know what DSF is, but they do calculate the wavetables upon loading, yes.

I thought 'Discrete Summation Formula' was the 'technical' way of saying 'adding up lots of sine waves' - to make a bandlimited sawtooth, for example.

If I've got that wrong let me know 😉

Shif.

stefan ·

Shifrin wrote: stefancrs wrote: I don't know what DSF is, but they do calculate the wavetables upon loading, yes.

I thought 'Discrete Summation Formula' was the 'technical' way of saying 'adding up lots of sine waves' - to make a bandlimited sawtooth, for example.

If I've got that wrong let me know 😉

Shif.

It's probably right 🙂

infuzion ·

I wonder if having multiple layers of sub-modules could slow things down. In my Float_IF-OP-THEN-ELSE , by simply expanding the NOT ops (un-making them sub-modules) I saved 25% filesize.

Also, I imagine loading BMPs will increase file size...

ake ·

Why is that so ? Why not compile when generating the VST ? Just curious.

Åke

Shifrin ·

infuzion wrote: Also, I imagine loading BMPs will increase file size...

I'm wondering about this, if I have a knob module with a bitmap inside it does that bitmap get replicated in memory for each knob module I use? Or can SM recognise it is the same resource, and share it across all of the knob modules? Does this depend on whether the knob module is 'synchronised' or not? Just curious 🙂

Shif.

stefan ·

ake wrote: Why is that so ? Why not compile when generating the VST ? Just curious.

Åke

Because you want to relink the schematic when disabling components etc. What to be compiled is basicly a dynamic set of components, in a synth that is.

malc ·

Two issues have been raised here: file size and load time. Both we know we can reduce significantly.

As Shif suggests, each bitmap you use is replicated on disk and in memory - there is no clever stuff going on here. We have some ideas on how to sort this out so don't worry too much about it.

The biggest thing affecting load time is the calculation of the wavetables for the standard oscillators. We can get round this problem and make things much faster. Recompiling does occur too but it's pretty quick.

Tom7777 ·

Good to hear Malc 🙂

infuzion ·

Thanks for keeping these tweaks in mind malc!

Tom7777 ·

Uh, bump, basically becuase with the latest versions of SM this has got much worse to the point i cannot edit a schematic so i either have to start new projects or not use SM.

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.