Modifiers and action on same knob - seems action comes first then modifier change

Ingyar · 2024-04-16T16:17:24+00:00

There was an error rendering this rich post.

I was working on configuring a knob (pot) to move back & forward in the track.

When i turn left from knob center, track moves (beatjumps) backwards.

Turning from center toward right moves track forward.

In the left half of the pot, turning towards the center no movement till it reaches the activation zone in the right half.

In the right half of the pot, turning towards the center no movement till it reaches the left activation range.

I managed to distinguish the zones with one modifier changing 0 when being in left half and 7 in the right half.

Direction of movement was done with other modifier changing to 7 when moving right and 0 when moving left - regardless where the pot is in the 270 arc.

Action was done when pot moves and M1=7 and M2=7 for moving forward

and pot moves and M1=0 and M2=0 for moving backwards.

Now the problem.

When i stop the pot and want to change direction, as i start turning in the opposite direction, the last action is executed one more time (step) despite the modifiers showing changed state so no condition met for that command to be executed.

IF it sound confusing here a chronological description:

Position at beginning of track
I turn knob right. After passing the 2'o clock position beatjumping occurs till i stop pot or reach end of travel
I stop pot. Want to change direction.
Start moving pot in opposite direction.
Modifiers change state, 1 beatjump forward still occurs then stops.

It seems internally the motion translates to the action binded to the pot and then changes the state of the modifiers...

Can someone confirm that?

Any workaround?

Used the same trick with jog motion and it works as it should. Stops dead at change of pot direction.

...

Experimenting on Traktor Pro V3.10.116 (DEMO) with

Xone: K2 and Novation Launch Control XL controllers on Windows 10 computer.

Find more posts tagged with

Accepted answers

All comments

Stevan

It sounds like you are trying to map the Move feature to an absolute message (0 to 127)? Encoders are much better option for this kind of controls.

Also, by uploading your mapping example you will get more replies.

My guess is that global midi control would do the trick. Split it's range into three different signals and output each one individually.

Value 0 to 62 sends CC.1

Value 63 to 64 sends CC.2

Value 65 to 127 sends CC.3

Ingyar

Here screenshots of the setting:

Screenshots for detail of the M7 and M8 modifiers.

The two move entries are obvious from the table.

M7 is for the direction - when knob moves CW its value ramps from 0 to 7 with every step.

When knob moves CCW its value ramps from 7 to 0 with every step.

To avoid the ramping and jump straight from 0 to 7 and vice versa, the rotary sensitivity is 300%

M8 is for defining in which half the pot is - 0 for left side, 7 for right.

Stevan

I understand what you are trying to accomplish and have been using the same modifier settings on Twisted Grat mapping for MF Twister.

Again, you might need to use global midi controls instead and divide the range of the midi knob because that doesn't work with an absolute message.. Controller will change the condition and trigger last value ot the move command with the same midi event.

This way you can have moving to left only when 49% going to 0% and moving to right only when 51% to 100%. Because sometimes you won't have any movement left being the message that hits 0 and 127 (not endless)

Otherwise you might need to come up with a timer (modifier in button\inc mode) so that the move command is slightly delayed from the signal that triggers a modifier.

Ingyar

Thanks for your replies Stevan.

When you mean Global Midi you mean Add > Global > MIDI Controls > Buttons/Knobs/Faders ?

From what I've red about it they are for usage toward other software/gear.

How to use that internally in Traktor? How to divide the physical control into as you suggested 3 CC's?

Logically it would seem to create 3 Global MIDI outputs, define the range via min-max and via some virtual midi port route it back into Traktor and assign to some parameter... ?

...

About the timer trick.

"(modifier in button\inc mode) so that the move command is slightly delayed from the signal that triggers a modifier."

I could not achieve something like that...

...

My combo and the logic behind it work great with just the unexpected realization that when a change occurs in the physical controller, Traktor first executes the directly tied command and then changes the state of the modifiers. So the first value change from the controller executes the action, then changes the modifiers and on the next value change the new state of the modifiers are taken into account...

...

I know encoders are better suited for what i want to achieve. Got a controller without ones and wanted to implement movement left and right as a ratchet via a knob. :)

Thanks anyway. :)

Quick links

Unanswered questions