![]() Going by the information provided here, most of the functionality of the first two loupedeck models (both midi based) should be supported, with the following exceptions and caveats: (and Loupedeck+ but not the later non-midi devices) For rotors linked to drop-down lists, just like on the X-touch the rotor, the light goes round twice for the first 15 options only one light goes on, for the second 15 options, two adjacent lights will be on. So at the moment only the 12-dot pattern is used. It also seems to be slower, so may not be doable in real-time for each update (like it is done for the X-touch). However, configuring these is more complicated, and not yet implemented. The top row of rotors (or the only row for the BCF2000) support different light patterns (like the X-Touch Midi, with some extra options and it has 15 instead of 13 leds). Once configured in this way, button and rotor lights should all work. This is to avoid feedback loops, but for darktable it means that it blocks the adjustments sent back immediately after each rotor move. There’s also a global setting called “Deadtime” that determines how long the BCR ignores arriving messages after sending out updates. You can send it to the machine with BC Manager or (under Linux) with amidi. The easiest thing to do is to reset all encoders and buttons to their simplest settings, which can be done (for the BCR2000) using this file. The BC Manager tool (available for Windows and MacOS) can be used to configure them. These machines are highly configurable so there are many settings that could complicate the interaction with darktable’s midi module. If you map the Beatstep’s buttons to ratings, color labels or toggle buttons, they should light up when the corresponding element is switched on. ![]() If you still have problems, you could try this. If you don’t succeed switching encodings on the first attempt, you can reinitialise the input modules by pressing Ctrl+Shift+Alt+I and try again. This allows the module to determine which of the several relative encodings is used. You can do this by turning one of the encoders slowly left (down) 5 times. After startup it therefore needs to be told that the device is sending relative movements. By default the darktable midi module assumes, for unknown devices, that rotors use absolute encodings. This can be configured with Midi Control Center, available for Windows or MacOS. The recommended setting is Relative #1 for all knobs with Knob Acceleration set to Slow (Off) or Medium. ![]() ![]() Individual rotors can be configured to send absolute (0-127) values or changes (+/- 1,2,3,… in different encodings). If the drop-down has many (more than 13) items (like the blending mode drop-down), the rotor will go around twice the first time with one light on, and the second time with two adjacent lights. If linked to a drop-down (or star rating) the rotor will step one light at the time. The light rings around the rotors show a different pattern depending on whether the associated slider has a symmetrical +/- range centered around 0, 0-100 (or 0-1) or anything else. Layers A & B are somewhat supported, however, since the device does not send a notification when switching between layers, and since the updates to “hidden” rotors and lights (both under buttons and the pattern used around the rotors) are ignored, everything will only be updated completely after you press or turn something in the “new” layer. The device should be in Standard Mode (not MC). A configuration framework (possibly in lua) to support additional device-specific features is on the to do list. All other devices are treated as “generic midi” and may or may not work (well) or need some manual setup each time. The shortcut mapping system has been most extensively tested with the Behringer X-Touch Mini and contains custom code to deal with the specific features of this device. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |