-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Which Fluidsynth version is used in recent released builds? #32
Comments
Hi |
Thanks! I’ll bother PawPaw maintainers then. 🙂 |
It got updated! 👏 Try using the newer version now. 🌊 |
Yes, it's using version 2.0.0 now. |
Oh my bad I haven’t checked that it’s just 2.0.0 which is earlier than 2.2.2 where the support was listed officially, but I’ll still check if maybe 2.0.0 somehow works too. 👍 EDIT: Yeah it seems we need 2.2.2 for this to work… |
Using the 0.9.2 release, I seemed to have a microtuning issue that should’ve been fixed in Fluidsynth 2.2.2 a while ago. Which version of Fluidsynth is used?
I see it doesn’t seem to appear in the dependencies explicitly, so maybe an outdated version is installed on a machine where the builds are generated? I don’t know.
I used the Windows build.
The way to check the bug is there (if in other builds it’s not there) is loading a melodic sf2 instrument, and applying a tuning...
Contrary, when the tuning is applied as should be in Fluidsynth ≥ 2.2.2, a note’s target sample, and thus timbre, will depend only on its actual pitch and not on which MIDI note was received (samples get chosen by notes’ frequencies).
I’ll re-check if I heard what I heard if you don’t find anything suspicious (or the version of Fluidsynth used is recent enough).
The text was updated successfully, but these errors were encountered: