-
Notifications
You must be signed in to change notification settings - Fork 17
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
Created SF3 files are invalid RIFF #36
Comments
I implemented a workaround in the script (if the input filename ends with
I still think this violates the RIFF standard and all kinds of spec-y things. Maybe it’s also responsible for some amount of playback bugs with SF3 soundfonts? |
Link to the script and the workaround applied in case someone is interested. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I’m stumbling over an issue… I’ve got a nifty Python3 script that outputs the structure and metadata of a soundfont, and I’m trying it on an SF3 for the first time today and it crashes. The cause can be traced to the soundfont file itself:
As you can easily see, the
LIST<pdta>
chunk is not properly aligned because the preceding chunk misses its mandatory padding.My parser comes up to:
The unaligned chunk is therefore
LIST<sdta>.smpl
andLIST<sdta>
itself as well.The file was generated by sf3convert.
I cannot find any reference to SF3 disabling RIFF padding… plus, the
LIST<INFO>
chunks clearly still do use padding. So I cannot even understand why this file even loads/plays in MuseScore in the first place…@davy7125 do you perhaps know? Polyphone’s sf2/sf3 loading code is very… nōn-validating, I think. Did you run into this?
I searched through all (old and current) issues and PRs here but could not find any hint regarding padding…
The text was updated successfully, but these errors were encountered: