[Clam-devel] Re: GSoC proposal for CLAM: Real-time synthesizer using SMS models

[Han, Yushen]

Pau,
I see. This is a good point.

I went to my CLAM_PLUGIN_PATH
There are two files now:
libplugins_continuous_excitation_synth.dylib
libplugins_spacialization.dylib

Can I know the files that you have to make the SDIF work in your
CLAM_PLUGIN_PATH?

Previously , you suggested that I could print out the loaded libraries in

void RunTimeLibraryLoader::LoadLibrariesFromPath(const std::string &
path) const
CLAM/src/Processing/Plugins/RunTimeLibraryLoader.cxx line 30

This is a good idea and I can try that later.

Best regards,
Han, Yushen

On Wed, Apr 16, 2008 at 11:19 AM, Pau Arumí Albó <parumi at iua.upf.edu> wrote:
>
>  A related issue: our current plugin loading strategy is quite "raw" in
>  the sense that we dynamically load *every* file in the plugin directory
>  list. While this works in Linux and Windows, in Mac (10.4.9) i get a
>  crash each time i provide a directory with binaries that are not clam
>  plugins.
>
>  For example if i point CLAM_PLUGIN_PATH to
>  plugins/continuousExcitationSynthesizer, and start NetworkEditor it
>  crashes when trying to load the binaries (executables, not plugins) in
>  that dir. The same happens if the clam_plugin_path points to somewhere
>  else like /usr/bin.
>
>  So this is a (not really annoying) bug, that should be fixed by
>  filtering the files we dynamically load.
>
>  P
>
>
>
>  El dc 16 de 04 del 2008 a les 17:10 +0200, en/na Pau Arumí Albó va
>  escriure:
>
>
> > > Hi, Pau
>  > >
>  > > No, it does not appear in the processing tree ( unlike what you had in
>  > > your snapshot).
>  > > By "use", I mean that
>  > > (1) I could not add it to the processing tree. (neither SDIFDatabaseReader)
>  > > (2) In SMSTools, I could do SMS analysis but could  not save the
>  > > result in SDIF (all SDIF related operation could not be done).
>  > >
>  > > Han, Yushen
>  >
>  > I've checked again now in my Mac OS 10.4.9. And it loads here.
>  > It could be some issure related on how dynamic libs are loaded in 10.5.
>  > We need some debuggin from you guys (as described in previous responses)
>  > to find out the problem.
>  >
>  > But to be sure we about the current status, could you (or Greg) confirm
>  > if other plugins are loading?
>  >
>  > To be specific, do you see the categories "[plugin] 3D Audio" and
>  > "[plugin] New Spectral Processing"?
>  > You should see them after having issued "scons install" in
>  > plugins/spacialization. And having done "export
>  > CLAM_PLUGIN_PATH=/your/prefix/lib/clam/"
>  >
>  > P
>  >
>  >
>  > >
>  > > On Wed, Apr 16, 2008 at 4:20 AM, Pau Arumí Albó <parumi at iua.upf.edu> wrote:
>  > > >
>  > > >  El dt 15 de 04 del 2008 a les 16:35 -0400, en/na Han, Yushen va
>  > > >  escriure:
>  > > >
>  > > > > Hi, Pau and Greg
>  > > >  >
>  > > >  > Thank you for your information with the snapshot, Pau.
>  > > >  >
>  > > >  > I checked out r11310 and just compiled both the CLAM and the plugin in
>  > > >  > my Mac OS X 10.5.2 again.
>  > > >  > Still, it gave the same error when I use the SDIFDatabaseProcessing.
>  > > >
>  > > >  What do you mean "use"? Does SDIFDatabaseReader appears in the
>  > > >  processing tree?? (else what kind of use?)
>  > > >
>  > > >  Note that the "SDIFDatabaseReader" entry in the processing tree (as
>  > > >  shown in the snapshot) corresponds to the "SDIFDatabseProcessing"
>  > > >
>  > > >  BTW, those comparison warnings seems totally inoffensive.
>  > > >
>  > > >  Pau
>  > > >
>  > > >
>  > > >
>  >
>  >
>
>
> > _______________________________________________
>  > Clam-devel mailing list
>  > Clam-devel at llistes.projectes.lafarga.org
>  > https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel
>
>