I thought we could come up with some items
for discussion when some of us meet in Berlin.
That will also allow us to get some views on
them from Michael and Anthony who will not be
there and from other people on this list.

So any suggestions?

Victor

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Ignore this message, just a test, sorry



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi,

I'm very disappointed to say I won't make it to Berlin.... I would have
loved to be there....

But I'll pitch in with some thoughts (maybe the developer meeting could
also include irc.... =) )

My main interest is also Victor's:
Dynamic loading and unloading of instruments.

I've given this some thought, and think this can be handled something
like this (I may be way off since I don't know csound internals):
- Named instruments would be created after the last named instrument
- Numbered instruments would be created in their proper place in the
instrument chain, possibly overwriting existing instruments. All notes
for the instrument should be stopped if any are still active. I'm not
sure about global variables that might have been created by the
instrument. Maybe they should not be deleted, but they just maintain
their value, though they will not be accessible for new instruments if
not defined elsewhere.
- An instrument can be created without name or number and it is placed
as a "Node" after all named instruments and previously created nodes.

-When a new instrument is to be added, a copy of the instrument chain in
made, the instrument added or inserted to the copy, and the copy
replaces the original when all error checking and note cancellation is
produced.

Additionally (I'm not sure if this is possible already) the API could be
able to receieve strings, with mixed score and orchestra statements, and
parse that all together in realtime to trigger notes and score events,
and to add or remove instruments.

Am I too way off?

Cheers,
Andres


Steven Yi wrote:
> Hi Victor and All,
>
> Some ideas on my mind to discuss:
>
> -New parser
> -Manual (I'd like to see useful boundary values on each parameter as
> well as done in a standardized way that is easy to parse)
> -Release build practice (we need an automated script for each platform
> that will pull from CVS and build the entire release, something anyone
> could do without much configuration)
> -Technical Documentation - beyond the API, perhaps looking at a need
> for documentation describing the Engine and how it operates, including
> how memory is allocated and opcodes set up, how things work at
> performance time, etc.  This kind of thing might be useful for
> everyone working on the program as well as for others studying
> computer music software.
>
> I'm sure there will be other ideas that pop up but just thought I'd
> get the brain storming started! =)
>
> steven
>
>
> On 3/13/07, Victor Lazzarini  wrote:
>   
>> I thought we could come up with some items
>> for discussion when some of us meet in Berlin.
>> That will also allow us to get some views on
>> them from Michael and Anthony who will not be
>> there and from other people on this list.
>>
>> So any suggestions?
>>
>> Victor
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>     
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>   



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Currently only score events (as strings as well).

At 15:20 15/03/2007, you wrote:
>Additionally (I'm not sure if this is possible already) the API could be
>able to receieve strings, with mixed score and orchestra statements, and
>parse that all together in realtime to trigger notes and score events,
>and to add or remove instruments.

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


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I mean after compilation.

At 09:10 16/03/2007, you wrote:
>Currently only score events (as strings as well).
>
>At 15:20 15/03/2007, you wrote:
> >Additionally (I'm not sure if this is possible already) the API could be
> >able to receieve strings, with mixed score and orchestra statements, and
> >parse that all together in realtime to trigger notes and score events,
> >and to add or remove instruments.
>
>Victor Lazzarini
>Music Technology Laboratory
>Music Department
>National University of Ireland, Maynooth
>
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys-and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

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


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net