You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having a lot of tempo changes throws fluidsynth off-timing somewhy (compared to timidity and audacity midi parsing).
Attached file is one case where it happens. file1.midi has repeated tempo change tags that all change it to the exact same value. file2.midi has just the first of them. Effectively, they should be synthesized to the same audio, but in practice file1 is longer.
It does a floating point calculation of the time diff between now and the last tempo change event. The result is then casted to int, every such cast results in an error. For file1.midstart_msec gets updated frequently and the error seems to increase, as start_msec is nearly the same as cur_msec.
For 1.1.7 the time diff after about 1.5 minutes of playback is about 0.15 seconds between the two files. For 1.1.6 the diff was 0.26 seconds. I dont think we can get it any better without rewriting fluid_player and I dont see this to happen soon. Closing for now.
Having a lot of tempo changes throws fluidsynth off-timing somewhy (compared to timidity and audacity midi parsing).
Attached file is one case where it happens. file1.midi has repeated tempo change tags that all change it to the exact same value. file2.midi has just the first of them. Effectively, they should be synthesized to the same audio, but in practice file1 is longer.
Reported by: velochy
Original Ticket: fluidsynth/tickets/143
The text was updated successfully, but these errors were encountered: