Dan Nigrin

I'm using a live.numbox, with type set to enum, and with 642 values defined in its Range/Enum section. When I mousescroll the object, I don't get all values, but even with the Command key pressing down to invoke more precise mouse control, I still can't select all values. Is this a limitation of the object, and if so, any suggestions for another MFL object I could use?

I'm using a live.numbox, with type set to enum, and with 642 values defined in its Range/Enum section.  When I mousescroll the object, I don't get all values, but even with the Command key pressing down to invoke more precise mouse control, I still can't select all values.  Is this a limitation of the object, and if so, any suggestions for another MFL object I could use?

I'm using a live.numbox, with type set to enum, and with 642 values defined in its Range/Enum section.  When I mousescroll the object, I don

live-numbox-resolution-for-mouse-control

hey Dan I've had issues with live patches recently, do you have an example to post? not sure if it matters but possibly doubling up scripting names might mess with things if you have multiple numboxes with the same name or order? are you doing any other configuration like tying that to a dial or something similar? have you tried the scale patcher along with the dial or numbox? or maybe it's just buggy in general.

No complex patch necessary. Just start with an empty patcher, create a live.numbox object, fill it with 600+ values in its enum section, and you'll see the behavior. Here you go anyway:

No complex patch necessary.  Just start with an empty patcher, create a live.numbox object, fill it with 600+ values in its enum section, and you'll see the behavior.  Here you go anyway:  

Hey Dan, I'm on Max 8, and admittedly, I've been having major issues with Max. Just today I could not open any patcher without live crashing, even an empty one on an empty set. I just reset Max4Live by deleting the Cycling74 folder. Now I can open a patch. I tested yours and everything seemed to work fine and I got to 630 no problem, starting with the note time values.. I suspect there's some other freggin horrible bug somewhere around Max4Live and dial patchers? Or something bigger? It just feels so sketch to me even though I got yours to work..

First, I'm only working in Max, even though I'm using a MFL object in my patch. Second, were you able to scroll with your mouse through 

First, I'm only working in Max, even though I'm using a MFL object in my patch.  Second, were you able to scroll  with your mouse through all the text-based values at the beginning?   

Hey yes I was able to scroll through all the text based values and number values with no problem.. however I have seen dials that behave really weird sometimes like, barely able to move them at all!!

Interesting, thanks - not sure what's going on for me then...

Bumping this thread back from the dead with the same question. Did you ever find an answer?

it is mouse to live.numbox or other live gui objects that do not

work as one would expect with that many values.

128 steps is maximum resolution for mouse control.

maybe restriction because of automation ?

live.numbox resolution for mouse control?