Ruby sring module always saves preset as -1

[kortezzzz]

Hi,

Tried to feed string arrays into 2 of Trog's superstring modules and noticed a very strange behavior of the preset
manager:

The first module gets values from a static text array. The second is controlled by the first, but gets values from
3 arrays that change (by a selector).
The first module (that fed by a static array) works ok with presets and save their index values, but the second one saves always (-1) as an index value, no matter what I do.
Its really driving me crazy! how that possible? and why?

attached a schematic. In the big circle you will see the loaded preset value whenever a preset is loaded.

Thanks

[billv]

Works if "lock" is selected in PM.

[kortezzzz]

Thanks Billv,

It does works in my example schematic, but unfortunately, not in my original schematic. In my original one, i'm feeding text file names in to it, so i use an array of names that comes out of the "find file" primitive. The first selector works just fine (maybe because its driven by a static array?...). the second one is driven by dynamic array that chosen in real time by the selector that controlled by the first module. and it's not works, although the string preset module has to save only a single integer... it's always -1!
saved the preset to a file and opened it, and saw that the "string" parameter that should be shown under the "value" title is too close to the preset name. and its happen only with that module's preset. Have no idea how to fix it. Tried almost any possible solution and nothing.

[tulamide]

Thanks Billv,

It does works in my example schematic, but unfortunately, not in my original schematic. In my original one, i'm feeding text file names in to it, so i use an array of names that comes out of the "find file" primitive. The first selector works just fine (maybe because its driven by a static array?...). the second one is driven by dynamic array that chosen in real time by the selector that controlled by the first module. and it's not works, although the string preset module has to save only a single integer... it's always -1!
saved the preset to a file and opened it, and saw that the "string" parameter that should be shown under the "value" title is too close to the preset name. and its happen only with that module's preset. Have no idea how to fix it. Tried almost any possible solution and nothing.

If it is an issue in a specific schematic only, chances are that it's just a slip. So you might ask one of the gurus that you trust for help by sending that schematic via pm?

[kortezzzz]

So you might ask one of the gurus that you trust for help by sending that schematic via pm?

Of course. Would love to get some help. If any of you, Gurus, are available, please PM me.

[Nubeat7]

after the input data of the second module changes with programchange you need to unselect 'new data unselects' in the properties of the second module, when 'new data unselects' it is selected it will be set to -1 always when the input data changes.

[kortezzzz]

you need to unselect 'new data unselects' in the properties of the second module, when 'new data unselects' it is selected it will be set to -1 always when the input data changes.

@Nubeat,

It works. Everywhere, except in my own project... (damn murphy low, I guess )

Something like that never happened to me before. something in my schematics refuses to store the given value into preset. What reasons would prevent the preset manager to save a simple 2 digits index value into a preset and keep returning always (-1) ??
Also have no idea whose fault it is; the preset manager? the string preset primitive? the superstring module (maybe it hates to be fed by dynamic arrays)?

[tulamide]

If every hint works in a simple schematic but just not in your project, then you made an error somewhere. Two heads (or three or four or...) are better than one. But if you can't share your schematic, try what most developers do in such a situation: Strip down your schematic bit by bit in order to locate the trouble part in your schematic.

[kortezzzz]

Strip down your schematic bit by bit in order to locate the trouble part in your schematic.

Already did it. I have only one problematic part there. other then that, everything works. The problematic part is that ruby string module that refuses to keep it's preset index value.The problems starts and ends there. maybe the ruby module itself should be tweaked, who knows...

[kortezzzz]

Finally, the problem is solved.

conclusions:

If you ever want to connect dynamic arrays to this module and make it save presets correctly, you should make sure you connect to it's string array input only a string array type output. Never send to it an array in string format (using the text primitive) or this module doesn't functions correctly with presets saving. oh, and make sure you turn on the "lock" in the preset manager properties as well.

Thanks to billv and especially Nubeat7 for helping. A new generation of gurus is rising here