Linux & Midi control center

[Plop]

Hi,
Like the others linux user here i'm trying to use MCC without windows, and it seem nobody can really do it (maybe some with the use of a VM)

So far i was able to install and run MCC with wine, but i use playonlinux to do so (it's better to tweak wine to make thing work)
The problem is my beatstep pro is not showing as connected in the MCC, but work great as a midi controller with my DAW.

So the midi messages can transit from the beatstep pro to the computer, but cannot from the BSP to the MCC
I also see other saying that there is no problems with other gears with the same setup so i think the probleme come from the BeatStep Pro and the way it's recognize by the computer.

A bit about my setup :
Wine version : wine-5.0 (Ubuntu 5.0-3ubuntu1)
OS: Ubuntu 20.04.4 LTS x86_64 (Ubuntu Studio)
Host: HP ProBook 4530s A0001D02
Kernel: 5.4.0-100-lowlatency
CPU: Intel i3-2310M (4) @ 2.100GHz
GPU: Intel 2nd Generation Core Proce

With dmesg i get this :

Code: [Select]

[ 4828.481291] usb 2-1.3: new full-speed USB device number 5 using ehci-pci
[ 4828.562072] usb 2-1.3: New USB device found, idVendor=1c75, idProduct=0287, bcdDevice= 1.00
[ 4828.562079] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4828.562084] usb 2-1.3: Product: Arturia BeatStep Pro
[ 4828.562087] usb 2-1.3: Manufacturer: Arturia
[ 4828.641041] mc: Linux media interface: v0.10
[ 4828.696001] usbcore: registered new interface driver snd-usb-audio
And with the same commande after powering on the beastep pro in update mode (rec + play + stop) i get this :

Code: [Select]

[ 5431.683893] usb 2-1.1: New USB device found, idVendor=1c75, idProduct=0207, bcdDevice= 1.00
[ 5431.683901] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5431.683905] usb 2-1.1: Product: BeatStepPro Updater
[ 5431.683908] usb 2-1.1: Manufacturer: Arturia PROFESSIONAL,LP
When i run

Code: [Select]

ls -la /dev/ttyUSB*
I get nothing BUT

If i plug it and run

Code: [Select]

ls -lta /dev | head (to list only the last plugged device)
i get this :

Code: [Select]

crw-rw-rw-   1 root tty         5,   2 mars   7  2022 ptmx
drwxr-xr-x   2 root root          4460 mars   7 13:01 char
drwxr-xr-x   4 root root           300 mars   7 13:01 snd
crw-rw----+  1 root audio      14,  18 mars   7 13:01 midi1
crw-rw----+  1 root audio      14,  25 mars   7 13:01 dmmidi1
So there is 2 midi devices shown midi1 and dmmidi1, and if i list thing in /dev/snd (sound device)

Without the update mode i get this :

Code: [Select]

lrwxrwxrwx 1 root root  12 mars   7 13:13 usb-Arturia_Arturia_BeatStep_Pro-00 -> ../controlC1
With the update mode i get that :

Code: [Select]

lrwxrwxrwx 1 root root  12 mars   7 13:13 usb-Arturia_PROFESSIONAL_LP_BeatStepPro_Updater-00 -> ../controlC1
Ok so a quick recap, Midi control center work but doesnt see the beatstep pro, my computer can see the beatstep pro and my daw work fine with it.

So the problem seem to be narrowed to the signal not being routed correctly to wine

https://wiki.winehq.org/Wine_User's_Guide#Serial_and_Parallel_Ports

4.3.1 Serial and Parallel Ports

Serial and parallel ports are detected automatically when Wine starts. Windows serial ports follow a naming convention of the word COM followed by a number, such as COM1, COM2, etc. Similarly, parallel ports use LPT followed by a number, such as LPT1. Linux, Mac, and BSD each have their own device naming conventions, but in every case the serial or parallel device is located somewhere in /dev. You can see the mapping of Windows devices to Unix devices by looking in ~/.wine/dosdevices.

At this point my guess is, some devices are shown as USB device and work well with wine, and some others are shown as audio device wine need to be tweak in order to work with them.

I'm still digging the wine documentation for now, but i'm pretty sure i'm close to understand the probleme

I will post update if/when it's work
I know it's a lot a talk to say well that still doesn't work, but if anyone here know wine a bit better than i am please send help

[Plop]

Oh and if any of you have gear that do work with Midi control center and wine could you please just switch it on then run the following command :

Code: [Select]

ls -lta /dev | head

Code: [Select]

dmesg
And past the output of those commands here 
Just to confirm my theory about some gear being shown as USBtty* and some other as audio device