Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install on Raspberry Pi 3 model B - raspbian Jesse Lite #13

Open
jwhittin744 opened this issue Mar 6, 2018 · 13 comments
Open

Install on Raspberry Pi 3 model B - raspbian Jesse Lite #13

jwhittin744 opened this issue Mar 6, 2018 · 13 comments

Comments

@jwhittin744
Copy link

The install seems to go fine, but when i follow the steps through to the "Show_Interfaces" command, the last line beginning with 'USB' is missing from the output as shown here... Because of this, I cannot update the Start file for the midi tokens...

/katana-midi-bridge $ sudo ./show_interfaces
Output Ports

KATANA:KATANA MIDI 1 20:0
KATANA:KATANA MIDI 2 20:1
KATANA:KATANA MIDI 3 20:2
Midi Through:Midi Through Port-0 14:0

Input Ports

KATANA:KATANA MIDI 1 20:0
KATANA:KATANA MIDI 2 20:1
KATANA:KATANA MIDI 3 20:2
Midi Through:Midi Through Port-0 14:0

any ideas?

@snhirsch
Copy link
Owner

snhirsch commented Mar 6, 2018

It appears that your MIDI controller is either not connected to the Pi or not being recognized. What make and model of controller are you using?

@jwhittin744
Copy link
Author

jwhittin744 commented Mar 6, 2018 via email

@snhirsch
Copy link
Owner

snhirsch commented Mar 6, 2018

Hmm. If you tail the system log file on the Pi, do you see anything happening when you plug the M-audio Uno in? Also try running 'lsusb' to see if the Uno device is even being enumerated.

It really does sound as if the USB/MIDI adapter is not being properly recognized.

I've used an M-Audio MidiSport 1x1 and had no compatibility issues ever.

@jwhittin744
Copy link
Author

jwhittin744 commented Mar 6, 2018 via email

@snhirsch
Copy link
Owner

snhirsch commented Mar 7, 2018

Wait, you said M-Audio Uno, but your log calls out a Midisport 1x1 (the same USB/MIDI interface I'm using). Which hardware are you using? Are you sure you have all the prerequisite libraries installed on the Pi? ALSA is supposed to identify it and bind it to a MIDI device. A couple more things:

  1. Did you add the command flag from my instructions to force "full-speed" operation? If so, try without it. If not, please add it.

  2. Try uninstalling the katana bridge in case the failed startup is interfering with ALSA in some manner.

  3. Are you using a USB hub?

  4. Does 'aconnect -l' show you the Midisport?

@jwhittin744
Copy link
Author

jwhittin744 commented Mar 7, 2018 via email

@jwhittin744
Copy link
Author

jwhittin744 commented Mar 8, 2018 via email

@snhirsch
Copy link
Owner

snhirsch commented Mar 8, 2018

What about the boot command line parameter to setup USB speed? - Sorry missed your comment about the high-speed setting.

I'm about out of ideas. Can you tell me which OS and version you're running on the Pi and which Pi model you have? I guess it's possible your USB adapter is not MIDI class-compliant. The ALSA layer will automatically recognize any interface that's class-compliant and has been extended to do this also for Roland/Boss products (which are NOT class-compliant). Since the Katana is being recognized, I think it's down to your USB/MIDI adapter. A Roland UM-1 or Midisport 1x1 should work properly (even though yours ids as a midisport, I think it's different from what I have here).

@jwhittin744
Copy link
Author

jwhittin744 commented Mar 8, 2018 via email

@snhirsch
Copy link
Owner

snhirsch commented Mar 8, 2018

That could possibly predate the current "class compliance" specification. May be worth sending a note to M-Audio to see if there's a firmware upgrade, or if they can shed any light on why it's not recognized by a contemporary Linux system.

Or, go on Amazon and purchase a new Midisport 1x1 and be done with it :-)

@jwhittin744
Copy link
Author

jwhittin744 commented Mar 9, 2018 via email

@jwhittin744
Copy link
Author

jwhittin744 commented Mar 11, 2018 via email

@snhirsch
Copy link
Owner

Excellent! Glad you were able to sort it out. I hope you find the bridge software useful. I had originally planned to expose the entire sysex API, but ran out of time and motivation. A few folks have found the snapshot feature to be useful, though.

I'm hoping someone with Python coding skills can pickup the API work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants