SOLVED next page
I'm trying to get OSCulator to use a variable in an OSC message from an encoder that uses Command Changes.
When I turn my encoder Clockwise it gives a velocity of 1-10 (never got it higher no matter how fast I turned it.)
And When I turn it Counter Clockwise it gives a velocity of 65-75 (Again never got it higher by turning it faster)
CW and CCW are the same command change number just with different velocities
I can very easily set a variable for the velocity and then stick it into an OSC message that will give an increasing value as I turn it faster which works perfectly.
However my problem is with the CCW turn. I need my variable to start at 1 even when it is turned CCW. Is it possible to simply do something like "var21f -64" in OSCulator? (also I need my variable to be multiplied by 2.55 for my light software. Is that possible as well)
However even if that were possible it won't fix my problem because both CW and CCW turns will trigger both variables when I turn them because they are simply picking up any velocity that comes from the specific Command Change. What I need is for my CW variable to omit sending any value higher than 64 and for my CCW variable to omit sending any value lower than 65 and then subtracting the sent value by 64, and then invert the value to the negative (Which I can do with scaling).
I don't think that scaling can fix this issue because when I tried, it just halved my numbers when I capped the scale at 64. What I need is for it to omit sending any number that's higher than a given range of numbers
edit- I have already tried demultiplexing but that simply gives me a bunch of numbers (0 to .1[CW] and .5 to .6[CCW]). I can put OSC messages on each of them which is what I did before successfully. But sometimes when I turn my encoder I will get a new value that wasn't there before and therefore has no message attached to it. I can input multiple OSC messages and increase the output number I need my software to read as the values increase from the command change; I can even start my negative output number from where the CCW value starts, but that is a manual way of doing things and again sometimes I have new values that pop up. The best solution is being able to trigger OSC messages starting at a certain value as I described earlier.
Manual solution Screen Shot 2018-02-07 at 4.33.07 PM.png
I'm trying to get OSCulator to use a variable in an OSC message from an encoder that uses Command Changes.
When I turn my encoder Clockwise it gives a velocity of 1-10 (never got it higher no matter how fast I turned it.)
And When I turn it Counter Clockwise it gives a velocity of 65-75 (Again never got it higher by turning it faster)
CW and CCW are the same command change number just with different velocities
I can very easily set a variable for the velocity and then stick it into an OSC message that will give an increasing value as I turn it faster which works perfectly.
However my problem is with the CCW turn. I need my variable to start at 1 even when it is turned CCW. Is it possible to simply do something like "var21f -64" in OSCulator? (also I need my variable to be multiplied by 2.55 for my light software. Is that possible as well)
However even if that were possible it won't fix my problem because both CW and CCW turns will trigger both variables when I turn them because they are simply picking up any velocity that comes from the specific Command Change. What I need is for my CW variable to omit sending any value higher than 64 and for my CCW variable to omit sending any value lower than 65 and then subtracting the sent value by 64, and then invert the value to the negative (Which I can do with scaling).
I don't think that scaling can fix this issue because when I tried, it just halved my numbers when I capped the scale at 64. What I need is for it to omit sending any number that's higher than a given range of numbers
edit- I have already tried demultiplexing but that simply gives me a bunch of numbers (0 to .1[CW] and .5 to .6[CCW]). I can put OSC messages on each of them which is what I did before successfully. But sometimes when I turn my encoder I will get a new value that wasn't there before and therefore has no message attached to it. I can input multiple OSC messages and increase the output number I need my software to read as the values increase from the command change; I can even start my negative output number from where the CCW value starts, but that is a manual way of doing things and again sometimes I have new values that pop up. The best solution is being able to trigger OSC messages starting at a certain value as I described earlier.
Manual solution Screen Shot 2018-02-07 at 4.33.07 PM.png
Comment