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
I've found a bug in the soundfont implementation of meltysynth. It is not related to modulators or unsupported/unplanned features, so I'm opening an issue.
SF Specification, section 8.1.2:
26 attackModEnv
This is the time, in absolute timecents, from the end of the Modulation Envelope
Delay Time until the point at which the Modulation Envelope value reaches its peak.
Note that the attack is “convex”; the curve is nominally such that when applied to a
decibel or semitone parameter, the result is linear in amplitude or Hz respectively.
As you can see below, meltysynth uses linear attack instead of convex, and it is too short, compared to fluidsynth:
It seems that this issue happens because MeltySynth was made based on TinySoundFont. Below is a similar issue reported for TinySoundFont: schellingb/TinySoundFont#94
About the problem with the short attack time, it looks like TinySoundFont changes the attack based on velocity. It can probably be fixed by just removing this process:
Thank you for the information. However, I cannot use FluidSynth's code because it is under the LGPL, and I want to maintain the MIT license. I'll do some more research on this.
Hi sinshu,
I've found a bug in the soundfont implementation of meltysynth. It is not related to modulators or unsupported/unplanned features, so I'm opening an issue.
SF Specification, section 8.1.2:
As you can see below, meltysynth uses linear attack instead of convex, and it is too short, compared to fluidsynth:
This was tested using the soundfont specification test
This code was used to render the file:
The text was updated successfully, but these errors were encountered: