From the original SynthMaker forum (2004–2014), with its members’ names and dates.
infuzion ·
Would a Multiplexer/Selector with a Stream-Int Index be helpful? I was thinking it would be handy for stream compares to re-route audio, or even to turn off the audio stream. I'm wondering even if the Multi-stage envelope would benefit from this.
exonerate ·
i voted yes for this 🙂 , it would be very handy. the way i see it you should be able to do what you do in the code component with just stream primatives, we have the stream compare primatives but there not very useful because theres nowhere to connect them, (although i did manage to make a square wave that used a stream compare but i had to force a connection)
so yeah if there was a selector with a poly int input, and you could also connect the stream compare to it, you would be able to do lots more things with stream primatives, you could create masks like in the code component.
also what would be really good is a stream component like the'float select' where you could connect the polybool output of the stream compare to the bool input on the 'stream select' and then this would output from either stream depending on wether the polybool input is true or false. thinking about it there lots of green maths components that i would love to see as stream components, things like a stream sine component ect...
things like these would enable you to lots more things which at the moment you can only do in the code component, i wouldn't replace my code for just stream primatives, even if that was possible, but things like a stream selector or stream select component, would be great for simple things.
cheers 😉
Tom7777 ·
I voted yes also, i dunno when i would need it but it's always handy to have stuff like that.
oddson ·
I voted Emmental because I don't get it... there's only one primitive that uses this data type (apart from the convert 'to' and 'from'). AFAIK even the code module doesn't support it. So you end up converting to it when you need to anyway so why not do any routing as a standard poly and convert right before it. Once there are other components supporting that data type it would make sense to have the selector and multiplexer support it as well.
(All of this is subject to the assumption that they don't support it now... I assume you confirmed they don't.)
EDIT - Oh the index! Now I get it...
oddson ·
OK... now that I've read the question with a little more care I would vote Gruyère.
I still don't see what it would do for you. You'd be changing input/output streams at audio rate!?
If you really want this behaviour you can code it... I don't see enough use for it to warrant primitive components (as I imagine it would be a radically different thing than the green selected versions).
For turning off the audio stream I'd assume you are dealing with duration more than a dozen milliseconds and so dropping down to green stream would be adequate.
infuzion ·
I'm wondering if the de-zipper could be re-written to help squash this bug: [old link] So, the gate wouldn't close (to move around the de-zipper) until both the values stopped changing & the de-zipper was done.
I also wonder if such a Selector could help reduce CPU for compressors, etc.
infuzion ·
Eska gave me an idea that would actually make this idea very useful: "hop" primitives, epically the expensive ones like Float Array To Poly.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker