TempoEvent Parsing Issue about drywetmidi HOT 8 CLOSED

Hi @Yorgg,

Thank you for reporting the issue. But I don't see a file you've attached. Please attach it again. And the problem is last tempo change event is missed in TempoMap, yes?

from drywetmidi.

Hi,

Yes, correct. Here is the file:
prelude_124bpm.mid.zip

from drywetmidi.

Thanks, I see that last tempo change event. But this is the only tempo change event in the file and it is the last event as you said. This event presented in tempo map. And... What's wrong?

What does this mean: Drywetmidi does not seem to correctly parse them and always uses the default (120bpm) tempo? Events in MIDI file are processed according to time where they are placed. If you expect that this tempo change should apply to entire file from its start, it is wrong assumption.

from drywetmidi.

Hi,

Thanks for clarifying.
I wasn't sure if this is a bug for Logic Pro X. I guess it is probably a bug?
I'm not sure why Logic is placing the tempo change event at the end, and not at the beginning.

from drywetmidi.

Hmm, strange behavior.. especially from professional DAW like Logic Pro. Please describe entire workflow starting from placing tempo change in Logic Pro and ending with exporting a MIDI file.

Also: are you sure you're placing tempo change at the start of MIDI file in Logic Pro? Maybe at this moment cursor is placed at the end of file?

from drywetmidi.

@Yorgg Did you solve the problem?

from drywetmidi.

Hi,
I wasn't able to figure out what was causing Logic to save the file in this way.
I will close this issue. Thanks for the help!

from drywetmidi.

@Yorgg Although you've closed the issue please try to install latest version of Logic Pro since it can have fixes for some bugs including the one you discovered.

from drywetmidi.