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

microphone in ubuntu gutsy
by AlgoMantra 15 Dec '07

15 Dec '07

Dear All, Attached is the screenshot of my $alsamixer status in Ubuntu Gutsy. audio outputs are all working fine, but I can't seem to get my external microphone working with anything - Chuck programming language, Audacity, etc. Any ideas on how to fix this? I'm on a Compaq Presarion C500. And here is a portion of my $lspci which might be relevant here: *00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01)* thanks in advance, -- fadereu ------- -.- 1/f ))) --. ------- ... http://www.algomantra.com

3 6

chuck and 64-bit
by rubber glove 13 Dec '07

13 Dec '07

>From reading through the mailinglist archives, I've learned that chuck is not compatible with 64-bit operating systems. The incompatibility I can understand, but I'd just like to suggest that that information be added to the build notes/download page to save some potential frustration... The situation is especially confusing since there are (non-functional) 64-bit packages available for Debian and Ubuntu. Please let me know if I'm mistaken here, otherwise I'll add a page to the wiki detailing how to get chuck working in a 32-bit chroot environment. thanks, Martin

2 1

shreds, namespace, functions, classes, etc
by Kassen 12 Dec '07

12 Dec '07

Dear list, Shreds are objects (of type Shred) and functions aren't objects. This is all good and well but it gets harder when we spork a function and the function becomes a Shred and hence a Object. Consider this; ------------------------ fun void tester() { "boom" => string beep; while(1) { <<<beep>>>; second => now; } } spork ~ tester() @=> Shred foo; 5::second => now; "clik" => foo.beep; //this doesn't work day=> now; ---------------------------------------- It's not so clear to me *why* the offending line doesn't work. Maybe I'm misunderstanding something or making a syntax error but I think that what we are seeing here is a loss of namespace that would be useful and I don't understand why this happens. I also tried stuff along these lines; ---------------------- class Bar extends Shred { //stuff including variables and a constructor } ------------------------------ If I do that I can instantiate a "Bar" but all it does is run it's constructor; I can't manage to spork a Bar or assign a sporked shred to a Bar. I can also make a array of Bar's but all that gets me is the constructor running; --------------------------- class Bar extends Shred { static int number; <<<number++>>>; } //print a series of numbers, no shreds in sight Bar array[5]; ---------------------------------- So, now I'm quite happy I said so many times that there are no "stupid n00b questions" because now it's my turn to ask exactly what a "Shred" is because I'm starting to feel like I have no idea. :¬) Could somebody please explain to me exactly what's going on here? Yours, Kas.

4 10

Sending an OSC Message with no Parameters
by Christopher Graham 03 Dec '07

03 Dec '07

I'm trying to send an OSC message with no parameters, just an address string, but the examples all show the message being created with xmit.startMsg( "/..., ..."), and then sent when the last parameter is provided with say a xmit.addInt. The tutorial also says that the message is sent when all parameters have been provided. Therefore I would expect that xmit.startMsg( "/...") with no OSC parameters specified sends the message immediately. How would one trigger the sending of an OSC message such as xmit.startMsg( "/Start") ? - Chris

2 1

Sitar, hearing voices, Miniaudicle
by Kassen 02 Dec '07

02 Dec '07

Dear ChucKists, Last night I was fooling around with some STK instruments and it looks like Sitar needs some attention. First of all Sitar.pluck() doesn't.... well, pluck. Sitar.moteOn() does pluck and as far as I can see .noteOn could simply be refered to by .pluck(). Second one is slightly more complicated and turns out to be downright dangerous. I accidentally send Sitar some every low notes (in the bottom octave of the MIDI range) and this results in a error that the delay line is too short. Strangely StifKarp doesn't do the same (that one "plucks" as well). This gets dangerous as I believe Sitar will report on this issue for every sample so that's 44 Kilo-errors per second. This was too much for the poor MiniAudicle to deal with and I had to quit it. If it's intended behaviour that Sitar has a minimum frequency (for example because real sitars don't go into the very low range either) it would be bettter to have a sanity check on the frequency before this happens. I could probably fix these myself tomorow and send in the fixed STK Ugens cpp file if that would be helpfull? Next up; VoicForm's documentation doesn't include any mention of the allowed phonemes (sp?) and the only way that I could find them was read the source. Without those this Ugens is almost unusable for non-random usage so that probably needs a fix. I realise, BTW, that figuring out the parameters is time-consuming and probably boring as well but wouldn't it be a lot of fun if ChucK could say it's own name? I tried to persuade it to do that but I think we are short a few sounds.Generally we don't seem to have any plosives or "C"/"k" type clicking sounds so that"s no "chucK', "spork" or "crash" maybe "shred" would be possible. It's kinda trivial but it would be so much fun for demonstrations. I could submit a sugested addition for the docs to the WiKi as well tomorow, the source is quite clear on this once you know your way around. Finally, I did some more testing and I'm now sure that on XP the Mini affects keyboard settings. More speciffically on startup the Mini switches the keyboard layout in the "langiuage bar" to the default one that XP asumes on startup. This can get anoying; my default setting is the Dutch one so I can use my trusty IBM model M but the laptop itself has a US layout so when traveling lightly ( a Model M clocks in at 2.5KG, roughly 5 pounds) I use the US layout. It gets iritating if the Mini keeps switching this back to NL every time it's started (which can get frequent when hunting bugs), especially as I can't see a reason for that. Note that characters like "=" and ">" are in different places on various layouts, as are all the brackets.... It also looks like the Mini doesn't use XP's clip-board so pasting from the Mini to other aplications is impossible, it's also not possible to use "copy", re-start the Mini (or crash it!), then paste. So, that's it, quite a few issues for a 1.5::hour session but that's how it goes :-) Yours, Kas.

4 6

Better explain Myself about kb triggering.
by Alpha Core 01 Dec '07

01 Dec '07

Thanks for all the help first of all I played around with the kb.ck in the hid folder and saw that it typed out the letters i pressed so i can use the same setup and say omodify it to trigger for a example when press A triggers a SinOsc to play a freq for say 1 sec ? About the variable question sorry about that I ment a char array like in C++ thanks again . Gabriel aka ALPHACORE --------------------------------- Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how.

1 0

Re: [chuck-users] chuck-users Digest, Vol 29, Issue 1
by Alpha Core 01 Dec '07

01 Dec '07

thank you for the help I think I understand it now I'll read the Kb.ck file and play around with it as far as Charcter variables in think you already answered it thanks Again.. Alphacore chuck-users-request(a)lists.cs.princeton.edu wrote: 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: Question about Routing instruments? (Kassen) 2. Re: parab0xx in Wired News (robin.escalation) From: Kassen <signal.automatique(a)gmail.com> Subject: Re: [chuck-users] Question about Routing instruments? Date: Fri, 30 Nov 2007 19:58:37 +0100 To: "ChucK Users Mailing List" <chuck-users(a)lists.cs.princeton.edu> Hi, Alpha! My question is this Can I say create a Osc with setting that I want which i know how to do But can i say route it to the computer keyboard say trigger it by pressing the letter A Yes, you can. This is quite easy. First thing to do would be to have a look at kb.ck in the /examples/hid/ folder, this will teach you how to use the keyboard as a input device. Run that, press the key you'd like to use and see what id it has. You then include a shred that reads from the keyboard like that file does, write some rules to detect the keys you are interested in and link those to commands like; if(msg.which == my_keynumber) my_envelope.keyOn; Quite easy once you get the hang of it. or can I just setup a char. variable to trigger it? I don't quite understand this question, could you re-phrase it? What do you mean by "char. variable"? Yours, Kas. From: "robin.escalation" <robin.escalation(a)acm.org> Subject: Re: [chuck-users] parab0xx in Wired News Date: Sat, 1 Dec 2007 05:07:51 -0800 (PST) To: chuck-users(a)lists.cs.princeton.edu AlgoMantra wrote: > We didn't use ChucK in this one, but you can using OSC! > I have used Python, and released the source too. Check out > the story, and please feel free to embellish and improve upon > the code for your own evil purposes. I'm also happy to look > at collaborative opportunities/ideas. The code is at my website > (see below). That is pretty freakin' cool and similar to something I wanted to do myself. Plus in Python... perfect! Will check out the details. -- robin ----- Robin Parmar robinparmar.com _______________________________________________ chuck-users mailing list chuck-users(a)lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users --------------------------------- Get easy, one-click access to your favorites. Make Yahoo! your homepage.

1 0

Re: [chuck-users] parab0xx in Wired News
by robin.escalation 01 Dec '07

01 Dec '07

AlgoMantra <algomantra(a)gmail.com> wrote: > We didn't use ChucK in this one, but you can using OSC! > I have used Python, and released the source too. Check out > the story, and please feel free to embellish and improve upon > the code for your own evil purposes. I'm also happy to look > at collaborative opportunities/ideas. The code is at my website > (see below). That is pretty freakin' cool and similar to something I wanted to do myself. Plus in Python... perfect! Will check out the details. -- robin ----- Robin Parmar robinparmar.com

2 1

Question about Routing instruments?
by Alpha Core 30 Nov '07

30 Nov '07

Hello I had A question about routing intsturment and triggering them via keyboard I produce text to midi music And now that I have found and been using CHUCK i think its great.. My question is this Can I say create a Osc with setting that I want which i know how to do But can i say route it to the computer keyboard say trigger it by pressing the letter A or can I just setup a char. variable to trigger it? Thanks for any Help Alphacore --------------------------------- Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.

2 1

Compiling Chuck on Ubuntu 7.04
by Christian Werthschuĺte 30 Nov '07

30 Nov '07

Hello, I'm trying to compile and install chuck on Ubuntu 7.04 with OSS yet have come across the following error message: What have I done wrong? Thanks, Christian christian@christian-laptop:~/Downloads/chuck-1.2.1.1/src$ make linux-oss make -f makefile.oss make[1]: Betrete Verzeichnis '/home/christian/Downloads/chuck-1.2.1.1/src' g++ -D__LINUX_OSS__ -c -O3 -D__CK_SNDFILE_NATIVE__ rtaudio.cpp g++ -D__LINUX_OSS__ -c -O3 -D__CK_SNDFILE_NATIVE__ rtmidi.cpp g++ -D__LINUX_OSS__ -c -O3 -D__CK_SNDFILE_NATIVE__ ugen_osc.cpp g++ -D__LINUX_OSS__ -c -O3 -D__CK_SNDFILE_NATIVE__ ugen_filter.cpp g++ -D__LINUX_OSS__ -c -O3 -D__CK_SNDFILE_NATIVE__ ugen_stk.cpp g++ -D__LINUX_OSS__ -c -O3 -D__CK_SNDFILE_NATIVE__ ugen_xxx.cpp ugen_xxx.cpp:43:21: error: sndfile.h: No such file or directory ugen_xxx.cpp:2075: Fehler: ISO-C++ verbietet Deklaration von »SNDFILE« ohne Typ ugen_xxx.cpp:2075: Fehler: expected »;« before »*« token ugen_xxx.cpp: In constructor »sndbuf_data::sndbuf_data()«: ugen_xxx.cpp:2111: Fehler: »fd« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp: In function »long unsigned int sndbuf_read(sndbuf_data*, long unsigned int, long unsigned int)«: ugen_xxx.cpp:2142: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2154: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2154: Fehler: »sf_seek« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2158: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2158: Fehler: »sf_readf_float« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2168: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2168: Fehler: »sf_close« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2169: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp: In function »void sndbuf_setpos(sndbuf_data*, double)«: ugen_xxx.cpp:2216: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp: In function »float sndbuf_sampleAt(sndbuf_data*, long int)«: ugen_xxx.cpp:2236: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp: In function »void sndbuf_ctrl_read(Chuck_Object*, void*, Chuck_DL_Return*, Chuck_VM_Shred*)«: ugen_xxx.cpp:2457: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2459: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2459: Fehler: »sf_close« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2460: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2588: Fehler: »SF_INFO« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2588: Fehler: expected `;' before »info« ugen_xxx.cpp:2589: Fehler: »info« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2594: Fehler: »SF_FORMAT_RAW« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2594: Fehler: »SF_FORMAT_PCM_16« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2594: Fehler: »SF_ENDIAN_CPU« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2600: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2600: Fehler: »SFM_READ« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2600: Fehler: »sf_open« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2601: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2601: Fehler: »sf_error« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2605: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2605: Fehler: »sf_strerror« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2606: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2606: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2606: Fehler: »sf_close« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2630: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2630: Fehler: »sf_seek« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2643: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2643: Fehler: »sf_close« wurde in diesem Gültigkeitsbereich nicht definiert ugen_xxx.cpp:2643: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp:2647: Fehler: »struct sndbuf_data« hat kein Element namens »fd« ugen_xxx.cpp: In function »void sndbuf_cget_valueAt(Chuck_Object*, void*, Chuck_DL_Return*, Chuck_VM_Shred*)«: ugen_xxx.cpp:2840: Fehler: »struct sndbuf_data« hat kein Element namens »fd« make[1]: *** [ugen_xxx.o] Fehler 1 make[1]: Verlasse Verzeichnis '/home/christian/Downloads/chuck-1.2.1.1/src' make: [linux-oss] Fehler 2 (ignoriert)

3 4