Bug. live.remote~ not outputting its inputs accurately. Reproducible. Example inside.
Sonoran Music Devices
Jan 27, 2025, 2:47 PM
live.remote~ is not accurately outputting its inputs. The larger the number, the worse the difference.
The below patch clearly demonstrates this.
It really appears to be an issue with live.remote~ and not any of the other objects. You can see the signal is being printed accurately right before it hits live.remote~.
I spent a lot of time ruling out every possible setting.
It would be nice to get a confirmation before I raise a ticket.
A lot of people do not use such big numbers, but they matter a lot when doing bit packing.
Windows 11 | Live 12.1.10b2 | Bundled Max version | Intel i9-13900HX
Sonoran Music Devices
Mar 16, 2025, 12:19 AM
Here is some more information I discovered after more testing.
It seems the maximum value that live.remote~ can handle is 16,777,216. That happens to be 2^24, which is the limit of a 32-bit integer's 24-bit mantissa. Therefore, I suspect maybe live.remote~ never got its code updated to 64-bit during the time when Max was updated to 64-bit. Might be a simple fix.
Ableton reproduced the behavior. They said they will investigate further and eventually file a bug report.