Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Still timing issues - now with the command line program #519

Closed
prof-spock opened this issue Mar 14, 2019 · 4 comments
Closed

Still timing issues - now with the command line program #519

prof-spock opened this issue Mar 14, 2019 · 4 comments
Labels
Milestone

Comments

@prof-spock
Copy link

This is a repetition of #192 (that has already been closed for 1.1.7).
But there still seems to be some problem with the timing; I have tried version 1.1.10, 1.1.11 and 2.0.1 with
drums-test.zip
The midi file and the flac file generated by fluidsynth on a Windows command line are not in sync (but they should).
Any ideas?

@derselbst
Copy link
Member

derselbst commented Mar 15, 2019

I see, the flac plays slightly faster than it's supposed to be. Did you use the file renderer? I also wonder why the AllNotesOff event triggers a noteon.

@prof-spock
Copy link
Author

I used the commandline fluidsynth with the "-F" flag as follows:
fluidsynth.exe -n -i -g 1 -R 0 -F drums-test.wav FluidR3_GM.SF2 drums-test.mid

@derselbst derselbst added the bug label Mar 15, 2019
@derselbst derselbst added this to the 2.0-post milestone Mar 15, 2019
@derselbst
Copy link
Member

I looked into this. The midi file you provided does not specify the tempo. The MIDI spec says that in this case a default of 120 BPM should be assumed. The midi player of fluidsynth however uses 125 BPM as default. I've fixed that in the commit above.

@prof-spock
Copy link
Author

Thanks a lot, derselbst! Precise analysis, quick fix...

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants