eriser / protrekkr

Automatically exported from code.google.com/p/protrekkr
0 stars 0 forks source link

Synthesizer Issues and thoughts #5

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

The synthesizer is excellent but there are a few minor problems, some of
them we've discussed before but I'll talk about them in case you don't
remember. I've looked at the code but I'm not a programmer yet, once I
learn more I'd like to help develop this though. 

Env 1 always modulates Osc 1 volume by 100%. This can be affected by the
modulation sliders but still remains so. For example if the Env 1 -> Osc 1
modulation slider is set to zero then the modulation still occurs. One
possible fix for this could be to have the synth initialize the modulation
settings for the connection at 0 instead of 1, I noticed everything else
initializes at 0, but I don't have the skills to really tell. 

The same as above applies to Env 2 -> Osc 2 volume.

Also the synth is tuned 2 Octaves too low, what plays at C4 (middle c)
should play at C2.

One last problem is that the LFO modulation of pitch doesn't really
modulate the pitch. This I'm a little hazy on it's been a while since I
checked and I'm not in front of it right now but I'll check it and let you
know for sure what it was.

And I don't know how hard it would be but it would be really nice to be
able to automate synth parameters from within the patterns. There's a bunch
of parameters but one way of doing it would be to maybe have a way of
setting which effect call applies to what parameter, a way of assigning it,
this way you could have a patch where you could tell it to modulate the
envelope decay time or the filter cutoff or resonance. You could have
maximum flexibility with only a few added pattern effect calls added. I'm
picturing something like the way you choose a filter, maybe in the globals
slider section you could choose it or even just from the pattern itself. 

Original issue reported on code.google.com by theorize...@gmail.com on 1 Dec 2009 at 4:57

GoogleCodeExporter commented 9 years ago
the easiest way to see what's going on with the envelopes is set envelope 1 to
modulate both osc 1&2 at 100% and envelope 2 to modulate osc 2 at 0%, set the 
sustain
on env 1 to 100% and on env 2 to 0%, then the decay on envelope 2 to around 
50%. Make
sure the two oscs are a bit detuned and both on saws helps. you should hear the
phasing go down to nothing as the second osc lowers down to nothing and you're 
left
with just osc 1. funny thing is if you set env 2 to like 1% then you don't even 
hear
osc 2 at all.. I think part of the problem is that a modulation of 0% defaults 
it to
100%. 

Sorry about that the LFO's seem fine now I probably didn't have the sustain up 
on the
envelope or something.

Original comment by theorize...@gmail.com on 1 Dec 2009 at 4:45

GoogleCodeExporter commented 9 years ago
What did you expect exactly ?
The ENV to OSC coefficient are modifying (multiplying) the values of the ADSR
carriers so having values of 100% = (carrier value*1.0) which is a harmless
operation, the 0% positions are like "off" positions since they're translated 
to 1.0.

Original comment by hhhikr@gmail.com on 15 Dec 2009 at 5:58

GoogleCodeExporter commented 9 years ago
I expect to just hear a buzzing of the oscillator if I turn of the amp envelope
routing to it, not the envelope modulating it full on. It's like a hardwired
architecture fighting a semi-modular for control. 

Original comment by theorize...@gmail.com on 17 Dec 2009 at 10:56

GoogleCodeExporter commented 9 years ago

Original comment by hhhikr@gmail.com on 21 Mar 2010 at 10:12