I'm sorry to be replying so late to this, but I was away for a week.
The first argument to [polywavesynth] is a tag which is prepended to all
sssad-saved settings for that instance. For example,
An instance created with [polywavesynth wav1 32 1] will, when sssad-save
is called, save a list somet
I found the solution myself...after a bit of hackingIf anyone is interested, its attached (The trick was to OSCroute and get rid of the " " - space in the listbye Luigi
sssadpanel_independent.pd
Description: Binary data
Am 16.06.2008 um 19:31 schrieb Enrique Erne:hi Luigicould you pack the synth
hi Luigi
could you pack the synth in an abstraction and give it an ID as
arguemnt? then u could use the $1 as prefix for all your parameters and
sssad.
but this way you can't load a preset from the other instance. this
problem could be solved with OSC or a list for each parameter.
i.e. "synthA
Dear List
If someone also uses the great "Polywavesynth".well
i have a little weird problem..
I would like to use two of them in one patch and store and recall
presets for each of them..
lets say poly1 and poly2...
i create sssad_panel poly1 and poly2
but if i save a preset from poly1
