Hi all,

I'm thinking it might be a good idea if Csound applied for mentorship
in this year's Google Summer of Code:

http://code.google.com/soc/
http://socghop.appspot.com/

I for one would be interested and eligible to participate as a student
coder, but I think Google's visibility might attract new interesting
contributors from unexpected places.

What do you think? Would devs be interested in mentoring student
coders? Are there any ideas that you want realised but haven't because
of lack of time?

Cheers,
Andrés

P.D. Here's what's need to be a mentoring organisation, from the FAQs:

How does a mentoring organization apply?
The organization should choose a single administrator to submit its
application via the Google Summer of Code 2010 site between March
8-12, 2010.
What should a mentoring organization application look like?
In addition to anything else your organization would like to submit as
an application, Google will be asking (at least) the following
questions as part of the application process:
	1.	Describe your organization.
	2.	Why is your organization applying to participate in GSoC 2010?
What do you hope to gain by participating?
	3.	Did your organization participate in past GSoCs? If so, please
summarize your involvement and the successes and challenges of your
participation.
	4.	If your organization has not previously participated in GSoC, have
you applied in the past? If so, for what year(s)?
	5.	What license(s) does your project use?
	6.	What is the URL for your ideas page?
	7.	What is the main development mailing list for your organization?
	8.	What is the main IRC channel for your organization?
	9.	Does your organization have an application template you would like
to see students use? If so, please provide it now.
	10.	Who will be your backup organization administrator?
	11.	What criteria did you use to select these individuals as mentors?
Please be as specific as possible.
	12.	What is your plan for dealing with disappearing students?
	13.	What is your plan for dealing with disappearing mentors?
	14.	What steps will you take to encourage students to interact with
your project's community before, during and after the program?
	15.	What will you do to ensure that your accepted students stick with
the project after GSoC concludes?
A few notes on the mentoring organization application:
	•	If you take a look at the program timeline, we've left about two
weeks for students to get to know you before submitting their
applications. It is critical that it be obvious how students should
reach you to discuss applying to your organization; plan to link this
information from your "Ideas" list at the very least.
	•	The email addresses associated with the Google Account information
provided during application process will be used as the primary mode
of contact by Google throughout the program, e.g. the email address
which we will use to subscribe you to the GSoC mentors/admins-only
mailing list.
What is an "Ideas" list?
An "Ideas" list should be a list of suggested student projects. This
list is meant to introduce contributors to your project's needs and to
provide inspiration to would-be student applicants. It is useful to
classify each idea as specifically as possible, e.g. "must know
Python" or "easier project; good for a student with more limited
experience with C++." If your organization plans to provide an
application template, it would be good to include it on your Ideas
list.
Keep in mind that your Ideas list should be a starting point for
student applications; we've heard from past mentoring organization
participants that some of their best student projects are those that
greatly expanded on a proposed idea or were blue-sky proposals not
mentioned on the Ideas list at all.

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-

I am interested on this. I'l have a look.

Victor
On 4 Mar 2010, at 14:58, Andres Cabrera wrote:

> Hi all,
>
> I'm thinking it might be a good idea if Csound applied for mentorship
> in this year's Google Summer of Code:
>
> http://code.google.com/soc/
> http://socghop.appspot.com/
>
> I for one would be interested and eligible to participate as a student
> coder, but I think Google's visibility might attract new interesting
> contributors from unexpected places.
>
> What do you think? Would devs be interested in mentoring student
> coders? Are there any ideas that you want realised but haven't because
> of lack of time?
>
> Cheers,
> Andrés
>
> P.D. Here's what's need to be a mentoring organisation, from the FAQs:
>
> How does a mentoring organization apply?
> The organization should choose a single administrator to submit its
> application via the Google Summer of Code 2010 site between March
> 8-12, 2010.
> What should a mentoring organization application look like?
> In addition to anything else your organization would like to submit as
> an application, Google will be asking (at least) the following
> questions as part of the application process:
> 	1.	Describe your organization.
> 	2.	Why is your organization applying to participate in GSoC 2010?
> What do you hope to gain by participating?
> 	3.	Did your organization participate in past GSoCs? If so, please
> summarize your involvement and the successes and challenges of your
> participation.
> 	4.	If your organization has not previously participated in GSoC, have
> you applied in the past? If so, for what year(s)?
> 	5.	What license(s) does your project use?
> 	6.	What is the URL for your ideas page?
> 	7.	What is the main development mailing list for your organization?
> 	8.	What is the main IRC channel for your organization?
> 	9.	Does your organization have an application template you would like
> to see students use? If so, please provide it now.
> 	10.	Who will be your backup organization administrator?
> 	11.	What criteria did you use to select these individuals as mentors?
> Please be as specific as possible.
> 	12.	What is your plan for dealing with disappearing students?
> 	13.	What is your plan for dealing with disappearing mentors?
> 	14.	What steps will you take to encourage students to interact with
> your project's community before, during and after the program?
> 	15.	What will you do to ensure that your accepted students stick with
> the project after GSoC concludes?
> A few notes on the mentoring organization application:
> 	•	If you take a look at the program timeline, we've left about two
> weeks for students to get to know you before submitting their
> applications. It is critical that it be obvious how students should
> reach you to discuss applying to your organization; plan to link this
> information from your "Ideas" list at the very least.
> 	•	The email addresses associated with the Google Account information
> provided during application process will be used as the primary mode
> of contact by Google throughout the program, e.g. the email address
> which we will use to subscribe you to the GSoC mentors/admins-only
> mailing list.
> What is an "Ideas" list?
> An "Ideas" list should be a list of suggested student projects. This
> list is meant to introduce contributors to your project's needs and to
> provide inspiration to would-be student applicants. It is useful to
> classify each idea as specifically as possible, e.g. "must know
> Python" or "easier project; good for a student with more limited
> experience with C++." If your organization plans to provide an
> application template, it would be good to include it on your Ideas
> list.
> Keep in mind that your Ideas list should be a starting point for
> student applications; we've heard from past mentoring organization
> participants that some of their best student projects are those that
> greatly expanded on a proposed idea or were blue-sky proposals not
> mentioned on the Ideas list at all.
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Thu, Mar 4, 2010 at 4:58 PM, Andres Cabrera  wrote:
> P.D. Here's what's need to be a mentoring organisation, from the FAQs:

I take it you meant P.S.? lol

This is a wonderful idea and I'm thrilled to see it brought up. I hope
it becomes a reality!
I'm neither mentor nor coder material myself, but I'll gladly buy a
"Csound Google Summer of Code" T-shirt.

-Chuckk


-- 
http://www.badmuthahubbard.com

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

But you can write Csound code! Depending on what's described in the
application you don't necessarily have to be able to code in C/C++. I
think the Pd guys did this a while back and created a set of
abstractions in Pd as part of their project, (I might be wrong but I
remember seeing it in a few threads). We can look for students to help
with documentation and examples as well as low level programming.

Rory.




On 4 March 2010 18:47, Chuckk Hubbard  wrote:
> On Thu, Mar 4, 2010 at 4:58 PM, Andres Cabrera  wrote:
>> P.D. Here's what's need to be a mentoring organisation, from the FAQs:
>
> I take it you meant P.S.? lol
>
> This is a wonderful idea and I'm thrilled to see it brought up. I hope
> it becomes a reality!
> I'm neither mentor nor coder material myself, but I'll gladly buy a
> "Csound Google Summer of Code" T-shirt.
>
> -Chuckk
>
>
> --
> http://www.badmuthahubbard.com
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I think a library of synthesizers and effects that have predefined ins
and outs using the bus for GUI connections and the signal flow graph
for orchestra interconnects would be fabulous. Especially if the sound
code was state of the art.

Regards,
Mike

On Thu, Mar 4, 2010 at 2:01 PM, Rory Walsh  wrote:
> But you can write Csound code! Depending on what's described in the
> application you don't necessarily have to be able to code in C/C++. I
> think the Pd guys did this a while back and created a set of
> abstractions in Pd as part of their project, (I might be wrong but I
> remember seeing it in a few threads). We can look for students to help
> with documentation and examples as well as low level programming.
>
> Rory.
>
>
>
>
> On 4 March 2010 18:47, Chuckk Hubbard  wrote:
>> On Thu, Mar 4, 2010 at 4:58 PM, Andres Cabrera  wrote:
>>> P.D. Here's what's need to be a mentoring organisation, from the FAQs:
>>
>> I take it you meant P.S.? lol
>>
>> This is a wonderful idea and I'm thrilled to see it brought up. I hope
>> it becomes a reality!
>> I'm neither mentor nor coder material myself, but I'll gladly buy a
>> "Csound Google Summer of Code" T-shirt.
>>
>> -Chuckk
>>
>>
>> --
>> http://www.badmuthahubbard.com
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Definitely agree with Michael on this!

Also, if anyone wants to do work on Csound's parser and/or engine
internals, I'd be happy to explain as much as I know.

On Thu, Mar 4, 2010 at 2:36 PM, Michael Gogins  wrote:
> I think a library of synthesizers and effects that have predefined ins
> and outs using the bus for GUI connections and the signal flow graph
> for orchestra interconnects would be fabulous. Especially if the sound
> code was state of the art.
>
> Regards,
> Mike
>
> On Thu, Mar 4, 2010 at 2:01 PM, Rory Walsh  wrote:
>> But you can write Csound code! Depending on what's described in the
>> application you don't necessarily have to be able to code in C/C++. I
>> think the Pd guys did this a while back and created a set of
>> abstractions in Pd as part of their project, (I might be wrong but I
>> remember seeing it in a few threads). We can look for students to help
>> with documentation and examples as well as low level programming.
>>
>> Rory.
>>
>>
>>
>>
>> On 4 March 2010 18:47, Chuckk Hubbard  wrote:
>>> On Thu, Mar 4, 2010 at 4:58 PM, Andres Cabrera  wrote:
>>>> P.D. Here's what's need to be a mentoring organisation, from the FAQs:
>>>
>>> I take it you meant P.S.? lol
>>>
>>> This is a wonderful idea and I'm thrilled to see it brought up. I hope
>>> it becomes a reality!
>>> I'm neither mentor nor coder material myself, but I'll gladly buy a
>>> "Csound Google Summer of Code" T-shirt.
>>>
>>> -Chuckk
>>>
>>>
>>> --
>>> http://www.badmuthahubbard.com
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I thinking of getting into something this deep. One of my wishes is
the abilty to modify the instrument graph while csound is running...

Cheers,
Andrés

On Thu, Mar 4, 2010 at 8:08 PM, Steven Yi  wrote:
> Definitely agree with Michael on this!
>
> Also, if anyone wants to do work on Csound's parser and/or engine
> internals, I'd be happy to explain as much as I know.
>
> On Thu, Mar 4, 2010 at 2:36 PM, Michael Gogins  wrote:
>> I think a library of synthesizers and effects that have predefined ins
>> and outs using the bus for GUI connections and the signal flow graph
>> for orchestra interconnects would be fabulous. Especially if the sound
>> code was state of the art.
>>
>> Regards,
>> Mike
>>
>> On Thu, Mar 4, 2010 at 2:01 PM, Rory Walsh  wrote:
>>> But you can write Csound code! Depending on what's described in the
>>> application you don't necessarily have to be able to code in C/C++. I
>>> think the Pd guys did this a while back and created a set of
>>> abstractions in Pd as part of their project, (I might be wrong but I
>>> remember seeing it in a few threads). We can look for students to help
>>> with documentation and examples as well as low level programming.
>>>
>>> Rory.
>>>
>>>
>>>
>>>
>>> On 4 March 2010 18:47, Chuckk Hubbard  wrote:
>>>> On Thu, Mar 4, 2010 at 4:58 PM, Andres Cabrera  wrote:
>>>>> P.D. Here's what's need to be a mentoring organisation, from the FAQs:
>>>>
>>>> I take it you meant P.S.? lol
>>>>
>>>> This is a wonderful idea and I'm thrilled to see it brought up. I hope
>>>> it becomes a reality!
>>>> I'm neither mentor nor coder material myself, but I'll gladly buy a
>>>> "Csound Google Summer of Code" T-shirt.
>>>>
>>>> -Chuckk
>>>>
>>>>
>>>> --
>>>> http://www.badmuthahubbard.com
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Download Intel® Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>> --
>> Michael Gogins
>> Irreducible Productions
>> http://www.michael-gogins.com
>> Michael dot Gogins at gmail dot com
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cs

Yes, this is definitely of interest.  We've talked about this in the
past and have identified a number of the necessary changes required.
Now we just need someone with time to do it. :)

On Thu, Mar 4, 2010 at 3:21 PM, Andres Cabrera  wrote:
> I thinking of getting into something this deep. One of my wishes is
> the abilty to modify the instrument graph while csound is running...
>
> Cheers,
> Andrés
>
> On Thu, Mar 4, 2010 at 8:08 PM, Steven Yi  wrote:
>> Definitely agree with Michael on this!
>>
>> Also, if anyone wants to do work on Csound's parser and/or engine
>> internals, I'd be happy to explain as much as I know.
>>
>> On Thu, Mar 4, 2010 at 2:36 PM, Michael Gogins  wrote:
>>> I think a library of synthesizers and effects that have predefined ins
>>> and outs using the bus for GUI connections and the signal flow graph
>>> for orchestra interconnects would be fabulous. Especially if the sound
>>> code was state of the art.
>>>
>>> Regards,
>>> Mike
>>>
>>> On Thu, Mar 4, 2010 at 2:01 PM, Rory Walsh  wrote:
>>>> But you can write Csound code! Depending on what's described in the
>>>> application you don't necessarily have to be able to code in C/C++. I
>>>> think the Pd guys did this a while back and created a set of
>>>> abstractions in Pd as part of their project, (I might be wrong but I
>>>> remember seeing it in a few threads). We can look for students to help
>>>> with documentation and examples as well as low level programming.
>>>>
>>>> Rory.
>>>>
>>>>
>>>>
>>>>
>>>> On 4 March 2010 18:47, Chuckk Hubbard  wrote:
>>>>> On Thu, Mar 4, 2010 at 4:58 PM, Andres Cabrera  wrote:
>>>>>> P.D. Here's what's need to be a mentoring organisation, from the FAQs:
>>>>>
>>>>> I take it you meant P.S.? lol
>>>>>
>>>>> This is a wonderful idea and I'm thrilled to see it brought up. I hope
>>>>> it becomes a reality!
>>>>> I'm neither mentor nor coder material myself, but I'll gladly buy a
>>>>> "Csound Google Summer of Code" T-shirt.
>>>>>
>>>>> -Chuckk
>>>>>
>>>>>
>>>>> --
>>>>> http://www.badmuthahubbard.com
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Download Intel® Parallel Studio Eval
>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>> proactively, and fine-tune applications for parallel performance.
>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Download Intel® Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>> --
>>> Michael Gogins
>>> Irreducible Productions
>>> http://www.michael-gogins.com
>>> Michael dot Gogins at gmail dot com
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
>
>
> Andrés
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi,

Mentoring organization registration for GSOC is now open, until
midnight this Friday 12 of March.

Here are the questions needed to complete registration, so I wanted to
propose some ideas, and wanted to ask who wants to set up the
application and who wants to volunteer as a mentor. Since I'm
interested in being a student coder, I can't do any of these...
The link for registration is here (you need a google login):
http://socghop.appspot.com/gsoc/org_app/take/gsoc_program/google/gsoc2010/orgapp

So here it goes, please speak out any ideas:

Organization name
Csound developer community

Description
This community takes care of the development and maintenance of the
Csound language.

Home page:
www.csounds.com

Main licence: LGPL

Why is your organization applying to participate in GSoC 2010? What do
you hope to gain by participating?
There are some ideas for additions and changes in Csound, that have
not been implemented due to developer lack of a large slot of time. It
is hoped that students may provide the extra time needed to get these
done.

Ideas page:
Where shall we put them?

Here are some of my ideas:
- Allow dynamic modification of the Csound enigne (dynamic loading and
unloading of instruments)
- Do a complete revision of opcodes and opcode plugins, to move
deprecated and redundant opcodes to a separate "deprecated" plugin
- Finish work on the new parser
- Using the new parser, allow usage of all opcodes as functions for
arguments to other opcodes


Development mailing list:
https://lists.sourceforge.net/lists/listinfo/csound-devel

IRC channel:
#csound but it is rarely used by the developers

Application template:
What should it look like?

What criteria did you use to select the individuals who will act as
mentors for your organization? Please be as specific as possible:
The mentors were chosen from a group of the core developers, who know
the central code of Csound well. They also were the ones who
volunteered for mentoring for the program.

What is your plan for dealing with disappearing students?
We hope to select the students appropriately to avoid this from
happening, but if it does, there's not much we can do appart from
being encouraging and supportive...

What is your plan for dealing with disappearing mentors?
This is unlikely as the main developers have a high commitment to
development, but if this were to happen, a second developer would take
their place.

What steps will you take to encourage students to interact with your
project's community before, during and after the program?
The Csound community is a mature community which is very friendly,
encouraging and helpful. Not only the developers, but also the users
which are active to the community are always supportive of new commers
and people with interest, so it is hoped that students will feel
comfortable interacting with the community.


What will you do to ensure that your accepted students stick with the
project after GSoC concludes?
Apart from the great community, Csound is also a big and interesting
program with many potential uses, both artistic and technical, so we
hope a student that gets to know it well will find it challenging to
continue.

Is there anything else you would like to tell the Google Summer of
Code program administration team?


Cheers,
Andrés

On Thu, Mar 4, 2010 at 8:24 PM, Steven Yi  wrote:
> Yes, this is definitely of interest.  We've talked about this in the
> past and have identified a number of the necessary changes required.
> Now we just need someone with time to do it. :)
>
> On Thu, Mar 4, 2010 at 3:21 PM, Andres Cabrera  wrote:
>> I thinking of getting into something this deep. One of my wishes is
>> the abilty to modify the instrument graph while csound is running...
>>
>> Cheers,
>> Andrés
>>
>> On Thu, Mar 4, 2010 at 8:08 PM, Steven Yi  wrote:
>>> Definitely agree with Michael on this!
>>>
>>> Also, if anyone wants to do work on Csound's parser and/or engine
>>> internals, I'd be happy to explain as much as I know.
>>>
>>> On Thu, Mar 4, 2010 at 2:36 PM, Michael Gogins  wrote:
>>>> I think a library of synthesizers and effects that have predefined ins
>>>> and outs using the bus for GUI connections and the signal flow graph
>>>> for orchestra interconnects would be fabulous. Especially if the sound
>>>> code was state of the art.
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>> On Thu, Mar 4, 2010 at 2:01 PM, Rory Walsh  wrote:
>>>>> But you can write Csound code! Depending on what's described in the
>>>>> application you don't necessarily have to be able to code in C/C++. I
>>>>> think the Pd guys did this a while back and created a set of
>>>>> abstractions in Pd as part of their project, (I might be wrong but I
>>>>> remember seeing it in a few threads). We can look for students to help
>>>>> with documentation and examples as well as low level programming.
>>>>>
>>>>> Rory.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 4 March 2010 18:47, Chuckk Hubbard  wrote:
>>>>>> On Thu, Mar 4, 2010 at 4:58 PM, Andres Cabrera  wrote:
>>>>>>> P.D. Here's what's need to be a mentoring organisation, from the FAQs:
>>>>>>
>>>>>> I take it you meant P.S.? lol
>>>>>>
>>>>>> This is a wonderful idea and I'm thrilled to see it brought up. I hope
>>>>>> it becomes a reality!
>>>>>> I'm neither mentor nor coder material myself, but I'll gladly buy a
>>>>>> "Csound Google Summer of Code" T-shirt.
>>>>>>
>>>>>> -Chuckk
>>>>>>
>>>>>>
>>>>>> --
>>>>>> http://www.badmuthahubbard.com
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Download Intel® Parallel Studio Eval
>>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Download Intel® Parallel Studio Eval
>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>> proactively, and fine-tune applications for parallel performance.
>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://www.michael-gogins.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Download Intel® Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sou

Thanks, Andres. I'm hoping to work on this tomorrow. I might get back  
to you to ask some questions.

Victor
On 9 Mar 2010, at 20:56, Andres Cabrera wrote:

> Hi,
>
> Mentoring organization registration for GSOC is now open, until
> midnight this Friday 12 of March.
>
> Here are the questions needed to complete registration, so I wanted to
> propose some ideas, and wanted to ask who wants to set up the
> application and who wants to volunteer as a mentor. Since I'm
> interested in being a student coder, I can't do any of these...
> The link for registration is here (you need a google login):
> http://socghop.appspot.com/gsoc/org_app/take/gsoc_program/google/gsoc2010/orgapp
>
> So here it goes, please speak out any ideas:
>
> Organization name
> Csound developer community
>
> Description
> This community takes care of the development and maintenance of the
> Csound language.
>
> Home page:
> www.csounds.com
>
> Main licence: LGPL
>
> Why is your organization applying to participate in GSoC 2010? What do
> you hope to gain by participating?
> There are some ideas for additions and changes in Csound, that have
> not been implemented due to developer lack of a large slot of time. It
> is hoped that students may provide the extra time needed to get these
> done.
>
> Ideas page:
> Where shall we put them?
>
> Here are some of my ideas:
> - Allow dynamic modification of the Csound enigne (dynamic loading and
> unloading of instruments)
> - Do a complete revision of opcodes and opcode plugins, to move
> deprecated and redundant opcodes to a separate "deprecated" plugin
> - Finish work on the new parser
> - Using the new parser, allow usage of all opcodes as functions for
> arguments to other opcodes
>
>
> Development mailing list:
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> IRC channel:
> #csound but it is rarely used by the developers
>
> Application template:
> What should it look like?
>
> What criteria did you use to select the individuals who will act as
> mentors for your organization? Please be as specific as possible:
> The mentors were chosen from a group of the core developers, who know
> the central code of Csound well. They also were the ones who
> volunteered for mentoring for the program.
>
> What is your plan for dealing with disappearing students?
> We hope to select the students appropriately to avoid this from
> happening, but if it does, there's not much we can do appart from
> being encouraging and supportive...
>
> What is your plan for dealing with disappearing mentors?
> This is unlikely as the main developers have a high commitment to
> development, but if this were to happen, a second developer would take
> their place.
>
> What steps will you take to encourage students to interact with your
> project's community before, during and after the program?
> The Csound community is a mature community which is very friendly,
> encouraging and helpful. Not only the developers, but also the users
> which are active to the community are always supportive of new commers
> and people with interest, so it is hoped that students will feel
> comfortable interacting with the community.
>
>
> What will you do to ensure that your accepted students stick with the
> project after GSoC concludes?
> Apart from the great community, Csound is also a big and interesting
> program with many potential uses, both artistic and technical, so we
> hope a student that gets to know it well will find it challenging to
> continue.
>
> Is there anything else you would like to tell the Google Summer of
> Code program administration team?
>
>
> Cheers,
> Andrés
>
> On Thu, Mar 4, 2010 at 8:24 PM, Steven Yi  wrote:
>> Yes, this is definitely of interest.  We've talked about this in the
>> past and have identified a number of the necessary changes required.
>> Now we just need someone with time to do it. :)
>>
>> On Thu, Mar 4, 2010 at 3:21 PM, Andres Cabrera  
>>  wrote:
>>> I thinking of getting into something this deep. One of my wishes is
>>> the abilty to modify the instrument graph while csound is running...
>>>
>>> Cheers,
>>> Andrés
>>>
>>> On Thu, Mar 4, 2010 at 8:08 PM, Steven Yi   
>>> wrote:
>>>> Definitely agree with Michael on this!
>>>>
>>>> Also, if anyone wants to do work on Csound's parser and/or engine
>>>> internals, I'd be happy to explain as much as I know.
>>>>
>>>> On Thu, Mar 4, 2010 at 2:36 PM, Michael Gogins >>> > wrote:
>>>>> I think a library of synthesizers and effects that have  
>>>>> predefined ins
>>>>> and outs using the bus for GUI connections and the signal flow  
>>>>> graph
>>>>> for orchestra interconnects would be fabulous. Especially if the  
>>>>> sound
>>>>> code was state of the art.
>>>>>
>>>>> Regards,
>>>>> Mike
>>>>>
>>>>> On Thu, Mar 4, 2010 at 2:01 PM, Rory Walsh   
>>>>> wrote:
>>>>>> But you can write Csound code! Depending on what's described in  
>>>>>> the
>>>>>> application you don't necessarily have to be able to code in C/C 
>>>>>> ++. I
>>>>>> think the Pd guys did this a while back and created a set of
>>>>>> abstractions in Pd as part of their project, (I might be wrong  
>>>>>> but I
>>>>>> remember seeing it in a few threads). We can look for students  
>>>>>> to help
>>>>>> with documentation and examples as well as low level programming.
>>>>>>
>>>>>> Rory.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 4 March 2010 18:47, Chuckk Hubbard  
>>>>>>  wrote:
>>>>>>> On Thu, Mar 4, 2010 at 4:58 PM, Andres Cabrera >>>>>> > wrote:
>>>>>>>> P.D. Here's what's need to be a mentoring organisation, from  
>>>>>>>> the FAQs:
>>>>>>>
>>>>>>> I take it you meant P.S.? lol
>>>>>>>
>>>>>>> This is a wonderful idea and I'm thrilled to see it brought  
>>>>>>> up. I hope
>>>>>>> it becomes a reality!
>>>>>>> I'm neither mentor nor coder material myself, but I'll gladly  
>>>>>>> buy a
>>>>>>> "Csound Google Summer of Code" T-shirt.
>>>>>>>
>>>>>>> -Chuckk
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> http://www.badmuthahubbard.com
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Download Intel® Parallel Studio Eval
>>>>>>> Try the new software tools for yourself. Speed compiling, find  
>>>>>>> bugs
>>>>>>> proactively, and fine-tune applications for parallel  
>>>>>>> performance.
>>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Download Intel® Parallel Studio Eval
>>>>>> Try the new software tools for yourself. Speed compiling, find  
>>>>>> bugs
>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://www.michael-gogins.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Download Intel® Parallel Studio Eval
>>>>> Try the new software tools for yourself. Speed compiling, find  
>>>>> bugs
>>>>> proactively, and fine-tune applications for parallel performance.
>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Download Intel® Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Andrés
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> -- 
>
>
> Andrés
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Can we place the 'ideas' page in sourceforge?

Andres, could you take care of that and send me the link? I'll add it  
to the application

Victor



On 9 Mar 2010, at 20:56, Andres Cabrera wrote:

> Hi,
>
> Mentoring organization registration for GSOC is now open, until
> midnight this Friday 12 of March.
>
> Here are the questions needed to complete registration, so I wanted to
> propose some ideas, and wanted to ask who wants to set up the
> application and who wants to volunteer as a mentor. Since I'm
> interested in being a student coder, I can't do any of these...
> The link for registration is here (you need a google login):
> http://socghop.appspot.com/gsoc/org_app/take/gsoc_program/google/gsoc2010/orgapp
>
> So here it goes, please speak out any ideas:
>
> Organization name
> Csound developer community
>
> Description
> This community takes care of the development and maintenance of the
> Csound language.
>
> Home page:
> www.csounds.com
>
> Main licence: LGPL
>
> Why is your organization applying to participate in GSoC 2010? What do
> you hope to gain by participating?
> There are some ideas for additions and changes in Csound, that have
> not been implemented due to developer lack of a large slot of time. It
> is hoped that students may provide the extra time needed to get these
> done.
>
> Ideas page:
> Where shall we put them?
>
> Here are some of my ideas:
> - Allow dynamic modification of the Csound enigne (dynamic loading and
> unloading of instruments)
> - Do a complete revision of opcodes and opcode plugins, to move
> deprecated and redundant opcodes to a separate "deprecated" plugin
> - Finish work on the new parser
> - Using the new parser, allow usage of all opcodes as functions for
> arguments to other opcodes
>
>
> Development mailing list:
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> IRC channel:
> #csound but it is rarely used by the developers
>
> Application template:
> What should it look like?
>
> What criteria did you use to select the individuals who will act as
> mentors for your organization? Please be as specific as possible:
> The mentors were chosen from a group of the core developers, who know
> the central code of Csound well. They also were the ones who
> volunteered for mentoring for the program.
>
> What is your plan for dealing with disappearing students?
> We hope to select the students appropriately to avoid this from
> happening, but if it does, there's not much we can do appart from
> being encouraging and supportive...
>
> What is your plan for dealing with disappearing mentors?
> This is unlikely as the main developers have a high commitment to
> development, but if this were to happen, a second developer would take
> their place.
>
> What steps will you take to encourage students to interact with your
> project's community before, during and after the program?
> The Csound community is a mature community which is very friendly,
> encouraging and helpful. Not only the developers, but also the users
> which are active to the community are always supportive of new commers
> and people with interest, so it is hoped that students will feel
> comfortable interacting with the community.
>
>
> What will you do to ensure that your accepted students stick with the
> project after GSoC concludes?
> Apart from the great community, Csound is also a big and interesting
> program with many potential uses, both artistic and technical, so we
> hope a student that gets to know it well will find it challenging to
> continue.
>
> Is there anything else you would like to tell the Google Summer of
> Code program administration team?
>
>
> Cheers,
> Andrés
>
> On Thu, Mar 4, 2010 at 8:24 PM, Steven Yi  wrote:
>> Yes, this is definitely of interest.  We've talked about this in the
>> past and have identified a number of the necessary changes required.
>> Now we just need someone with time to do it. :)
>>
>> On Thu, Mar 4, 2010 at 3:21 PM, Andres Cabrera  
>>  wrote:
>>> I thinking of getting into something this deep. One of my wishes is
>>> the abilty to modify the instrument graph while csound is running...
>>>
>>> Cheers,
>>> Andrés
>>>
>>> On Thu, Mar 4, 2010 at 8:08 PM, Steven Yi   
>>> wrote:
>>>> Definitely agree with Michael on this!
>>>>
>>>> Also, if anyone wants to do work on Csound's parser and/or engine
>>>> internals, I'd be happy to explain as much as I know.
>>>>
>>>> On Thu, Mar 4, 2010 at 2:36 PM, Michael Gogins >>> > wrote:
>>>>> I think a library of synthesizers and effects that have  
>>>>> predefined ins
>>>>> and outs using the bus for GUI connections and the signal flow  
>>>>> graph
>>>>> for orchestra interconnects would be fabulous. Especially if the  
>>>>> sound
>>>>> code was state of the art.
>>>>>
>>>>> Regards,
>>>>> Mike
>>>>>
>>>>> On Thu, Mar 4, 2010 at 2:01 PM, Rory Walsh   
>>>>> wrote:
>>>>>> But you can write Csound code! Depending on what's described in  
>>>>>> the
>>>>>> application you don't necessarily have to be able to code in C/C 
>>>>>> ++. I
>>>>>> think the Pd guys did this a while back and created a set of
>>>>>> abstractions in Pd as part of their project, (I might be wrong  
>>>>>> but I
>>>>>> remember seeing it in a few threads). We can look for students  
>>>>>> to help
>>>>>> with documentation and examples as well as low level programming.
>>>>>>
>>>>>> Rory.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 4 March 2010 18:47, Chuckk Hubbard  
>>>>>>  wrote:
>>>>>>> On Thu, Mar 4, 2010 at 4:58 PM, Andres Cabrera >>>>>> > wrote:
>>>>>>>> P.D. Here's what's need to be a mentoring organisation, from  
>>>>>>>> the FAQs:
>>>>>>>
>>>>>>> I take it you meant P.S.? lol
>>>>>>>
>>>>>>> This is a wonderful idea and I'm thrilled to see it brought  
>>>>>>> up. I hope
>>>>>>> it becomes a reality!
>>>>>>> I'm neither mentor nor coder material myself, but I'll gladly  
>>>>>>> buy a
>>>>>>> "Csound Google Summer of Code" T-shirt.
>>>>>>>
>>>>>>> -Chuckk
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> http://www.badmuthahubbard.com
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Download Intel® Parallel Studio Eval
>>>>>>> Try the new software tools for yourself. Speed compiling, find  
>>>>>>> bugs
>>>>>>> proactively, and fine-tune applications for parallel  
>>>>>>> performance.
>>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Download Intel® Parallel Studio Eval
>>>>>> Try the new software tools for yourself. Speed compiling, find  
>>>>>> bugs
>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://www.michael-gogins.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Download Intel® Parallel Studio Eval
>>>>> Try the new software tools for yourself. Speed compiling, find  
>>>>> bugs
>>>>> proactively, and fine-tune applications for parallel performance.
>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Download Intel® Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Andrés
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> -- 
>
>
> Andrés
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Application Template

Applicant's Name:
Address:
e-mail:
Contact phone number:
Institutional Affiliation (if any):
Qualifications:
Short biography:

Csound user: [ ]yes [ ] no

Have you ever developed any software related to Csound: [ ]yes [ ]no
if yes, please give details:


Have you ever developed any Free or Open Source software for audio/ 
music: [ ]yes [ ]no
if yes, please give details:


Have you ever developed any other Free or Open Source software: [ ]yes  
[ ]no
if yes, please give details:


Anything else I should add?

We should place the template in sourceforge.

Victor





On 10 Mar 2010, at 11:52, Victor Lazzarini wrote:

> Can we place the 'ideas' page in sourceforge?
>
> Andres, could you take care of that and send me the link? I'll add it
> to the application
>
> Victor
>
>
>
> On 9 Mar 2010, at 20:56, Andres Cabrera wrote:
>
>> Hi,
>>
>> Mentoring organization registration for GSOC is now open, until
>> midnight this Friday 12 of March.
>>
>> Here are the questions needed to complete registration, so I wanted  
>> to
>> propose some ideas, and wanted to ask who wants to set up the
>> application and who wants to volunteer as a mentor. Since I'm
>> interested in being a student coder, I can't do any of these...
>> The link for registration is here (you need a google login):
>> http://socghop.appspot.com/gsoc/org_app/take/gsoc_program/google/gsoc2010/orgapp
>>
>> So here it goes, please speak out any ideas:
>>
>> Organization name
>> Csound developer community
>>
>> Description
>> This community takes care of the development and maintenance of the
>> Csound language.
>>
>> Home page:
>> www.csounds.com
>>
>> Main licence: LGPL
>>
>> Why is your organization applying to participate in GSoC 2010? What  
>> do
>> you hope to gain by participating?
>> There are some ideas for additions and changes in Csound, that have
>> not been implemented due to developer lack of a large slot of time.  
>> It
>> is hoped that students may provide the extra time needed to get these
>> done.
>>
>> Ideas page:
>> Where shall we put them?
>>
>> Here are some of my ideas:
>> - Allow dynamic modification of the Csound enigne (dynamic loading  
>> and
>> unloading of instruments)
>> - Do a complete revision of opcodes and opcode plugins, to move
>> deprecated and redundant opcodes to a separate "deprecated" plugin
>> - Finish work on the new parser
>> - Using the new parser, allow usage of all opcodes as functions for
>> arguments to other opcodes
>>
>>
>> Development mailing list:
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> IRC channel:
>> #csound but it is rarely used by the developers
>>
>> Application template:
>> What should it look like?
>>
>> What criteria did you use to select the individuals who will act as
>> mentors for your organization? Please be as specific as possible:
>> The mentors were chosen from a group of the core developers, who know
>> the central code of Csound well. They also were the ones who
>> volunteered for mentoring for the program.
>>
>> What is your plan for dealing with disappearing students?
>> We hope to select the students appropriately to avoid this from
>> happening, but if it does, there's not much we can do appart from
>> being encouraging and supportive...
>>
>> What is your plan for dealing with disappearing mentors?
>> This is unlikely as the main developers have a high commitment to
>> development, but if this were to happen, a second developer would  
>> take
>> their place.
>>
>> What steps will you take to encourage students to interact with your
>> project's community before, during and after the program?
>> The Csound community is a mature community which is very friendly,
>> encouraging and helpful. Not only the developers, but also the users
>> which are active to the community are always supportive of new  
>> commers
>> and people with interest, so it is hoped that students will feel
>> comfortable interacting with the community.
>>
>>
>> What will you do to ensure that your accepted students stick with the
>> project after GSoC concludes?
>> Apart from the great community, Csound is also a big and interesting
>> program with many potential uses, both artistic and technical, so we
>> hope a student that gets to know it well will find it challenging to
>> continue.
>>
>> Is there anything else you would like to tell the Google Summer of
>> Code program administration team?
>>
>>
>> Cheers,
>> Andrés
>>
>> On Thu, Mar 4, 2010 at 8:24 PM, Steven Yi  wrote:
>>> Yes, this is definitely of interest.  We've talked about this in the
>>> past and have identified a number of the necessary changes required.
>>> Now we just need someone with time to do it. :)
>>>
>>> On Thu, Mar 4, 2010 at 3:21 PM, Andres Cabrera
>>>  wrote:
>>>> I thinking of getting into something this deep. One of my wishes is
>>>> the abilty to modify the instrument graph while csound is  
>>>> running...
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> On Thu, Mar 4, 2010 at 8:08 PM, Steven Yi 
>>>> wrote:
>>>>> Definitely agree with Michael on this!
>>>>>
>>>>> Also, if anyone wants to do work on Csound's parser and/or engine
>>>>> internals, I'd be happy to explain as much as I know.
>>>>>
>>>>> On Thu, Mar 4, 2010 at 2:36 PM, Michael Gogins >>>>> wrote:
>>>>>> I think a library of synthesizers and effects that have
>>>>>> predefined ins
>>>>>> and outs using the bus for GUI connections and the signal flow
>>>>>> graph
>>>>>> for orchestra interconnects would be fabulous. Especially if the
>>>>>> sound
>>>>>> code was state of the art.
>>>>>>
>>>>>> Regards,
>>>>>> Mike
>>>>>>
>>>>>> On Thu, Mar 4, 2010 at 2:01 PM, Rory Walsh 
>>>>>> wrote:
>>>>>>> But you can write Csound code! Depending on what's described in
>>>>>>> the
>>>>>>> application you don't necessarily have to be able to code in C/C
>>>>>>> ++. I
>>>>>>> think the Pd guys did this a while back and created a set of
>>>>>>> abstractions in Pd as part of their project, (I might be wrong
>>>>>>> but I
>>>>>>> remember seeing it in a few threads). We can look for students
>>>>>>> to help
>>>>>>> with documentation and examples as well as low level  
>>>>>>> programming.
>>>>>>>
>>>>>>> Rory.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 4 March 2010 18:47, Chuckk Hubbard
>>>>>>>  wrote:
>>>>>>>> On Thu, Mar 4, 2010 at 4:58 PM, Andres Cabrera >>>>>>>> wrote:
>>>>>>>>> P.D. Here's what's need to be a mentoring organisation, from
>>>>>>>>> the FAQs:
>>>>>>>>
>>>>>>>> I take it you meant P.S.? lol
>>>>>>>>
>>>>>>>> This is a wonderful idea and I'm thrilled to see it brought
>>>>>>>> up. I hope
>>>>>>>> it becomes a reality!
>>>>>>>> I'm neither mentor nor coder material myself, but I'll gladly
>>>>>>>> buy a
>>>>>>>> "Csound Google Summer of Code" T-shirt.
>>>>>>>>
>>>>>>>> -Chuckk
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> http://www.badmuthahubbard.com
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Download Intel® Parallel Studio Eval
>>>>>>>> Try the new software tools for yourself. Speed compiling, find
>>>>>>>> bugs
>>>>>>>> proactively, and fine-tune applications for parallel
>>>>>>>> performance.
>>>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>>>> _______________________________________________
>>>>>>>> Csound-devel mailing list
>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Download Intel® Parallel Studio Eval
>>>>>>> Try the new software tools for yourself. Speed compiling, find
>>>>>>> bugs
>>>>>>> proactively, and fine-tune applications for parallel  
>>>>>>> performance.
>>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://www.michael-gogins.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Download Intel® Parallel Studio Eval
>>>>>> Try the new software tools for yourself. Speed compiling, find
>>>>>> bugs
>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Download Intel® Parallel Studio Eval
>>>>> Try the new software tools for yourself. Speed compiling, find  
>>>>> bugs
>>>>> proactively, and fine-tune applications for parallel performance.
>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Andrés
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Download Intel® Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>> -- 
>>
>>
>> Andrés
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Some from me:

- Implement additions/improvements to the streaming phase vocoder  
signal system:
   - provide a better means of extracting residuals from sinusoidal  
tracks
   - implement onset and transient detection / processing
   - implement phase locking
   - implement real-imaginary (complex) and amp-phase signal  
operations (analysis, conversion, resynthesis,
processing).




On 9 Mar 2010, at 20:56, Andres Cabrera wrote:

> Here are some of my ideas:
> - Allow dynamic modification of the Csound enigne (dynamic loading and
> unloading of instruments)
> - Do a complete revision of opcodes and opcode plugins, to move
> deprecated and redundant opcodes to a separate "deprecated" plugin
> - Finish work on the new parser
> - Using the new parser, allow usage of all opcodes as functions for
> arguments to other opcodes


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Is here

http://socghop.appspot.com/document/show/user/csound_2010/csound_2010_ideas


On 10 Mar 2010, at 12:22, Victor Lazzarini wrote:

> Some from me:
>
> - Implement additions/improvements to the streaming phase vocoder
> signal system:
>   - provide a better means of extracting residuals from sinusoidal
> tracks
>   - implement onset and transient detection / processing
>   - implement phase locking
>   - implement real-imaginary (complex) and amp-phase signal
> operations (analysis, conversion, resynthesis,
> processing).
>
>
>
>
> On 9 Mar 2010, at 20:56, Andres Cabrera wrote:
>
>> Here are some of my ideas:
>> - Allow dynamic modification of the Csound enigne (dynamic loading  
>> and
>> unloading of instruments)
>> - Do a complete revision of opcodes and opcode plugins, to move
>> deprecated and redundant opcodes to a separate "deprecated" plugin
>> - Finish work on the new parser
>> - Using the new parser, allow usage of all opcodes as functions for
>> arguments to other opcodes
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I need a backup admin link for GSoC. Would anyone else mind  
registering at

http://socghop.appspot.com/

and then providing me with their Link ID?

Victor


On 10 Mar 2010, at 12:22, Victor Lazzarini wrote:

> Some from me:
>
> - Implement additions/improvements to the streaming phase vocoder
> signal system:
>   - provide a better means of extracting residuals from sinusoidal
> tracks
>   - implement onset and transient detection / processing
>   - implement phase locking
>   - implement real-imaginary (complex) and amp-phase signal
> operations (analysis, conversion, resynthesis,
> processing).
>
>
>
>
> On 9 Mar 2010, at 20:56, Andres Cabrera wrote:
>
>> Here are some of my ideas:
>> - Allow dynamic modification of the Csound enigne (dynamic loading  
>> and
>> unloading of instruments)
>> - Do a complete revision of opcodes and opcode plugins, to move
>> deprecated and redundant opcodes to a separate "deprecated" plugin
>> - Finish work on the new parser
>> - Using the new parser, allow usage of all opcodes as functions for
>> arguments to other opcodes
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I tried just there to set my link ID but I keep getting a server
error, surely google knows something about servers at this stage!

On 10 March 2010 13:00, Victor Lazzarini  wrote:
> I need a backup admin link for GSoC. Would anyone else mind
> registering at
>
> http://socghop.appspot.com/
>
> and then providing me with their Link ID?
>
> Victor
>
>
> On 10 Mar 2010, at 12:22, Victor Lazzarini wrote:
>
>> Some from me:
>>
>> - Implement additions/improvements to the streaming phase vocoder
>> signal system:
>>   - provide a better means of extracting residuals from sinusoidal
>> tracks
>>   - implement onset and transient detection / processing
>>   - implement phase locking
>>   - implement real-imaginary (complex) and amp-phase signal
>> operations (analysis, conversion, resynthesis,
>> processing).
>>
>>
>>
>>
>> On 9 Mar 2010, at 20:56, Andres Cabrera wrote:
>>
>>> Here are some of my ideas:
>>> - Allow dynamic modification of the Csound enigne (dynamic loading
>>> and
>>> unloading of instruments)
>>> - Do a complete revision of opcodes and opcode plugins, to move
>>> deprecated and redundant opcodes to a separate "deprecated" plugin
>>> - Finish work on the new parser
>>> - Using the new parser, allow usage of all opcodes as functions for
>>> arguments to other opcodes
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks. John's done it for me.
On 10 Mar 2010, at 15:27, Rory Walsh wrote:

> I tried just there to set my link ID but I keep getting a server
> error, surely google knows something about servers at this stage!
>
> On 10 March 2010 13:00, Victor Lazzarini   
> wrote:
>> I need a backup admin link for GSoC. Would anyone else mind
>> registering at
>>
>> http://socghop.appspot.com/
>>
>> and then providing me with their Link ID?
>>
>> Victor
>>
>>
>> On 10 Mar 2010, at 12:22, Victor Lazzarini wrote:
>>
>>> Some from me:
>>>
>>> - Implement additions/improvements to the streaming phase vocoder
>>> signal system:
>>>   - provide a better means of extracting residuals from sinusoidal
>>> tracks
>>>   - implement onset and transient detection / processing
>>>   - implement phase locking
>>>   - implement real-imaginary (complex) and amp-phase signal
>>> operations (analysis, conversion, resynthesis,
>>> processing).
>>>
>>>
>>>
>>>
>>> On 9 Mar 2010, at 20:56, Andres Cabrera wrote:
>>>
>>>> Here are some of my ideas:
>>>> - Allow dynamic modification of the Csound enigne (dynamic loading
>>>> and
>>>> unloading of instruments)
>>>> - Do a complete revision of opcodes and opcode plugins, to move
>>>> deprecated and redundant opcodes to a separate "deprecated" plugin
>>>> - Finish work on the new parser
>>>> - Using the new parser, allow usage of all opcodes as functions for
>>>> arguments to other opcodes
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

from me:

Add tracking of global variables so we can remove all an instrument
(we already have the delete opcode)

New parser verification, (a?b:c) construction, checking, type
inference etc

With new parser rework the Wilson multi-core/multi-thread code

Dynamic loading of instruments

Score sorting revisited

ConstantQ SDFT

Automated amplitude correction of instruments

Performance measurements of each opcode (needed for multi-core)

Cache-memory behaviour of opcodes

Finish the non-powerof2 oscillators

,......not so direct but spectral analysis tools to track peaks etc

 and that is before thinking

==John ffitch

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks.

New parser is there already (I will refine).
Dynamic loading too.
Multi-core code -> automatic parallelisation (there)
Peak tracking improvements (code exists and works) is also in the list.

I'll add the others.

Victor


On 10 Mar 2010, at 16:52, jpff wrote:

> from me:
>
> Add tracking of global variables so we can remove all an instrument
> (we already have the delete opcode)
>
> New parser verification, (a?b:c) construction, checking, type
> inference etc
>
> With new parser rework the Wilson multi-core/multi-thread code
>
> Dynamic loading of instruments
>
> Score sorting revisited
>
> ConstantQ SDFT
>
> Automated amplitude correction of instruments
>
> Performance measurements of each opcode (needed for multi-core)
>
> Cache-memory behaviour of opcodes
>
> Finish the non-powerof2 oscillators
>
> ,......not so direct but spectral analysis tools to track peaks etc
>
> and that is before thinking
>
> ==John ffitch
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net