[img align=c]http://www.sensomusic.com/forums/upload ... trol-2.JPG[/url]
http://www.sensomusic.com/forums/uploads.php?file=GAINCONTROL2.pat
Attached is an image & an example of a slightly different approach. I didn't like the "feel" of the increments/decrements, it felt like the speed was out of control.
So... On this patch...
- a click on the left half of the button increments or decrements by your inc/dec value
- a double-click on the left half of the button increments or decrements by a bunch of your inc/dec values
- holding the right half of the button scrolls smoothly
Try it out!
Very helpfull, thanks a lot. Although y created a similar patch that suites my needs.
http://www.sensomusic.com/forums/uploads.php?file=GAINCONTROL2.pat
Attached is an image & an example of a slightly different approach. I didn't like the "feel" of the increments/decrements, it felt like the speed was out of control.
So... On this patch...
- a click on the left half of the button increments or decrements by your inc/dec value
- a double-click on the left half of the button increments or decrements by a bunch of your inc/dec values
- holding the right half of the button scrolls smoothly
Try it out!
Statistics: Posted by Ariajazz — 10 Aug 2016, 04:11
]]>
http://www.sensomusic.com/forums/uploads.php?file=GAINCONTROL2.pat
Attached is an image & an example of a slightly different approach. I didn't like the "feel" of the increments/decrements, it felt like the speed was out of control.
So... On this patch...
- a click on the left half of the button increments or decrements by your inc/dec value
- a double-click on the left half of the button increments or decrements by a bunch of your inc/dec values
- holding the right half of the button scrolls smoothly
Try it out!
Statistics: Posted by shawnb — 26 Jul 2016, 04:18
]]>
]]>
If you need one decimal value, then your inc/dec must be 0.1 and your fader precision must be x.x.
If this doesn't work, we may need to do the math & range check completely outside of the fader control. Then we can clip it & provide full control PRIOR to setting the fader value.
It is exactly what I did but I wonder why it does not work for DECREASING. It does the job for INCREASING the values as it stops at the maximum value.If this doesn't work, we may need to do the math & range check completely outside of the fader control. Then we can clip it & provide full control PRIOR to setting the fader value.
Here is the patch
http://www.sensomusic.com/forums/upload ... ontrol.pat
Statistics: Posted by Ariajazz — 25 Jul 2016, 15:30
]]>
If this doesn't work, we may need to do the math & range check completely outside of the fader control. Then we can clip it & provide full control PRIOR to setting the fader value.
Statistics: Posted by shawnb — 25 Jul 2016, 07:15
]]>
http://www.sensomusic.com/forums/upload ... tled-2.jpg
Statistics: Posted by Ariajazz — 25 Jul 2016, 05:38
]]>
]]>
The above shows the technique I described above.
A couple of notes:
- The clock was a little more versatile, you can adjust the speed by changing the interval
- Note that since it will keep incrementing whenever the curr value <> the max value, you do have to pay careful attention to some of the fader values. I set the Fader "inc/dec val" to 1 and the Fader "precision" to integer. That way you know you won't get a value of 127.35 or smoething like that, which will just cause another cycle thru from min to max.
Hope this makes sense...
Statistics: Posted by shawnb — 25 Jul 2016, 03:57
]]>
Use my module !
I'm using USINE STAGE. I downloaded your modules pack but I cannot get them seen by USINE STAGE. 5.80. OK with Hollyhock but don't know how to use itStatistics: Posted by Ariajazz — 25 Jul 2016, 03:41
]]>
]]>
You gotta think these things thru logically...
The first step is to figure out the rule. You ONLY want the button to increment the fader if the fader value < the max, correct? That's the rule.
So there are probably many ways to do this, but here is one way:
Add an AND logical module between the button & the Pass module above
Add a 'not equal' (<>) logical module after the Fader
Fader value => Not Equal A inlet
Fader max => Not Equal B inlet
Button mouse down => AND A inlet
Not Equal out => AND B inlet
AND out => Pass Flow pass inlet
and, of course, remove the existing Button mouse down connection to the Pass Flow pass inlet
As long as the fader value <> max, there will be a '1', or TRUE coming from the Not Equal <> module.
The AND between the button & the fader will thus only work when this is so. When the fader value = max, the Not Equal will return FALSE, or 0, and the Pass will withhold the flow.
Hope this helps,
I tried this several times and checked if i was doing something wrong but did not work. Could you please show a diagram with the modules involved in the patch?The first step is to figure out the rule. You ONLY want the button to increment the fader if the fader value < the max, correct? That's the rule.
So there are probably many ways to do this, but here is one way:
Add an AND logical module between the button & the Pass module above
Add a 'not equal' (<>) logical module after the Fader
Fader value => Not Equal A inlet
Fader max => Not Equal B inlet
Button mouse down => AND A inlet
Not Equal out => AND B inlet
AND out => Pass Flow pass inlet
and, of course, remove the existing Button mouse down connection to the Pass Flow pass inlet
As long as the fader value <> max, there will be a '1', or TRUE coming from the Not Equal <> module.
The AND between the button & the fader will thus only work when this is so. When the fader value = max, the Not Equal will return FALSE, or 0, and the Pass will withhold the flow.
Hope this helps,
Statistics: Posted by Ariajazz — 22 Jul 2016, 05:49
]]>
check the Oli_Lab module pack on the addon page
cheers.
Statistics: Posted by oli_lab — 01 Jul 2016, 10:11
]]>
The first step is to figure out the rule. You ONLY want the button to increment the fader if the fader value < the max, correct? That's the rule.
So there are probably many ways to do this, but here is one way:
Add an AND logical module between the button & the Pass module above
Add a 'not equal' (<>) logical module after the Fader
Fader value => Not Equal A inlet
Fader max => Not Equal B inlet
Button mouse down => AND A inlet
Not Equal out => AND B inlet
AND out => Pass Flow pass inlet
and, of course, remove the existing Button mouse down connection to the Pass Flow pass inlet
As long as the fader value <> max, there will be a '1', or TRUE coming from the Not Equal <> module.
The AND between the button & the fader will thus only work when this is so. When the fader value = max, the Not Equal will return FALSE, or 0, and the Pass will withhold the flow.
Hope this helps,
Statistics: Posted by shawnb — 01 Jul 2016, 06:17
]]>
]]>
Thanks in advance.
Statistics: Posted by Ariajazz — 25 Jun 2016, 07:41
]]>
]]>
Statistics: Posted by nay-seven — 19 Jun 2016, 12:15
]]>
]]>