Not sure how you came to the first conclusion but a live.numbox can easily work with negative integers. In my example here I've set the range to -10 25 and as you can see it handles both ends quite well.

As to precision; try pressing control while moving the mouse, that will increase precision. Don't forget that live.numbox is a Live object thus fully conforms to the standards set out in Ableton Live.

Hi ShellUser. The point is the range is only 0-255 for type Int. Even in your example where the low of the range is a negative number, the range itself cant' be larger than 255.

So if i want a numberbox to send -100 to 1000, you actually cant' do that in live.numberbox but can in [number].

To demonstrate, in your example patch, go to inspector and change the range in Range/Enum such that the lower number is -200. You will see now that the highest number on the top end it will accept is only 55.

Agreed that this is probably a limitation of Live and not Max but it seriously sucks.

Ah, yeah. Well, although a lot of languages (such as Max) use 32bit for an Integer by default, the standard value sits at 8bit and if needed can extend on it (also why some languages separate between 'integer', 'smallint' and 'bigint'). My guess is that Live itself works with 8bit integers in order to keep memory usage as optimal as possible (depending on the setup; storing 8bit numbers can take less space than storing 16 or 32bit numbers).

I think that could be the reason why a lot of Live objects utilize 8bit integer values. Another reason could be because MIDI usually doesn't go higher than 127.

But that's all speculating on my part mind you.

Good points. I can get around it by just having it output a float and putting an [int] after it. It's just a pain. More interested really in the mouse sensitivity request.