Maxime Chevalier-Boisvert wrote:
> Hmm, seems I can't. I don't remember how I did it last time. When my
> virtual port is connected to the hardware, amidi reports the hardware
> port is busy.
Yes, raw MIDI ports don't allow sharing; this is why you should use
sequencer ports.
Try running only "am
> Is the file /usr/bin/alsamixer present, or /sbin/alsa ?
>
> Or the /usr/share/alsa directory?
>
> You should have these or equivalents IIUC.
/usr/bin/alsamixer is present and gives:
cannot open mixer: No such file or directory
/sbin/alsa also is present. Gives the usual:
Usage: /sbin/alsa {unlo
Hmm, seems I can't. I don't remember how I did it last time. When my
virtual port is connected to the hardware, amidi reports the hardware
port is busy. Do you know of any bug in ALSA that could cause this, or
any programming error on my part that could cause bytes to be dropped
when I'm on a v
In article
,
Marcin Szyniszewski wrote:
> $ alsamixer
> cannot open mixer: No such file or directory
[snip other details]
Is the file /usr/bin/alsamixer present, or /sbin/alsa ?
Or the /usr/share/alsa directory?
You should have these or equivalents IIUC.
I'm also fairly new at this, but
Maxime Chevalier-Boisvert wrote:
> I seem to be experiencing a problem with raw midi access.
>
> I wrote a program to capture MIDI bytes using the ALSA raw MIDI API. It
> works 100% fine if I connect directly to the device for my hardware MIDI
> controller (hw:1,0,0). However, if I try to connect
