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
Is your feature request related to a problem? Please describe.
Spessasynth cannot decode preset names that are in UTF-8; it can only work with Ascii characters. This is a significant problem as some users may want to use Kana or CJK characters (Kanji) in their preset names.
Is your feature related to the sound library or the app/website?
App/website
Describe the solution you'd like
Make sure that preset names entered in UTF-8 render correctly.
Describe alternatives you've considered
SFe only recently included UTF-8 support for preset names (4.00.9), so nothing.
Additional context
SFe 4.00.9 now permits the use of UTF-8 in preset, instrument and sample names. Previously, UTF-8 was only permitted in the info-list chunk and not pdta.
The text was updated successfully, but these errors were encountered:
This is going to be a problematic one. You see, the soundfont parser has to woth both in the main thread and the AudioWorklet thread. The latter of which doesn't have the TextDecoder interface available, so currently spessasynth just uses String.fromCharCode
So the only way would be to implement our own UTF-8 decoder.
Is your feature request related to a problem? Please describe.
Spessasynth cannot decode preset names that are in UTF-8; it can only work with Ascii characters. This is a significant problem as some users may want to use Kana or CJK characters (Kanji) in their preset names.
Is your feature related to the sound library or the app/website?
App/website
Describe the solution you'd like
Make sure that preset names entered in UTF-8 render correctly.
Describe alternatives you've considered
SFe only recently included UTF-8 support for preset names (4.00.9), so nothing.
Additional context
SFe 4.00.9 now permits the use of UTF-8 in preset, instrument and sample names. Previously, UTF-8 was only permitted in the info-list chunk and not pdta.
The text was updated successfully, but these errors were encountered: