>> Your program behaves as if it reads two bytes in each call. Please
print out the value of "err" when it succeeds.
This is for one note on, one note off.
Opening MIDI input port: "virtual"
90
Bytes read: 1
Byte type size: 1
3C
Bytes read: 1
Byte type size: 1
80
Bytes read: 1
Byte type size: 1
It seems I can sidestep the bug by setting my raw midi port to
nonblocking mode and then reading as much data as I can with each call.
Is there somewhere I can report this bug so it will get fixed in future
releases?
- Maxime
On 11-02-11 11:30 PM, Maxime Chevalier-Boisvert wrote
Interestingly, if I use the same blocking loop and try to read the bytes
3 at a time, there are no dropped bytes. It only seems to happen when I
ask to read one byte at a time.
- Maxime
On 11-02-11 02:07 AM, Clemens Ladisch wrote:
> Maxime Chevalier-Boisvert wrote:
>> Hmm, seems I
>> Try running only "amidi --dump -p virtual", and then connecting the
hardware sequencer port to the virtual on
It works fine when amidi connects to it. Shows 3 bytes for each key
on/key off.
>> When the sequencer converts the messages back to raw MIDI bytes, it
uses running status by defau
n I'm on a virtual port but not when I connect directly to the hardware?
- Maxime
On 11-02-10 04:20 AM, Clemens Ladisch wrote:
> Maxime Chevalier-Boisvert wrote:
>> I seem to be experiencing a problem with raw midi access.
>>
>> I wrote a program to capture MIDI bytes usin
I seem to be experiencing a problem with raw midi access.
I'm on Ubuntu 10.04, using ALSA 10.0.22.
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 t
