live.numberbox feature requests
There doesn’t seem to be a way to have live.numberbox send negative integers? The lowest an int can go is 0. You have to use float, then it goes to negative numbers, and run the output through an [int] object to convert the float to int after the fact. What a pain.
1) A regular [number] object does this easy. Why not in live.numberbox?
Another killer feature of the Max number/floatnum objects is that they change numbers faster or slower depending on where you click and drag. You can go from -100 to 100 quickly by clicking and dragging towards the left side of the box. Conversely you can go from 0.002 to 0.01 precisely by clicking and draging on teh right side of the box. Very handy. Seems that live.numberbox flies through the range the same no matter where you click.
2) Would be great to have this feature in live.numberbox too. I find myself using floatnums still in my maxforlive devices because they are so much better when using the mouse and I lose the ability to easily store the value in the live set or use Live’s MIDI mapping on them. :(
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.
-- Pasted Max Patch, click to expand. --Copy all of the following text. Then, in Max, select New From Clipboard.----------begin_max5_patcher---------- 478.3ockTEsqaBCC8YpT+GP4YtHfstVs212wzUUoMlVuEbPDSUu6p8uOR.Jz cCnsWHHebrO93X+91MQhSl6fUD+03uGGE8dmkHuMmknQCQhJ48yZo06nnBrV 4EPjL.xvc1C7x9G1pk74qHc4XCbl6C+9CoYIwG9r66tL227NKwuNdEpsBIMv 9jTLZszPLIq.eB9VCJ0hYWvzxi2HezLp79ZN8iY7o2Q9sZnmLBwThcovh+xi jWjl4M+6sabmcGI+yBiFuAocrx41XvuIadP+P3ADpCEdIxKTe5KdgZ2hBU9T fZ5xCCMGARdRCOA9rTUDPp1shTkDKJ0FIOSyrxaf5nj4F7TKCS+YGDnQExo. 5VvTNZ+AvbJaZTPiyirj.nJnbETaM.JMV4K3zftfzMzhChR3fvPscQTIQFVx ngN9nYJB4Hbu1P.wqvkVBYK+1Jbop6QkuMsKcAbjb3ujmE1gwdWdXs.4tonY uRBKHWMM7ZubelRF0.oyK1GlTZCc4+Jd8E4BknFoe5h1x8LWHLpkKPjJMK2H 8cod3AzgEBS+LsgnernqnnOrJ0Od6.9q8FVSay4wArg4u3Yy3JvxH4exMyot 8Yw4SNcEUJflWghJTUaPhG3Q7qefpa2zc7G.3+Icf. -----------end_max5_patcher-----------
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.
Forums > Max For Live