My plan is for CsoundVST to load and use the csnd module as one Python extension, and the Silence algo-comp classes as another Python extension module. But, I may simply drop the Python support from CsoundVST and let it be purely a VST plugin. I prefer to code and compose in a Python code editor anyway.

So, do you think it would work to run Csound from Python importing "csnd" on OS X?

Thanks,
Mike

-----Original Message-----
From: Victor Lazzarini 
Sent: Oct 27, 2005 11:03 AM
To: csound-devel@lists.sourceforge.net
Subject: [Cs-dev] OSX CsoundVST issues

| At 15:31 27/10/2005, you wrote:
| What would need to be changed to build and run it on OS X?

I'm still looking at it, but I think the problem lies in the
way the same dynamic lib is used twice in the program. In other
systems, this is not a problem as the same type of dynamic lib
is used as an ordinary shared library and a loadable module.

The problem on OSX lies in the fact that, and that seems to be
a python-specific issue, python loadable modules are bundles,
and not shared libs.

There is no way that the same file can be used as a python module
and a dynamic-link library. So I tried creating two: this  generates two
separate instances of csound. Then, as Istvan suggested, I tried
linking the bundle to the dynamic library: python can't find the
entry point. Finally, moved the wrapper object code to the bundle
from the dynamic library. Now python can see the entry point,
but CsoundVST crashes. Gdb tells me that the program
received EXC_BAD_ACCESS, could not access memory (in
__dynamic_cast()).

When running python and then loading the module, gdb tells me
it is stuck in _semaphore_wait_signal_trap().

So I am not sure now, given what gdb is telling me, what problems
are there. But one thing is sure, the wrapper code works, because
if I build a bundle with all the csoundVST sources statically in it,
the module loads OK in Python.

I noticed that System.cpp was throwing a lot of warnings. One of them
was a linking problem of symbol redefinition (basename(), which is
found in libpthread and I renamed to basename_(), but that did not
change anything).

The answer to your question is probably I don't know. However,
you could consider making a CsoundVST program that is not a
python module, since there is now a python module in _csnd.so.
I'm not sure it would be what you want, though.

Victor



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net