I have a Csound plugin opcode version of Peter Hannape's Fluidsynth (used to
be iiwusynth). This is a creditable SoundFont2 synthesizer with, apparently,
all bells and whistles. My version of this opcode also functions as a VST
plugin.

I would like to contribute this plugin to the Csound CVS. I ask any Csound
developer to let me know whether he or she prefers the plugin as Csound
only, or as a combination of Csound and VST. The VST version is rudimentary
but functional.

In either case, the Fluidsynth library itself, as well as any VST SDK files,
would have to be separately downloaded by the developer before building the
plugin.

============================================
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: "stevenyi" 
To: "Csound Developers Discussion List" 
Sent: Wednesday, October 15, 2003 10:17 PM
Subject: [CSOUND-DEV:3152] --opcode-lib stuff


> Hi all,
>
> I sent a few emails this morning but I don't think they got to the
> server.  (BTW: is it ella or earth.mills.edu? apologies if everyone has
> already read the following...)  I'm having problems with loading
> --opcode-lib=Opcodes/spectra.so (similar errors with other opcode
> libs).  I added and committed some code for error information using
> dl_error() in Top/dl_opcodes.c in loadCsoundExternals().  I am receiving
> this error when trying to load spectra.so:
>
> A dynamic linking error occurred: (Opcodes/spectra.so: undefined symbol:
> auxalloc)
>
> The whole process ran as such:
>
> [root@localhost csound5]# ./csound --opcode-lib=Opcodes/spectra.so
> test.csd
> Using csound.xmg
> 0dBFS level = 32767.0
> Csound Version 4.24beta (Oct 15 2003)
> UnifiedCSD:  test.csd
> STARTING FILE
> Creating orchestra
> Creating /tmp/file6OqOY0.orc (0x813f118)
> Creating score
> orchname:  /tmp/file6OqOY0.orc
> scorename: /tmp/fileSWAhLe.sco
> Loading libraries Opcodes/spectra.so
> libname Opcodes/spectra.so
> A dynamic linking error occurred: (Opcodes/spectra.so: undefined symbol:
> auxalloc)
> Failed to load Opcodes/spectra.so
> All loaded
> opcode=specdisp
> unknown opcode
> Compile returns -1
> Removing temporary file /tmp/fileSWAhLe.sco ...
> Removing temporary file /tmp/file6OqOY0.orc ...
>
> originally I had problems with not finding getstring, but now it's
> auxalloc (for what reason it's changed I have no clue).  This happens
> with other opcode-lib's as well.
>
> I tried it again with three opcode-libs and got:
>
> Loading libraries Opcodes/spectra.so,Opcodes/pluck.so,Opcodes/space.so
> libname Opcodes/spectra.so
> A dynamic linking error occurred: (Opcodes/spectra.so: undefined symbol:
> auxalloc)
> Failed to load Opcodes/spectra.so
> A dynamic linking error occurred: (Opcodes/pluck.so: undefined symbol:
> auxalloc)Failed to load Opcodes/pluck.so
> A dynamic linking error occurred: (Opcodes/space.so: undefined symbol:
> getstring)
>
>
> I'm a bit stumped here and have been most of the night.  Been stepping
> through with gdb and not much luck trying to figure out much.  Any
> thoughts here appreciated!
>
> thanks,
> steven
>

Maybe we should set up another repository for plugins so that they 
clearly remain separate from the core csound src tree, something like 
csound-plugins, or plugin-opcodes (so that when file releases are done 
they're clearly labeled).  Then anyone who needs cvs for their plugin 
can get a directory under that main directory, etc.

I'd personally prefer that.  As for Fluidsynth, I'm only interested in 
the Csound aspect of it but I don't see how it could hurt to have the 
VST stuff there.

Looking forward to checking it out!
steven


Michael Gogins wrote:

>I have a Csound plugin opcode version of Peter Hannape's Fluidsynth (used to
>be iiwusynth). This is a creditable SoundFont2 synthesizer with, apparently,
>all bells and whistles. My version of this opcode also functions as a VST
>plugin.
>
>I would like to contribute this plugin to the Csound CVS. I ask any Csound
>developer to let me know whether he or she prefers the plugin as Csound
>only, or as a combination of Csound and VST. The VST version is rudimentary
>but functional.
>
>In either case, the Fluidsynth library itself, as well as any VST SDK files,
>would have to be separately downloaded by the developer before building the
>plugin.
>  
>
>  
>