Problem with detecting midi controller on Solus OS

Fixxx your Mixxx

Moderator: garth

Problem with detecting midi controller on Solus OS

Postby Visi0n » Sun Dec 02, 2018 2:40 pm

Hello!
I have a problem with detecting my controller (Numark Party Mix) by Mixxx (version 2.1.4 x64) in Solus OS (version 3.999 x64).
I read all documents how to resolve issues with controlles on Linux and checked also all possible alternative ways to resolve it, but unfortunately without success. My linux user is in 'users' group and i have mixxx.usb.rules (read below about it) but Mixxx is still does not see my controller. I tried another distibutive of Linux (latest Mint) on LiveUSB and installed 2.0 Mixxx on it - and it found my device successfully but i don't want to reinstall whole system only for fixing this issue. Please read my investigation below. I hope you can help me by directing me in the right way.

This command shows that device is connected to the computer and identified:
Code: Select all
> lsusb
Bus 001 Device 013: ID 15e4:0038 Numark


This command shows that the midi device works and responds to changes in sliders and button presses:
Code: Select all
> amidi --dump
B0 06 7F
9A
8B
C4
BF 20 02
B0 06 7F
...


I also checked 100-mixxx.usb.rules files and found this string that applies for my device:
Code: Select all
# Numark (may be needed for NS7 & V7)
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="15e4", GROUP="users", MODE="0660"


But unfortunately this command does not show that this rules are applied to my device:
Code: Select all
> udevadm test $(udevadm info -q path -n /dev/midi) 2>&1
...
rules contain 393216 bytes tokens (32768 * 12 bytes), 37764 bytes strings
32372 strings (259804 bytes), 28394 de-duplicated (226019 bytes), 3979 trie nodes used
GROUP 11 /usr/lib64/udev/rules.d/50-udev-default.rules:43
RUN 'uaccess' /usr/lib64/udev/rules.d/73-seat-late.rules:17
handling device node '/dev/midi', devnum=c14:2, mode=0660, uid=0, gid=11
set permissions /dev/midi, 020660, uid=0, gid=11
setting mode of /dev/midi to 020660 failed: Operation not permitted
setting owner of /dev/midi to uid=0, gid=11 failed: Operation not permitted
.MM_USBIFNUM=00
ACTION=add
DEVNAME=/dev/midi
DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/sound/card0/midi
MAJOR=14
MINOR=2
SUBSYSTEM=sound
TAGS=:uaccess:
USEC_INITIALIZED=46763441273
run: 'uaccess'
Unload module index
Unloaded link configuration context.


So i checked what rules are in 50-udev-default.rules that applies to my device and made couple changes to mixxx.usb.rules. First of all i renamed it to 51-mixxx.usb.rules (for some reasons 51 has higher priority than 100). Next is rules string changing to:
Code: Select all
SUBSYSTEMS=="usb", ATTRS{idVendor}=="15e4", GROUP="users", MODE="0660"

And now this command shows:
Code: Select all
> udevadm test $(udevadm info -q path -n /dev/midi) 2>&1
...
rules contain 393216 bytes tokens (32768 * 12 bytes), 37764 bytes strings
32370 strings (259787 bytes), 28392 de-duplicated (226002 bytes), 3979 trie nodes used
GROUP 11 /usr/lib64/udev/rules.d/50-udev-default.rules:43
GROUP 100 /usr/lib64/udev/rules.d/51-mixxx.usb.rules:15
MODE 0660 /usr/lib64/udev/rules.d/51-mixxx.usb.rules:15
RUN 'uaccess' /usr/lib64/udev/rules.d/73-seat-late.rules:17
handling device node '/dev/midi', devnum=c14:2, mode=0660, uid=0, gid=100
preserve permissions /dev/midi, 020660, uid=0, gid=100
preserve already existing symlink '/dev/char/14:2' to '../midi'
.MM_USBIFNUM=00
ACTION=add
DEVNAME=/dev/midi
DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/sound/card0/midi
MAJOR=14
MINOR=2
SUBSYSTEM=sound
TAGS=:uaccess:
USEC_INITIALIZED=46763441273
run: 'uaccess'
Unload module index
Unloaded link configuration context.


As you can see mixxx.usb.rules are applied now. But Mixxx does not show device in devices list:
Code: Select all
> mixxx --developer
...
Debug [Controller]: ControllerManager: Setting up devices
Debug [Controller]: Scanning PortMIDI devices:
Debug [Controller]: Scanning USB Bulk devices:
Debug [Controller]: Scanning HID devices:
...


I am attaching the whole log file here. Thanks in advance.
Attachments
mixxx.log
(12.74 KiB) Downloaded 14 times
Visi0n
 
Posts: 1
Joined: Sun Dec 02, 2018 2:11 pm

Return to Troubleshooting & FAQ

Who is online

Users browsing this forum: No registered users and 1 guest