Tempo overflows for any value greater than 256 about midi-parser

[davidluzgouveia]

Hello @Phibonacci, I appreciate your feedback!

Looking back, I realize this was a significant oversight on my part. I probably didn't encounter songs with such high tempos before, which led me to overlook this aspect.

Initially, when I wrote this, it wasn't intended to be universally applicable; rather, it was tailored to a specific project I was working on at that time, which had its own set of constraints, such as rounding BPM tempos to whole numbers being acceptable.

In hindsight, opting to use bytes on the model to conserve memory seems unnecessary, especially considering the small size of these files.

I'll make some time to review and update the code to fix these issues!

[cauto84]

How to get the BPM of the track? I'm a bit confused, each note is returning a different value for the tempo or BeatsMinute

[Phibonacci]

You should have a look at the MIDI protocol first to understand how it works.

Only the meta event packets of type MetaEventType.Tempo are setting the tempo. In this library it is directly converted into BPM from PPQ (Pulses per quarter note) following this formula: 60000 / (BPM * PPQ)

But there is a bug where a BPM > 256 will result in an overflow.

If you want to get the original MIDI tempo expressed in PPQ instead you should have a look at my modification.

Whatever you decide you should at least change the types of data1 and data2 from bytes to int as I did to avoid an overflow for high tempos.