[LAU] send a midi CC signal to my midi controller from bash

Athanasios Silis athanasios.silis at gmail.com
Sat Oct 24 01:26:14 UTC 2015


Hi Ralf,
so I finally sat down to write this command line (bash) midi function.
I seem to be getting stuck on .... choosing the port instead of something
like the data stream (haven't reached there yet).

You see I have the following midi port , which I can see from "aplaymidi"
through port (14:0)
> aplaymidi -l
 Port    Client name                      Port name
 14:0    Midi Through                     Midi Through Port-0
 16:0    BCR2000                          BCR2000 MIDI 1
 16:1    BCR2000                          BCR2000 MIDI 2
 16:2    BCR2000                          BCR2000 MIDI 3
 20:0    Arturia BeatStep                 Arturia BeatStep MIDI 1
 28:0    TerraTec DMX6Fire                MIDI-Front DMX6fire 3
 28:32   TerraTec DMX6Fire                Wavetable DMX6fire 3
 32:0    Hoontech SoundTrack Audio DSP24  MIDI-1 Hoontech/STA DSP24 4
 32:32   Hoontech SoundTrack Audio DSP24  MIDI-2 Hoontech/STA DSP24 4


however in amidi -l does not show this port.
> amidi -l
Dir Device    Name
IO  hw:0,0,0  BCR2000 MIDI 1
IO  hw:0,0,1  BCR2000 MIDI 2
 O  hw:0,0,2  BCR2000 MIDI 3
IO  hw:1,0,0  Arturia BeatStep MIDI 1
IO  hw:3,0    MIDI-Front DMX6fire 3
 O  hw:3,1    Wavetable DMX6fire 3
IO  hw:4,0    MIDI-1 Hoontech/STA DSP24 4
IO  hw:4,1    MIDI-2 Hoontech/STA DSP24 4

I understand client:14 is a software port, but it registers with jack
properly - through the use of a2jmidid (shows up both in "ALSA" and "JACK"
tabs in qjackctl connections window) and with aplaymidi.

So why not show up in amidi too?
and how can I send data to this port ? I mean I can send from midish to
this port, so why not from amidi too?

Thank you!








On Thu, Oct 15, 2015 at 2:29 PM, Paul Davis <paul at linuxaudiosystems.com>
wrote:

> On Wed, Oct 14, 2015 at 4:03 PM, Clemens Ladisch <clemens at ladisch.de>
> wrote:
> > Paul Davis wrote:
> >> On Tue, Oct 13, 2015 at 5:44 PM, Len Ovens <len at ovenwerks.net> wrote:
> >>> If your midi info includes sysex events of any length I would think you
> >>> should use alsa midi over jack midi. Jack has event length limits.
> >>
> >> Actually, so do the ALSA MIDI command line tools.
> >
> > Neither amidi nor aplaymidi have length limits.
>
> Sorry, I stand corrected. It has been a long time since I tried to
> grab a sysex dump from an alesis digital recorder (about 4MB) ... at
> that time none of the ALSA tools could deal with it. Glad that has
> been corrected.
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user at lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxaudio.org/pipermail/linux-audio-user/attachments/20151024/41474457/attachment.html>


More information about the Linux-audio-user mailing list