[sdiy] MIDI parser

[paula at synth.net]

I don't think a scoring system is what's needed.
simply a comparison so people can evaluate which suits them best.

As for the criteria, I would also like to see a "speed" of processing.

Paula

On 2017-11-15 14:09, Tom Wiltshire wrote:
>> On 15 Nov 2017, at 13:39, Neil Johnson <neil.johnson71 at gmail.com> 
>> wrote:
>> 
>> Brian wrote:
>>> I second Jay’s interest in seeing a (complete) list of available MIDI 
>>> parsers. That would be quite interesting. We could even review them 
>>> to see whether some have advantages or disadvantages.
>> 
>> For this to be really useful you would need to define a set of
>> characteristics and then gauge each library against it.  That would
>> then provide objective data to sift through, rather than woolly
>> better/worse subjective opinions.
>> Things like:
>> - licence (BSD, GPL2, GPL3, etc)
>> - implementation language (C, C++, PIC Asm, etc)
>> - code footprint (kB)
>> - runtime storage footprint (kB)
>> - supported MIDI features:
>>   - realtime
>>   - MIDI modes (omni on/off, mono, poly)
>>   - SysEx
>>   - (N)RPN
>> and so on.
>> 
>> A googledocs spreadsheet would be a start.
>> 
>> Neil
> 
> While I agree with Neil’s method of evaluation, I think Roman has made
> a good point - the best MIDI parser depends on the job you’re doing.
> 
> The highest scoring parser by some set of criteria like the above
> would likely be the one that does the most things (code and runtime kB
> scores notwithstanding). But often that’s not required, and you can
> pare it down for a specific job.
> 
> Tom
> _______________________________________________
> Synth-diy mailing list
> Synth-diy at synth-diy.org
> http://synth-diy.org/mailman/listinfo/synth-diy