osc slider control help
hey new friends - i just got heavyM and i'm having a little bit of trouble getting the osc controls to work. Maybe you can help?
Here's what's going on:
* I have touchosc and heavyM setup on my windows machine, as well as protokol. protokol touch osc outputs to heavym and to protokol simultaneously via different ports
* in touch osc i made a fader, I gave it a name and made it an integer slider between 0 and 100.
* when i slide the fader, I see the named osc control send integer values from 0 to 100 in protokol
* In heavyM, I can successfully map the osc control to the opacity slider using learn mode
* This is the problem: When the fader is zero the slider in heavym is 0, this is right. When the fader is greater than 0 (1 to 100), the value of the slider in heavyM is 100.
What i want of course is each integer value sent by the touchosc fader to be represented in the opacity slider which goes from 0 to 100.
I'm not sure what i'm doing wrong. I did the tutorial and searched this forum, i'm kind of stuck. any tips?
-
ah ha floats between 0 and 1 - yep that totally works. Thank you!
1 -
Hi. This might be the issue:
Assignment settings
Each assignement you configure has a set of settings, as you can see in the assignments table of the Controls window.
For OSC assignments, you can edit:
- The Range: this setting appears on sliders or spinboxes for instance. By setting a Min and a Max, you can override the range of the interface element in HeavyM. For example if you set the range to 1 - 15 for the Thickness of the Border effect, when you move the fader you have assigned to it the values will only vary between 1 and 15 no matter how hard you move your fader!
0 -
hi - i appreciate your response. I am aware of that feature. If the opacity slider goes from 0 to 100 and my fader sends integer values 0 to 100, why would i set the range '1 to 15'. It would make more sense to send the integer value representing the slider value i wanted unless i needed to like compress values somehow (like the fader was 0 to 1000 and i needed it to be 0 to 100). In this case there's a one-to-one relationship of fader values to opacity slider values.
I've already read that page (i mentioned that in my original post) - while it's helpful in setting up the basic connection for touchosc, it makes no mention on how heavyM handles different data types -- there's not even an example in that document of sending a continuous control. So yea, what i need to know simply isn't covered in the document.
0 -
Hi all,
To control a slider precisely in HeavyM, try sending Float values instead of Integers: 0,00 will correspond to the minimum and 1,00 to the maximum (and you still get 100 steps in between these limits). By default, the "minimum value" is the minimum value of the slider in HeavyM, but you can change it with the "min" Range setting. Same for the maximum value ("max").
For instance, if I put min=0 and max=10 on a slider in HeavyM, sending 0,00 via OSC will put the slider at 0 and sending 1,00 will set it to 10.
Hope that helps! The behavior of OSC in HeavyM has changed quite a bit since HeavyM 1 (and we've also made some adjustments in the last few HM2 versions). We'll try to make the tutorial clearer with your input!
Have a nice day.
0 -
Hi Carl, you're right, we'll try to update the tutorial with more examples. You're not the first person to ask about how HeavyM 2 reacts to different Controls since we've made changes.
Have a nice day!
0
Please sign in to leave a comment.
Comments
5 comments