From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Enderborg Subject: Re: Rawmidi bug or missed feature? Date: Sat, 02 Mar 2002 23:20:08 +0100 Message-ID: <3C815018.DD8FA324@ufh.se> References: <3C80D439.90AC04A9@ufh.se> <15489.4604.699052.853933@elf2.elf.org> <3C811BA0.633E219D@ufh.se> <15489.14682.987661.705929@elf2.elf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: Cc: "alsa-devel@lists.sourceforge.net" List-Id: alsa-devel@alsa-project.org Roger E Critchlow Jr wrote: > Peter Enderborg writes: > > > > Roger E Critchlow Jr wrote: > > [ ... ] > > > > Does this help? > > > > > > > Well. I guess it do. I will give it a try. It should work. What about non midi > > snd_seq_event_t. > > The internal alsa stuff, like subscribe? > > > > Hmm, hadn't thought about it. You can look at the event type and > decide whether it's worth decoding, or just hand it to the decoder > and see if events which don't translate to midi just go away by > themselves, or you could look at the source for the library and see > if snd_seq_set_client_event_filter can do the work for you. > Im playing with it now. Realy nice. But there are some feature that are missing I think There are some undefined messages within the midi spec. The bytes F4, F5,F9,FD are undefined. Right now the parser ignores them and that make's thinks a little harder for me... An idea is that alsa could encapulate them in a own variable length message. Otherwise we can not be transparant! (or have I missed something?) > > -- rec -- > > _______________________________________________ > Alsa-devel mailing list > Alsa-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-devel -- foo! _______________________________________________ Alsa-devel mailing list Alsa-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-devel