[PD] [polywavesynth] and [polygrainsynth] bug fix

Phil Stone pkstone at ucdavis.edu
Sat Nov 29 08:41:24 CET 2008


Thanks for the feedback, Mr. Off. :-)  Seriously, I really appreciate 
it.  (responses interleaved below).


hard off wrote:
> yeah getting some quite lush sounds out of this polywavesynth now.  
> says its only using 4% of my cpu as well, which is a bonus.  haven't 
> tried the grain one yet.

Fast machine!   This means you can use big voice numbers, like 64 (if 
you can find a use for that kind of polyphony).  Alternatively, you can 
throw up multiple [polywavesynth]s and/or [polygrainsynth]s, for 
polytimbral polyphony, or fattened unison voices.

> a couple of things:
>
> 1) the message box going into the sssadpanel currently contains 
> [example_presets/example1(
> but the folder is actually [Example_Presets], my system doesn't work 
> with the change in capitalization.

This is in [polywavesynth_example] -- good catch; I'll fix it on the 
next release.

> 2) it's hard to adjust the ADSR sliders at low values.  particularly 
> for attack, it is important to be able to choose values around 20ms or 
> 50ms.  so i think a log, or exponential scaling would be better for 
> the ADSR sliders.

This is such an excellent idea, I implemented it immediately (changed 
the sliders to log).  Not nearly so much shift-dragging is necessary 
now.  You have to watch out for attack/decay/release values of less than 
11 msecs. or so, though.  They can sound very clicky (although this may 
actually be desired in certain circumstances).  Again, this will be 
available on the next release; it's easy to change on your own, though, 
and it has no ill effects.

> 3) i had a look, and i can't figure out why, but it seems that the 
> global gain is still somehow affecting the sound further up the 
> chain.  ie..when i adjust the global gain, the attack of the sound is 
> also changing.  still not sure where this is coming from, but maybe 
> something connected to the adsr?

I don't understand what you mean here...the gain slider on the 
[polywavesynth] UI is interacting with the attack?  Are you sure it's 
not clipping - it's easy to clip with higher gain settings.  The more 
notes you hold down, the higher the output, so for big polyphony, you 
have to bring the slider down a bit.  If I'm totally misreading what 
you're saying here, let me know.

> 4) would be nice to have more control over the amount of panning.

Like all the controls, it's available via OSC:

[an lfo, or anything else you like]
 |
[/example/pan/position $1 <
 |
(connect to the rightmost inlet of [polywavesynth])

Similarly, you can change the pan lagtime with a message like 
"/example/pan/speed 0.8". The OSC implementation of [polywavesynth] 
(polygrainsynth works the same way) is here:  
http://www.pkstonemusic.com/polyWaveSynth.html#osc

> but yeah, there are lots of really good sounds possible with this, 
> great synth!!!

Thanks again for the excellent critique.


Phil
http://www.pkstonemusic.com




More information about the Pd-list mailing list