Csound Csound-dev Csound-tekno Search About

Re: [Cs-dev] New file release for Csound 5 and CsoundVST

Date2005-04-15 14:48
FromMichael Gogins
SubjectRe: [Cs-dev] New file release for Csound 5 and CsoundVST
All the Instrmnt classes from the "demo" program (listed by that program when you run it), except Mesh2D. No effects. Not all of the opcodes work perfectly, but some of them are very good and very useful.

This is not to denigrate the work done by John ffitch to port many of these as opcodes in C. Some of John's opcodes now also are very good. I just wanted to schlepp them all in as they were. 

In the future I may code some opcodes of my own using the STK and include them in this plugin.  I wrote a template adapter class so that once you have the Instrmnt class defined, you just have to set the OENTRY structure up to have a new opcode.

Here's a question for John ffitch or Istvan Varga or others who probably know more about kperf and musmon and whatnot than I do: what would it take to have plugin INSTRUMENTS in Csound? This is something that I have long wanted. In other words, instead of defining instr N in the orc file, you would define an instance for a new module, similar to an opcode, written and compiled in C or C++, that would show up as instr N for the score.

-----Original Message-----
From: Victor Lazzarini 
Sent: Apr 15, 2005 4:00 AM
To: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] New file release for Csound 5 and CsoundVST

Could you give us some more info on this? What classes from his toolkit are
available as a plugin opcode? Can you give us a quick csound example?
Thanks


>Recent changes include an improved Windows installer, the addition of 
>Perry Cook's Synthesis Toolkit in C++ (original code) as a plugin opcode 
>library

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-04-16 07:01
FromAnthony Kozar
SubjectRe: [Cs-dev] New file release for Csound 5 and CsoundVST
This is an interesting idea -- more akin to Music4C or something.

I'm not very knowledgable about the internals, but I was thinking that maybe
this could be done a little bit along the lines of UDOs.  By which I mean
that an instrument library is loaded and a new entry in the opcode list
could be created for that instrument.  Then a new instrument template would
be created with that opcode as an entry (the sole entry?) in its opcode
chain.

pfields could be plugged in to the opcode parameters.  I'm not sure how to
handle audio output (or input) though.  Either direct output via some macro
or API call or perhaps the instrument should work similarly to an opcode and
fill a number of a-rate variables for out parameters.  In the latter case,
adding an appropriate "out" opcode to the instrument template would be
necessary.

It does kind of beg the question though of why not just write the instrument
as a single opcode and write the simple instrument to interface with it in
the orchestra ??

*shrug*

Just some late-night thoughts ...

Anthony

On 4/15/05 9:48 AM, Michael Gogins  etched in stone:

> Here's a question for John ffitch or Istvan Varga or others who probably know
> more about kperf and musmon and whatnot than I do: what would it take to have
> plugin INSTRUMENTS in Csound? This is something that I have long wanted. In
> other words, instead of defining instr N in the orc file, you would define an
> instance for a new module, similar to an opcode, written and compiled in C or
> C++, that would show up as instr N for the score.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net