General
Lemur 3.03: Endless knob still broken
Started by mat on .
Sign in or create an account to join the conversation.
Dear Liine crew,
I just downloaded the latest update (3.03). Unfortunately the knob is in endless mode still broken!
Before the update the endless knob falls back to 0 every time it was touched (instead of carry on with last value).
Now that works.
The new problem appears if you touch the middle of the knob - which can happen, especially in endless mode!
Interestingly the bug depends on the physics mode(tested with iPad2 latest OS):
"none": value falls back to 0 or 3.142 (?)
"interpolate" (default!): value falls to "nan" and in some cases it even looses the curser (if you leave the finger in that situation). Thats really bad, cause now the knob is dead. The only way to reanimate it is to stop Jazzeditor - iPad sync and than to resync and send the template again. So in use or during perfomance thats a bigger problem than before!
"mass-spring": value goes mad, behaves like fast foreward or rewind...nice effect, if the direction was controllable
Well, I know that bugs can happen.... but how can you miss that during a bugfix on that object ???
And is there hope for a real fix ?
Instead of the strange behavior now, I think the endless knob should send nothing in the middle position.
Till than ATTENTION to all Sequencomat users:
Set physics of the 3 endless knobs (BPMraw, BPMfine, Position) to "none" or "mass-spring", whatever kind of behavior you prefer!
The actually moduls have set physics to interpolate... which can cause the above mentioned behavior resulting in a crash - lost of BPM control. I will update the moduls asap.
cheers
mat
I just downloaded the latest update (3.03). Unfortunately the knob is in endless mode still broken!
Before the update the endless knob falls back to 0 every time it was touched (instead of carry on with last value).
Now that works.
The new problem appears if you touch the middle of the knob - which can happen, especially in endless mode!
Interestingly the bug depends on the physics mode(tested with iPad2 latest OS):
"none": value falls back to 0 or 3.142 (?)
"interpolate" (default!): value falls to "nan" and in some cases it even looses the curser (if you leave the finger in that situation). Thats really bad, cause now the knob is dead. The only way to reanimate it is to stop Jazzeditor - iPad sync and than to resync and send the template again. So in use or during perfomance thats a bigger problem than before!
"mass-spring": value goes mad, behaves like fast foreward or rewind...nice effect, if the direction was controllable
Well, I know that bugs can happen.... but how can you miss that during a bugfix on that object ???
And is there hope for a real fix ?
Instead of the strange behavior now, I think the endless knob should send nothing in the middle position.
Till than ATTENTION to all Sequencomat users:
Set physics of the 3 endless knobs (BPMraw, BPMfine, Position) to "none" or "mass-spring", whatever kind of behavior you prefer!
The actually moduls have set physics to interpolate... which can cause the above mentioned behavior resulting in a crash - lost of BPM control. I will update the moduls asap.
cheers
mat
I am using iPad 1 OS 4.3.3 and the endless knobs in Sequencomat are working just fine!!
Weird..
Weird..
Oops wrong!!I touched the centre more precisely and the cursor dissapeared. You are right.
Sorry for that, 3.0.3 includes the fix for polar/linear mode, but the fix for endless behaviour didn't make it on time for the Apple review process of 3.0.3
The bug has been located, and the fix will be included in the next Lemur app update.
The bug has been located, and the fix will be included in the next Lemur app update.
Is it possible to limit the OSC scale for endless knob from 0 to 1 ?
Hi
Knob.x-floor(Knob.x)
MM
Knob.x-floor(Knob.x)
MM
Thanks Macciza, it works the way it is suppose to be, but the behavior of the knob is erratic, i will wait until update.
Not sure if this is now fixed, I would assume so. But I have the following problem:
I am setting endless knob
expression: foobar=x*5
foobar is send over OSC. \foobar
Lemur sends this fine, it is received correctly on the pc.
However when i send the vairable back from the pc, it is received by Lemur but then the lemur forces back to the old value it had.
It does not matter which physics i use. When i do not use the expression but directly use x it works fine.
is this a bug or a mistake in my script thinking?
I am setting endless knob
expression: foobar=x*5
foobar is send over OSC. \foobar
Lemur sends this fine, it is received correctly on the pc.
However when i send the vairable back from the pc, it is received by Lemur but then the lemur forces back to the old value it had.
It does not matter which physics i use. When i do not use the expression but directly use x it works fine.
is this a bug or a mistake in my script thinking?
Another Example.
I am scaling a normal knob, 0.5-1.0
Now I send from PC to Lemur 0.25, it still displays the knob a quarter in. Not realy expected behaviour in this case for me.
I am scaling a normal knob, 0.5-1.0
Now I send from PC to Lemur 0.25, it still displays the knob a quarter in. Not realy expected behaviour in this case for me.