soundfont target engines
I've noticed that many of the handbook linked soundfont files including Msc's own were designed and edited with an E-MU chipset supporting Sound Blaster!. Is this just a historical curiosity or do the synthesizer parameters for mods, osc, filters, vib, reverb etc represent settings within Sound Blaster's DSP software? I have a lot of other sf2 files that appear, from what I can tell, to have been built on either pure hardware synths or keyboard samplers from the late 80's and 90's. (Ensoniq Mirage for example) This all occurred before the collapse of the big studios. I can imagine a number of electronic keyboard players and synth "geeks" sitting at home and creating these things with their home computers. I wonder if there is any real reason to keep the sf2/3 format going anymore, and if not, just start all over again at the source.
Comments
Nobody can know about the future.
Today, all the sf2/sf3 technology works so fine, as it is.
Will be some change about this? ???
How to know that? ???
For the moment... It is a good idea to keep all the soundfonts we have... Just in case...
In reply to Nobody can know about the… by jotape1960
It does work pretty well, doesn't it? And Fluid is moving right along too. But the secret sauce is lagging behind. This would be the depth and frequency of the "additive" acoustical ingredient. Yet this is understandable for historical reasons.
With appropriate software, many parameters in the sound font can be controlled externally.
Also, many settings can be accessed with the MIDI-CC parameters.
For both Fluid and BASS synthesizers can support the desired settings if one creates an appropriate user interface that supports the required parameters.
Someone just needs to take a look :)