- chuck-users - lists.cs.princeton.edu

CNoise
by Kassen 14 Jul '09

14 Jul '09

Fellow ChucKists. CNoise is under-documented, the only official reference to it seems to be that "cnoise" is depreciated, with "CNoise" being prefered since 1.2.0.7. Still it's there in the source and can be used without errors. However, it doesn't seem to work like I expect it to. Based on the source I'd say correct usage should be something like this; CNoise n => dac; "white" => n.mode; second => now; "pink" => n.mode; second => now; "flip" => n.mode; second => now; "xor" => n.mode; second => now; "brown" => n.mode; second => now; "fbm" => n.mode; second => now; This does indeed compile but all I get is one type of noise only. Could somebody kindly help or explain? Yours, Kas.

2 2

Std.srand() abuse
by Kassen 14 Jul '09

14 Jul '09

Dear list, While exploring noise UGens I chanced upon the rather interesting technique of periodically resetting Std.srand() which sets the seed for noise in ChucK, thus resetting the output of the noise UGens; //mind your speakers, ears and neighbours! SubNoise n => dac; .2 => n.gain; while(1) { ((now/2::second)$int)%8 + 2 => n.rate; now%250::ms+ms=>now; 5 => Std.srand; } Interestingly this type of modulation is system-wide so running two files that both try to do this at the same time will result in rather complex sounds. Have fun, Kas.

1 0

The ChucK Show
by Les Hall 11 Jul '09

11 Jul '09

Hi folks, The ChucK Show this week was our best one ever. Sunshine is back in town and she always makes the show fun. I wrote a 1,000 line controller program with lots of bells and whistles. There were contributions from two newbie ChucKists, mattb was the ChucKist of the week, we took a quick tour of the Princeton ChucK website and went through a bunch of examples. Plus I played guitar a little bit as I have newly learned a basic finger picking technique. For next week I'd like to continue the exploration of the examples, but I'm not overly familiar with the entire collection of what's there. Would anyone on the list mind suggesting some examples that make good audio for the show? I will go through the STK directory, but I am unfamiliar with all of the other directories and it would be torture to go through *everything* this week before the show. So suggestions are welcome, thanks. Enjoy! Les (Inventor)

1 0

chuck mode for emacs
by Kao Cardoso Felix 05 Jul '09

05 Jul '09

Hello folks, I've just discovered and started learning ChucK and It's very neat. As I'm an Emacs user I downloaded the emacs mode for editing ChucK files. It was rather old and was missing some functionality so I've made an update. http://bitbucket.org/kcfelix/emacsd/src/tip/my-lisp/chuck-mode.el I've changed the syntax highlight to be more consistent with how other languages are highlighted inside Emacs and added all keywords, types and library functions listed on the documentation. Class and method name highlighting is not working yet, but I plan on adding it soon. Code to run the ChucK VM as an inferior process inside Emacs was commented because it wasn't working before. I've made it work and changed some keybings. Now it work like this: C-c C-c inside a ChucK buffer will send the buffer code to the VM. If there's no VM process one will be created. C-c C-d remove a shred from the VM by a numeric id (is there other ways to identify shreds besides numbers?) C-c C-r replace a shred with the code on the current buffer. I also added support for easy customization for the path of the chuck executable, so you don't have to edit lisp code to change it. Well, I'm planning to update it frequently to make it better according to my use of it, but if there's anyone using Emacs for ChucK and want to give some advice it would be very nice :) []'s -- Kao Cardoso Félix Página pessoal: http://www.inf.ufrgs.br/~kcfelix Blog: http://kaofelix.blogspot.com

4 8

Music Hack Day, London 11-12th July.
by ynohtna 03 Jul '09

03 Jul '09

Any ChucKists attending Music Hack Day next weekend? http://musichackday.org/ If you are, and fancy collaborating on a project that involves using ChucK to generate something hopefully (!) cool, then please get in touch. :) Cheers, Anthony.

1 0

The ChucK Show
by Les Hall 30 Jun '09

30 Jun '09

Hi all, Last week's show went very smoothly, including lots of me talking and playing guitar into ChucK effects pedals. Next week I will feature some more basic introductory vocal content about ChucK, such as the origins of ChucK, what you can do with ChucK, and introductory programming information. I think the show so far has been very technical and geared to the expert music coders and electronics buffs, so this change will hopefully address a broader audience. I also have one piece of new material, the song "onTheFly - Ben Zimmerman.mp3". Thanks Ben! I'd also like to mention that someone named Alphacore will be doing a show involving ChucK in some way on Thursdays at 5pm EST. The schedule is on the front page of www.electro-music.com and click on radio to hear the shows. Enjoy! Les (Inventor)

1 0

Re: [chuck-users] chuck-users Digest, Vol 47, Issue 28
by gary hiebner 28 Jun '09

28 Jun '09

Thanks Stefan, Finally got it to work I deleted the chuck file out of /usr/bin Unpacked the chuck installer package, copied it to my applications. Then used this handy site ( http://wiki.cs.princeton.edu/index.php/ChucK/OSX_Install_and_Run) to install it again to my /usr/bin Now runs fine. Thanks guys for all the tips, Can't wait to get my head stuck in the Chuck code! 2009/6/27 <chuck-users-request(a)lists.cs.princeton.edu> > Send chuck-users mailing list submissions to > chuck-users(a)lists.cs.princeton.edu > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > or, via email, send a message with subject or body 'help' to > chuck-users-request(a)lists.cs.princeton.edu > > You can reach the person managing the list at > chuck-users-owner(a)lists.cs.princeton.edu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chuck-users digest..." > > Today's Topics: > > 1. Re: chuck-users Digest, Vol 47, Issue 26 (Stefan Blixt) > 2. Re: chuck-users Digest, Vol 47, Issue 26 (Kassen) > > > ---------- Forwarded message ---------- > From: Stefan Blixt <stefan.blixt(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Date: Sat, 27 Jun 2009 18:53:59 +0200 > Subject: Re: [chuck-users] chuck-users Digest, Vol 47, Issue 26 > I usually leav Chuck where it is (currently in > /Applications/chuck-1.2.1.2-exe/bin), and add that to my path, like this: > Hailstone:~ stefanblixt$ echo $PATH > > /Applications/chuck-1.2.1.2-exe/bin:/Library/Frameworks/Python.framework/Versions/Current/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:. > Hailstone:~ stefanblixt$ which chuck > /Applications/chuck-1.2.1.2-exe/bin/chuck > Hailstone:~ stefanblixt$ chuck > [chuck]: no input files... (try --help) > Hailstone:~ stefanblixt$ > > Maybe chuck is confused if you put it in /usr/bin, and tries to locate some > file using a relative path or something? A long shot... > > /Stefan > > 2009/6/27 gary hiebner <gary(a)soundbase.co.za> > >> Hi Kas, >> Thanks. No offense taken. From my email it did sound like I didn't >> understand the Terminal. I should have added that in. >> >> I'll try install the chuck app. Again. I have installed on my new Macbook. >> I know when I had it on my G5 I used to get the 'no input message' >> >> Regards, >> Gary >> >> 2009/6/27 <chuck-users-request(a)lists.cs.princeton.edu> >> >>> Send chuck-users mailing list submissions to >>> chuck-users(a)lists.cs.princeton.edu >>> >>> To subscribe or unsubscribe via the World Wide Web, visit >>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >>> or, via email, send a message with subject or body 'help' to >>> chuck-users-request(a)lists.cs.princeton.edu >>> >>> You can reach the person managing the list at >>> chuck-users-owner(a)lists.cs.princeton.edu >>> >>> When replying, please edit your Subject line so it is more specific >>> than "Re: Contents of chuck-users digest..." >>> >>> Today's Topics: >>> >>> 1. Re: chuck-users Digest, Vol 47, Issue 24 (Kassen) >>> 2. Re: chuck-users Digest, Vol 47, Issue 24 (Cody Loyd) >>> 3. Re: Trying to get start with Chuck on MAC - USING TERMINAL >>> (Hans Aberg) >>> >>> >>> ---------- Forwarded message ---------- >>> From: Kassen <signal.automatique(a)gmail.com> >>> To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> >>> Date: Sat, 27 Jun 2009 16:02:25 +0200 >>> Subject: Re: [chuck-users] chuck-users Digest, Vol 47, Issue 24 >>> gary hiebner; >>> >>> I have an understanding of the Terminal. So that is not my problem. >>>> >>> >>> Ah, I see. I hope I didn't offend you by going back to the very basics. >>> There are after all many people who never laid eye on a terminal or prompt >>> before encountering ChucK. >>> >>> >>> >>>> It just goes to another prompt, so I don't know if it is working >>>> correctly in the Terminal >>>> >>>> eg I get this: >>>> >>>> matchbox$ chuck >>>> matchbox$ >>>> >>>> >>> OW.... that's quite odd, I've never seen or heard of that. The one thing >>> I can think of is that the program might not be marked as a executable or >>> that the file somehow got corrupted. I'm reaching here, to be honest I'm out >>> of ideas on what might be wrong here. >>> >>> Hoping others have better solutions, >>> Kas. >>> >>> >>> >>> ---------- Forwarded message ---------- >>> From: Cody Loyd <codyloyd(a)gmail.com> >>> To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> >>> Date: Sat, 27 Jun 2009 09:31:07 -0500 >>> Subject: Re: [chuck-users] chuck-users Digest, Vol 47, Issue 24 >>> have you tried using /usr/bin/chuck (or wherever it is installed) >>> instead of just 'chuck'? >>> >>> 2009/6/27 Kassen <signal.automatique(a)gmail.com>: >>> > gary hiebner; >>> > >>> >> I have an understanding of the Terminal. So that is not my problem. >>> > >>> > Ah, I see. I hope I didn't offend you by going back to the very basics. >>> > There are after all many people who never laid eye on a terminal or >>> prompt >>> > before encountering ChucK. >>> > >>> > >>> >> >>> >> It just goes to another prompt, so I don't know if it is working >>> correctly >>> >> in the Terminal >>> >> eg I get this: >>> >> matchbox$ chuck >>> >> matchbox$ >>> > >>> > OW.... that's quite odd, I've never seen or heard of that. The one >>> thing I >>> > can think of is that the program might not be marked as a executable or >>> that >>> > the file somehow got corrupted. I'm reaching here, to be honest I'm out >>> of >>> > ideas on what might be wrong here. >>> > >>> > Hoping others have better solutions, >>> > Kas. >>> > >>> > >>> > _______________________________________________ >>> > chuck-users mailing list >>> > chuck-users(a)lists.cs.princeton.edu >>> > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >>> > >>> > >>> >>> >>> >>> ---------- Forwarded message ---------- >>> From: Hans Aberg <haberg(a)math.su.se> >>> To: gary hiebner <gary(a)soundbase.co.za> >>> Date: Sat, 27 Jun 2009 17:58:28 +0200 >>> Subject: Re: [chuck-users] Trying to get start with Chuck on MAC - USING >>> TERMINAL >>> Fine! >>> >>> Hans >>> >>> >>> On 27 Jun 2009, at 15:21, gary hiebner wrote: >>> >>> Don't worry I found it in the chuck installer package under examples and >>> basic. Busy running some of the chuck files now. really fun. Starting t see >>> the potential of the aplication. >>> >>> On Sat, Jun 27, 2009 at 3:04 PM, gary hiebner <gary(a)soundbase.co.za>wrote: >>> >>>> I dont hav the miniaudicle documentations. I went to the website. But >>>> can't seem to find it. Can you send me a link to the documentatin so that I >>>> can test it out? >>>> Thanks in advance, >>>> >>>> Gary >>>> >>>> >>>> On Sat, Jun 27, 2009 at 2:37 PM, Hans Aberg <haberg(a)math.su.se> wrote: >>>> >>>>> 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 >>>> 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 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(a)lists.cs.princeton.edu >>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >>> >>> >> >> >> -- >> 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(a)lists.cs.princeton.edu >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >> >> > > > -- > Release me, insect, or I will destroy the Cosmos! > > > ---------- Forwarded message ---------- > From: Kassen <signal.automatique(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Date: Sat, 27 Jun 2009 19:13:51 +0200 > Subject: Re: [chuck-users] chuck-users Digest, Vol 47, Issue 26 > Stefan; > > Maybe chuck is confused if you put it in /usr/bin, and tries to locate some >> file using a relative path or something? A long shot... >> > > As far as I know the executable contains everything needed aside from your > .ck files (it even includes some short samples in the executable itself). Of > course it is linked to your system for audio, HID, etc, but it's location > shouldn't matter. If you don't like touching /usr/bin/ or /windows/system32/ > you can keep it in some dr of your own choice with no adverse effect. > > Yours, > Kas. > > _______________________________________________ > chuck-users mailing list > chuck-users(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > -- 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.

4 4

Re: [chuck-users] chuck-users Digest, Vol 47, Issue 26
by gary hiebner 27 Jun '09

27 Jun '09

Hi Kas, Thanks. No offense taken. From my email it did sound like I didn't understand the Terminal. I should have added that in. I'll try install the chuck app. Again. I have installed on my new Macbook. I know when I had it on my G5 I used to get the 'no input message' Regards, Gary 2009/6/27 <chuck-users-request(a)lists.cs.princeton.edu> > Send chuck-users mailing list submissions to > chuck-users(a)lists.cs.princeton.edu > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > or, via email, send a message with subject or body 'help' to > chuck-users-request(a)lists.cs.princeton.edu > > You can reach the person managing the list at > chuck-users-owner(a)lists.cs.princeton.edu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chuck-users digest..." > > Today's Topics: > > 1. Re: chuck-users Digest, Vol 47, Issue 24 (Kassen) > 2. Re: chuck-users Digest, Vol 47, Issue 24 (Cody Loyd) > 3. Re: Trying to get start with Chuck on MAC - USING TERMINAL > (Hans Aberg) > > > ---------- Forwarded message ---------- > From: Kassen <signal.automatique(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Date: Sat, 27 Jun 2009 16:02:25 +0200 > Subject: Re: [chuck-users] chuck-users Digest, Vol 47, Issue 24 > gary hiebner; > > I have an understanding of the Terminal. So that is not my problem. >> > > Ah, I see. I hope I didn't offend you by going back to the very basics. > There are after all many people who never laid eye on a terminal or prompt > before encountering ChucK. > > > >> It just goes to another prompt, so I don't know if it is working correctly >> in the Terminal >> >> eg I get this: >> >> matchbox$ chuck >> matchbox$ >> >> > OW.... that's quite odd, I've never seen or heard of that. The one thing I > can think of is that the program might not be marked as a executable or that > the file somehow got corrupted. I'm reaching here, to be honest I'm out of > ideas on what might be wrong here. > > Hoping others have better solutions, > Kas. > > > > ---------- Forwarded message ---------- > From: Cody Loyd <codyloyd(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Date: Sat, 27 Jun 2009 09:31:07 -0500 > Subject: Re: [chuck-users] chuck-users Digest, Vol 47, Issue 24 > have you tried using /usr/bin/chuck (or wherever it is installed) > instead of just 'chuck'? > > 2009/6/27 Kassen <signal.automatique(a)gmail.com>: > > gary hiebner; > > > >> I have an understanding of the Terminal. So that is not my problem. > > > > Ah, I see. I hope I didn't offend you by going back to the very basics. > > There are after all many people who never laid eye on a terminal or > prompt > > before encountering ChucK. > > > > > >> > >> It just goes to another prompt, so I don't know if it is working > correctly > >> in the Terminal > >> eg I get this: > >> matchbox$ chuck > >> matchbox$ > > > > OW.... that's quite odd, I've never seen or heard of that. The one thing > I > > can think of is that the program might not be marked as a executable or > that > > the file somehow got corrupted. I'm reaching here, to be honest I'm out > of > > ideas on what might be wrong here. > > > > Hoping others have better solutions, > > Kas. > > > > > > _______________________________________________ > > chuck-users mailing list > > chuck-users(a)lists.cs.princeton.edu > > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > > > > > > > ---------- Forwarded message ---------- > From: Hans Aberg <haberg(a)math.su.se> > To: gary hiebner <gary(a)soundbase.co.za> > Date: Sat, 27 Jun 2009 17:58:28 +0200 > Subject: Re: [chuck-users] Trying to get start with Chuck on MAC - USING > TERMINAL > Fine! > > Hans > > > On 27 Jun 2009, at 15:21, gary hiebner wrote: > > Don't worry I found it in the chuck installer package under examples and > basic. Busy running some of the chuck files now. really fun. Starting t see > the potential of the aplication. > > On Sat, Jun 27, 2009 at 3:04 PM, gary hiebner <gary(a)soundbase.co.za>wrote: > >> I dont hav the miniaudicle documentations. I went to the website. But >> can't seem to find it. Can you send me a link to the documentatin so that I >> can test it out? >> Thanks in advance, >> >> Gary >> >> >> On Sat, Jun 27, 2009 at 2:37 PM, Hans Aberg <haberg(a)math.su.se> wrote: >> >>> 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 >> 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 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(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > -- 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.

3 3

Re: [chuck-users] Trying to get start with Chuck on MAC - USING TERMINAL
by Hans Aberg 27 Jun '09

27 Jun '09

Fine! Hans On 27 Jun 2009, at 15:21, gary hiebner wrote: > Don't worry I found it in the chuck installer package under examples > and basic. Busy running some of the chuck files now. really fun. > Starting t see the potential of the aplication. > > On Sat, Jun 27, 2009 at 3:04 PM, gary hiebner <gary(a)soundbase.co.za> > wrote: > I dont hav the miniaudicle documentations. I went to the website. > But can't seem to find it. Can you send me a link to the > documentatin so that I can test it out? > > Thanks in advance, > > Gary > > > On Sat, Jun 27, 2009 at 2:37 PM, Hans Aberg <haberg(a)math.su.se> wrote: > 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 > 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 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. > >

1 0

Re: [chuck-users] chuck-users Digest, Vol 47, Issue 24
by gary hiebner 27 Jun '09

27 Jun '09

Thanks Kas, And Andrew. I have an understanding of the Terminal. So that is not my problem. My problem is that when I try run chuck from the Terminal, I don't get anything, even when I try run a file ( >chuck foo.ck). But when I run the file in miniAudicle, it runs fine. When I am in the Treminal, and I type >Chuck (Thanks for spotting the > kas, was putting it there to represent the prompt). I dont get the [chuck]: no input files.... message. It just goes to another prompt, so I don't know if it is working correctly in the Terminal eg I get this: matchbox$ chuck matchbox$ If I log in under sudo, it does the same thing: sh-3.2# chuck sh-3.2# Then if I try run the foo.ck file, I don't get anything, but when I run it in miniAudilce, it runs fine. On the Mac, you can drag the file into the Terminal, and it gives the correct location to run the ck file, so I know it is pointing to the right path. p.s. here is the link to the Ge Wang vid I saw on the Apple site. Nice video. Really inspired me to try this application out http://www.apple.com/pro/profiles/slork/ Looks like they are using the Terminal. I like it how they are using the trackpad and motion sensors on the Macbook, to generate different sounds. I just got a Macbook Pro 3 days ago, and am rwally excited about trying the motion sensors and trackpad with Chuck. 2009/6/27 <chuck-users-request(a)lists.cs.princeton.edu> > Send chuck-users mailing list submissions to > chuck-users(a)lists.cs.princeton.edu > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > or, via email, send a message with subject or body 'help' to > chuck-users-request(a)lists.cs.princeton.edu > > You can reach the person managing the list at > chuck-users-owner(a)lists.cs.princeton.edu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chuck-users digest..." > > Today's Topics: > > 1. Trying to get start with Chuck on MAC - USING TERMINAL > (gary hiebner) > 2. Re: Trying to get start with Chuck on MAC - USING TERMINAL > (Andrew Turley) > 3. Re: Trying to get start with Chuck on MAC - USING TERMINAL > (Kassen) > 4. Re: Trying to get start with Chuck on MAC - USING TERMINAL > (Hans Aberg) > 5. Re: Trying to get start with Chuck on MAC - USING TERMINAL > (Kassen) > > > ---------- Forwarded message ---------- > From: gary hiebner <soundbasestudios(a)gmail.com> > To: chuck-users(a)lists.cs.princeton.edu > Date: Sat, 27 Jun 2009 06:05:13 +0200 > Subject: [chuck-users] 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. > > > > > ---------- Forwarded message ---------- > From: Andrew Turley <aturley(a)acm.org> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Date: Fri, 26 Jun 2009 23:08:08 -0700 > Subject: Re: [chuck-users] Trying to get start with Chuck on MAC - USING > TERMINAL > 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 <soundbasestudios(a)gmail.com>: > > 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(a)lists.cs.princeton.edu > > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > > > > > > > ---------- Forwarded message ---------- > From: Kassen <signal.automatique(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Date: Sat, 27 Jun 2009 13:19:22 +0200 > Subject: Re: [chuck-users] Trying to get start with Chuck on MAC - USING > TERMINAL > > 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. > > > ---------- Forwarded message ---------- > From: Hans Aberg <haberg(a)math.su.se> > To: gary hiebner <soundbasestudios(a)gmail.com> > Date: Sat, 27 Jun 2009 14:37:07 +0200 > Subject: Re: [chuck-users] Trying to get start with Chuck on MAC - USING > TERMINAL > 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 > > > > > > > ---------- Forwarded message ---------- > From: Kassen <signal.automatique(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Date: Sat, 27 Jun 2009 15:28:36 +0200 > Subject: Re: [chuck-users] Trying to get start with Chuck on MAC - USING > TERMINAL > > 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-users mailing list > chuck-users(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > -- 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.

3 2