Hi Dirk,
the problem is that this is probably non-trivial:
MIDI has something that is called "running-status" where some commands
are abbreviated by ommiting the first octet if that is the same in
the consecutive commands.
I really don't know how I could do the MIDI-dissection without knowing
where the actual Status-Byte comes from (in RTP-MIDI each packet still
contains a "phantom" running-status at the beginning of the command
section). This might not be the case for all ip-based MIDI-protocols...
Tobias
> -----Ursprüngliche Nachricht-----
> Von: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] Im Auftrag von
> Dirk Jagdmann
> Gesendet: Donnerstag, 9. Dezember 2010 17:47
> An: Developer support list for Wireshark
> Betreff: Re: [Wireshark-dev] Enhancement-Request: RTP-MIDI dissector
>
> Tobias Erichsen wrote:
> > Hi everyone,is there anyone who can give me some feedback
> on the time
> > it will take,until someone takes a look at my enhancement
> >
> request:https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=54
51Thanks
> > a lot...Best regards,Tobias
>
> So far I have only looked at your code and it looks fine.
> However there are some other MIDI over network (on different
> layers) protocols out there. Since you have made such a nice
> general MIDI dissector, how about factoring out that into a
> separate "module", which can be called from other/future
> dissectors, so that we don't need to have a new MIDI
> dissection implementation for other protocols.
>
> --
> ---> Dirk Jagdmann
> ----> http://cubic.org/~doj
> -----> http://llg.cubic.org
> ______________________________________________________________
> _____________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
