Problem connecting MiniLab on Linux OS

[vodkainn]

Hello!

I'm linux user and create music in Renoise. Few days ago I got a box with Arturia MiniLab. In Win7 it works very fine but in Linux it doesn't work.

So...

Code: Select all

# uname -a
Linux evp 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux

If I only plug in...
reconnect in loop

Code: Select all

~$ dmesg | tail -30
[ 4442.772480] usb 1-2.4: new full-speed USB device number 25 using xhci_hcd
[ 4442.795472] usb 1-2.4: New USB device found, idVendor=1c75, idProduct=0204
[ 4442.795483] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4442.795488] usb 1-2.4: Product: Arturia MINILAB
[ 4442.795493] usb 1-2.4: Manufacturer: Arturia
[ 4442.807139] usb 1-2.4: USB disconnect, device number 25
[ 4443.024325] usb 1-2.4: new full-speed USB device number 26 using xhci_hcd
[ 4443.047059] usb 1-2.4: New USB device found, idVendor=1c75, idProduct=0204
[ 4443.047070] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4443.047076] usb 1-2.4: Product: Arturia MINILAB
[ 4443.047080] usb 1-2.4: Manufacturer: Arturia
[ 4443.057191] usb 1-2.4: USB disconnect, device number 26
[ 4443.271859] usb 1-2.4: new full-speed USB device number 27 using xhci_hcd
[ 4443.295041] usb 1-2.4: New USB device found, idVendor=1c75, idProduct=0204
[ 4443.295054] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4443.295064] usb 1-2.4: Product: Arturia MINILAB
[ 4443.295071] usb 1-2.4: Manufacturer: Arturia
[ 4443.305121] usb 1-2.4: USB disconnect, device number 27
[ 4443.519617] usb 1-2.4: new full-speed USB device number 28 using xhci_hcd
[ 4443.542342] usb 1-2.4: New USB device found, idVendor=1c75, idProduct=0204
[ 4443.542345] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4443.542347] usb 1-2.4: Product: Arturia MINILAB
[ 4443.542348] usb 1-2.4: Manufacturer: Arturia
[ 4443.551681] usb 1-2.4: USB disconnect, device number 28
[ 4443.767222] usb 1-2.4: new full-speed USB device number 29 using xhci_hcd
[ 4443.790009] usb 1-2.4: New USB device found, idVendor=1c75, idProduct=0204
[ 4443.790023] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4443.790032] usb 1-2.4: Product: Arturia MINILAB
[ 4443.790038] usb 1-2.4: Manufacturer: Arturia
[ 4443.799496] usb 1-2.4: USB disconnect, device number 29

then I push the button "Shift" on MiniLab

Code: Select all

# dmesg
...
[ 1279.173210] usb 2-2: new full-speed USB device number 31 using xhci_hcd
[ 1279.211120] usb 2-2: New USB device found, idVendor=1c75, idProduct=0204
[ 1279.211133] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1279.211141] usb 2-2: Product: Arturia MINILAB
[ 1279.211146] usb 2-2: Manufacturer: Arturia

Code: Select all

# lsusb
...
Bus 002 Device 031: ID 1c75:0204

Code: Select all

# amidi -l
Dir Device    Name
IO  hw:1,0,0  Arturia MINILAB MIDI 1

but it doesn't help. MiniLab sleeps.

On Ubuntu 13.10 and Ubuntu Studio 13.10

Code: Select all

~$ dmesg | tail -n 50
...
[  354.204210] usb 3-2.4: new full-speed USB device number 14 using xhci_hcd
[  354.227471] usb 3-2.4: New USB device found, idVendor=1c75, idProduct=0204
[  354.227483] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  354.227490] usb 3-2.4: Product: Arturia MINILAB
[  354.227494] usb 3-2.4: Manufacturer: Arturia
[  354.237774] usb 3-2.4: USB disconnect, device number 14
[  354.249388] systemd-udevd[3676]: error opening ATTR{/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0/usb3/3-2/3-2.4/3-2.4:1.0/sound/card1/controlC1/../uevent} for writing: No such file or directory
[  354.250025] systemd-udevd[3676]: Failed to apply ACL on /dev/snd/controlC1: No such file or directory
[  354.250057] systemd-udevd[3676]: Failed to apply ACL on /dev/snd/controlC1: No such file or directory
[  354.252820] systemd-udevd[3674]: Failed to apply ACL on /dev/snd/midiC1D0: No such file or directory
[  354.252853] systemd-udevd[3674]: Failed to apply ACL on /dev/snd/midiC1D0: No such file or directory

If you know how solve this problem, I'll be so happy. Thx a lot!

[Shadow_7]

I'm seeing two main issues.

[ 354.237774] usb 3-2.4: USB disconnect, device number 14

and

[ 354.250025] systemd-udevd[3676]: Failed to apply ACL on /dev/snd/controlC1: No such file or directory

The ACL, I assume is access control list, which implies some sort of security / permissions issue.

# modprobe snd-usb-audio

And replug the device plus checking to see if the user is in the audio group.

$ aconnect -iol

And see if it lists the device there. The disconnects is odd, perhaps some firmware that it needs? Try the latest and greatest kernel and worship diety's? I don't know. But 3.2.x is almost ancient these days. If ATIs legacy driver is any indication, 3.4.x support and no updates since January. We're almost at a 3.12.x kernel wise. You've certainly plastered the interwebs with an identicle post on various sites. I seem to recall disconnect oddities when I was using my mobilepre with a faulty usb cable. Or not since yours apparently works in windows 7, I assume with the same cable.

[vodkainn]

I'm seeing two main issues.

[ 354.237774] usb 3-2.4: USB disconnect, device number 14

and

[ 354.250025] systemd-udevd[3676]: Failed to apply ACL on /dev/snd/controlC1: No such file or directory

The ACL, I assume is access control list, which implies some sort of security / permissions issue.

# modprobe snd-usb-audio

And replug the device plus checking to see if the user is in the audio group.

$ aconnect -iol

And see if it lists the device there. The disconnects is odd, perhaps some firmware that it needs? Try the latest and greatest kernel and worship diety's? I don't know. But 3.2.x is almost ancient these days. If ATIs legacy driver is any indication, 3.4.x support and no updates since January. We're almost at a 3.12.x kernel wise. You've certainly plastered the interwebs with an identicle post on various sites. I seem to recall disconnect oddities when I was using my mobilepre with a faulty usb cable. Or not since yours apparently works in windows 7, I assume with the same cable.

Code: Select all

[  354.250025] systemd-udevd[3676]: Failed to apply ACL on /dev/snd/controlC1: No such file or directory

It happens in Live CD Ubuntu 13.10 OR Ubuntu Studio 13.10. The main system is Debian Wheezy.

In the latest:

Code: Select all

~$ dmesg | tail -21
[ 2021.013613] usb 1-2.4: new full-speed USB device number 27 using xhci_hcd
[ 2021.036525] usb 1-2.4: New USB device found, idVendor=1c75, idProduct=0204
[ 2021.036535] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2021.036541] usb 1-2.4: Product: Arturia MINILAB
[ 2021.036545] usb 1-2.4: Manufacturer: Arturia
[ 2021.045214] ALSA midi.c:216 urb status -32
[ 2021.047078] usb 1-2.4: USB disconnect, device number 27
[ 2021.265286] usb 1-2.4: new full-speed USB device number 28 using xhci_hcd
[ 2021.288209] usb 1-2.4: New USB device found, idVendor=1c75, idProduct=0204
[ 2021.288217] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2021.288222] usb 1-2.4: Product: Arturia MINILAB
[ 2021.288225] usb 1-2.4: Manufacturer: Arturia
[ 2021.296510] ALSA midi.c:216 urb status -32
[ 2021.297757] usb 1-2.4: USB disconnect, device number 28
[ 2021.513168] usb 1-2.4: new full-speed USB device number 29 using xhci_hcd
[ 2021.535978] usb 1-2.4: New USB device found, idVendor=1c75, idProduct=0204
[ 2021.535991] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2021.535998] usb 1-2.4: Product: Arturia MINILAB
[ 2021.536004] usb 1-2.4: Manufacturer: Arturia
[ 2021.544442] ALSA midi.c:216 urb status -32
[ 2021.546632] usb 1-2.4: USB disconnect, device number 29

[Shadow_7]

It?

http://www.arturia.com/evolution/smf/in ... oard=103.0

Which you already found and posted in. Sadly with 0 replies.

Have you tried the latest firmware? FirmWare 2.1.0.2
http://www.arturia.com/evolution/en/pro ... urces.html

Not that I hold much hope, it seems that people have just as many issues with the device in any OS. But at least updates seem recent enough to have hope.

[vodkainn]

It?

http://www.arturia.com/evolution/smf/in ... oard=103.0

Which you already found and posted in. Sadly with 0 replies.

Have you tried the latest firmware? FirmWare 2.1.0.2
http://www.arturia.com/evolution/en/pro ... urces.html

Not that I hold much hope, it seems that people have just as many issues with the device in any OS. But at least updates seem recent enough to have hope.

I hope the problem will be solved. Of course I tried the latest firmware 2.1.0.2. And I tried earliest too.

It use Class-Compliant and very strangely that it doesn't want to work.

[nickture]

I'm having the same issue. Has anyone found an answer?

[Linuxmusician01]

Hope nobody minds me answering this old post. But it kept popping up in Google when I searched for tips on the Arturia MiniLab.

Strangely enough I do not have any problems w/ this Midi keyboard in Linux Mint 17 (which is based on Ubuntu 14). Maybe kernel 3.13 has the support that we need for this keyboard. I always disable PulseAudio (PA) when I work w/ Midi. Like so:

Code: Select all

sudo mv ~/.pulse ~/.pulse-backup
sudo rm -rf ~/.pulse

And edit the file '/etc/pulse/client.conf' and add:

Code: Select all

autospawn = no
daemon-binary =/bin/true

If you want to you can restart PA w/:

Code: Select all

pulseaudio --start

Now check what the Midi port number is from the MiniLab:

Code: Select all

$ aconnect -i
client 24: 'Arturia MINILAB' [type=kernel]
    0 'Arturia MINILAB MIDI 1'

So its port number is 24 in my case. Now check its output:

Code: Select all

aseqdump -p 24

The Hat Trick however, is to use the Arturia tool/software called 'Midi Control Center'. Download from: http://www.arturia.com/minilab/resources . Download under 'Extra resources' the WinXP version of the software called 'Midi Control Center (old)'. Mistakenly the Windows version is under the Mac link. Here are my personal notes on the thing:

The Arturia Minilab midi keyboard controller works in Linux as a standard controller. It does need some configuration, however. It must be in "absolute mode" as opposed to "relative mode". The first is selected by pressing Shift + 1 after the keyboard is connected to your computer.

Summary
~~~~~~~~~~
The Arturia Minilab midi keyboard controller works in Linux as a standard controller. It does need some configuration, however. It must be in "absolute mode" as opposed to "relative mode". The first is selected by pressing Shift + 1 after the keyboard is connected to your computer.


1. Midi Control Center
~~~~~~~~~~~~~~~~~~~~~~
Since the keyboard cannot be reset to its factory settings by a hardware switch or key combo one MUST use the settings software from the Arturia page. It's called 'Midi control center' (MCC). Luckily the Windows XP version works in Wine. I've got firmware version 3.0.0.5 (the latest). Strangely enough that firmware is supposed to only work w/ devices w/ an N in the serial number, but mine has no letter at all in the serial...

Make sure no other process is accessing the keyboard. Plug in the keyb. Now start MCC. If its connected properly then it will recognize the firmware version. If not: stop MCC and reconnect keyb. (it appears that you may not have touched any of its controls for MCC to work).

Notice that all controls are pre-set to the dreaded, wretched "relative mode". If you were to click on the button 'Send to keybrd.' you might be stuck w/ an Arturia that's in relative mode.

Click on "Default values" and watch the controls flick to "absolute", which is what you want. Test if the keyboard behaves yet like a good little midi device from the command line w/:

aseqdump -p 24

(if the port number is 24; determine port w/ the command "aconnect -i"). Turn some knobs and make sure the value goes all the way from 0 to 127.

If you want to use the pads as switches for your synth do the following in CCM: set the pads channel to global (the same as the channel from the k.brd.); mode = switched & toggle. Want no velocity sensitivity for the keys of the keyb.? Set velocity curve to 'full' then.

Important notice! CCM cannot detect your current settings, no matter what the manual says. So when you want to change a setting you must set the k.brd. to default values and re-do all your customizations. Or save and load your settings.


2. Connect
~~~~~~~~~~
After connection to a PC press Shift + 1 for it to be in proper Midi mode (i.e. "absolute mode")!


How to use Midi on Linux w/ Jack, Jack-rack, aconnect and other Alsa Midi stuff is another difficult story altogether.

[acbakhit]

The Minilab seems to work with Linux systems only if you're running firmware 3.0.0.5, but if you're running firmware 2.1.0.2 or below then you'll likely run into issues-- such is the case I'm in. My Minilab is running firmware 2.1.0.2, I haven't successfully found a way to upgrade to 3.0.0.5. When running MIDI Control Center it only allows for a .bin file selection when searching for a firmware file (.bin being the filetype of 2.1.0.2), but firmware 3.0.0.5 is a .led file. Has anyone found a way to allow for a .led selection if running 2.1.0.2 firmware?

[Linuxmusician01]

The Minilab seems to work with Linux systems only if you're running firmware 3.0.0.5, but if you're running firmware 2.1.0.2 or below then you'll likely run into issues-- such is the case I'm in. My Minilab is running firmware 2.1.0.2, I haven't successfully found a way to upgrade to 3.0.0.5. When running MIDI Control Center it only allows for a .bin file selection when searching for a firmware file (.bin being the filetype of 2.1.0.2), but firmware 3.0.0.5 is a .led file. Has anyone found a way to allow for a .led selection if running 2.1.0.2 firmware?

That's strange. Are you sure you've got the latest version of 'Midi Control Center' (MCC)? The version that I have looks exactly the same as on the Arturia website (link) but it says "version 1.1" next to the "Upgrade Firmware" button. When I try to upgrade firmware it starts to look for a .led file. Maybe in the dialog window that lets you select the firmware file you need to check that it is looking for "all files" instead of just .led or .bin.

I also noticed that the old 2.1.0.2 firmware has the extension .bin and the new 3.0.0.5 firmware the .led extension. And the new firmware is in Zip file together w/ the MCC software. I think that the version of MCC and firmware must match.


P.S. I can only get MCC' version for Win XP to work. So make sure that on the Arturia Minilab download page you click the green "Show Archives" button at the top right. Then, in the "Extra Resource" category at the bottom, you can download MCC version 1.1 that is 3,5 MB in size (mistakenly placed in the Mac row of the table). That's the one!

[glowrak guy]

I'd never do a firmware upgrade of an entrenched mainstream device, usine wine.
And I use wine a lot. Go find a machine with the matching OS that the firmware routine is designed for,
or risk creating a brick with silent keys and pads. Good luck!
Cheers

[Linuxmusician01]

I'd never do a firmware upgrade of an entrenched mainstream device, usine wine.
And I use wine a lot. Go find a machine with the matching OS that the firmware routine is designed for,
or risk creating a brick with silent keys and pads. Good luck!
Cheers

I agree. I did not have to upgrade the firmware itself of my MiniLab (it came w/ ver. 3). But the programming of the keys and resetting it to its factory settings worked fine for me using Wine and the Win XP executable of MCC (Midi Control Center).

[acbakhit]

Still no luck, I'm thinking maybe it looks for some serial number from the MiniLab to determine what filetype it'll allow you to select?

[Linuxmusician01]

Still no luck, I'm thinking maybe it looks for some serial number from the MiniLab to determine what filetype it'll allow you to select?

Are you absolutely, definitely, super duper sure you've got version 1.1 of the Midi Control Center software from Arturia?



This is when my Minilab is not connected (it wants a BIN):


This is when I connect my MiniLab keyboard (it wants a LED type of file):

[glowrak guy]

Maybe a registry leftover? You can rename .wine folder to .wine-original
run winecfg to generate a fresh .wine, and do a fresh arturia software install
before you plugin the minilab, and reboot. Then plugin it in, and test.
(But if a manual describes otherwise, believe the manual. Too many
modern products have the software install before the hardware.

If it works, you can copy back non-arturia items, from the .wine-original.
Then inspect the .wine-original registry for arturia entries, if curious.

Some expensive software with both plugin and standalone versions require
the standalone to run first, before the plugin will initialize correctly.

Sometimes you get what you pay for...
Sometimes you pay for what you get

[Linuxmusician01]

Maybe a registry leftover? You can rename .wine folder to .wine-original run winecfg to generate a fresh .wine, and do a fresh arturia software install before you plugin the minilab, and reboot. Then plugin it in, and test. (But if a manual describes otherwise, believe the manual. Too many modern products have the software install before the hardware.

If it works, you can copy back non-arturia items, from the .wine-original. Then inspect the .wine-original registry for arturia entries, if curious.

Some expensive software with both plugin and standalone versions require the standalone to run first, before the plugin will initialize correctly.

Sometimes you get what you pay for...
Sometimes you pay for what you get

I don't think so. The software version we're talking about does not need to be "installed" in Wine (or Windows for that matter): it runs standalone. So there would be no entry in the .wine folder.

I'd sooner urge Acbakhit to check his MCC version and to let MCC look for the firmware after connecting the Minilab, not before. Because my MCC version appears to look for .bin and .led on and off, depending on the procedure used (see my March 5 post).