JuSchu

I'm having a problem that looks like it's a bug in Max For Live.

When I move the mouse up and down very fast to change the value of a [live.dial] it shows the minimum/maximum value of 0/127 but often that's not the last value that's send through the patch chord. Instead it's a number which is just close to the actual minimum/maximum. The [live.dial] shows the correct value but when I send a bang to get the current value I still only get the wrong value which is just close to the correct one.

I managed to reproduce the bug with the following steps:

- I added a [live.dial] and a [number] and connected the two objects with a patch chord.

- I turn the dial up and down very fast. Everything is still fine. 

- I checked "Include in Presetation" for the [live.dial]. Everything is still fine. 

- I saved the patch as an amxd file. Now the error occurs.

It looks like the error really doesn't occur before you checked "Include in Presetation" and then save the file. It also only occurs with amxd files and not with maxpat files. It doesn't matter if it's and audio device, midi device or an instrument. It also doesn't change anything when you get the raw value between 0 and 1 from the right outlet.

I'm running Max 8.0, Live 10.0.1 and Windows 10.

I'm having a problem that looks like it's a bug in Max For Live.
When I move the mouse up and down very fast to change the value of a [live.dial] it shows the minimum/maximum value of 0/127 but often that's not the last value that's send through the patch chord. Instead it's a number which is just close to the actual minimum/maximum. The [live.dial] shows the correct value but when I send a bang to get the current value I still only get the wrong value which is just close to the correct one.

I managed to reproduce the bug with the following steps:
- I created a new Max For Live device.
- I added a [live.dial] and a [number] and connected the two objects with a patch chord.
- I turn the dial up and down very fast.  Everything is still fine. 
- I checked "Include in Presetation" for the [live.dial]. Everything is still fine.  
- I saved the patch as an amxd file. Now the error  occurs.

It looks like the error really doesn't occur before you checked "Include in Presetation" and then save the file. It also only occurs with amxd files and not with maxpat files. It doesn't matter if it's and audio device, midi device or an instrument. It also doesn't change anything when you get the raw value between 0 and 1 from the right outlet.

I'm running Max 8.0, Live 10.0.1 and Windows 10.


I'm having a problem that looks like it's a bug in Max For Live.
When I move the mouse up and down very fast to change the value of a [live.

[live.dial] doesn't output its minimum/maximum value after fast mouse movement