Behringer MIDI X Touch Mini controller #118
Replies: 13 comments 2 replies
-
MIDI control of Jamulus is possible. I tried it with a different MIDI controller and it works pretty well (jamulus sliders move, LEDs change). x-touch mini has endless rotary encoders, I'm not sure yet if that's an issue with Jamulus. FYI the midi flow is: Things need to be started/connected in proper sequence, so it's a bit tedious to do manually. Edit 12/1/21: a2jmidid mentioned above seems to negatively impact audio, instead of a2jmidid, start jack with "-X raw" option and it will capture midi devices and present as jack ports. Instead of patchage, for midi patching I am using a python script with the mididings package (in jambox-project repo) to automatically patch, and process midi events, Most other apps which use midi are using alsa instead of jack, so the "-X raw" jack argument should only be used for Jamulus or other app which needs midi as a jack port. |
Beta Was this translation helpful? Give feedback.
-
@jazzjohn27 I posted Jambox release v1.5.0-b.1 under "releases". Support for x-touch mini should be plug-and-play (other MIDI controllers would require a config string at least). This turned out to be a bit more complex than I expected, because x-touch mini buttons produce note on/off messages, and Jamulus requires control change messages. This required introducing a software layer between the them to toggle a button state and send control change messages to Jamulus, and LED feedback to the x-touch mini. The result works quite nicely. I made the slider control ALSA master volume. If you switch to layer B, the knobs control pan, and the slider controls ALSA capture level. Please check it out and let me know what you think. |
Beta Was this translation helpful? Give feedback.
-
Kevin,
Wow!
I will test this out during the coming week and let you know.
Thank you so much.
John
…On Sun, Nov 28, 2021, 5:07 AM Kevin Doren ***@***.***> wrote:
@jazzjohn27 <https://github.com/jazzjohn27> I posted Jambox release
v1.5.0-b.1 under "releases".
Support for x-touch mini should be plug-and-play (other MIDI controllers
would require a config string at least). This turned out to be a bit more
complex than I expected, because x-touch mini buttons produce note on/off
messages, and Jamulus requires control change messages. This required
introducing a software layer between the them to toggle a button state and
send control change messages to Jamulus, and LED feedback to the x-touch
mini. The result works quite nicely. I made the slider control ALSA master
volume. If you switch to layer B, the knobs control pan, and the slider
controls ALSA capture level.
Please check it out and let me know what you think.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#118 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATYSSTYMJUXE7TCBTY6FRZ3UOIEQXANCNFSM5H3CX22A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
I used this image:
https://github.com/kdoren/jambox-pi-gen/releases/download/v1.5.0-b.2/image_2021-11-20-Jambox_pi-gen_v1.5.0-b.2.zip
Pi boots, Jamulus runs, but the Mini does not control sliders or buttons. I
am probably missing something.
…On Sun, Nov 28, 2021 at 5:07 AM Kevin Doren ***@***.***> wrote:
@jazzjohn27 <https://github.com/jazzjohn27> I posted Jambox release
v1.5.0-b.1 under "releases".
Support for x-touch mini should be plug-and-play (other MIDI controllers
would require a config string at least). This turned out to be a bit more
complex than I expected, because x-touch mini buttons produce note on/off
messages, and Jamulus requires control change messages. This required
introducing a software layer between the them to toggle a button state and
send control change messages to Jamulus, and LED feedback to the x-touch
mini. The result works quite nicely. I made the slider control ALSA master
volume. If you switch to layer B, the knobs control pan, and the slider
controls ALSA capture level.
Please check it out and let me know what you think.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#118 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATYSSTYMJUXE7TCBTY6FRZ3UOIEQXANCNFSM5H3CX22A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
@jazzjohn27 That image should be plug and play with x-touch mini with default settings. I used x-touch mini in its out-of-the-box default setup (channel 11, not in mackie control mode). If you have made any changes (which I think can be done using behringer windows app), it might not work the same. Try the following command, it should show midi hardware devices: "amidi -l | grep hw:"
also, with jamulus running: "ps aux | grep midi"
if midi is in use with jamulus, in Patchage you should see red midi boxes connected together: Lastly, for low level debug if the device shows up under amidi command above:
|
Beta Was this translation helpful? Give feedback.
-
The below changes did the trick.
Plus the Mini was in MC mode.
Thanks a lot. I'll put it to the test on the next jam session.
Stop jamulus to release jack from alsa midi hardware
run qmidiroute from pi -> Sound & Video menu
launch "Patchage" from destop or menu
in Patchage, connect purple alsa midi device output "X-TOUCH MINI MIDI 1"
to "qmidiroute in"
qmidiroute should show events when you change x-touch mini controls:
…On Thu, Dec 2, 2021 at 4:05 PM Kevin Doren ***@***.***> wrote:
@jazzjohn27 <https://github.com/jazzjohn27> That image should be plug and
play with x-touch mini with default settings.
I used x-touch mini in its out-of-the-box default setup (channel 11, not
in mackie control mode). If you have made any changes (which I think can be
done using behringer windows app), it might not work the same.
Try the following command, it should show midi hardware devices: "amidi -l
| grep hw:"
***@***.***:~ $ amidi -l | grep hw:
IO hw:0,0,0 X-TOUCH MINI MIDI 1
also: "ps aux | grep midi"
***@***.***:~ $ ps aux | grep midi
pi 1212 1.9 3.1 686680 123084 pts/1 SLl+ Dec01 40:03 /usr/bin/python3 /usr/local/bin/midi-jamulus-xtouchmini.py
pi 1213 15.9 4.6 420488 181804 pts/1 S<Ll+ Dec01 325:59 jamulus --nojackconnect --ctrlmidich 11;f1*8;p11*8;m19*8;s27*8
pi 3255 0.0 0.0 7348 584 pts/0 S+ 13:22 0:00 grep --color=auto midi
if midi is in use with jamulus, in Patchage you should see red midi boxes
connected together:
[image: image]
<https://user-images.githubusercontent.com/28682457/144507580-22b25ab2-9885-4d84-82ff-da667445e2aa.png>
Lastly, for low level debug if the device shows up under amidi command
above:
1. Stop jamulus to release jack from alsa midi hardware
2. run qmidiroute from pi -> Sound & Video menu
3. launch "Patchage" from destop or menu
4. in Patchage, connect purple alsa midi device output "X-TOUCH MINI
MIDI 1" to "qmidiroute in"
5. qmidiroute should show events when you change x-touch mini controls:
[image: image]
<https://user-images.githubusercontent.com/28682457/144507210-9da3992b-c6bd-4f8e-af14-7df166336555.png>
[image: image]
<https://user-images.githubusercontent.com/28682457/144507078-ff196155-975a-4385-bed1-0d475b6d9045.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#118 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATYSST4LN4VTQOWZJYD34UTUO7UR5ANCNFSM5H3CX22A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
I had it out of MC mode but still didn't work until I made the connection
in Patchage.
Now there's a strange behavior: On a server with 4 musicians connected,
the first knob worked the first screen fader, but the 6th knob worked the
second fader and no other knobs worked the other two faders.
…On Thu, Dec 2, 2021 at 6:48 PM Kevin Doren ***@***.***> wrote:
Good to hear. Taking it out of MC mode was probably the issue.
Those commands not persistent, they are only for debug; you can't use
qmidiroute (to see midi messages) while running Jamulus.
That's because jamulus requires jack midi, which you get by having jack
capture the alsa midi devices. But then you can't route alsa midi to
qmidiroute.
When you start jamulus, the start script sets jack back to capture the
alsa midi ports, and the mididings script patches the jack midi ports.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#118 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATYSST5UUO67GS3DYFVL5YTUPAHVJANCNFSM5H3CX22A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
Since the strange behavior mentioned, it has worked correctly on other
servers, so maybe there was an issue with the server.
Overall it seems to be working fine now. Had a good jam session with 5
players and it performed well as expected.
…On Thu, Dec 2, 2021, 7:09 PM JohnL ***@***.***> wrote:
I had it out of MC mode but still didn't work until I made the connection
in Patchage.
Now there's a strange behavior: On a server with 4 musicians connected,
the first knob worked the first screen fader, but the 6th knob worked the
second fader and no other knobs worked the other two faders.
On Thu, Dec 2, 2021 at 6:48 PM Kevin Doren ***@***.***>
wrote:
> Good to hear. Taking it out of MC mode was probably the issue.
>
> Those commands not persistent, they are only for debug; you can't use
> qmidiroute (to see midi messages) while running Jamulus.
> That's because jamulus requires jack midi, which you get by having jack
> capture the alsa midi devices. But then you can't route alsa midi to
> qmidiroute.
>
> When you start jamulus, the start script sets jack back to capture the
> alsa midi ports, and the mididings script patches the jack midi ports.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#118 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ATYSST5UUO67GS3DYFVL5YTUPAHVJANCNFSM5H3CX22A>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
|
Beta Was this translation helpful? Give feedback.
-
@jazzjohn27 There is a bug in jamulus-server 3.8.1 that messes up the channel numbering, I just filed an issue: jamulussoftware/jamulus#2144 If you are using MIDI control, you'll want to set client to "View" -> "Sort users by name". When using MIDI, the channel number gets prepended to the client name, so this should sort the faders in MIDI channel order. If a client disconnect, it's fader will disappear from the GUI but that will not change the channel numbers of the remaining clients (if it did the knobs would shift around). However, channels should start again from 0 when server goes idle. That is broken in 3.8.1 which explains the behavior you saw. I could probably change the mididings script to user Layer B for an additional 8 channels .... but that's not the answer to the server bug.... |
Beta Was this translation helpful? Give feedback.
-
I updated the mididings script for xtouch mini. You should be able to install the new script into 1.5.0-b.2 as follows:
|
Beta Was this translation helpful? Give feedback.
-
I'll try it out in the next few days. Thank you.
…On Tue, Dec 7, 2021, 6:10 AM Kevin Doren ***@***.***> wrote:
@jazzjohn27 <https://github.com/jazzjohn27>
I updated the mididings script for xtouch mini.
This one handles 16 channels, 8 on each layer.
Pushing on the encoder changes between fader (led ring fan pattern) and
pan (led ring pan pattern)
You should be able to install the new script into 1.5.0-b.2 as follows:
wget https://raw.githubusercontent.com/kdoren/jambox-pi-gen/1981124c169f363d87f0b5ab423b9caa62f45533/stage3/06-install-jamulus/files/midi-jamulus-xtouchmini-16ch.py
chmod +x midi-jamulus-xtouchmini-16ch.py
sudo cp midi-jamulus-xtouchmini-16ch.py /usr/local/bin/https://raw.githubusercontent.com/kdoren/jambox-pi-gen/1981124c169f363d87f0b5ab423b9caa62f45533/stage3/06-install-jamulus/files/jamulus_start.sh
chmod +x jamulus_start.sh
sudo cp /usr/local/bin/jamulus_start.sh{,.bak}
sudo cp jamulus_start.sh /usr/local/bin/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#118 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATYSST52RF2QNXVY7NSHQ2LUPX2R3ANCNFSM5H3CX22A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
@jazzjohn27 FYI I posted a new release v1.5.0 that includes the updated script. |
Beta Was this translation helpful? Give feedback.
-
Thank you!
…On Sun, Dec 19, 2021 at 4:12 PM Kevin Doren ***@***.***> wrote:
@jazzjohn27 <https://github.com/jazzjohn27> FYI I posted a new release
v1.5.0 that includes the updated script.
—
Reply to this email directly, view it on GitHub
<#118 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATYSST2R7JG5XXBHENMR5XTURZKEHANCNFSM5H3CX22A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Anyone know how to get this MIDI controller working with Jambox?
The goal is to have it control the fader sliders and the mute and solo buttons.
Any clues would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions