Thanks for the clarification. I may have lost sight of the needs of those
who wish access to the samples within SoundFonts without SoundFont
processing, to perform their own processing in Csound. As you say, there is
definitely room for both opcodes in the Csound world.

The fluid opcode does perform various kinds of interpolation.

============================================
Michael Gogins
gogins at pipeline period com
Irreducible Productions
Silence, a language for programming music and sound
Available at http://sourceforge.net/projects/silencevst/
============================================


----- Original Message ----- 
From: "Gabriel Maldonado" 
To: "Csound Developers Discussion List" 
Sent: Thursday, October 23, 2003 4:31 AM
Subject: [CSOUND-DEV:3206] Re: New commits for CsoundVST


> I remember that the old soundfont opcodes (i.e. sfload, sfplist,
> sfilist, sfpassign, sfpreset, sfplay, sfplaym, sfinstr, sfinstrm)
> were never intended to provide a literal emulation of CreativeLabs
> synthesizers. They have been introduced only with the purpose to easily
> access to sf2 sample keymaps (not the parameters related to LFOs,
> envelopes, filters and so on), whose output (and input) can be modified
> and processed by means of all the csound power. These opcodes, if used
> together with other Csound native opcodes, allow to handle the sf2
> sample keymaps in several ways that creativelabs synthesizers simply
> cannot allow, such as, for example:
>
> FM (and AM) with samples at audio rate,
> customized and asymmetrical micro-tuning scales
> modify the starting read point of a sample note per note
>
> On the other part, the sound quality of original Live and Audigy card
> sampler surpasses that of the other software emulation, due to a
> proprietary 8-point realtime interpolation.
>
> Summing up, i think that both fluidsynth and old sf2 opcodes can be
> useful for different categories of use.
>
> Gabriel
>
> Michael Gogins wrote:
>
> > I have also committed the "fluid" plugin opcode (also runs as a VST
plugin),
> > based on Peter Hanappe's FluidSynth SoundFont 2 synthesizer. While
Csound
> > has had a degree of SoundFont support for some time, the fluid opcode
> > implements all aspects of the SoundFont 2 specification and enables
> > SoundFonts to be used with their key mappings and effects intact.
> >
>