Hi, i replied in the reverse order..
At Wed, 5 Dec 2001 01:16:35 -0500, Michael Ashton wrote: > > > I've been poking through the sequencer code a bit, and noticed two > things which puzzle me. Both are to do with the way variable-length > events are transmitted: > > 1. Why does snd_seq_event_output_direct() allocate a temporary buffer > and copy the data to it? Wouldn't it be more efficient to read > directly from the pointer provided with the event? Yes, definetely. > 2. The kernel code seems to have the ability to read data for > variable-length packets directly out of user space, but this > doesn't seem to be used by the library code - why not? Yes. As mentioned in the last mail, it's just because of implementation of VARIABLE length events. If it's VARUSR event, no need for that. So far, both length-types are checked according the event type, and SYSEX is assigned only to VARIABLE event. Perhaps this can be fixed soon. Takashi _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
