Re: csoundtekno digest, Vol 1 #406 - 3 msgs

Simone,
Here is another link that might be useful when learning Terminal in OSX:

http://www.oreillynet.com/pub/ct/51

Mitch





On Jan 31, 2004, at 6:00 AM, [email protected] wrote:

> Send csoundtekno mailing list submissions to
> 	[email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://plot.bek.no/mailman/listinfo/csoundtekno
> or, via email, send a message with subject or body 'help' to
> 	[email protected]
>
> You can reach the person managing the list at
> 	[email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of csoundtekno digest..."
>
>
> Today's Topics:
>
>    1. Re: csound in OSX... (steven yi)
>    2. Re: csound in OSX... (Simone Ghetti)
>    3. Re: csound in OSX... (steven yi)
>
> --__--__--
>
> Message: 1
> Date: Fri, 30 Jan 2004 10:07:50 -0800
> From: steven yi <stevenyi-h9wucfWDa/[email protected]>
> To: [email protected]
> Subject: Re: [CsndTek] csound in OSX...
> Reply-To: [email protected]
>
> Hi Simone,
>
> In that case, here's some background information for using on the
> commandline (sorry if some of this is too simple but I'll write to
> assume no knowledge in case others are interested)
>
> 1) When you open the terminal app, you'll see a prompt. Most OS's
> preconfigure the prompt to tell you what user you are as well as what
> directory you are currently in.
>
> 2) Once you get a commandline version of Csound, unpack the file and 
> put
> it somewhere convenient. To start out, you might want to put it in your
> home directory. If you're user name is simoneg, then your home 
> directory
> on OSX would be /Users/simoneg.
>
> 3) When you open the terminal app, you start off in your home 
> directory.
> If you've unpacked csound into that directory, you should be able to 
> run
> it by typing:
>
> ./csound
>
> and then press enter. If all goes well, you should see a bunch of
> messages from csound telling you that you didn't give it an orc or sco
> and what the flags for csound are.
>
> 4) When you type a command in the prompt, the shell (the environment
> which you are interacting with via the prompt) tries to locate that
> command in the PATH to run it. The PATH is a list of directories that
> the prompt searches for executable programs. Normally, the PATH is
> configured to some default directories. In the users shell 
> configuration
> (the .cshrc file in the users home directory on OSX), you are able to
> add directories to your path with something like:
>
> export PATH = $PATH:/some/other/directory
>
> this is generally complicated for first-time terminal users.
>
> 5)Something easier to do might be to see what your path is already set
> to, and see if you can't copy csound into one of those directories. To
> see what your path is, type this on the command line of ther terminal:
>
> echo $PATH
>
> and press enter. It should give you a list of directories, separated by
> colons. Any of those directories can be used to house csound and let 
> you
> run csound without first prepending it with ./
>
> 6)Commandline programs generally have the convention:
>
> programName [optional arguments] requiredArguments
>
> where optional and required arguments can sometimes be interspersed
> (depends on the program). If you have an orc and sco to test out, copy
> them into your home directory and if csound is copied there too, open
> the terminal app and try this:
>
> ./csound -A -o test.aiff test.orc test.sco
>
> or:
>
> ./csound -o dac test.orc test.sco
>
> the first one writes and AIFF file called test.aiff using test.orc and
> test.sco, while the second one outputs in realtime to the soundcard
> using test.orc and test.sco. You can replace test.orc and test.sco with
> test.csd if you have a .csd file.
>
> Well, hope that helps! I'm sure there are tutorials floating around the
> internet for how to use the terminal which can explain these concepts 
> in
> more detail.
>
> Good luck!
> steven
>
>
>
>
> Simone Ghetti wrote:
>
>> hello,
>> yes I know about MacCsound...I have been putting off installing and
>> using MacCsound because I would like to become better acquainted with
>> the command line version of Csound along with learning how to interact
>> with my computer through the terminal.app. I think it would be a
>> useful skill to learn...
>>
>> anyway...thanks for the suggestion...
>> sg
>>
>>
>>> From: steven yi <stevenyi-h9wucfWDa/[email protected]>
>>> Reply-To: [email protected]
>>> To: [email protected]
>>> Subject: Re: [CsndTek] csound in OSX...
>>> Date: Thu, 29 Jan 2004 15:19:28 -0800
>>>
>>> Hello Simone,
>>>
>>> If you're used Winsound on PC, you might be interested to use
>>> MacCsound, developed my Matt Ingalls, available at:
>>>
>>> http://www.csounds.com/matt
>>>
>>> I think for those accustomed to Winsound that it's an easier path to
>>> Csounding on the Mac. It's also has a very nice syntax-hilighting
>>> editor, a GUI widget system, as well as some nice examples to get you
>>> started.
>>>
>>> Just thought I'd throw that out as an option. =)
>>>
>>> Good luck!
>>> steven
>>>
>>>
>>> Simone Ghetti wrote:
>>>
>>>> Hello...I haven't posted in quite some time...
>>>>
>>>> I apologize in advance for this question which I am sure has been
>>>> asked numerous times before...I tried searching the archives but
>>>> couldn't find much help...
>>>>
>>>> I have been using csound on the pc platform using CsoundWin... I'd
>>>> like to start using csound on my laptop running OS X. I have
>>>> downloaded Csound following the CsoundMacPPC link on the csound.com
>>>> website. I know that this version uses the command line and that I
>>>> need to use the terminal.app to run csound. Since I am new to (but
>>>> very willing to learn) using the terminal.app I am not sure how to
>>>> proceed. Do I need to follow the linux instructions for installing
>>>> and running csound? I would appreciate if someone could help point
>>>> me in the right direction...even off the list. Any information on
>>>> running csound through the terminal.app as well as how I can get
>>>> more familiar with working through the terminal.app in general would
>>>> be a great help.
>>>>
>>>> thanks
>>>> sg
>>>>
>>>> _________________________________________________________________
>>>> Let the new MSN Premium Internet Software make the most of your
>>>> high-speed experience.
>>>> http://join.msn.com/?pgmarket=en-us&page=byoa/prem&ST=1
>>>>
>>>> _______________________________________________
>>>> csoundtekno mailing list
>>>> [email protected]
>>>>
>>>> Subscribe, unsubscribe, change mailing list options:
>>>> http://plot.bek.no/mailman/listinfo/csoundtekno
>>>>
>>>>
>>>
>>> _______________________________________________
>>> csoundtekno mailing list
>>> [email protected]
>>>
>>> Subscribe, unsubscribe, change mailing list options:
>>> http://plot.bek.no/mailman/listinfo/csoundtekno
>>
>>
>> _________________________________________________________________
>> Scope out the new MSN Plus Internet Software — optimizes dial-up to
>> the max! http://join.msn.com/?pgmarket=en-us&page=byoa/plus&ST=1
>>
>> _______________________________________________
>> csoundtekno mailing list
>> [email protected]
>>
>> Subscribe, unsubscribe, change mailing list options:
>> http://plot.bek.no/mailman/listinfo/csoundtekno
>>
>>
>
>
> --__--__--
>
> Message: 2
> From: "Simone Ghetti" <[email protected]>
> To: [email protected]
> Subject: Re: [CsndTek] csound in OSX...
> Date: Fri, 30 Jan 2004 20:37:01 +0000
> Reply-To: [email protected]
>
> Steve,
>
> Thanks so much...that is exactly what I needed...  I did find a few
> tutorials on using the terminal.app in osX...  one tutorial recommended
> changing the default shell from tcsh to bash... is this necessary?  
> just
> curious to know if it affects working with csound at all...
>
> again thank you...
>
>> From: steven yi <stevenyi-h9wucfWDa/[email protected]>
>> Reply-To: [email protected]
>> To: [email protected]
>> Subject: Re: [CsndTek] csound in OSX...
>> Date: Fri, 30 Jan 2004 10:07:50 -0800
>>
>> Hi Simone,
>>
>> In that case, here's some background information for using on the
>> commandline (sorry if some of this is too simple but I'll write to 
>> assume
>> no knowledge in case others are interested)
>> ...
>
> _________________________________________________________________
> Check out the coupons and bargains on MSN Offers!
> http://shopping.msn.com/softcontent/softcontent.aspx?scmId=1418
>
>
> --__--__--
>
> Message: 3
> Date: Fri, 30 Jan 2004 12:46:28 -0800
> From: steven yi <stevenyi-h9wucfWDa/[email protected]>
> To: [email protected]
> Subject: Re: [CsndTek] csound in OSX...
> Reply-To: [email protected]
>
> Hi Simone,
>
> It's not necessary to run bash.  However, most people who use Linux use
> bash so if I'd guess there's more information on bash than on tcsh.  I
> also happen to find tcsh confusing as I'm used to bash.  =)
>
> To run csound it won't really matter which shell you use, as they will
> all allow you to execute csound.  The part where the different shells
> might affect you is that the way they set variables is different; some 
> use:
>
> set PATH = $PATH:/some/other/dir
>
> others use:
>
> setenv PATH $PATH:/some/other/dir
>
> tcsh uses two different ways to set variables; I can't remember the
> reason (one if the variable is all uppercase and considered a system
> variable and one if it is a script variable I think).
>
> I think really the only things that will affect you in terms of using
> csound with either shell will be to set the path and csound variables
> (SADIR, SFDIR, INCDIR, and SSDIR), which you might not even use (I like
> using them however =)).
>
> So... it's your choice!  If it's of any concern, I've been using only
> commandline csound for a long time and I rarely ever spend time editing
> shell scripts (.cshrc or .bashrc), pretty much only have to do it once.
>
> Glad the other email helped!
> steven
>
> Simone Ghetti wrote:
>
>> Steve,
>>
>> Thanks so much...that is exactly what I needed...  I did find a few
>> tutorials on using the terminal.app in osX...  one tutorial
>> recommended changing the default shell from tcsh to bash... is this
>> necessary?  just curious to know if it affects working with csound at
>> all...
>>
>> again thank you...
>>
>
>
>
> --__--__--
>
> _______________________________________________
> csoundtekno mailing list
> [email protected]
>
> Subscribe, unsubscribe, change mailing list options:
> http://plot.bek.no/mailman/listinfo/csoundtekno
>
>
> End of csoundtekno Digest
>

_______________________________________________
csoundtekno mailing list
[email protected]

Subscribe, unsubscribe, change mailing list options:
http://plot.bek.no/mailman/listinfo/csoundtekno