Keyboard is recognised but doesn't work

[khz]

Nothing related to alsa or pulse or jack has never been on a list.

No, pulse is not running as I disabled and removed it.

Pulseaudio may not be displayed because you have uninstalled it.
If Ableton supports ALSA/jackd it will also be listed.

[sunrat]

I didn't know Ableton even works in Linux so can't help there. I'd suggest using a standalone synth to test that MIDI is working for starters.

[davis]

I didn't know Ableton even works in Linux so can't help there. I'd suggest using a standalone synth to test that MIDI is working for starters.

If it works on Windows, it works on Linux (using wine)
That is good idea. Any of those would be fine or could you recommend something else? http://www.vintagesynth.com/articles/5- ... nths-linux

[merlyn]

I use Ableton:

With WINE? The problem is then exposing MIDI in WINE. So this topic should be in 'Running Non-Linux Software'. Or start a new topic -- WINE MIDI in that forum.

[davis]

I use Ableton:

With WINE? The problem is then exposing MIDI in WINE. So this topic should be in 'Running Non-Linux Software'. Or start a new topic -- WINE MIDI in that forum.

You're maybe right. But i've been using Yamaha-CP33 as midi with a same setup (linux + ableton). I had yamaha-cp33 driver though. Keyboard showed up in ableton and that's all.. it was super simple process.

[merlyn]

The CP33 driver you refer to -- a Windows driver? I haven't found Linux needs drivers for MIDI devices. Sometimes firmware is required.

If JACK isn't running you could use aseqdump from the command line to see if MIDI is getting in. Start with aseqdump -l to find the port:

Code: Select all

$ aseqdump -l
 Port    Client name                      Port name
  0:0    System                           Timer
  0:1    System                           Announce
 14:0    Midi Through                     Midi Through Port-0
 16:0    Virtual Raw MIDI 0-0             VirMIDI 0-0
 28:0    Hoontech SoundTrack Audio DSP24  MIDI-1 Hoontech/STA DSP24 3
 28:32   Hoontech SoundTrack Audio DSP24  MIDI-2 Hoontech/STA DSP24 3
 32:0    PhotonX25                        PhotonX25 MIDI 1
 32:1    PhotonX25                        PhotonX25 MIDI 2

Then use the port number e.g 32:0 for my Photon :

Code: Select all

$ aseqdump -p32:0
Waiting for data. Press Ctrl+C to end.
Source  Event                  Ch  Data
 32:0   Note on                 0, note 60, velocity 104
 32:0   Note off                0, note 60
 32:0   Note on                 0, note 59, velocity 110
 32:0   Note off                0, note 59
 32:0   Note on                 0, note 60, velocity 110
 32:0   Note off                0, note 60

[davis]

lsusb
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 8087:07dc Intel Corp.
Bus 002 Device 004: ID 5986:055e Acer, Inc Lenovo EasyCamera
Bus 002 Device 003: ID 1fc9:81dc NXP Semiconductors Vivo S9
Bus 002 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0

I tried that already but I have no any output. Something remotely close looked on 14:0 so I did `aseqdump -p14:0`
So wierd thing is that Vivo is recognised but doesn't respond anyway. I even thought it might be wire but in that case lsusb wouldn't show my keyboard.

[merlyn]

Do you have 5 pin MIDI inputs? They would work in the meantime until you figure this out. I would expect your keyboard to just work over USB.

[davis]

Do you have 5 pin MIDI inputs? They would work in the meantime until you figure this out. I would expect your keyboard to just work over USB.

3 pin midi. Memory midi. And usb midi which my cable is connected to. You think I must isolate that USB midi and possibly disable the rest pins? (sorry if I totally misunderstood)

[merlyn]

I mean old school MIDI connectors like these :



You would need them on your audio interface along with a MIDI lead.

[davis]

I mean old school MIDI connectors like these :



You would need them on your audio interface along with a MIDI lead.

huh wtf..
I had same thing on yamaha cp-33 and all I had was usb cable. What do you mean i need them in my audio interface?

[merlyn]

As far as I can make out USB MIDI isn't working so instead of USB MIDI you could use 5 pin MIDI if you have the inputs.

[davis]

As far as I can make out USB MIDI isn't working so instead of USB MIDI you could use 5 pin MIDI if you have the inputs.

Oh, I need to buy cables I guess. Well, it's worth a try.

[merlyn]

Oh, I need to buy cables I guess.

I see. Using 5 pin MIDI is a workaround rather than a solution. Have you got the latest firmware for your keyboard? Other than that I don't have an explanation for why your keyboard appears in lsusb and not aseqdump.

[Baggypants]

lsusb just detects if a usb device is connected. Just because it's detected it doesn't mean a driver is available in order for you to use it. I've the same behaviour with quite a few usb devices. e.g. the Novation Mininova. In fact, the usb device has to be detected first so that Linux knows which driver to load.

The Yamaha CP-33 is probably what is called a "Class Compliant" device, it can use an optional generic MIDI-USB driver and it will work with all operating systems that support it, e.g. Linux, iOS, MacOS, Windows, Android. I haven't seen anything in the Dexibell page that suggests it is also Class Compliant.