From the original SynthMaker forum (2004–2014), with its members’ names and dates.
infuzion ·
(An altered module from skOre)
I would assume that values would pass though the FloatSelect like a gate switching from one side to another (True value/False value). However, it is acting more like a piar of FloatSampleAndHolds, where the value won't pass untill the boolian is switched, or the output Float connector is un/reconnected.
Not only that, it seems somehow a 0 value got in the FloatSelect output:
This module is inside a slider. "IF this" & "ELSE" inputs are connected to the ratio of the DragY. The only ways a 0 value can get to the FloatSelect is
- somehow a value of 0.0000000000000000000000000000000000000000000001 gets passed which gets rounded to 0.0.
or
- the FloatEquals output changes to False and switches the FloatSelect before the actual value travels down the Data:Float connected to the THEN gets changed.
or (edit)
- the FloatEquals switches to True after the value 0 (or number rounded to 0) passes through to the float select. (edit end)
Repoduceable, & the 0 sneaks in when I flick the slider to 0 & away quickly everytime.
fustrating
infuzion ·
Workaround: Inserting a FloatSampleAndHold between the FloatSelect & the Data:Float will give the disired behavour. IMHO this is too much work for the way I expect FloatSelect should work.
Tom7777 ·
Its not really a bug its just that sometimes the modules name will make you think it does something a certain way but then does not when you test it, i think slightly more detailed hints/info for modules would fix this. Becuase SM is so low level some modules can be confusing, but i don't really want the way the module works to change as i have lots of stuff using it. I think that variation modules should be added though for stuff like FloatSelect which are similar but work slightly different.
infuzion ·
While I see your point Tom, it still seems to me FloatSelect is kinda mislabled &/or has incomplete info in the popup. With the SampleAndHolds, you know the value won't change until the trigger is signaled. FloatSelect does mention "flicking", but the following statement about "weither True or False" leads me to expect the values to be channeled consistantly, not just when the Boolian is changed.
So if something is a bug because of misbehaving on the part of one's misunderstanding is indeed debateable.
However, I still can't see how the 0 value sneaking in isn't a bug; according to my schamatic, any 0 should be changed to -0.5, shouldn't it?
malc ·
infuzion wrote: according to my schamatic, any 0 should be changed to -0.5, shouldn't it?
Yeah it should. The behaviour you're expecting is what is intended ie. the select just acts like a gate as you say (or at least it's supposed to).
So something is a bit odd here. Any chance you could send me your schematic and I'll have a look. I tried setting up the same thing from scratch and it works fine so something else must be coming into play.
Thanks.
infuzion ·
malc wrote: So something is a bit odd here. Any chance you could send me your schematic and I'll have a look. I tried setting up the same thing from scratch and it works fine so something else must be coming into play.
I just tested it again, & now it works (no excaping 0s). Hmmm obviously it didn't work before, maybe it got scared being sent over the inet 😉
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker