Hey, thanks so much for this project, it truly helps a lot and since the code is open allows for further customization.
You mentioned that the X-Touch encoders can be replaced. How exactly did you remove the original ones and put the new ones? I don't want to accidentally end up damaging my device.
BCF reports multiple Error 14 "Meaning: Invalid number of arguments (too few or too many)." while sending Sysex to device (in my case using MIDI-OX).
Anyway preset is working with Bitwig.
Script Version 1.0.7
whenever the bcf is connected and enabled in the settings, I can only write single charakters in track-names, before having to select it again by clicking.
What are possible reasons for the midi-connection interrupting keyboard typing? How can i fix this?
the 8 motorized faders are mapped to tracks 1-8, 9-17,.. When e.g. grouping tracks 1-8 , the group also gets assigned to a fader, track 8 is not longer part of the first 8 faders.
So is it possible to exclude groups from midi mapping so only my actual tracks get mapped?
Layer A of the X-touch mini will not smoothly go from one value to the next one in sequence.
It will jump to unconnected values in a repeating pattern. This behavior stops as soon as the script no longer controls the device, only layer A turn encoders are affected.
I'm experiencing this issue on Bitwig version 4.2.3 running on Windows 10, X-touch mini had the latest firmware (1.08).
This behavior can be reproduced by enabling the controller in settings automatically or manually and then using layer A to control any parameter.
Jumpy.Encoder.mp4
I have tried deleting and reinstalling the scripts both by re-extracting the zip and downloading new zips and extracting those. Versions 2.3.1 and 2.3.0 both had this issue.
Hi! Do you think you could take some time to describe quickly or make a documentation about this script? I was thinking to buy a Behringer X-Touch Mini. Thanks
API documentation says the callback of CursorDevice.addPageNamesObserver(callback) is getting a single array of strings with the names. In fact it gets the strings themselves as arguments.
The parameters of CursorDevice.getParameter(index), CursorDevice.getCommonParameter(index) and CursorDevice.getParameter(index) are normally updated when adding one of Bitwig's own devices.
However, if you add some VST device via drag-drop from the righthand Browser Panel (instead of the Plus-icon-dialog "Select content to insert into device chain") which you already saved some parameter mappings for, the parameters are not being updated after insertion. You have to first focus some other device, the re-focus the VST to refresh the CursorDevice's params. They will then continue to work correctly.
I'd like to map an Electribe's knob to some Bitwig fader but only for an specific channel. I understand CC messages have a channel associated so I should be able to do this. Is this possible?
After grouping two channels, the TrackBank contains a redundant channel for the Group Master, one before the two grouped tracks, and another one after them, while only the one before the grouped tracks is actually visible in the GUI. Opened a thread on KVR for it:
First of all, thank you for your work on the scripts, they are a great starting point for getting things to work. That said, I just got an X-Touch compact and am trying to get it to work with Bitwig. With the script from this repo it mostly works, but there are some rather annoying issues.
The knobs don't really work. When I turn them, the values they control change seemingly at random. My guess is that something with value ranges is wrong, I'll have to investigate further.
No matter how many times I try pressing SHIFT + Type/MIX keys, I can't seem to get the controller into the MIX mode as described in the documentation.
The lights in the buttons don't seem to be working at all, which makes keeping track in which mode you currently are rather difficult.
I'll keep this issue updated as I investigate further and attempt some fixes.