From the original SynthMaker forum (2004–2014), with its members’ names and dates.
McBarGig ·
Hey all. I have created a simple interface that you can place your effects into and select different positions for them. There is a a ton of improvements that can be made. And I also have a question about it. Instead of using Multiplexors, someone here created a "Fast Multiplexor Demo", not sure who that was off hand, but anyways I was wondering if Multiple Selectors used in the way they are in this OSM are actually any better than using a single multiplexor? Like what is the difference between the two?
So, the only thing left on this is being able to block when someone has selected the same effect twice in different locations. So for example, I select a delay in slot 1, and then select a delay again in slot 2, this Schematic does not allow for that as there is only a single copy of the delay.I did this this way because of the code size limit error...Otherwise I would have just had multiple copies of the same set of effects for each of the three slots.
Don't mind the messy schematic guys...
McBarGig ·
Man is that ever perplexing...
How the heck can you get that code to block multiple selections of the same effect....?? Perhaps a re-write is in order?
KM
philter5 ·
hey man i got the same problems here. i´ve downloaded your osm and tried some ways but it wasn´t that easy
as i thought first. another thing i noticed is that the rack module sometimes change their positions.
but, here is what i´ve done so far. i´ve added a message box if you select the same fx two times.
McBarGig ·
I think I got it, Yeah you're right this really isn't easy. I ended up making like a Case select type thing to detect when there are 2 values selected that are equal..I'll upload in a couple mins..
KM
McBarGig ·
OK So there is still more work to be done, and I think this can be done a lot more elegantly. It would be nice to have actual code that does a Case Select/Switch function. Where you could just send it a delimited list of selection, it sends back true if a double selection is present.
Also that MsgBox function is really good! I think you are basically doing the same thing as me, except when an effect is selected twice this code routes the signal into a bypass..
Anyways here is it and once again sorry about the mess..
McBarGig ·
I just created a second one of these using Multiplexors and I got a 20% CPU Usage drop. So, in this situation, 90 Selectors are more expensive on CPU than 9 Multiplexors.. I don't know at which point a selector is better to use than a Multiplexor, but definitely in this situation I would suggest you use Multiplexors and get rid of the selectors..
KM
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker