Quantcast

which opcodes to port?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

which opcodes to port?

Niklas Klügel
Hi,
I am wondering which opcodes exactly should be ported over to the new plugin
design.
is it in general the whole Oops/ directory that has to be ported? I checked
the code which is responsible for plugin loading as well as the already
working plugins and I think I am able to start working on it; however,
are there any pitfalls and stumbling blocks that I might not expect because of
certain csound internals that I am not familiar with?
Thanks,
Niklas


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Csound-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: which opcodes to port?

Michael Gogins
The major issue will be opcodes that do not restrict themselves to using the Csound API (i.e. the function pointers hanging of the ENVIRON *object that is passed with all opcode calls), but directly access objects or functions in the Csound code. Most of this should be pretty easy to fix. The commonest and easiest to fix is using csound->Message in place of other ways of printing messages. In some cases, you may identify an object that requires access for which there needs to be a new API function. In such cases, you can go ahead and add the new API at the end of the ENVIRON list -- making sure that it follows the established naming conventions and takes ENVIRON *csound as its first parameter.

Another issue might be opcodes that link with external shared libraries that also link with Csound. Different operating systems may behave differently with respect to shared libraries.

In addition to making plugins out of static opcodes, there are bugs and other problems. As you may or may not know, there is a Csound orchestra by Oeyvind Brandtsegg called "Improsculpt", a very ambitious live performance instrument, that has so far refused to run properly with Csound 5. Getting this to work would be a real plus, and probably end up fixing a good chunk of the outstanding issues.

Regards,
Mike

-----Original Message-----
From: Niklas Kl�gel <[hidden email]>
Sent: May 13, 2005 1:07 PM
To: [hidden email]
Subject: [Cs-dev] which opcodes to port?

Hi,
I am wondering which opcodes exactly should be ported over to the new plugin
design.
is it in general the whole Oops/ directory that has to be ported? I checked
the code which is responsible for plugin loading as well as the already
working plugins and I think I am able to start working on it; however,
are there any pitfalls and stumbling blocks that I might not expect because of
certain csound internals that I am not familiar with?
Thanks,
Niklas


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Csound-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
<a href="http://ads.osdn.com/?ad_ids93&alloc_id281&op=click">http://ads.osdn.com/?ad_ids93&alloc_id281&op=click
_______________________________________________
Csound-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/csound-devel
Loading...