Antichambre

Why live.dial outputs value on a 'set' message, when message pass trough a js.

This error appears when the dial is set rapidly from a ctlin and via a js. and disappears when the speed lim is high

Someone can help me please, don't find any topic

Why live.dial outputs value on a 'set' message, when message pass trough a js.
This error appears when the dial is set rapidly from a ctlin and via a js. and disappears when the speed lim is high
Someone can help me please, don't find any topic


live-dial-behaviour-on-set-message

Just open input of the track for receive CC#7 volume, move the controller very fast, you will see the error!

js only send 'set' message to the dial and it ouputs the value sometimes :(((

This mades problematic cc feedback to/from my synth...

For exemple under Max4live:
Just open input of the track for receive CC#7 volume, move the controller very fast, you will see the error!
js only send 'set' message to the dial and it ouputs the value sometimes :(((
This mades problematic cc feedback to/from my synth...


live.dial does that, unfortunately, when set messages arrive too fast. It has to do with the way it is implemented into Live. It's a known issue by cycling, but considered a "design flaw" not a bug.

btw. this "set flaw" only appears with M4L not within Max...

Yes i know that now, Andrew said be that... "This one is a known problem in 617 and it will be addressed in 618"

But i already found a workaround by closing output with a gate and reopen it after a 10ms delay. Go to see if your solution is better, maybe the same ;)

Yes i know that now, Andrew said be that... "This one is a known problem in 617 and it will be addressed in 618"
But i already found a workaround by closing output with a gate and reopen it after a 10ms delay. Go to see if your solution is better, maybe the same ;)
Thank you for your reply Jan.
Bruno


Yeah! Your workaround is better No 'del', just trigger thread timing... :)

Yeah! Your workaround is better No 'del', just trigger thread timing... :)
THX


It's a bug alright - it will be fixed in Max 6.1.8

Jan, try your workaround, and it doesn't work sometimes, same problem...

Jan, try your workaround, and it doesn't work sometimes, same problem...
Mine:
BR


Live.dial behaviour on 'set' message ????