From the original SynthMaker forum (2004–2014), with its members’ names and dates.
overhishead ·
i was thinking of ways to cut down on memory and cpu (however negligible the differences would be) and came up with this:
in certain cases, is it possible to draw one gui for several modules of a multi-oscillator synth?
instead of doing the multiplexer switch with multiple mgui's, can one gui be redrawn each time that a different synth module is selected? except redrawn showing the settings and interacting with the chosen module?
with a 48 oscillator drum machine, for example, i think such technology would be useful.
for some applications, i think its wasteful to have the same exact gui copied 48 times for example, when the same exact code, appearing once, could be used over and over.
it ought to save a few bytes here and there.
thoughts?
angstrom ·
the duplicated version may use more memory, but I dont think there will be much CPU usage difference eh?
If the 'hidden' duplicates aren't refreshing then they shouldnt be much of a drain on resources.
Its certainly a lot of hassle for you to go the route you are proposing with possibly minimal benefits. How will you handle the automation for instance,
drum 1 pitch and drum 2 pitch still need to appear in the VST host as separate parameters, meaning the gains from reducing graphic modules will be losses in switching and loops.
well, perhaps I will be proven wrong here. you could do a non-musically-functional prototype to see what the load is na dif it is worth the headache.
🙂
oddson ·
I tried that with my DrawnEnvelope but it's more trouble than it's worth. Turns out getting presets to save is a major hassle. Plus, as Angstrom says there's no real CPU saving (just RAM size).
rl ·
OTOH you could save some common ressources like background bitmaps, labels, etc by defining them once in the schematic and send them using wireless transceivers where you need them. Seems a good idea to me if you need to do modifications.
Wrote something here? To have a post removed or your name hidden, write to [email protected].