Csound Csound-dev Csound-tekno Search About

[Cs-dev] csoundInitialize

Date2013-06-29 04:01
FromAndres Cabrera
Subject[Cs-dev] csoundInitialize
AttachmentsNone  None  
Hi,

Looking at the sources for csoundInitialize, it seems that argv and argc are now longer required. Maybe they should be removed?

Cheers,
Andrés

Date2013-06-29 08:41
FromPINOT Francois
SubjectRe: [Cs-dev] csoundInitialize
They were never required. I once asked if they were a placeholder for 
further development and Victor answered yes if I remember.

Regards

Francois

Le 29/06/2013 05:01, Andres Cabrera a écrit :
> Hi,
>
> Looking at the sources for csoundInitialize, it seems that argv and 
> argc are now longer required. Maybe they should be removed?
>
> Cheers,
> Andrés
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
>
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2013-06-29 08:57
FromVictor Lazzarini
SubjectRe: [Cs-dev] csoundInitialize
yes, but that was Istvan's idea, and I am not sure what he had in mind back then. Maybe they can go.
On 29 Jun 2013, at 08:41, PINOT Francois wrote:

> They were never required. I once asked if they were a placeholder for 
> further development and Victor answered yes if I remember.
> 
> Regards
> 
> Francois
> 
> Le 29/06/2013 05:01, Andres Cabrera a écrit :
>> Hi,
>> 
>> Looking at the sources for csoundInitialize, it seems that argv and 
>> argc are now longer required. Maybe they should be removed?
>> 
>> Cheers,
>> Andrés
>> 
>> 
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>> 
>> Build for Windows Store.
>> 
>> http://p.sf.net/sfu/windows-dev2dev
>> 
>> 
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2013-06-29 16:57
FromAndres Cabrera
SubjectRe: [Cs-dev] csoundInitialize
AttachmentsNone  None  
I think they can go, especially since there are many new functions to set options.

In fact, the only thing the function does is protect against running itself simultaneously from another thread, check whether the time resolution of the system is not 0 (very unlikely that it is on most current platforms), registers signal handlers and atexit functions (which have caused me some grief recently...), and set the global init_done function to 1. I also see that csoundCreate checks if csound has been initialized and runs csoundInitialize if it hasn't.

So it seems there might be no reason to have csoundInitialize in the API, as it will always be called by csoundCreate?

Cheers,
Andrés



On Sat, Jun 29, 2013 at 12:57 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
yes, but that was Istvan's idea, and I am not sure what he had in mind back then. Maybe they can go.
On 29 Jun 2013, at 08:41, PINOT Francois wrote:

> They were never required. I once asked if they were a placeholder for
> further development and Victor answered yes if I remember.
>
> Regards
>
> Francois
>
> Le 29/06/2013 05:01, Andres Cabrera a écrit :
>> Hi,
>>
>> Looking at the sources for csoundInitialize, it seems that argv and
>> argc are now longer required. Maybe they should be removed?
>>
>> Cheers,
>> Andrés
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>>
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


Date2013-06-29 17:34
FromVictor Lazzarini
SubjectRe: [Cs-dev] csoundInitialize
AttachmentsNone  None  
We just need to check whether there are any functions that can be called between csoundInitialize and csoundCreate, that would be affected if we removed
csoundInitialize. Or if there are any scenarios where we need to call csoundInitialize first and then call csoundCreate.

On 29 Jun 2013, at 16:57, Andres Cabrera wrote:

I think they can go, especially since there are many new functions to set options.

In fact, the only thing the function does is protect against running itself simultaneously from another thread, check whether the time resolution of the system is not 0 (very unlikely that it is on most current platforms), registers signal handlers and atexit functions (which have caused me some grief recently...), and set the global init_done function to 1. I also see that csoundCreate checks if csound has been initialized and runs csoundInitialize if it hasn't.

So it seems there might be no reason to have csoundInitialize in the API, as it will always be called by csoundCreate?

Cheers,
Andrés



On Sat, Jun 29, 2013 at 12:57 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
yes, but that was Istvan's idea, and I am not sure what he had in mind back then. Maybe they can go.
On 29 Jun 2013, at 08:41, PINOT Francois wrote:

> They were never required. I once asked if they were a placeholder for
> further development and Victor answered yes if I remember.
>
> Regards
>
> Francois
>
> Le 29/06/2013 05:01, Andres Cabrera a écrit :
>> Hi,
>>
>> Looking at the sources for csoundInitialize, it seems that argv and
>> argc are now longer required. Maybe they should be removed?
>>
>> Cheers,
>> Andrés
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>>
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




Date2013-06-29 20:36
FromAndres Cabrera
SubjectRe: [Cs-dev] csoundInitialize
AttachmentsNone  None  
Thinking about it, there may be times when hosts might want to initialize Csound without the signal handlers or the atexit, so I think csoundInitialize is still justified. But it needs to be clear in the docs that it's no longer compulsory, as csoundCreate will check for previous initialization.

Cheers,
Andrés


On Sat, Jun 29, 2013 at 9:34 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
We just need to check whether there are any functions that can be called between csoundInitialize and csoundCreate, that would be affected if we removed
csoundInitialize. Or if there are any scenarios where we need to call csoundInitialize first and then call csoundCreate.


On 29 Jun 2013, at 16:57, Andres Cabrera wrote:

I think they can go, especially since there are many new functions to set options.

In fact, the only thing the function does is protect against running itself simultaneously from another thread, check whether the time resolution of the system is not 0 (very unlikely that it is on most current platforms), registers signal handlers and atexit functions (which have caused me some grief recently...), and set the global init_done function to 1. I also see that csoundCreate checks if csound has been initialized and runs csoundInitialize if it hasn't.

So it seems there might be no reason to have csoundInitialize in the API, as it will always be called by csoundCreate?

Cheers,
Andrés



On Sat, Jun 29, 2013 at 12:57 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
yes, but that was Istvan's idea, and I am not sure what he had in mind back then. Maybe they can go.
On 29 Jun 2013, at 08:41, PINOT Francois wrote:

> They were never required. I once asked if they were a placeholder for
> further development and Victor answered yes if I remember.
>
> Regards
>
> Francois
>
> Le 29/06/2013 05:01, Andres Cabrera a écrit :
>> Hi,
>>
>> Looking at the sources for csoundInitialize, it seems that argv and
>> argc are now longer required. Maybe they should be removed?
>>
>> Cheers,
>> Andrés
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>>
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel



Date2013-06-29 21:17
FromVictor Lazzarini
SubjectRe: [Cs-dev] csoundInitialize
AttachmentsNone  None  
I think that was always the case in Csound 5 too.
On 29 Jun 2013, at 20:36, Andres Cabrera wrote:

Thinking about it, there may be times when hosts might want to initialize Csound without the signal handlers or the atexit, so I think csoundInitialize is still justified. But it needs to be clear in the docs that it's no longer compulsory, as csoundCreate will check for previous initialization.

Cheers,
Andrés


On Sat, Jun 29, 2013 at 9:34 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
We just need to check whether there are any functions that can be called between csoundInitialize and csoundCreate, that would be affected if we removed
csoundInitialize. Or if there are any scenarios where we need to call csoundInitialize first and then call csoundCreate.


On 29 Jun 2013, at 16:57, Andres Cabrera wrote:

I think they can go, especially since there are many new functions to set options.

In fact, the only thing the function does is protect against running itself simultaneously from another thread, check whether the time resolution of the system is not 0 (very unlikely that it is on most current platforms), registers signal handlers and atexit functions (which have caused me some grief recently...), and set the global init_done function to 1. I also see that csoundCreate checks if csound has been initialized and runs csoundInitialize if it hasn't.

So it seems there might be no reason to have csoundInitialize in the API, as it will always be called by csoundCreate?

Cheers,
Andrés



On Sat, Jun 29, 2013 at 12:57 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
yes, but that was Istvan's idea, and I am not sure what he had in mind back then. Maybe they can go.
On 29 Jun 2013, at 08:41, PINOT Francois wrote:

> They were never required. I once asked if they were a placeholder for
> further development and Victor answered yes if I remember.
>
> Regards
>
> Francois
>
> Le 29/06/2013 05:01, Andres Cabrera a écrit :
>> Hi,
>>
>> Looking at the sources for csoundInitialize, it seems that argv and
>> argc are now longer required. Maybe they should be removed?
>>
>> Cheers,
>> Andrés
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>>
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




Date2013-07-02 17:01
FromAndres Cabrera
SubjectRe: [Cs-dev] csoundInitialize
AttachmentsNone  None  
OK, removed the unnecessary arguments and adjusted the documentation.

Cheers,
Andrés


On Sat, Jun 29, 2013 at 1:17 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
I think that was always the case in Csound 5 too.

On 29 Jun 2013, at 20:36, Andres Cabrera wrote:

Thinking about it, there may be times when hosts might want to initialize Csound without the signal handlers or the atexit, so I think csoundInitialize is still justified. But it needs to be clear in the docs that it's no longer compulsory, as csoundCreate will check for previous initialization.

Cheers,
Andrés


On Sat, Jun 29, 2013 at 9:34 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
We just need to check whether there are any functions that can be called between csoundInitialize and csoundCreate, that would be affected if we removed
csoundInitialize. Or if there are any scenarios where we need to call csoundInitialize first and then call csoundCreate.


On 29 Jun 2013, at 16:57, Andres Cabrera wrote:

I think they can go, especially since there are many new functions to set options.

In fact, the only thing the function does is protect against running itself simultaneously from another thread, check whether the time resolution of the system is not 0 (very unlikely that it is on most current platforms), registers signal handlers and atexit functions (which have caused me some grief recently...), and set the global init_done function to 1. I also see that csoundCreate checks if csound has been initialized and runs csoundInitialize if it hasn't.

So it seems there might be no reason to have csoundInitialize in the API, as it will always be called by csoundCreate?

Cheers,
Andrés



On Sat, Jun 29, 2013 at 12:57 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
yes, but that was Istvan's idea, and I am not sure what he had in mind back then. Maybe they can go.
On 29 Jun 2013, at 08:41, PINOT Francois wrote:

> They were never required. I once asked if they were a placeholder for
> further development and Victor answered yes if I remember.
>
> Regards
>
> Francois
>
> Le 29/06/2013 05:01, Andres Cabrera a écrit :
>> Hi,
>>
>> Looking at the sources for csoundInitialize, it seems that argv and
>> argc are now longer required. Maybe they should be removed?
>>
>> Cheers,
>> Andrés
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>>
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel



Date2013-07-02 19:09
FromDave Phillips
SubjectRe: [Cs-dev] csoundInitialize
AttachmentsNone  None  
On 07/02/2013 12:01 PM, Andres Cabrera wrote:
OK, removed the unnecessary arguments and adjusted the documentation.


Okay, I need a little help here. Because of this change, the new csnd6.jar throws an error during the build of AVSynthesis. The offending code is :

            csnd6.csnd6.csoundInitialize(null, null, csnd6.csnd6.CSOUNDINIT_NO_SIGNAL_HANDLER);

And the error (in Eclipse) :

        The method csoundInitialize(int) in the type csnd6 is not applicable for the arguments (null, null, int)    APageRendering.java    /avs-build/src/org/avs/editor    line 21    Java Problem

Can someone give me a heads-up as to what needs changed/removed ?

Best,

dp



Cheers,
Andrés


On Sat, Jun 29, 2013 at 1:17 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
I think that was always the case in Csound 5 too.

On 29 Jun 2013, at 20:36, Andres Cabrera wrote:

Thinking about it, there may be times when hosts might want to initialize Csound without the signal handlers or the atexit, so I think csoundInitialize is still justified. But it needs to be clear in the docs that it's no longer compulsory, as csoundCreate will check for previous initialization.

Cheers,
Andrés


On Sat, Jun 29, 2013 at 9:34 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
We just need to check whether there are any functions that can be called between csoundInitialize and csoundCreate, that would be affected if we removed
csoundInitialize. Or if there are any scenarios where we need to call csoundInitialize first and then call csoundCreate.


On 29 Jun 2013, at 16:57, Andres Cabrera wrote:

I think they can go, especially since there are many new functions to set options.

In fact, the only thing the function does is protect against running itself simultaneously from another thread, check whether the time resolution of the system is not 0 (very unlikely that it is on most current platforms), registers signal handlers and atexit functions (which have caused me some grief recently...), and set the global init_done function to 1. I also see that csoundCreate checks if csound has been initialized and runs csoundInitialize if it hasn't.

So it seems there might be no reason to have csoundInitialize in the API, as it will always be called by csoundCreate?

Cheers,
Andrés



On Sat, Jun 29, 2013 at 12:57 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
yes, but that was Istvan's idea, and I am not sure what he had in mind back then. Maybe they can go.
On 29 Jun 2013, at 08:41, PINOT Francois wrote:

> They were never required. I once asked if they were a placeholder for
> further development and Victor answered yes if I remember.
>
> Regards
>
> Francois
>
> Le 29/06/2013 05:01, Andres Cabrera a écrit :
>> Hi,
>>
>> Looking at the sources for csoundInitialize, it seems that argv and
>> argc are now longer required. Maybe they should be removed?
>>
>> Cheers,
>> Andrés
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>>
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev


_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


Date2013-07-02 19:54
FromAndres Cabrera
SubjectRe: [Cs-dev] csoundInitialize
AttachmentsNone  None  
Hi,

The first two arguments were removed. They weren't being used. Just use:
csnd6.csnd6.csoundInitialize(csnd6.csnd6.CSOUNDINIT_NO_SIGNAL_HANDLER);

Cheers,
Andrés


On Tue, Jul 2, 2013 at 11:09 AM, Dave Phillips <dlphillips@woh.rr.com> wrote:
On 07/02/2013 12:01 PM, Andres Cabrera wrote:
OK, removed the unnecessary arguments and adjusted the documentation.


Okay, I need a little help here. Because of this change, the new csnd6.jar throws an error during the build of AVSynthesis. The offending code is :

            csnd6.csnd6.csoundInitialize(null, null, csnd6.csnd6.CSOUNDINIT_NO_SIGNAL_HANDLER);

And the error (in Eclipse) :

        The method csoundInitialize(int) in the type csnd6 is not applicable for the arguments (null, null, int)    APageRendering.java    /avs-build/src/org/avs/editor    line 21    Java Problem

Can someone give me a heads-up as to what needs changed/removed ?

Best,

dp




Cheers,
Andrés


On Sat, Jun 29, 2013 at 1:17 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
I think that was always the case in Csound 5 too.

On 29 Jun 2013, at 20:36, Andres Cabrera wrote:

Thinking about it, there may be times when hosts might want to initialize Csound without the signal handlers or the atexit, so I think csoundInitialize is still justified. But it needs to be clear in the docs that it's no longer compulsory, as csoundCreate will check for previous initialization.

Cheers,
Andrés


On Sat, Jun 29, 2013 at 9:34 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
We just need to check whether there are any functions that can be called between csoundInitialize and csoundCreate, that would be affected if we removed
csoundInitialize. Or if there are any scenarios where we need to call csoundInitialize first and then call csoundCreate.


On 29 Jun 2013, at 16:57, Andres Cabrera wrote:

I think they can go, especially since there are many new functions to set options.

In fact, the only thing the function does is protect against running itself simultaneously from another thread, check whether the time resolution of the system is not 0 (very unlikely that it is on most current platforms), registers signal handlers and atexit functions (which have caused me some grief recently...), and set the global init_done function to 1. I also see that csoundCreate checks if csound has been initialized and runs csoundInitialize if it hasn't.

So it seems there might be no reason to have csoundInitialize in the API, as it will always be called by csoundCreate?

Cheers,
Andrés



On Sat, Jun 29, 2013 at 12:57 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
yes, but that was Istvan's idea, and I am not sure what he had in mind back then. Maybe they can go.
On 29 Jun 2013, at 08:41, PINOT Francois wrote:

> They were never required. I once asked if they were a placeholder for
> further development and Victor answered yes if I remember.
>
> Regards
>
> Francois
>
> Le 29/06/2013 05:01, Andres Cabrera a écrit :
>> Hi,
>>
>> Looking at the sources for csoundInitialize, it seems that argv and
>> argc are now longer required. Maybe they should be removed?
>>
>> Cheers,
>> Andrés
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>>
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev


_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel



Date2013-07-02 21:03
FromDave Phillips
SubjectRe: [Cs-dev] csoundInitialize
AttachmentsNone  None  
On 07/02/2013 02:54 PM, Andres Cabrera wrote:
Hi,

The first two arguments were removed. They weren't being used. Just use:
csnd6.csnd6.csoundInitialize(csnd6.csnd6.CSOUNDINIT_NO_SIGNAL_HANDLER);

Cheers,
Andrés


Excellent, thank you !

All problems solved. :)

Best,

dp





On Tue, Jul 2, 2013 at 11:09 AM, Dave Phillips <dlphillips@woh.rr.com> wrote:
On 07/02/2013 12:01 PM, Andres Cabrera wrote:
OK, removed the unnecessary arguments and adjusted the documentation.


Okay, I need a little help here. Because of this change, the new csnd6.jar throws an error during the build of AVSynthesis. The offending code is :

            csnd6.csnd6.csoundInitialize(null, null, csnd6.csnd6.CSOUNDINIT_NO_SIGNAL_HANDLER);

And the error (in Eclipse) :

        The method csoundInitialize(int) in the type csnd6 is not applicable for the arguments (null, null, int)    APageRendering.java    /avs-build/src/org/avs/editor    line 21    Java Problem

Can someone give me a heads-up as to what needs changed/removed ?

Best,

dp




Cheers,
Andrés


On Sat, Jun 29, 2013 at 1:17 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
I think that was always the case in Csound 5 too.

On 29 Jun 2013, at 20:36, Andres Cabrera wrote:

Thinking about it, there may be times when hosts might want to initialize Csound without the signal handlers or the atexit, so I think csoundInitialize is still justified. But it needs to be clear in the docs that it's no longer compulsory, as csoundCreate will check for previous initialization.

Cheers,
Andrés


On Sat, Jun 29, 2013 at 9:34 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
We just need to check whether there are any functions that can be called between csoundInitialize and csoundCreate, that would be affected if we removed
csoundInitialize. Or if there are any scenarios where we need to call csoundInitialize first and then call csoundCreate.


On 29 Jun 2013, at 16:57, Andres Cabrera wrote:

I think they can go, especially since there are many new functions to set options.

In fact, the only thing the function does is protect against running itself simultaneously from another thread, check whether the time resolution of the system is not 0 (very unlikely that it is on most current platforms), registers signal handlers and atexit functions (which have caused me some grief recently...), and set the global init_done function to 1. I also see that csoundCreate checks if csound has been initialized and runs csoundInitialize if it hasn't.

So it seems there might be no reason to have csoundInitialize in the API, as it will always be called by csoundCreate?

Cheers,
Andrés



On Sat, Jun 29, 2013 at 12:57 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
yes, but that was Istvan's idea, and I am not sure what he had in mind back then. Maybe they can go.
On 29 Jun 2013, at 08:41, PINOT Francois wrote:

> They were never required. I once asked if they were a placeholder for
> further development and Victor answered yes if I remember.
>
> Regards
>
> Francois
>
> Le 29/06/2013 05:01, Andres Cabrera a écrit :
>> Hi,
>>
>> Looking at the sources for csoundInitialize, it seems that argv and
>> argc are now longer required. Maybe they should be removed?
>>
>> Cheers,
>> Andrés
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>>
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev


_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev


_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel