From the original SynthMaker forum (2004–2014), with its members’ names and dates.
lalo ·
Hi guys!
i think this is not properly a bug but a matter of the 'live' compilation of the SM schematic.
If you are playing a synth (i'm just playing with the example one at the moment) and while playing you switch something (for example you change oscillator waveform or turn on/off the lfo-gate) , you will hear a glitch like a very quick interruption of the sound process... is this avoidable in the SM engine?
lalo
Tom7777 ·
I doubt it, i think i asked about this before once. You can't do much about this at the moment as far as i know.
lalo ·
Tom7777 wrote: I doubt it, i think i asked about this before once. You can't do much about this at the moment as far as i know.
🙁 ohh...
i hope jorge and malc will find a way to solve it.... as i am mostly a 'live' freak, often i find myself tweakin sounds in live concerts...it's beautiful to change wavefoms while feeding the synth in complex delay lines and filters or FFT stuff (wich i do in bidule).. and i don't want that glitch...only sometimes when i like to play with...errors 😀
lalo
lalo ·
jorge any opinion? i think this is an important one. thanx lalo
stefan ·
You can switch waveforms in SM without any glitching, as long as you don't actually disconnect stuff from your schematic. Do for instance quick volume changes of oscillators instead, or change the phase distortion, or whatever, just don't use switches, because switching in and out parts of a schematic will force SM to relink the schematic. Which is a good thing most of the time, but not when you want glitch-free changes of a sound 🙂
You can probably quite easy make a modified selector module where you can choose between using a switching or a multiplying (multiply all connections but the selected one with 0.0, and the selected with 1.0, basicly) version.
lalo ·
yes i was thinkin' about this way...but this means a lot more cpu usage.. if i have a 4 waveform oscillator this means i'll have 4 active oscillator instead of just one... in my humble opinion is an issue to think about... am i wrong? thanx for the suggestion anyway stefan.
lalo
lalo ·
another idea could be to have a kind of 'filter' for that glitch.... every synth do a little pop when you switch things...but is far more un-noticeable (some mis-spelling here for sure 🙂 ) than the SM switching glitch.
thanx lalo
stefan ·
lalo wrote: yes i was thinkin' about this way...but this means a lot more cpu usage.. if i have a 4 waveform oscillator this means i'll have 4 active oscillator instead of just one... in my humble opinion is an issue to think about... am i wrong? thanx for the suggestion anyway stefan.
lalo
This does ofcourse depend on the actual implementation of choice. You could make waveforms that freely can blend between for instance sine, saw and pulse waveforms with FM and PWM on all of them by using Nildon styled oscillators with more inputs (to set the amount of "pulsiness, sininess and sawiness 🙂). It would still eat more cpu than just using for instance one saw that is "locked" etc, but not all too much methinks.
Too busy to throw a schematic together, sorry.
lalo ·
thanx stefan... don't worry i'll do my researches on the subject ..no need for a schematic from you..thanx for the offering tho 🙂 i'll analyze the nildon oscs to learn.... anyway i'd like to have an opinion from jorge too 🙂
lalo
jorge ·
lalo wrote: anyway i'd like to have an opinion from jorge too 🙂
🙂 I think you're right and we'll eventually get it right. At the moment SM does a full relinking of the code whenever you change the routing with a selector or multiplexer. The way to fix the problem is to change SM to do an initial relinking where both selections are running, one fading out and the other in and then after a short time another relink would happen to completely remove the old selection. That way you'd get rid of the clicks and would still have the current efficiency of SM where it only runs what it needs to run.
lalo ·
jorge wrote: lalo wrote: anyway i'd like to have an opinion from jorge too 🙂
🙂 I think you're right and we'll eventually get it right. At the moment SM does a full relinking of the code whenever you change the routing with a selector or multiplexer. The way to fix the problem is to change SM to do an initial relinking where both selections are running, one fading out and the other in and then after a short time another relink would happen to completely remove the old selection. That way you'd get rid of the clicks and would still have the current efficiency of SM where it only runs what it needs to run.
yes! i'm very happy you have i strategy 🙂 i was sure about it... just lemme know when you'll put your hands on it 🙂
thanx again! lalo
Tom7777 ·
Well i use switches all the time i don't know if you saw my post on how to make a shooting game but basically switches allow you to do some amazing things. Any improvements with the flow modules will make me very happy 🙂
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker