From the original SynthMaker forum (2004–2014), with its members’ names and dates.
NothanUmber ·
If one creates a module with a template filter input (this undefined one) and creates synchronized copies of that module the template input gets always fixed to the type one connected the first (original) instance to for all further ones. Combined with the old int->string conversion bug that leads to nasty results 🙁 (The workaround is to create separate versions for int input, string input etc. although the template concept would be a more general solution here)
Greetings,
NothanUmber
malc ·
Hi NothanUmber,
I'm not quite sure what you mean by this. Any chance you could post a pic or a schematic that illustrates this.
Also, remind me what the int->string conversion bug is - I'm sure I must know this but I 'm having a mental block 🙂
Thanks
NothanUmber ·
malc wrote: I'm not quite sure what you mean by this. Any chance you could post a pic or a schematic that illustrates this.
Hm, strange can't reproduce it now 🙁 Perhaps it was a side effect of something else that I misinterpreted. Unfortunately I saved over the old version long ago so I don't know how much I'd have to revert back. But on a "clean" field everything seems to be fine, sorry most probably false alarm...
malc wrote: Also, remind me what the int->string conversion bug is - I'm sure I must know this but I 'm having a mental block Smile
E.g. connect the Status output of the MIDI Split component to a string then you'll see nothing (using an int instead works so there seems something wrong with the conversion)
Greetings,
NothanUmber
Tom7777 ·
All paste syncronized module will have exactly the same contents so its usually best to make sets of them if they need to do slightly different things each time.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker