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

Re: WvOut
by Jim Hinds 08 Nov '05

08 Nov '05

I'd like to learn from Eduard's example of "not working." My conjecture is that the fan-out of the ugen whitenoise is only one, and that the last "chuck" operator (whitenoise => dac) un-chucks the previous line. That is, for a general ugen (or other chuckable object): fan-in == many; fan-out == 1. Yes? Jim Hinds > > From: eduard <eduard.aylon(a)gmail.com> > Date: November 8, 2005 1:28:57 AM HST > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: [chuck-users] WvOut > Reply-To: ChucK Users Mailing List <chuck- > users(a)lists.cs.princeton.edu> > > > Could you give a quick example on how to use WvOut in order to > write to a file? > I have tried the following with no success, a part from having an > empty "audio" file: > > WvOut waveOut; > gain g; > 0.9 =>g.gain; > noise whitenoise; > 0.5 => whitenoise.gain; > "/CHUCK/samples/test.wav"=>waveOut.wavFilename; > whitenoise => waveOut; > whitenoise => dac; > 2::second => now; > waveOut.closeFile; > whitenoise =< dac; > >

2 1

(no subject)
by andreas＠smartelectronix.com 05 Nov '05

05 Nov '05

Hey all, just started playing with the 'new' chuck...hmmm , fun:) now, i'm wondering, is it possible to get the contents of a directory (and loop thru all the file(name)s...)? i want to load a whole directory full of samples into an array of sndbuf's... thanks, regards -andreas

6 8

audicle question
by Ken 04 Nov '05

04 Nov '05

i read the .pdf about the audicle and a quick question i have about the user programmable face, will it be possible to create synth interfaces in opengl, and 3d graphics projection for vj projects within chuck? thanks, ken

2 1

RE: [chuck-users] include
by Robin Davies 01 Nov '05

01 Nov '05

There were remnants and vestiges of an "auto-include" feature in Chuck sources last time I looked. These looked fairly promising. I'm not sure what the original intent was -- it didn't seem to be terribly functional in the last set of sources I looked at, but the general intention seemed like a good idea. As I read it, the intention was to look for a matching source file for undefined classes and load the matching source file on demand. The complication, presumably, is that the class implementations have to be loaded in multiple steps: parse all declarations of auto-included files first, and then bind references in a separate pass, in order to avoid problems with circular references. The code for the multi-step binding seems to be mostly there too -- more there, than the auto-include flag, anyway. The basic idea seemed sound, and is somewhat better than providing a lexical include facility. > -----Original Message----- > From: chuck-users-bounces(a)lists.cs.princeton.edu [mailto:chuck-users- > bounces(a)lists.cs.princeton.edu] On Behalf Of Rasmus Kaj > Sent: Tuesday, November 01, 2005 2:16 PM > To: ChucK Users Mailing List > Subject: Re: [chuck-users] include > > >>>>> "PD" == Philip Davidson <philipd(a)CS.Princeton.EDU> writes: > > PD> yes, but it's in development / testing phases. > > Ah, I should take a look at that, then ... Is it a "simple lexical" > include (like with the c preprocessor), or is it in a higher level, > (what I'd like to call require/provide, like in elisp), so that the > included code only needs to be compiled once? > > Basically, I'd like "require foo" to check (in a hash table) if foo > allready is provided, and in that case just return. If foo isn't > provided, it could search the load path for "foo.ck", and compile that > if found. > > This would be very simple given a global namespace for functions and > classes (so that the classes in foo is available for all shreds when > foo is required in one). Otherwise require would also have to include > the foo namespace into the current namespace. > > -- > Rasmus Kaj --+-- rasmus(a)kaj.se --+-- http://www.stacken.kth.se/~kaj/ > Det är alldeles för mycket sport inom idrotten > _______________________________________________ > chuck-users mailing list > chuck-users(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

1 0

include
by Atte André Jensen 01 Nov '05

01 Nov '05

Is there an include or equivalent in chuck (Still thinking about how to modulize code)? -- peace, love & harmony Atte http://www.atte.dk

3 3

emacs.el?
by Ken 01 Nov '05

01 Nov '05

i read somewhere that there is a chuck mode for emacs, but i can't seem o find it. does anyone have that available? thanks, ken

4 6

which language?
by Ken 31 Oct '05

31 Oct '05

i'd like to take a stab at developing for chuck. which language do i need to develop in? is c supported? Thanks, Ken

2 1

building an instrument library
by Atte André Jensen 30 Oct '05

30 Oct '05

Hi I'm just beginning to explore chuck. I set out to find a way to seperate instrument definitions from note-playing-code. I wrapped up my result so far and put them here: http://www.atte.dk/download/modular_instrument_defs.tgz The README.txt explains what to do with it, but let me re-state the problems I have: 1. Removing a shread (by "chuck - SOME_ID") stops the shred in the middle of the current note, resulting in a click. 2. Since a new shread is sporked on each note, the shread ID's quickly grow to inconveniently large proportions. The reason for sporking each note is an attempt to rid the pattern of any knowledge of the time it actually takes to play the note. 3. Sometimes adding the hh.ck pattern (not the instrument) is playing the first note very loud. Of course this is heavily inspired by the otf_* files and reveals my so far very limited understanding of chuck. But eventually I think some way of seperating out instrument design (and other stuff as well; keys, scales, tempo and meter comes to mind) would benefit my productivity in the long run... I'm not at all sure that this is the way to go, so I'd appreciate any feedback. How many of my problems are due to bugs, wrong implementations or conceptual misunderstanding? -- peace, love & harmony Atte http://www.atte.dk

1 0

2 questions
by Atte André Jensen 29 Oct '05

29 Oct '05

Basically: 1) I'd like to define a library of instruments for reuse. Seems like this *could* be achieved by defining one class per .ck file and adding these files (possibly by a script) to a running chuck before use. Has the disadvantage that the first zillion shreds will be taken up by instrument-def files, not too handy if a replace/remove a schred. Is there a best/better way to do this? I found no include, did I overlook something? 2) Supposed I want to do a slightly complex pitch envelope. How is that best achieved? Which example to look at? -- peace, love & harmony Atte http://www.atte.dk

1 0

1.2.0.3 compilation problem
by Michal Seta 29 Oct '05

29 Oct '05

Hello all, First of all, I am glad to see that since 1.2.0.1 the linux version of chuck behaves so much nicer! (for me, anyways) I jumped to the 1.2.0.3 now and can't get it to compile: make -f makefile.jack make[1]: Entering directory `/home/mis/downloads/chuck-1.2.0.3/src' gcc -D__LINUX_JACK__ -O3 -c -D__CK_SNDFILE_NATIVE__ chuck.yy.c chuck.lex: In function `block_comment': chuck.lex:280: error: `yytext_ptr' undeclared (first use in this function) chuck.lex:280: error: (Each undeclared identifier is reported only once chuck.lex:280: error: for each function it appears in.) make[1]: *** [chuck.yy.o] Error 1 make[1]: Leaving directory `/home/mis/downloads/chuck-1.2.0.3/src' make: [linux-jack] Error 2 (ignored) 1.2.0.1 compiled fine, have the requirements changed since then? thanks (should this be going to chuck-dev or something? I'm subbed to this list only). ./MiS

2 3