davidvj
(David Vincent-Jones)
March 23, 2023, 12:01am
1
Do all of the Midi controllers mentioned in the manual support Linux interface?
Midi is a protocol and standard. I think most midi controllers work on Linux.
1 Like
Christian-B
(Christian Bouhon)
March 23, 2023, 8:38am
3
Hello,
Personally, I use the Xtouch mini, and I’m very happy with it, it’s very customizable.
I also tried it with an AKAI of my son which was not named in the instructions, it worked very well but less practical. The sliders did not reset, it was not motorized.
I invite you to read the post on GitHub where @hannoschwalm shares his settings for the Loupedeck+
darktable-org:master ← dterrahe:focused_sc
opened 01:44AM - 09 Nov 22 UTC
This adds a virtual module (like "blending") called "focused" under processing m… odules that represents the currently focused module. Any shortcuts assigned to it will impact different modules, depending on which one you are currently working with. So you could assign one shortcut to _processing modules/focused_ with element _presets_ and use that to scroll through presets for whichever module you are working on, rather than having to define separate shortcuts for each one.
Within this virtual module, there are virtual widgets, representing all the widgets of the same type in the focused module. By assigning midi knobs to _processing modules/focused/sliders_ for example, and setting a different _element_ for each (1st, 2nd, etc) you can use the same knobs for (almost) all the sliders across all modules.
If a module contains a notebook / tabs, only the widgets in the currently visible tab are considered/counted. So this can also be used to assign the same three knobs to be used for all the sliders across the _color calibration_ tabs (although you have to make sure the module is the focused one to use this).
The notebook tabs themselves can be switched by assigning shortcuts to _processing modules/focused/tabs_. The _elements_ has generic (1st, 2nd etc) names rather than the actual tab names because of course they differ between modules.
@jenshannoschwalm maybe you would be able to give feedback?
Greetings from Brussels,
Christian
1 Like
dterrahe
(Dterrahe)
March 25, 2023, 8:52pm
4
In 4.4 it will be even more customizable; you can use a lua script to tailor its behavior in different modules. See an example here
master ← dterrahe:x_touch_mimic
opened 03:04PM - 25 Mar 23 UTC
An example script that sets up 8 mimic sliders that the x-touch's 8 knobs can be… mapped to and that will then send any moves to the currently focused module or default.
For this to be useful, the users has to set up the mappings. This can be easily done in the shortcuts dialog or via import of a shortcuts file:
None;midi:CC1=lua/x-touch/knob 1
None;midi:CC2=lua/x-touch/knob 2
None;midi:CC3=lua/x-touch/knob 3
None;midi:CC4=lua/x-touch/knob 4
None;midi:CC5=lua/x-touch/knob 5
None;midi:CC6=lua/x-touch/knob 6
None;midi:CC7=lua/x-touch/knob 7
None;midi:CC8=lua/x-touch/knob 8
Do I understand correctly that the best practice for documenting this would be in a second comment block at the top and that this would be fully shown as a tooltip in the script manager?
1 Like