Mapping something (e.g. loop size/out) to jog wheel

To manipulate the tension you first have to adjust the following line

MappingPropertyDescriptor { path: "mapping.settings.haptic.tension"; type: MappingPropertyDescriptor.Integer; value: 50; min: 0; max: 255 }

so that it looks something like this (the name is your choice, but the first letter must be lower case):

MappingPropertyDescriptor { id: hapticTensionProp; path: "mapping.settings.haptic.tension"; type: MappingPropertyDescriptor.Integer; value: 50; min: 0; max: 255 }

Then, define a variable to store the original value:

property int storeHapticTension: 0

Then you can do the ButtonScriptAdapter:

Wire
    {
      from: "%surface%.shift";
      to: ButtonScriptAdapter
      {
        onPress:
        {
          module.encoderMode = module.treeMode;
          module.shift = true;
          // Something like this:
          storeHapticTension = hapticTensionProp.value;
          hapticTensionProp.value = 0;
        }
        onRelease:
        {
          module.encoderMode = module.listMode;
          module.shift = false;
          // Something like this:
          hapticTensionProp.value = storeHapticTension ;
        }
      }
    }

********

app.traktor.browser.list.select_up_down

This is one of those Traktor parameter that we (those that have done qml mods in the past) have scraped from the original Traktor exe file by loading it into a hex-editor and reading it. The most useful info found is usually bunched up in a few places and once you find one piece (by accident, by using good search terms or simply by browsing the text), there is usually something useful close by.

Here is a bare bones compilation (a lot you can play with):

If the RelativePropertyAdapter is not suited, you may want to try the EncoderScriptAdapter.

There is an example which is used for adjusting the Beat Grid (turn jogwheel while holding the Grid button).

 Wire
 {
   enabled: gridAdjustEnableProp.value;
   from: "%surface%.jogwheel";
   to: EncoderScriptAdapter
   {
     onTick:
     {
       const minimalTickValue = 0.0035;
       const rotationScaleFactor = 20;
       if (value < -minimalTickValue || value > minimalTickValue)
         gridAdjust.value = value * rotationScaleFactor;
     }
   }
 }

You will need to name the browser list value like this to plug it in:

 AppProperty { id: listSelectBrowserProp; path: "app.traktor.browser.list.select_up_down" }

and then you can manipulate listSelectBrowserProp.value instead of gridAdjust.value.

Btw, minimalTickValue is used to define a minimum turn speed for the jogwheel to react at all, rotaionScaleFactor defines the turning sensitivity. value is the tick count of the jogwheel (or other endless encoder) and is usually a fractional real number, as you can see when observing the used minimalTickValue.

Plug it in and play with the numbers. Enjoy! :)

Hm.

Did you make a syntax error? These things always happen to be the reason for me why things don't work. Some syntax errors don't crash Traktor, some do:

MappingPropretyDescriptor { id: hapticTensionProp; path: "mapping.settings.haptic.tension"; type: MappingPropertyDescriptor.Integer; value: 50; min: 0; max: 255; }

Wire {
  from: "%surface%.browse.view";
  to: ButtonScriptAdapter {
    onPress: {
      hapticTensionProp.value = 0;
    }
  }
}

In particular this

MappingPropretyDescriptor 

should be this

MappingPropertyDescriptor 

I am always hoping it's something stupidly simple at the root... :p

I always use copy-paste in the forum, that's why i asked.

Anyway, if you edit S4MK3.qml (the basic controller file) you can't write it like this:

"%surface%.browse.view"

%surface% is defined at the bottom of the file for S4MK3Side.qml

 S4MK3Side
 {
   id: left
   name: "left"
   surface: "s4mk3.left"
   propertiesPath: "mapping.state.left"
   topDeckIdx: 1
   bottomDeckIdx: 3
   hapticHotcuesEnabled: hapticHotcuesEnabledProp.value
 }

 S4MK3Side
 {
   id: right
   name: "right"
   surface: "s4mk3.right"
   propertiesPath: "mapping.state.right"
   topDeckIdx: 2
   bottomDeckIdx: 4
   hapticHotcuesEnabled: hapticHotcuesEnabledProp.value
 }

So, either place the wire in S4MK3Side.qml (for both buttons at the same time), or write the wire(s) like this:

Wire {
  from: "s4mk3.left.browse.view";
  to: ButtonScriptAdapter {
    onPress: {
      hapticTensionProp.value = 0;
    }
  }
}

and/or

Wire {
  from: "s4mk3.right.browse.view";
  to: ButtonScriptAdapter {
    onPress: {
      hapticTensionProp.value = 0;
    }
  }
}

See, if it works now.

Also, the EncoderScriptAdapter may have trouble making browserListSelectProp.value accept anything other than an integer. In addition, the value does not gravitate/centre around zero, with values that are not zero having an effect plus resetting the value back to zero (as with the grid adjust property). The EncoderScriptAdapter may work with addition/subtraction rather than multiplication.

  Wire {
    enabled: !module.shift;
    from: "%surface%.jogwheel.rotation";
    to: EncoderScriptAdapter {
      onTick: {
        const minimalTickValue = 0.0035;
        const rotationScaleFactor = 20;
        if (value < -minimalTickValue || value > minimalTickValue) {
          // browserListSelectProp.value = value * rotationScaleFactor;
          browserListSelectProp.value = browserListSelectProp.value + (value * rotationScaleFactor);
        }
      }
    }
  }

🦋

Once you have the MappingPropertyDescriptor in the foundation file (S4MK3.qml), you don't have to (and shouldn't) define it anywhere else (apart from the basic screen file, which needs an additional MappingProperty). Once you give it an ID, you can read and adjust it's name.value from everywhere.

The browser list property as well as the jogwheel wires are best placed in S4MK3Deck.qml. Too bad my S4 is sitting in storage or i would co-tinker to get it right.

Please post your progress... :)

I think you should keep the MappingPropertyDescriptor in S4MK3.qml. You can still access the value from all subfiles, like from S4MK3Deck.qml.

I may copy your EncoderScriptAdapter code for my own S4 once you get it fine-tuned. :)

For your information: The encoder spits out a value that is exactly zero when it isn't turned, a positive number when it is turned clockwise (exact value depends on the turn speed) and a negative number when turned counterclockwise.

That means this code

(value < -minTickValue || value > minTickValue )

simply measures if the absolute value (positive or negative) exceeds minTickValue. Not sure if that was understood. ;-)