Hi Clemens,
finally got home and went back to this issue
2011/8/13 Clemens Ladisch <cladisch@xxxxxxxxxxxxxx>:
> Use SND_SEQ_OPEN_DUPLEX in snd_seq_open.
> Drop the snd_seq_event_input_pending call; snd_seq_event_input
> automatically waits for new events.
I did it - no change.
But finally I started to address ports of my client in a different
way. After calling twice
err = snd_seq_create_simple_port( handle, "IN",
SND_SEQ_PORT_CAP_WRITE |
SND_SEQ_PORT_CAP_SUBS_WRITE,
SND_SEQ_PORT_TYPE_PORT |
SND_SEQ_PORT_TYPE_APPLICATION );
and then twice
err = snd_seq_create_simple_port( handle, "OUT",
SND_SEQ_PORT_CAP_READ |
SND_SEQ_PORT_CAP_SUBS_READ,
SND_SEQ_PORT_TYPE_PORT |
SND_SEQ_PORT_TYPE_APPLICATION );
I was addressing them in order:
snd_seq_connect_from( handle, 0, UNITOR, 2 );
snd_seq_connect_from( handle, 1, UNITOR, 5 );
snd_seq_connect_to( handle, 2, UNITOR, 2 );
snd_seq_connect_to( handle, 3, UNITOR, 3 );
Now I use them as a pair fo bi-directional ports:
snd_seq_connect_from( handle, 0, UNITOR, 2 );
snd_seq_connect_from( handle, 1, UNITOR, 5 );
snd_seq_connect_to( handle, 0, UNITOR, 2 );
snd_seq_connect_to( handle, 1, UNITOR, 3 );
and it works OK, both ports in Unitor8 receive the events! So the Perl
wrapper must be buggy somewhere ;-)
Thank you for all your help, Clemens. I will also try to recompile
alsa on my ubuntu with init SysEsex for two Unitors included, and see
how it works.
Cheers,
Bruno
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
