DSP Robotics Support

Because "preset string" can't be turned off, I'm trying to mess around something. I'm stuck.

So here it is.
1. Go to "osc 01" and load example1 shape.
2. From preset manager "save current unit"
3. Go to "osc 02" and "osc 03" and in each one of them - "load current unit" from preset manager.

It almost works correctly. Almost, because it turned out, that while shapes are loaded to wavetable as they should be, "preset string" requires some additional re-sending of shape paths, that were either loaded manually or via preset manager ("load program", "load all programs") when "current unit" is being loaded. Otherwise, preset itself - will save something different from what is sent to wavetable. You can see it when you "save program", or by going into "shape loader" sub-modules in osc 01-03.

I don't know how to work around it correctly.

p.s.: this "current unit" mode works perfect for regular preset values, and is used in projects in which multiple "clones" of basic idea are used.

p.s.2.: no ruby.

I run out of ideas. While I'm able to retrig or reload the path to the string preset primitive, a bug came out when switching between programs (guess some trigger order problem somewhere, or too many triggers?).

Hmm... Either it's not doable in current FS version (i.e. with current version of preset string primitive) or I'm missing something obvious or some "hidden" features. Any ideas?

hi tester here is a fixed version, not sure what was happening but it seemed to be a lost trigger problem!

I removed the preset string system you had and made it less complex and more stable



hope that helps!

...and not working, but thanks for interest.

In your solution, if you:

1. go to "osc 01" and load custom shape "example1.shp",
2. from preset manager - save individual unit setting using "save the current unit",
3. go to "osc 02" (or just else) and using "load current unit" load that saved program,
then nothing is being loaded to second unit.

Because preset string primitive can't be dynamically turned on/off from preset system (like the standard preset parameter), there is a tricky section, that treats "current unit" as unit without prefix (thus - it can be loaded anywhere; it's just a general unit); in this case - non-active units units are reset to previous state after "current unit" is loaded. While I was able to manage that one, it seems that probably (I'm not even sure if it will work) second "preset tring" should be added, to act as a buffer between preset programs (i.e. when you switch between p1, p2, p3... and so on). But this is just another "maybe".

ah righty, I misunderstood the problem! ok. now it seams to work like you asked for! well fingers crossed

what i have done to get it working is separated off your Current unit part and built it its own loading and saving system, it uses the text load and text save primitives instead of the preset text primitive. It is then fed into the path of the preset string primitives within the oscs, there is a bit of doodling done with triggers also

let me know if this is any use!


Best regards

Thanks, will check this weekend, hopefully this one works (gave me a very big virtual headache...). Quick question - what is this "Multi Trig" ruby section responsible for? Into what it can be exchanged in greens? In these old projects I'm avoiding ruby, because I don't know if it will not cause some unexpected trouble...

Hi Tester, yeh that multi trig is just something i made that takes 1 tick in and outputs three ticks simultaneously, it should be ok to just to replace it with a normal green trigger split without any problems!

it was a bit of a puzzle at first and i was getting some very weird results when working on it, like folder paths from your computer appearing out of empty string components etc! i should really try and replicate the anomalies and send a schematic into support !

lemmie know if you need any other help m8!

Thanks for explaining.

Regarding these weird folder paths. My guess is, that "sample and hold" primitive, in that particular loop setting - just remembers values "permanently" (i.e. is not reset to zero when reloading schematic). So I think this might be not a bug.

Hmm... Still not working (tested on unmodified fix).

When you go to "osc 01" and load shape ("s" button), then when you switch between programs on preset manager - that shape is fixed in "osc 01".