hard to begin...

[djeho]

Hi, I'm new in this forum as well as i'm totally new in programming.
I've tried to start with Chuck with a good motivation but there's some problems...

first, i can't install chuck! the problem is following;

in the instruction, it says;
On MacOS X (using Terminal): go to the bin/ directory and type

i do not understand. how can i "go" to the bin/ directory? what does it mean "go"?

anyway i type in terminal "sudo cp chuck /usr/bin/"

and it says,

cp: chuck: No such file or directory
Ordinateur-de-jaeho-YOUN:~ jaehoyoun$

sometimes it ask me password, so i type in my system password,

and again

cp: chuck: No such file or directory

second, i'd like to know the difference between using chuck commande line version and chuck miniaudicle version. miniaudicle works for me, but it seems that automatic sync function between patchs doesn't work on miniaudicle as described on tutorial (ChucK supports sample-synchronous concurrency, via the ChucK timing mechanism. Given any number of source files that uses the timing mechanism above, the ChucK VM can use the timing information to automatically synchronize all of them.) becuase i can't excute the following...

%> chuck moe.ck larry.ck curly.ck

in miniaudicle, i have to open each patch and i have to run manually each ones..in that way, the perfect sync isn't possible....

what's the advantage and disadvantage to run chuck commande line version and audicle version? if i know that, i may just use audicle version...

i hope that those questions are clear...(i've tried my best with my baaaad english!!) thanks a lot guys, and nice to meet everyone!!

[djeho]

ok, after 2 hours of battle, i've installed (?) chuck...

well, the thing is, i went to the folder usr/bin, and change the folder's authorization to drag&drop chuck file, and all of those exemple files, then it works...is it ok to do this? i definitely didn't do as written in the manual...i'm a bit worry about it...(because i think normally, we shouldn't touch this usr/bin directory..)

and also, that means each time i have to copy&paste chuck files to this directory...is it ok to do this???

[djeho]

actually, it doesn't work...i've tried the very first thing, and..

Ordinateur-de-jaeho-YOUN:/usr/bin jaehoyoun$ SinOsc s => dac;
-bash: SinOsc: command not found

please help me!!!!!!

[jbum]

I think you will find ChucK much easier to use if you start by using the MiniAudicle:

http://audicle.cs.princeton.edu/mini/mac/

This provides a development environment in which you can type chuck commands in an editing window.

To use it, first press the button (or execute the menu command) that says "Start Virtual Machine". Paste your ChucK examples into the editing window, and then press the "Add Shred" button.

[spencer]

[djeho]

well, it seems that i've finally made it...

i didn't know that i have to write code in TextEdit...i've tried to write code directly in Terminal.
so, Terminal is only an excution tool...right?

and i know about miniAudicle...but the only thing that i wonder is the possibility to syncronizing. in Terminal,

chuck xxx_1.ck xxx_2.ck

make these two patchs automatically syncronized.
but in miniAudicle, when i try to lauch xxx_1.ck and xxx_2.ck,
i have to start manually those two .ck files which make it very difficult to syncronize. if somebody knows about how to syncronize different patchs in miniAudicle, that'll be very helpful for me, who is, really really a baby in this domaine...(i start to tell myself; "maybe this is not for me...it's for other kind of human beings...)

thanks!

[djeho]

oops!
i didn't see spencer's qoute on miniAudicle,
now i understand better..

thanks!

[ge]

[spencer]

Hi there,

[Kassen]

djeho, it looks like it would be good if you looked up a text about using the terminal; the basic commands that you need are quite easy. There may be a manual that came with your computer, if not you can use any text that refers to "Bash". Bash is the name of the terminal, it's (mostly) the same on OSX and Linux.

I take it you already found the command "cd" ("cd .." to go up one level), it's also usefull to know "ls" which lists the files in the current directory. The way opf using the "chuck": command are in the PDF manual. I recomend that you also look up how to call your favourite text editor from the terminal (and the hotkeys for switching the active window) because that will mean you hardly ever need to touch your mouse.

Later you could look up how to move, make and delete files if it turns out you like the terminal. The terminal is a bit harder to get into then using a mouse but once you get the hang of it it can be a very fast way of doing things.

Notice that you don't need to type everything out. Often you can just type the begining of a file-name, then hit [tab] tab will automatically fill in the second half. with the arrow keys up and down you can go back and forth through the list of commands you entered lately, that's also usefull and time-saving.

You are right that it's perhaps wiser not to touch /usr/bin most of the time because it's a part of the system but here we are trying to make ChucK a part of the system too. Placing it in /usr/bin mean Unix will know it's a program. Once it's placed there you can call it from anywhere on the system, regardless of what directory you are "in". As Spencer said; you can just keep the chuck command there and keep your folder of ck files, examples, the manual and whatever in your home directory.

As for "kinds of human beings"; ChucK and the terminal may indeed require a certain kind of human being; it needs the kind of person who can figure (and try) a lot out on his own reading manuals and internet pages and who knows where and when to ask questions. So; looking at your posts that's you. You went from never having used the terminbal to installing a program yourself in a few hours. That's pritty good, you should be proud!

[djeho]

i have to say that i've never seen any forums where people can be this much kind!! thanks for all the helps!

it is very true that i have to know some basic commands on Terminal. (thanks for the link!) so, now i've re-installed Chuck as written on the manual, and everything seems workin' fine.

i start to try out some examples and it's really fun, though i don't understand all...(but i'm "the kind" of human being, so no problem! )

my goal was just to study on some synthesis in methodical way, but now i'm seriously thinking on using Chuck to replace those 2dvd full-plug-in synths...why i need all that craps?!!!!

thanks a lot