July 2004 - chuck - lists.cs.princeton.edu

errors with make linux-jack
by smoerk 28 Jul '04

28 Jul '04

am i doing something wrong? it builds for alsa, but not for jack... (jack 0.98) # make linux-jack make -f makefile.jack make[1]: Entering directory `/opt/cvs/chuck_dev/src' bison -dv -b chuck chuck.y gcc -D__LINUX_JACK__ -O3 -g -c chuck.tab.c flex -ochuck.yy.c chuck.lex gcc -D__LINUX_JACK__ -O3 -g -c chuck.yy.c gcc -D__LINUX_JACK__ -O3 -g -c chuck_main.cpp gcc -D__LINUX_JACK__ -O3 -g -c chuck_errormsg.c gcc -D__LINUX_JACK__ -O3 -g -c chuck_utils.c gcc -D__LINUX_JACK__ -O3 -g -c chuck_symbol.c gcc -D__LINUX_JACK__ -O3 -g -c chuck_table.c gcc -D__LINUX_JACK__ -O3 -g -c chuck_temp.c gcc -D__LINUX_JACK__ -O3 -g -c chuck_absyn.c gcc -D__LINUX_JACK__ -O3 -g -c chuck_type.cpp gcc -D__LINUX_JACK__ -O3 -g -c chuck_emit.cpp gcc -D__LINUX_JACK__ -O3 -g -c chuck_frame.cpp gcc -D__LINUX_JACK__ -O3 -g -c chuck_instr.cpp gcc -D__LINUX_JACK__ -O3 -g -c chuck_vm.cpp gcc -D__LINUX_JACK__ -O3 -g -c chuck_ugen.cpp gcc -D__LINUX_JACK__ -O3 -g -c chuck_bbq.cpp gcc -D__LINUX_JACK__ -O3 -g -c chuck_socket.c gcc -D__LINUX_JACK__ -O3 -g -c chuck_dl.cpp gcc -D__LINUX_JACK__ -O3 -g -c digitalio_rtaudio.cpp gcc -D__LINUX_JACK__ -O3 -g -c rtaudio.cpp gcc -D__LINUX_JACK__ -O3 -g -c midiio_alsa.cpp gcc -D__LINUX_JACK__ -O3 -g -c ugen_osc.cpp gcc -D__LINUX_JACK__ -O3 -g -c ugen_xxx.cpp In file included from ugen_xxx.cpp:627: util_sndfile.h:319: error: syntax error before `;' token util_sndfile.h:329: error: 'sf_count_t' is used as a type, but is not defined as a type. util_sndfile.h:382: error: 'sf_count_t' is used as a type, but is not defined as a type. util_sndfile.h:383: error: 'sf_count_t' is used as a type, but is not defined as a type. util_sndfile.h:476: error: parse error before `*' token util_sndfile.h:493: error: parse error before `*' token util_sndfile.h:494: error: parse error before `*' token util_sndfile.h:506: error: parse error before `*' token util_sndfile.h:507: error: parse error before `*' token util_sndfile.h:509: error: parse error before `*' token util_sndfile.h:510: error: parse error before `*' token util_sndfile.h:512: error: parse error before `*' token util_sndfile.h:513: error: parse error before `*' token util_sndfile.h:515: error: parse error before `*' token util_sndfile.h:516: error: parse error before `*' token util_sndfile.h:523: error: parse error before `*' token util_sndfile.h:524: error: parse error before `*' token util_sndfile.h:526: error: parse error before `*' token util_sndfile.h:527: error: parse error before `*' token util_sndfile.h:529: error: parse error before `*' token util_sndfile.h:530: error: parse error before `*' token util_sndfile.h:532: error: parse error before `*' token util_sndfile.h:533: error: parse error before `*' token util_sndfile.h:725: error: 'sf_count_t' is used as a type, but is not defined as a type. util_sndfile.h:737: error: 'sf_count_t' is used as a type, but is not defined as a type. util_sndfile.h:738: error: 'sf_count_t' is used as a type, but is not defined as a type. util_sndfile.h:740: error: 'sf_count_t' is used as a type, but is not defined as a type. util_sndfile.h:741: error: 'sf_count_t' is used as a type, but is not defined as a type. util_sndfile.h:742: error: 'sf_count_t' is used as a type, but is not defined as a type. util_sndfile.h:751: error: 'sf_count_t' is used as a type, but is not defined as a type. util_sndfile.h:752: error: 'sf_count_t' is used as a type, but is not defined as a type. util_sndfile.h:769: error: `read_short' was not declared in this scope util_sndfile.h:769: error: type specifier omitted for parameter `sf_count_t' util_sndfile.h:769: error: parse error before `)' token util_sndfile.h:769: error: variable declaration is not allowed here util_sndfile.h:770: error: `read_int' was not declared in this scope util_sndfile.h:770: error: type specifier omitted for parameter `sf_count_t' util_sndfile.h:770: error: parse error before `)' token util_sndfile.h:770: error: variable declaration is not allowed here util_sndfile.h:771: error: `read_float' was not declared in this scope util_sndfile.h:771: error: type specifier omitted for parameter `sf_count_t' util_sndfile.h:771: error: parse error before `)' token util_sndfile.h:771: error: variable declaration is not allowed here util_sndfile.h:772: error: `read_double' was not declared in this scope util_sndfile.h:772: error: type specifier omitted for parameter `sf_count_t' util_sndfile.h:772: error: parse error before `)' token util_sndfile.h:772: error: variable declaration is not allowed here util_sndfile.h:774: error: `write_short' was not declared in this scope util_sndfile.h:774: error: type specifier omitted for parameter `sf_count_t' util_sndfile.h:774: error: parse error before `)' token util_sndfile.h:774: error: variable declaration is not allowed here util_sndfile.h:775: error: `write_int' was not declared in this scope util_sndfile.h:775: error: type specifier omitted for parameter `sf_count_t' util_sndfile.h:775: error: parse error before `)' token util_sndfile.h:775: error: variable declaration is not allowed here util_sndfile.h:776: error: `write_float' was not declared in this scope util_sndfile.h:776: error: type specifier omitted for parameter `sf_count_t' util_sndfile.h:776: error: parse error before `)' token util_sndfile.h:776: error: variable declaration is not allowed here util_sndfile.h:777: error: `write_double' was not declared in this scope util_sndfile.h:777: error: type specifier omitted for parameter `sf_count_t' util_sndfile.h:777: error: parse error before `)' token util_sndfile.h:777: error: variable declaration is not allowed here util_sndfile.h:779: error: `seek' was not declared in this scope util_sndfile.h:779: error: type specifier omitted for parameter `sf_count_t' util_sndfile.h:779: error: parse error before `)' token util_sndfile.h:779: error: variable declaration is not allowed here util_sndfile.h:1017: error: parse error before `*' token util_sndfile.h:1034: error: parse error before `*' token util_sndfile.h:1035: error: parse error before `*' token util_sndfile.h:1036: error: parse error before `*' token util_sndfile.h:1037: error: parse error before `*' token util_sndfile.h:1038: error: parse error before `*' token util_sndfile.h:1039: error: parse error before `*' token util_sndfile.h:1043: error: type specifier omitted for parameter `sf_count_t' util_sndfile.h:1043: error: parse error before `)' token util_sndfile.h:1111: error: type specifier omitted for parameter `sf_count_t' util_sndfile.h:1111: error: parse error before `)' token In file included from ugen_xxx.cpp:627: util_sndfile.h:1434:10: #error "Target CPU endian-ness unknown. May need to hand edit src/config.h" util_sndfile.h:1463:10: #error "Target CPU endian-ness unknown. May need to hand edit src/config.h" util_sndfile.h:2489:10: warning: #warning "Don't have the functions lrint() and lrintf()." util_sndfile.h:2490:10: warning: #warning "Replacing these functions with a standard C cast." ugen_xxx.cpp: In function `void sndbuf_ctrl_read(double, void*, void*)': ugen_xxx.cpp:652: error: 'struct SF_INFO' has no member named 'frames' ugen_xxx.cpp:655: error: 'struct SF_INFO' has no member named 'frames' ugen_xxx.cpp:657: error: `sf_read_float' undeclared (first use this function) ugen_xxx.cpp:657: error: (Each undeclared identifier is reported only once for each function it appears in.) make[1]: *** [ugen_xxx.o] Error 1 make[1]: Leaving directory `/opt/cvs/chuck_dev/src' make: [linux-jack] Error 2 (ignored)

3 5

OSC + Documentation
by Ge Wang 27 Jul '04

27 Jul '04

> Is there support for OpenSoundControl in chuck or any other way to > control it from an external program (in my case from Python)? OSC support is (like a ton of other stuff) in the works (it's not there, as n++k noted) - look for OSC in about 1 month (many other features/bugs coming first). So far there is only shred-level control from the outside via on-the-fly programming mechanisms. Several more internal interfaces are on the way as well, such as asynchronous I/O events and networking. > The documentation is a little bit sparse. Will this change anytime soon > or are you busy with writing code? Documentation is a big priority, when Perry and I return to Princeton (next week for me), there will be a significant doc update. > How stable does it run on Linux and what is the recommended platform? So far, I don't think it runs stable anywhere. (always fixing to make better though) We don't really have a recommended platform (we embrace/abhor all platforms!) > Are there any sound samples available? Only in the form of ChucK source examples so far. Audio examples may a good idea. Best, Ge! ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

4 8

ChucK wins open source software competition
by Ge Wang 27 Jul '04

27 Jul '04

Dear All, We are happy to announce that ChucK was recently selected as one of two winners in the ACM Multimedia 2004 open source software competition. Our co-winner is FLAVOR, an audio/visual object description language (quite different from a synthesis language, this is used for audio/video encoding and representation). In the past few weeks, we have been preparing the write-up to be presented at the conference in New York (October), full-time implementation is now resumed. A new release is coming with several new features (such as arrays), and GLucK graphics API will be released in the next month as well. ThanKs to all (72 right now on chuck list) for being part of this ChucK community, including all who have contributed code/bug fixes/questions/answers/ideas and those who are brave to try using ChucK so far! This award is truly for everyone here. => Let's keep ChucKing! Best, Perry and Ge!

1 0

Re: [chuck-dev] gain ugen segmentation fault
by Niklas Werner 12 Jul '04

12 Jul '04

On Mon, 12 Jul 2004 15:25, Matthew Shanley wrote: > Sorry for the delay, I had to go out of town for the weekend. > Program received signal SIG32, Real-time event 32. > 0x402f79f4 in pthread_getconcurrency () from /lib/libpthread.so.0 > > > Is this helpful? not really. You might want to type "where" or "bt" after the crash, as Nicolas already wrote... This shows the whole trace of the function calls leading to the crash. I can run your example without worries on my gentoo machine, btw. (ppc) random ideas: - recent compiler upgrade and glibc not re-emerged? - different compiler used for alsa/kernel and chuck? (c++ can be very bitchy about different binary interfaces...) Cheers, Niklas -- Computer Music PhD-student University of Waikato Hamilton New Zealand

2 1

RE: [chuck] Call for Developers
by Ge Wang 08 Jul '04

08 Jul '04

Hi Matthew! > What areas are most in need of help? I don't have any strong > desire to work in any specific area yet. It's great to have you with us. There are many "disaster zones" (ha) - it would be good for you to join the developer list: https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev > In the quickstart tutorial, the section that begins "Now, let's try > changing the frequency randomly every 100ms" contains the code: > ~ 400.0 * ( std.rand() + 1.0 ) => s.freq; > but std.rand() returns an integer, so the code wouldn't compile for > me until I changed it to: > ~ 400.0 * ( (float)std.rand() * 1.0 ) => s.freq; Ah, this was changed online but not in the QUICKSTART. This will be fixed in the next release to match the online: OLD: 400.0 * ( std.rand() + 1.0 ) => s.freq; NEW: std.rand2f( 30.0, 800.0 ) => s.freq; > When a command is sent to an existing chuck process, the program > sends you back to the command prompt, and then prints the output > saying it did it. This is the reverse of most programs, I don't > know if it's intentional or not. We thought about this, and have decided to keep it as it is for now - in this mode, you can background the looping ChucK VM, and then run the commands in the same shell, which works out (Perry uses this mode often). Another option, of course, is to have two shells visible when doing on-the-fly ChucKing... In the future, there will most likely be a command line flag to choose where/how to output messages. > Using the gain ugen in any way seems to cause segmentation faults. > (This includes the gain parameter built into other ugens). We tried this on both OS X (.2/.3), and ALSA under Redhat 9, but couldn't reproduce the crash (we don't have a machine running Gentoo). can you send me (gewang(a)cs.princeton.edu) the offending code (or post to chuck-dev)? This would be a good thing to figure out on the developer list. > Trying to using sndbuf gives me this error message: > *** Fatal error : sizeof (off_t) != sizeof (sf_count_t) > *** This means that libsndfile was not configured correctly. Aha, we are on it! Best, Ge!

1 0

version 1.1.4.3 released
by Ge Wang 04 Jul '04

04 Jul '04

Dear All, version 1.1.4.3 is out, with many large/small "improvements" http://chuck.cs.princeton.edu/ Thanks to all who contributed to this release - especially Phil, Ari, n++k! --- 1.1.4.3 - 2004.6.18 - add sndfile support (Ari Lazier) - add sndbuf file reading/writing (Ari Lazier) - add sinosc.sfreq and phase (Phil Davidson) - add sndbuf rate and sinc interp (Phil Davidson) - add cget functions for unit generators parameters (many parameters are readable now) - add .last for last sample computed for all ugen's - add constants in lib import - add math.pi math.twopi math.e - add --srate(N) in command line (chuck --help) - typing .ck extension optional on command line - fixed spork bug involved local variables - fixed nested function calls - fixed math.min/max bug (Phil Davidson) - fixed audio stability OS X (Ari Lazier) - fixed MidiOut issue (thanks to n++k) new Unit Generators (from STK) ADSR (updated) BiQuad Delay DelayA DelayL Echo WaveLoop (updated) Online documentation also includes new additions (thanks to Phil and Ari) Coming soon... - GLucK (OpenGL for chuck) - n++k midi modules - arrays! - more tutorials - visual studio support Happy ChucKing - let us know if things go bad! Best, Perry and Ge!

1 0