live.dial step size?

ansolas · Post by **ansolas** » Sun Dec 01, 2013 4:24 pm

Hello,
lets say I have a live dial with the Range 20. 20000. and a step size of 1

If I now move it with the mouse it increments as expected by 1.

If I however tweak a know on Push it no longer increments by 1.

Is there a workaround to get fine tuning on Push working either ?

Since Push' Knobs are Encoders it should be possible, no?

Cheers
AnSolas

madlab · Post by **madlab** » Sun Dec 01, 2013 5:26 pm

Don't own Push but I guess its encoders deliver midi CC values ? (0-127)

ansolas · Post by **ansolas** » Sun Dec 01, 2013 5:36 pm

madlab wrote: I guess its encoders deliver midi CC values ? (0-127)

I don't think so. It has Encoders not Potis, so it should just in/decrement data by sending an offset,
eg +1 -1

stringtapper · Post by **stringtapper** » Mon Dec 02, 2013 1:08 am

Did you try setting the step size to 19980?

ansolas · Post by **ansolas** » Mon Dec 02, 2013 12:38 pm

stringtapper wrote:Did you try setting the step size to 19980?

no I try...

why ?

stringtapper · Post by **stringtapper** » Mon Dec 02, 2013 10:54 pm

Actually it's not called "step size" but just "Steps" in the Inspector.

And the reason is that 19980 should force the dial to increment by single integers between 20. and 20000.

ansolas · Post by **ansolas** » Tue Dec 03, 2013 9:40 am

stringtapper wrote:Actually it's not called "step size" but just "Steps" in the Inspector.

And the reason is that 19980 should force the dial to increment by single integers between 20. and 20000.

Anyways, it still jumps form 20 straight to 176

stringtapper · Post by **stringtapper** » Tue Dec 03, 2013 5:56 pm

I don't have a Push to test this. Can you make a [ctlin] object and monitor the output with a number box to see what the knob is sending?

ansolas · Post by **ansolas** » Wed Dec 04, 2013 5:41 pm

stringtapper wrote:I don't have a Push to test this. Can you make a [ctlin] object and monitor the output with a number box to see what the knob is sending?

Like this?
http://screencast.com/t/Ala7A72S95b0

I just turn the encoders clock and counter clock wise.

Looks like it just sends ~1 and ~127 depending on the tweaking speed?

stringtapper · Post by **stringtapper** » Wed Dec 04, 2013 7:22 pm

Hmm yes, now that I think about it I have run into similar problems with encoders sending values like that. I will have to go back through some patches with my controller at home to see if I ever found a solution to that.

ansolas · Post by **ansolas** » Wed Dec 04, 2013 10:03 pm

stringtapper wrote:Hmm yes, now that I think about it I have run into similar problems with encoders sending values like that. I will have to go back through some patches with my controller at home to see if I ever found a solution to that.

Thank you very much for your time !

stringtapper · Post by **stringtapper** » Thu Dec 05, 2013 7:22 pm

Well the encoders on the APC40 seem to be sending incremental values just fine. I think it might have been my Axiom controller that was giving me similar jumpy results. I'll dig it out and check.

aberkow · Post by **aberkow** » Mon Dec 09, 2013 12:27 am

The encoders on the Push are sending out float values. I've found this to be extremely annoying while patching. I haven't found a good solution yet either. However, you might try a [scale] to translate the values of 0.-127. But that didn't work for me because I wanted to "see" the value on the Push (not 0-127).

live.dial step size?

live.dial step size?

Re: live.dial step size?

Re: live.dial step size?

Re: live.dial step size?

Re: live.dial step size?

Re: live.dial step size?

Re: live.dial step size?

Re: live.dial step size?

Re: live.dial step size?

Re: live.dial step size?

Re: live.dial step size?

Re: live.dial step size?

Re: live.dial step size?