Problem with midi devices

  • 0
  • 7
Leinholz

Hi there!

I have an issue connecting midi devices to the browser. It's not Audiotool related but maybe someone has an idea. When I connect midi devices to the computer it's recognised by the system:

[ 28.173948] usb 2-2: new full-speed USB device number 2 using xhci_hcd [ 28.315597] usb 2-2: New USB device found, idVendor=0582, idProduct=010e, bcdDevice= 1.00 [ 28.315603] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 28.315606] usb 2-2: Product: A-500S [ 28.315609] usb 2-2: Manufacturer: ROLAND [ 28.352994] usbcore: registered new interface driver snd-usb-audio [ 39.269126] audit: type=1131 audit(1550842398.051:74): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success

However when I open the Midi devices page in Audiotool nothing shows up. On this web midi page it tells me midi failed to initialise:

Initializing MIDI... MIDI Init Error. Error code: 11

System Stats: OS: Arch Linux Kernel: x86_64 Linux 4.20.8-arch1-1-ARCH CPU: Intel Core i7-3520M @ 4x 3.6GHz [35.0°C] RAM: 816MiB / 6780MiB

Google Chrome 72.0.3626.109 (Offizieller Build) (64-Bit)

Using audiotool booster jar

Weird thing is, it always used to work without a problem.

Create an account or to write a comment.

  • User Avatar
    Known As I

    Glad it helped and thanks for giving feedback on the solution. This might help others as well.

  • User Avatar
    Leinholz

    @Known As I Yeah. Fixed the problem!! I started up rosegarden from terminal and it sayd something like: maybe you have to modprobe snd-seq-midi.

    Did that and now it's all working again! Thanks a lot for the hint! :)

  • User Avatar
    Leinholz

    @Known As I Thanks for the great tips! Haven't got round to try out rosegarden. Didn't know about that software. Have to check it out when I get round. I'll report if I find out more! :)

  • User Avatar
    Known As I

    The permissions are only required to obtain certain metadata. I compared your output with mine (Linux Mint, random cheap'o MIDI keyboard) and I got quite the same result. For me everything works fine in Chromium.

    I just installed "rosegarden" and it detected my keyboard out of the box - maybe you want to try this to tackle your issue. It might provide better error output.

  • User Avatar
    Leinholz

    Could it be possible that the software doesn't have the rights to access the USB port?

    Had to run lsusb command as root to get the full output.

    If I run it as my user it says this in the beginning:

    Couldn't open device, some information will be missing

  • User Avatar
    Leinholz

    Oh, there's lots of output from that!

    I run updates more or less frequently but other than that I can think of anything that has changed.

    I've tried it with chromium and the google-chrome package. Doesn't work with either.

    Also tried two different midi devices and different USB ports

  • User Avatar
    Known As I

    Phew ... looks fine to me on a first glance.

    What's the output of 'lsusb -vd 0582:010e'?

    When you say "always used to work" - did anything change in the meantime? New Browser/OS/Machine?