Trying to get start with Chuck on MAC - USING TERMINAL
Hi Everyone, I am new to Chuck. I saw Ge's video on the Apple website and am very interested in getting into Chuck as an audio tool for live performance. I seem to be having a problem getting it to run. I have tried going through the start up manual as it says, but keep getting the same error. I have added chuck to my usr/bin/ When I check through the /usr/bin I can see chuck there, so it has been added successfully. Then I type the >chuck in Terminal I don't get the [chuck]: no input files.... message i tried typing the command:
chuck // connect sine oscillator to D/A convertor (sound card)
But just get the following error message: -bash: syntax error near unexpected token `(' Is there something else I am not doing correctly? I have tried in miniAudicle, and everything works fine there, But would like to get this working from the Terminal. Thanks in advance for any assistance, Regards, -- Gary Hiebner SoundBase Productions cell: 082 877 6239 www.soundbase.co.za This message contains privileged and confidential information intended only for the person or legal entity to which it is addressed. Any review, re-transmission, copy or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient, is prohibited. If you received this message in error, please delete the material from any computer. Although all outgoing messages are scanned using Anti-virus Software, we can not accept responsibility for any harm or damage attributable to the distribution of electronic mail from our servers.
Gary,
Congratulations on taking the dive into ChucK. From what I can tell,
it looks like you're close to having things up and running. The
problem is that you are trying to run ChucK without any input file.
The command line version of ChucK needs you to specify the actual file
that you want to execute. You can either create this file, or use one
of the files that came with the ChucK installation. For example, if
you had a file called sounds.ck, then you would run it by going to the
directory that contained the file and typing the following at the
command prompt:
chuck sounds.ck
For more information about using the Unix command line, you might want
to take a look at this article:
http://db.tidbits.com/article/7003
I'm not sure which video you saw, but you might have been watching Ge
use Audicle. Audicle provides a graphical interface to chuck. You can
download it here:
http://audicle.cs.princeton.edu/
Good luck, and let me know if this helps.
andy
2009/6/26 gary hiebner
Hi Everyone, I am new to Chuck. I saw Ge's video on the Apple website and am very interested in getting into Chuck as an audio tool for live performance. I seem to be having a problem getting it to run. I have tried going through the start up manual as it says, but keep getting the same error. I have added chuck to my usr/bin/ When I check through the /usr/bin I can see chuck there, so it has been added successfully. Then I type the >chuck in Terminal I don't get the [chuck]: no input files.... message i tried typing the command:
chuck // connect sine oscillator to D/A convertor (sound card)
But just get the following error message:
-bash: syntax error near unexpected token `(' Is there something else I am not doing correctly? I have tried in miniAudicle, and everything works fine there, But would like to get this working from the Terminal. Thanks in advance for any assistance, Regards, -- Gary Hiebner SoundBase Productions cell: 082 877 6239 www.soundbase.co.za
This message contains privileged and confidential information intended only for the person or legal entity to which it is addressed. Any review, re-transmission, copy or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient, is prohibited. If you received this message in error, please delete the material from any computer. Although all outgoing messages are scanned using Anti-virus Software, we can not accept responsibility for any harm or damage attributable to the distribution of electronic mail from our servers.
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
gary hiebner ; I have tried in miniAudicle, and everything works fine there,
To add to Andrew's explanation; if it works for you in the miniAudicle then you are almost there. The thing to realise is that the mini uses one or a few windows to contain the ChucK code. We sometimes call these "editing buffers". These buffers contain code and they are analogous to files. Where we would tell the mini to run the code in one of these buffers we tell plain ChucK to run the code that is in a file that was previously saved. Code goes into files. These files then get send to ChucK. We don't (typically) send the code straight into ChucK though we may use a editor like the Mini to take care of the link for us. The process behind the scenes is the same, the Mini just makes it more convenient. There is one downside to these buffers that "pretend to be files"; if you would crash the Mini because you crash ChucK then you also lose all unsaved buffers while you won't crash plain ChucK in a way that makes you lose your files on your drive (at least I never heard of this happening)- I hope this clarifies, don't hesitate to ask more; both ChucK and a terminal can look a bit intimidating at first, especially if you are trying to get to grips with both at the same time. Yours, Kas.
On 27 Jun 2009, at 06:05, gary hiebner wrote:
I am new to Chuck. I saw Ge's video on the Apple website and am very interested in getting into Chuck as an audio tool for live performance. I seem to be having a problem getting it to run. I have tried going through the start up manual as it says, but keep getting the same error.
I have added chuck to my usr/bin/
When I check through the /usr/bin I can see chuck there, so it has been added successfully.
Then I type the >chuck in Terminal
I don't get the [chuck]: no input files.... message
If you installed the miniAudicle documentation in the folder / Applications/, then you can run an example by chuck /Applications/miniAudicle\ documentation/examples/basic/foo.ck (If you type it, you can <tab> to get file name completions.) Hans
gary hiebner; Then I type the >chuck in Terminal
I just noticed this and the "greater than" symbol in it. At the risk of stating the obvious; you wouldn't type that symbol, just the command "chuck" (without quotes). The symbol ">" is sometimes used to represent the prompt, probably because that's how a typical dos/windows setup represents it (preceded by the name of the dir we are in), I don't see it in my terminal on Linux and I don't think Mac uses it. Let's have a exageratedly detailed look at me running chuck in that way, copied straight from my BASH terminal; ghost@baido:~$ chuck [chuck]: no input files... (try --help) In the first line we see "ghost", that's my login. "baido" refers to the name of the computer (I'm a R-type fan, you see). The "@" means I'm loged in on this computer (that's no big news but I might use the same login on multiple systems) The "~" is a shorthand for my home dir so in this case that refers to "/home/ghost/" The "$" means I'm a ordinary user and not root. If I were root it would instead be a "#". Then we see a space after which we see "chuck", the "chuck" bit is the only thing I typed myself. The space just separates what the computer put there from what I wrote. On the second line we see ChucK's responce, it's basically saying "yes, I'm here but you're not giving me anything to do, type help if you'd like to know how to talk to me". Maybe that helps? If not it might be nice to copy the exact error you are getting because if ChucK is in /usr/bin/ it really should work. Yours, Kas.
Chuck wants an input file -- so you'd be typing something like > chuck
filename.ck
Try running some of the files in the example dirertory and taking a
ook at some of the user documentaton on the website.
Good luck!
On 6/27/09, gary hiebner
Hi Everyone, I am new to Chuck. I saw Ge's video on the Apple website and am very interested in getting into Chuck as an audio tool for live performance. I seem to be having a problem getting it to run. I have tried going through the start up manual as it says, but keep getting the same error.
I have added chuck to my usr/bin/
When I check through the /usr/bin I can see chuck there, so it has been added successfully.
Then I type the >chuck in Terminal
I don't get the [chuck]: no input files.... message
i tried typing the command:
chuck // connect sine oscillator to D/A convertor (sound card)
But just get the following error message:
-bash: syntax error near unexpected token `('
Is there something else I am not doing correctly?
I have tried in miniAudicle, and everything works fine there,
But would like to get this working from the Terminal.
Thanks in advance for any assistance,
Regards,
-- Gary Hiebner SoundBase Productions cell: 082 877 6239 www.soundbase.co.za
This message contains privileged and confidential information intended only for the person or legal entity to which it is addressed. Any review, re-transmission, copy or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient, is prohibited. If you received this message in error, please delete the material from any computer. Although all outgoing messages are scanned using Anti-virus Software, we can not accept responsibility for any harm or damage attributable to the distribution of electronic mail from our servers.
-- Sent from my mobile device
participants (5)
-
Andrew Turley -
Chris McDaniel -
gary hiebner -
Hans Aberg -
Kassen