Andres,

I'll be happy to, but please resend your text. (I no longer have your
original and I don't seem to find it yet online.)

Also let me mention that there are currently no install instructions for
WinXP! (only earlier versions of Windows)

Art Hunkins

----- Original Message -----
From: "Andres Cabrera" 
To: 
Sent: Thursday, April 20, 2006 8:47 AM
Subject: Re: [Cs-dev] Addition to manual


Hi Art,
Can you check the instructions for setting the Environment variables
using the control panel? I haven't used windows in a while and I'm
pretty sure what I wrote is not accurate.

Thanks,
Andrés

On Tue, 2006-04-18 at 16:27 -0400, Art Hunkins wrote:
> 
> Hi Andres--
>
> Here are a couple of suggestions:
>
> OPCODEDIR is only required when running csound32.exe
>
> OPCODEDIR64 is only required when running csound.exe
>
> (OTOH, I feel that the opcodedir nomenclature not corresponding to the
> csound execs is unfortunate. My preference would be: opcodedir with
> csound.exe and opcodedir64 with csound64.exe. However, if 64-bit is to
> be the norm, then opcodedir with csound.exe (64-bit) and opcodedir32
> with csound32.exe.)
>
> Also:
>
> For Windows OS's earlier than XP, environment variables are specified
> in the autoexec.bat file (My Computer, select C: drive, right click on
> Autoexec.bat, select Edit.)
>
> Art Hunkins
>
> ----- Original Message -----
>         From: Andres Cabrera
>         To: Csound-dev
>         Sent: Tuesday, April 18, 2006 1:32 PM
>         Subject: [Cs-dev] Addition to manual
>
>
>         Hi,
>         I've made the following addition to the manual. There are some
>         needed
>         additions and corrections, so any help is appreciated.
>
>         Cheers,
>         Andrés
>
>



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=k&kid0709&bid&3057&dat1642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Art,
Here's the latest version.


Cheers,
Andrés

On Thu, 2006-04-20 at 11:27 -0400, Art Hunkins wrote:
> Andres,
> 
> I'll be happy to, but please resend your text. (I no longer have your
> original and I don't seem to find it yet online.)
> 
> Also let me mention that there are currently no install instructions for
> WinXP! (only earlier versions of Windows)
> 
> Art Hunkins
> 
> ----- Original Message -----
> From: "Andres Cabrera" 
> To: 
> Sent: Thursday, April 20, 2006 8:47 AM
> Subject: Re: [Cs-dev] Addition to manual
> 
> 
> Hi Art,
> Can you check the instructions for setting the Environment variables
> using the control panel? I haven't used windows in a while and I'm
> pretty sure what I wrote is not accurate.
> 
> Thanks,
> Andrés
> 
> On Tue, 2006-04-18 at 16:27 -0400, Art Hunkins wrote:
> > 
> > Hi Andres--
> >
> > Here are a couple of suggestions:
> >
> > OPCODEDIR is only required when running csound32.exe
> >
> > OPCODEDIR64 is only required when running csound.exe
> >
> > (OTOH, I feel that the opcodedir nomenclature not corresponding to the
> > csound execs is unfortunate. My preference would be: opcodedir with
> > csound.exe and opcodedir64 with csound64.exe. However, if 64-bit is to
> > be the norm, then opcodedir with csound.exe (64-bit) and opcodedir32
> > with csound32.exe.)
> >
> > Also:
> >
> > For Windows OS's earlier than XP, environment variables are specified
> > in the autoexec.bat file (My Computer, select C: drive, right click on
> > Autoexec.bat, select Edit.)
> >
> > Art Hunkins
> >
> > ----- Original Message -----
> >         From: Andres Cabrera
> >         To: Csound-dev
> >         Sent: Tuesday, April 18, 2006 1:32 PM
> >         Subject: [Cs-dev] Addition to manual
> >
> >
> >         Hi,
> >         I've made the following addition to the manual. There are some
> >         needed
> >         additions and corrections, so any help is appreciated.
> >
> >         Cheers,
> >         Andrés
> >
> >
> 
> 
> 
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=k&kid0709&bid&3057&dat1642
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> 
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> m

Thanks Istvan for the feedback, I'm incorporation the info.
I'm wondering if someone can explain the usage of CSNOSTOP, I can't
really figure out its use from the Changelog entry. And the code I found
in InOut/FL_graph.cpp is commented out.

Also, is it accurate that csound5 currently isn't translated into other
languages?

I've also added what I could understand by grep' ing sources about
SFOUTYP, corrections welcome.


Cheers,
Andres

On Sun, 2006-04-23 at 11:26 +0200, Istvan Varga wrote:
> On Sunday 23 April 2006 04:44, Andres Cabrera wrote:
> 
> > Here's the latest version.
> 
> There is an environment variable not mentioned yet: RAWWAVE_PATH is used
> by the STK opcodes to find the raw wave files. Although, it is set by
> those binary releases of Csound that actually have the STK opcodes.
> 
> Another note: when setting environment variables with the --env command
> line option, not all of them may work, because some environment variables
> are used before parsing the command line. The following variables should
> be OK:
> 
>   SADIR
>   SSDIR
>   SFDIR
>   INCDIR
>   SNAPDIR
>   RAWWAVE_PATH
>   CSNOSTOP
>   SFOUTYP (not very useful on the command line, though)
> 
> These will surely not work when set on the command line, or in
>  or .csoundrc:
> 
>   OPCODEDIR
>   OPCODEDIR64
>   CSSTRNGS
>   CS_LANG
>   PATH (not a Csound environment variable)
>   PYTHONPATH (not a Csound environment variable)
> 
> Additionally, CSOUNDRC cannot be set in .csoundrc and ; it
> currently works when set on the command line with --env, but this
> way of setting CSOUNDRC is not guaranteed to be available in all future
> releases.
> 
> 
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> a

With regards Windows, as far as I can tell there is no 'Set Environment 
Variables' button as is suggested. Instead one must go to 'System 
Settings', click on the 'Advanced' tab and then click 'Environment 
Variables'. Then one must click 'New' to add any environment variables.

Rory.


Andres Cabrera wrote:
> Thanks Istvan for the feedback, I'm incorporation the info.
> I'm wondering if someone can explain the usage of CSNOSTOP, I can't
> really figure out its use from the Changelog entry. And the code I found
> in InOut/FL_graph.cpp is commented out.
> 
> Also, is it accurate that csound5 currently isn't translated into other
> languages?
> 
> I've also added what I could understand by grep' ing sources about
> SFOUTYP, corrections welcome.
> 
> 
> Cheers,
> Andres
> 
> On Sun, 2006-04-23 at 11:26 +0200, Istvan Varga wrote:
>> On Sunday 23 April 2006 04:44, Andres Cabrera wrote:
>>
>>> Here's the latest version.
>> There is an environment variable not mentioned yet: RAWWAVE_PATH is used
>> by the STK opcodes to find the raw wave files. Although, it is set by
>> those binary releases of Csound that actually have the STK opcodes.
>>
>> Another note: when setting environment variables with the --env command
>> line option, not all of them may work, because some environment variables
>> are used before parsing the command line. The following variables should
>> be OK:
>>
>>   SADIR
>>   SSDIR
>>   SFDIR
>>   INCDIR
>>   SNAPDIR
>>   RAWWAVE_PATH
>>   CSNOSTOP
>>   SFOUTYP (not very useful on the command line, though)
>>
>> These will surely not work when set on the command line, or in
>>  or .csoundrc:
>>
>>   OPCODEDIR
>>   OPCODEDIR64
>>   CSSTRNGS
>>   CS_LANG
>>   PATH (not a Csound environment variable)
>>   PYTHONPATH (not a Csound environment variable)
>>
>> Additionally, CSOUNDRC cannot be set in .csoundrc and ; it
>> currently works when set on the command line with --env, but this
>> way of setting CSOUNDRC is not guaranteed to be available in all future
>> releases.
>>
>>
>> -------------------------------------------------------
>> Using Tomcat but need to do more? Need to support web services, security?
>> Get stuff done quickly with pre-integrated technology to make your job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> a
>>
>> ------------------------------------------------------------------------
>>
>> Csound Environment Variables
>> Prev   	The Csound Command 	 Next 
>> 
>>
>> ------------------------------------------------------------------------
>>
>>
>>     Csound Environment Variables
>>
>> The following environment varibales can be used by Csound:
>>
>>     * SFDIR: Default directory for sound files. Used if no full path
>>       is given for sound files.
>>     * SSDIR: Default directory for input (source) sound files. Used if
>>       no full path is given for sound files. May be used in cinjuction
>>       with SFDIR to set separate input and output directories.
>>     * SADIR: Default directory for analysis files. Used if no full
>>       path is given for analysis files.
>>     * SFOUTYP: Sets the output file format. Currently only 'WAV',
>>       'AIFF' and 'IRCAM' are valid. This flag is checked by the csound
>>       executable and the utilities.
>>     * INCDIR: Include directory. Specifies the location of files used
>>       by /#include/  statements.
>>     * OPCODEDIR: Defines the location of csound opcode plugins for the
>>       single precision float (32-bit) version.
>>     * OPCODEDIR64: Defines the location of csound opcode plugins for
>>       the double precision float (64-bit) version.
>>     * SNAPDIR: Is used by the FLTK widget opcodes when loading and
>>       saving snapshots.
>>     * CSOUNDRC: Defines the csound resource (or configuration) file. A
>>       full path and filename containing csound flags must be
>>       specified. This variable defaults to .csoundrc if not present.
>>     * CSSTRNGS: In Csound 5.00 and later versions, the localization of
>>       messages is controlled by two environment variables CSSTRNGS and
>>       CS_LANG, both of which are optional. CSSTRNGS points to a
>>       directory containing .xmg files.
>>     * CS_LANG: Selects a language for csound messages.
>>     * RAWWAVE_PATH: Is used by the STK opcodes to find the raw wave
>>       files. Only relevant if you are using STK wrapper opcodes like
>>       STKBowed or STKBrass.
>>     * CSNOSTOP: ?.
>>
>> For more information about SFDIR, SSDIR, SADIR and INCDIR see 
>> /Directories and files/ .
>>
>> The only mandatory environment variables are OPCODEDIR and 
>> OPCODEDIR64. It is very important to set them correctly, otherwise 
>> most of the opcodes will not be available. Make sure you set the path 
>> correctly depending on the precision of your binary. if you run csound 
>> on a command line without any arguments you should see some text like 
>> : Csound version 5.01.0 beta (float samples) Mar 23 2006. This text 
>> refers to the single precicion version.
>>
>> CSSTRNGS and CS_LANG currently have no use since Csound has not yet 
>> been translated into other languages.
>>
>> Other environment variables which are not exclusive to Csound but 
>> which might be of importance are:
>>
>>     * /PATH/: The directory containing csound executables should be
>>       listed in this variable.
>>     * /PYTHONPATH/: If you intend to use CsoundVST and python, the
>>       directory containing the _CsoundVST shared library and the
>>       CsoundVST.py file must be in your /PYTHONPATH/ environment
>>       variable (or the default path python searches in), so that the
>>       Python runtime knows how to load these files.
>>     * /LADSPA_PATH and DSSI_PATH/: These environment variables are
>>       required if you are using the /dssi4cs/ (LADSPA and DSSI host)
>>       plugin opcodes.
>>
>>
>>       Setting environment varibales
>>
>>
>>     On the command line
>>
>> You can set environment varibales on the command line or the 
>> configuration file .csoundrc by using the command line flag 
>> --env:NAME=VALUE or --env:NAME+=VALUE, where NAME is the environment 
>> variable name, and VALUE is its value. See /Command-line Flags/ 
>> .
>>
>> [Note] 	Note
>>
>> Please note that this method of setting environment variables will not 
>> work for variables which are parsed before the command line arguments. 
>> SADIR, SSDIR, SFDIR, INCDIR, SNAPDIR, RAWWAVE_PATH, CSNOSTOP, SFOUTYP 
>> should work, but the following environment variables must be set on 
>> the system prior to running csound: OPCODEDIR, OPCODEDIR64, CSSTRINGS, 
>> and CS_LANG. CSOUNDRC can currently (v. 5.02) be set using --env, but 
>> this behaviour is not garanteed for future version.
>>
>>
>>     Windows
>>
>> To set a csound environment on Windows go to Control Panel->System 
>> Settings (or use the shortcut Win+Scroll Lock) and click on the button 
>> 'Set environment varibles'. On Windows earlier than XP you can also st 
>> environment varibles in the autoexec.bat file. Go to 'My Computer', 
>> select C: drive, right click on Autoexec.bat, and select select 'Edit'.
>>
>>
>>     Linux
>>
>> You can set environment variables on Linux in many ways. You can set 
>> them using the /export/ shell command, by setting them on .bashrc or 
>> similar files or by adding them to the /etc/profile file.
>>
>>
>>     Mac
>>
>> No info yet.
>>
>> ------------------------------------------------------------------------
>> Prev   	Up  	 Next 
>> 
>> Command-line Flags  	Home  	 Unified File Format for 
>> Orchestras and Scores
>>


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks Rory,
I wrote that from memory since I haven't used windows in  while, but I
knew it was wrong. Thanks for the correction.

Cheers,
Andres

On Sun, 2006-04-23 at 16:57 +0100, Rory Walsh wrote:
> With regards Windows, as far as I can tell there is no 'Set Environment 
> Variables' button as is suggested. Instead one must go to 'System 
> Settings', click on the 'Advanced' tab and then click 'Environment 
> Variables'. Then one must click 'New' to add any environment variables.
> 
> Rory.
> 
> 
> Andres Cabrera wrote:
> > Thanks Istvan for the feedback, I'm incorporation the info.
> > I'm wondering if someone can explain the usage of CSNOSTOP, I can't
> > really figure out its use from the Changelog entry. And the code I found
> > in InOut/FL_graph.cpp is commented out.
> > 
> > Also, is it accurate that csound5 currently isn't translated into other
> > languages?
> > 
> > I've also added what I could understand by grep' ing sources about
> > SFOUTYP, corrections welcome.
> > 
> > 
> > Cheers,
> > Andres
> > 
> > On Sun, 2006-04-23 at 11:26 +0200, Istvan Varga wrote:
> >> On Sunday 23 April 2006 04:44, Andres Cabrera wrote:
> >>
> >>> Here's the latest version.
> >> There is an environment variable not mentioned yet: RAWWAVE_PATH is used
> >> by the STK opcodes to find the raw wave files. Although, it is set by
> >> those binary releases of Csound that actually have the STK opcodes.
> >>
> >> Another note: when setting environment variables with the --env command
> >> line option, not all of them may work, because some environment variables
> >> are used before parsing the command line. The following variables should
> >> be OK:
> >>
> >>   SADIR
> >>   SSDIR
> >>   SFDIR
> >>   INCDIR
> >>   SNAPDIR
> >>   RAWWAVE_PATH
> >>   CSNOSTOP
> >>   SFOUTYP (not very useful on the command line, though)
> >>
> >> These will surely not work when set on the command line, or in
> >>  or .csoundrc:
> >>
> >>   OPCODEDIR
> >>   OPCODEDIR64
> >>   CSSTRNGS
> >>   CS_LANG
> >>   PATH (not a Csound environment variable)
> >>   PYTHONPATH (not a Csound environment variable)
> >>
> >> Additionally, CSOUNDRC cannot be set in .csoundrc and ; it
> >> currently works when set on the command line with --env, but this
> >> way of setting CSOUNDRC is not guaranteed to be available in all future
> >> releases.
> >>
> >>
> >> -------------------------------------------------------
> >> Using Tomcat but need to do more? Need to support web services, security?
> >> Get stuff done quickly with pre-integrated technology to make your job easier
> >> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> >> _______________________________________________
> >> Csound-devel mailing list
> >> Csound-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>
> >>
> >> a
> >>
> >> ------------------------------------------------------------------------
> >>
> >> Csound Environment Variables
> >> Prev   	The Csound Command 	 Next 
> >> 
> >>
> >> ------------------------------------------------------------------------
> >>
> >>
> >>     Csound Environment Variables
> >>
> >> The following environment varibales can be used by Csound:
> >>
> >>     * SFDIR: Default directory for sound files. Used if no full path
> >>       is given for sound files.
> >>     * SSDIR: Default directory for input (source) sound files. Used if
> >>       no full path is given for sound files. May be used in cinjuction
> >>       with SFDIR to set separate input and output directories.
> >>     * SADIR: Default directory for analysis files. Used if no full
> >>       path is given for analysis files.
> >>     * SFOUTYP: Sets the output file format. Currently only 'WAV',
> >>       'AIFF' and 'IRCAM' are valid. This flag is checked by the csound
> >>       executable and the utilities.
> >>     * INCDIR: Include directory. Specifies the location of files used
> >>       by /#include/  statements.
> >>     * OPCODEDIR: Defines the location of csound opcode plugins for the
> >>       single precision float (32-bit) version.
> >>     * OPCODEDIR64: Defines the location of csound opcode plugins for
> >>       the double precision float (64-bit) version.
> >>     * SNAPDIR: Is used by the FLTK widget opcodes when loading and
> >>       saving snapshots.
> >>     * CSOUNDRC: Defines the csound resource (or configuration) file. A
> >>       full path and filename containing csound flags must be
> >>       specified. This variable defaults to .csoundrc if not present.
> >>     * CSSTRNGS: In Csound 5.00 and later versions, the localization of
> >>       messages is controlled by two environment variables CSSTRNGS and
> >>       CS_LANG, both of which are optional. CSSTRNGS points to a
> >>       directory containing .xmg files.
> >>     * CS_LANG: Selects a language for csound messages.
> >>     * RAWWAVE_PATH: Is used by the STK opcodes to find the raw wave
> >>       files. Only relevant if you are using STK wrapper opcodes like
> >>       STKBowed or STKBrass.
> >>     * CSNOSTOP: ?.
> >>
> >> For more information about SFDIR, SSDIR, SADIR and INCDIR see 
> >> /Directories and files/ .
> >>
> >> The only mandatory environment variables are OPCODEDIR and 
> >> OPCODEDIR64. It is very important to set them correctly, otherwise 
> >> most of the opcodes will not be available. Make sure you set the path 
> >> correctly depending on the precision of your binary. if you run csound 
> >> on a command line without any arguments you should see some text like 
> >> : Csound version 5.01.0 beta (float samples) Mar 23 2006. This text 
> >> refers to the single precicion version.
> >>
> >> CSSTRNGS and CS_LANG currently have no use since Csound has not yet 
> >> been translated into other languages.
> >>
> >> Other environment variables which are not exclusive to Csound but 
> >> which might be of importance are:
> >>
> >>     * /PATH/: The directory containing csound executables should be
> >>       listed in this variable.
> >>     * /PYTHONPATH/: If you intend to use CsoundVST and python, the
> >>       directory containing the _CsoundVST shared library and the
> >>       CsoundVST.py file must be in your /PYTHONPATH/ environment
> >>       variable (or the default path python searches in), so that the
> >>       Python runtime knows how to load these files.
> >>     * /LADSPA_PATH and DSSI_PATH/: These environment variables are
> >>       required if you are using the /dssi4cs/ (LADSPA and DSSI host)
> >>       plugin opcodes.
> >>
> >>
> >>       Setting environment varibales
> >>
> >>
> >>     On the command line
> >>
> >> You can set environment varibales on the command line or the 
> >> configuration file .csoundrc by using the command line flag 
> >> --env:NAME=VALUE or --env:NAME+=VALUE, where NAME is the environment 
> >> variable name, and VALUE is its value. See /Command-line Flags/ 
> >> .
> >>
> >> [Note] 	Note
> >>
> >> Please note that this method of setting environment variables will not 
> >> work for variables which are parsed before the command line arguments. 
> >> SADIR, SSDIR, SFDIR, INCDIR, SNAPDIR, RAWWAVE_PATH, CSNOSTOP, SFOUTYP 
> >> should work, but the following environment variables must be set on 
> >> the system prior to running csound: OPCODEDIR, OPCODEDIR64, CSSTRINGS, 
> >> and CS_LANG. CSOUNDRC can currently (v. 5.02) be set using --env, but 
> >> this behaviour is not garanteed for future version.
> >>
> >>
> >>     Windows
> >>
> >> To set a csound environment on Windows go to Control Panel->System 
> >> Settings (or use the shortcut Win+Scroll Lock) and click on the button 
> >> 'Set environment varibles'. On Windows earlier than XP you can also st 
> >> environment varibles in the autoexec.bat file. Go to 'My Computer', 
> >> select C: drive, right click on Autoexec.bat, and select select 'Edit'.
> >>
> >>
> >>     Linux
> >>
> >> You can set environment variables on Linux in many ways. You can set 
> >> them using the /export/ shell command, by setting them on .bashrc or 
> >> similar files or by adding them to the /etc/profile file.
> >>
> >>
> >>     Mac
> >>
> >> No info yet.
> >>
> >> ------------------------------------------------------------------------
> >> Prev   	Up  	 Next 
> >> 
> >> Command-line Flags  	Home  	 Unified File Format for 
> >> Orchestras and Scores
> >>
> 
> 
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> �



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I think no-one... just like no-one maintains csound4 ....


Cheers,
Andres

On Sun, 2006-04-23 at 09:59 -0700, Ben Collver wrote:
> Just out of curiosity, who is maintaining the csound4 manual now?
> 
> Thank you,
> 
> Ben
> 
> On Sun, Apr 23, 2006 at 04:57:31PM +0100, Rory Walsh wrote:
> > With regards Windows, as far as I can tell there is no 'Set Environment 
> > Variables' button as is suggested. Instead one must go to 'System 
> > Settings', click on the 'Advanced' tab and then click 'Environment 
> > Variables'. Then one must click 'New' to add any environment variables.
> > 
> > Rory.
> 
> 
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> 3



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks for the information Istvan.

Andres

On Sun, 2006-04-23 at 18:35 +0200, Istvan Varga wrote:
> On Sunday 23 April 2006 17:21, Andres Cabrera wrote:
> 
> > Thanks Istvan for the feedback, I'm incorporation the info.
> > I'm wondering if someone can explain the usage of CSNOSTOP, I can't
> > really figure out its use from the Changelog entry.
> 
> If this environment variable is set to "yes", then any graph displays
> are closed automatically at the end of performance (meaning that you
> possibly will not see much of them in the case of a short non-realtime
> render). Otherwise, you need to click "Quit" in the FLTK display window
> to exit, allowing for viewing the graphs even after the end of score
> is reached.
> 
> > And the code I found in InOut/FL_graph.cpp is commented out.
> 
> It should not be if you have up to date sources from developer CVS
> (pserver is currently broken/outdated). However, versions 5.00 and 5.01
> do always behave as if CSNOSTOP was set to "yes".
> 
> > Also, is it accurate that csound5 currently isn't translated into other
> > languages?
> 
> There are some translated messages for French and US English, but this is
> very limited and outdated, and as a result only some of the strings are
> printed in these languages, and the rest would remain the built-in English
> version. Also, using the "American" .xmg file simply means that in some
> words "ise" is replaced by "ize" (e.g. initialise vs. initialize) or "cannot"
> is replaced by "can't" etc., and even then, only in some of the messages.
> In other words, it is not very inaccurate to say that Csound is not yet
> translated to other languages.
> 
> > I've also added what I could understand by grep' ing sources about
> > SFOUTYP, corrections welcome.
> 
> SFOUTYP is the default sound file format (WAV, AIFF, etc.); it is used
> only if a file format is not specified anywhere else with command line
> flags.
> 
> 
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> �



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

The environment.plist file works on 10.3 and 10.4, as far as I know (at 
least it
works here). However, logging out and back in is needed to refresh it, once
edited (Acqua loads it on login only). I think it works on 10.2 (but it 
might have
a different name on it).

Victor

At 19:30 24/04/2006, you wrote:
>Note that if users choose one of the above methods, ie editing the .bashrc 
>file then the environment variables are executed when a new shell is 
>created. This can be problematic if your application implements a Quartz 
>or Aqua interface and does not use the commandline. If this is the case, 
>then the standard solution (up to OS 10.3.9) is to create an XML property 
>list file (called a .plist file by the OS). This file should nominally be 
>located at ~/.MacOSX/Environment.plist. T

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



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Mon, 2006-04-24 at 14:30 -0400, David Akbari wrote:
> > >>
> > >>     Mac
> > >>
> > >> No info yet.
> 
> Well, that certainly will not do...

No, it won't.... I've added your info, Matt's and Art's.

Thanks for the needed feedback.

Cheers,
Andrés





-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net