How come soundfonts don't keep the ADSR settings?

[2Lazy]

When I load the SF's into Fruity Soundfont Player, the ADSR settings don't load correctly. Same thing with the SFZ soundfont player. All parameters are set at 0. Isn't the ADSR settings stored internally in the soundfont?

How do you all load soundfonts "the way they're supposed to sound?"

Thanks

[P.T.]

I think they do load the way they are supposed to sound.
Whatever envelope was put on the soundfont when it was created is the default "0" setting.

[pljones]

Of course, a lot of soundfonts sound rubbish without some additional processing. A lot of the tools for creating them are, uh, cumbersome and, sometimes, inaccurate. It's often easier to throw the soundfont together in a basic way and tart it up afterwards.

Adjusting the ADSR or other settings in the player while you're using the soundfont doesn't update the soundfont file. It's treated as "read-only". If you're storing the settings in a project file, then, yes, they should still be there when you load that project.

[M'Snah]

...

[2Lazy]

Yeah, well in the Fruity SF Player, the ADSR controls are VERY SENSITIVE! Especially the release. If I raise it even just 10%, the thing has like a 2 second release! I don't recall a single SF that sounded "correct ADSR" when loading into a SF player. Back when I used an SBLive, they seemed to load very nicely.

I guess what I'm looking for is in comparison with something like a Triton. It's hard to get horns to sound decent using soundfonts. I don't know...it just seems so much easier on a keyboard.

Thanks

[learjeff]

ADSR controls are VERY SENSITIVE

Time constants in soundfonts are logarithmic -- that is, they're logarithms of the actual time. This means that the actual time changes exponentially with a change in the raw values. This makes a lot of sense. The accuracy of a time interval is always a fixed percentage of the time interval. (gobble gook, foo dat moo shish, too!)