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

kilo-shred crashing!
by Kassen 02 Apr '07

02 Apr '07

Hi list! I think I ran into a new sort of issue. I thought I'd dabble a little in spatialisation and the technique I blundered into (invented is a rather large word) involves dealing with timing and modulation by generating a rather large amount of shreds that wait for some period of time, then write to a variable, then die. I'd write about it more but right now it's not so interesting because of being untested. Anyway, this made me generate quite a few shreds (some tens of thousands but I'd like to use hundreds of thousands eventually for multiple soundsources and channels and so on....). For this I thought it wise to render in non-real time (cough). Sadly it turns out that ChucK doesn't realy like this. On my laptop it simply crashed the whole computer (which then proceeded to turn itself off) on my GF's (also xp) computer it reports a "out of memory" issue with three rather odd characters (a Y with a dash on it amongst them). After that the computer had to be reset anyway but this one is tempramental in ways we can't blame on ChucK. I could try on my Debian box in a few days. So... now what? Are kilo-shreds simply a area one shouldn't venture into? I think I'm of the opinion that ChucK running in --silent mode should simply allocate more memory and time untill the swap (or one's patience) runs out but frankly I can't imagine that would happen over a test-file of a second and 15,000 or so (according to the mini before it gave up) shreds. Yours, Kas.

2 2

ckx files ?
by Lukas Degener 02 Apr '07

02 Apr '07

Hi list, I have just implemented my first simple test class in C and I had no problem linking it statically into the chuck executable and importing it (by adding a couple of lines to chuck_compile.cpp. But this is probably not the intended / most elegant way of deploying contributions :-) I read about ckx files in the developer's guide http://chuck.cs.princeton.edu/doc/develop/ Sounds like "The Way" (tm). so... any additional api/compiler flags needed to create those ckx files? how do I load them from within chuck? Could you point me to some examples? Thanks, --lu

2 1

Assertion `m_offset < obj->vtable->funcs.size()' failed.
by Lukas Degener 02 Apr '07

02 Apr '07

Hi, can anybody can tell me what might cause this error message? chuck: chuck_instr.cpp:3669: virtual void Chuck_Instr_Dot_Member_Func::execute(Chuck_VM*, Chuck_VM_Shred*): Assertion `m_offset < obj->vtable->funcs.size()' failed. I tracked it down to this piece of code: public OscEvent getOscEvent(OscRecv r){ <<<"enter FloatParam::getOscEvent">>>; r.event(id+"/value, f") @=> OscEvent e; <<<"exit FloatParam::getOscEvent">>>; return e; } The second message is never displayed. Any ideas? TIA + Best Regards, --lu

2 2

(FtRq) warn on missing return statement.
by Lukas Degener 01 Apr '07

01 Apr '07

Hi, just a detail: It would be great if chuck could produce a compile time error when a method that is declared with a return type other than "void" contains an execution path that does NOT end with a return statement. No vital requirement, just a suggestion. Cheers, --lu

2 1

OOP and Style Qs
by Veli-Pekka Tätilä 29 Mar '07

29 Mar '07

Hi, I have a number of relatively newbie Qs on my first-ever ChucK class I've written. the good thing is that it works, although it sounds pretty horrible. The bad thing is that I wish the ChucK language would have more features and might have discovered a bug related to null pointers. My idea in this class is to emulate the functionality of the various audio and event switch modules as well as the audio relay module in Reaktor. That is n inputs and one output such that you can select which input is patched to the output at any given time. The questions are: 1. Is the code in the class OK in terms of style and implementation i.e. is there something highly uncanonical in naming or some things that could be done smarter for such a simple thing? - In particular, I'm not sure if the gain module is needed in the output. - Is there a better way to grow the array on demand? In Perl I can just assign to higher indeces and it will grow, or use the push function to add an arbitraryly sized list at the end. And Java has array lists, too. - ALso in the test script, I would like to initialize my UGen array anonymously without having to make up variable names for each object and manully assign the indeces, I'm lazy I guess. - Is there a style manual for ChucK? Until we can inherit from UGen it would be great to have a common set of method names for UGen like modules. Currently I've drawn my influences from Java and Dinky.ck. - I've noticed that the names for most chuck properties are extremely short, for example. - Which reminds me, does chucK support duck typing? Abstractly put, Suppose a class or interface c with the method name m and an object o such that not o instanceof c. Does o.m() get called in its own class, even if o is not related to c by inheritance. Polymorphism that works based on a name is there in Perl and Python, I think, where as Java is stricter and requires that the object be a subclass or interface implementation of c, a common method name is not good enough. 2. How is ChucK naming like? Suppose we have a parameter p of type t. I would like to create its accessors as: - function void p(t i); // set function t p(); // get Yet although chucK supports overloading functions, it does not let them differ only by return type, right? In a test class I get stuff like: [test.ck]:line(5): function signatures differ in return type... The same thing with JAva really and I do understand it could often be ambiguous. Perl is one of the few languages in which this works well as scalar is the only primitive scalar type and it has list and void context to make things more or less unambiguous. But ChucK is not Perl, nough said. - As I think parameters with the verbs get and set are slightly redundant, if boolean stuff starts with e.g. is , I thought I would use: function t p(); function setP(t i); However, if there is already a data member named p chucK does not let me hav a member function named p in the same class, right? After modding my test class, I got: [test.ck]:line(4): function name 'p' is already used by another value 3. To save some duplicated code, and as there's no constructor support, it occurred to me I could write a function that given an array of UGens, instanciates my audio switch (OneOfN), populates it and returns a reference. Yet if I paste this at the top of my test script and try to run it ChucK claims UGen doesn't have the caps method, even though printing out the function argument says it is of type UGen[], that is an array. What might be wrong, i.e. why does it think an array of UGen is just a UGen rather than an array? I'm mightily confused here. The code: // Partially untested. function OneOfN newOneOfN(UGen choices[]) { // A pseudo-constructor for populating instances of OneOfN given an array. OneOfN selector; choices.caps() => int max; // Cache it, so only one method call. selector.setInputCount(max); for(0 => int i; i < max; ++i) selector.setInputAt(i, choices[i]); if(max > 0) // Array not empty. selector.selectInput(0); return selector; } // function 4. When I use my audio switch to determine whether audio flows through, i.e. as an audio relay one of whose inputs is practically disconnected (I've patched blackhole there), it seems to work OK i.e. I get the sound of silence when expected. However, if I change my array initializer in OneOfN.ck: from: blackhole @=> newIn[i]; // Not connected initially. to null @=> newIn[i]; // Not connected initially. Strange things start to happen. I don't get a null pointer exception at runtime as I would expect in my test script, as the unconnected input is actually null. In stead ChucK crashes spectacularly with the standard WIndows XP dialog about it. This happens at runtime, when the disconnected input is picked the first time. ChucK reports the version as: C:\audio\CHUCK-~1.7-E\bin>chuck.exe --version chuck version: 1.2.0.7b (dracula) exe target: microsoft win32 http://chuck.cs.princeton.edu/ [Speaking of Dracula, I'm just reading Frankenstein, talk about funny co-incidences. Hmm what's the code name for the next release?] I think these were my questions. As I tend to have a bad habbit of asking all too much, when someone who knows far more than I do is around, I'd actually be pleased if even half of these would get answered eventually, <smile>. And now finally the code: public class OneOfN { // A parameterizable audio multiplexer (switch). Todo: write user docs, -1 => int n; // Initially invalid. UGen in[]; Gain out; // Neede some Ugen for producing output? function void connect(UGen output) { out => output; } function void setInputAt(int i, UGen u) { u @=> in[i]; } function UGen getInputAt(int i) { return in[i]; } function UGen getOutput() { return out; } function int getSelectedInput() { return n; } function int getInputCount() { return in.cap(); } function void setSelectedInput(int i) { if(n > -1) in[n] =< out; // Disconnect only if size already set. i => n; // We have a new output. in[n] => out; } // function function void setInputCount(int newSize) { // Changes the size of the input array to accommodate that many inputs. UGen newIn[newSize]; for(0 => int i; i < newSize; ++i) blackhole @=> newIn[i]; // Not connected initially. newIn @=> in; // Not garbage collected, there's one ref left. } // function } // class And now the test script called patch.ck: I run it by saying C:\audio\CHUCK-~1.7-E\code>..\bin\chuck.exe OneOfN.ck patch.ck The code: // Use the switch to select one input and save CPU. OneOfN oscSelect; UGen @oscs[3]; // Our oscs. SinOsc o1 @=> oscs[0]; SawOsc o2 @=> oscs[1]; SqrOsc o3 @=> oscs[2]; oscSelect.setInputCount(oscs.cap()); // Tweak the gains to make an audible difference. for(0 => int i; i < oscs.cap(); ++i) { oscs[i].gain(1.0 / (i + 1)); // Avoid divide by 0! oscSelect.setInputAt(i, oscs[i]); } // for // Use the switch as an audio relay and do the patching. OneOfN audioRelay; audioRelay.setInputCount(2); // 1 real, 1 empty. audioRelay.setInputAt(0, oscSelect.getOutput()); audioRelay.connect(dac); // Times, they keep on changing. for(0 => int i; true; ++i) { Math.rand2(-10, 10) => int chance; oscSelect.setSelectedInput(i % oscs.cap()); // CYcle waveform. audioRelay.setSelectedInput(chance < 5 ? 0 : 1); // 1 is connected to GND0. 50::ms => now; } // for -- With kind regards Veli-Pekka Tätilä (vtatila(a)mail.student.oulu.fi) Accessibility, game music, synthesizers and programming: http://www.student.oulu.fi/~vtatila/

3 8

questions on osc, events and multi-shredding
by Lukas Degener 29 Mar '07

29 Mar '07

Hi List, Do I understand this correctly that I have to create an OscEvent for every single OSC method I want to listen for? The docs say I can use any valid OSC address pattern, but this does not seem to work. I have attached a (stupid) program that demonstrates the problem. So I need a separate shred for each OSC method? Which brings me to another thing I was wondering about lately: A shred can not wait for more than one event (including time passage) at the same time. So in many situtations, I will have no choice but to either do polling on a set of conditions, or create a separate shred for each event I am interested in. But this could be quite a large (theoretically infinit) number of shreds. Until now, I decided to use polling, but I was wondering if there was some kind of "proven pattern" that could be employed in such situations. What is the overhead of a shred anyway? Would it be a problem to create a *lot* of them? Like - let's say - a couple of thousands? From some primitive experiments, it seems that the creation involves some noticeable overhead, but I already had thousands of them running (well, mostly idle) without any problem. Are there any upper bounds? Otoh, is it a good idea to do polling in very short intervals, like the duration of one frame? Sorry, lots of questions. :-) Best Regards, --lu fun int sender(){ OscSend xmit; xmit.setHost("localhost",6449); while(true){ now + 1000::ms => now; xmit.startMsg("/test/bla", "i s"); 42 => xmit.addInt; "knarz" => xmit.addString; } } spork ~ sender(); OscRecv orec; 6449 => orec.port; orec.listen(); orec.event("/test/*, i s") @=> OscEvent e; while(true){ e => now; e.nextMsg(); <<<"event recieved!">>>; }

4 5

Delay gone missing? (and acoustics)
by Kassen 29 Mar '07

29 Mar '07

Hi, list! I seem to somehow remember we used to have a "variable write" delay but I can't seem to find it anymore. Am I overlooking it? Was it axed? (I think it was rather experimental). Yours, Kas.

2 2

Fwd: Re: miniAudicle version 0.1.3.7 no joy... compile error...
by Vince Werber 25 Mar '07

25 Mar '07

HI Spencer, I tried your code on the compile and it seems to have bailed with the same errors as before. I do have wxGTK-2.4 on this system... Perhaps we need a different version? Also I build everything from souce I'll have to check my logs to see if I compiled the wxGTK with my current GCC... just in case :-) later vince output below. -------------------------------------------------------------- root@crypto5:/miniAudicle-0.1.3.7# make clean; WX_OPTIONS=-toolkit=gtk2 make linux-alsa rm -rf *.o wxw/*.o wxw/miniAudicle wxw/miniAudicle.exe macosx/*.o macosx/miniAudicle.app make -f makefile.alsa make[1]: Entering directory `/miniAudicle-0.1.3.7' gcc -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config -toolkit=gtk2 --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.7 miniAudicle.cpp gcc -o wxw/mAParentFrame.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config -toolkit=gtk2 --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.7 wxw/mAParentFrame.cpp gcc -o wxw/mADocument.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config -toolkit=gtk2 --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.7 wxw/mADocument.cpp gcc -o wxw/mAView.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config -toolkit=gtk2 --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.7 wxw/mAView.cpp gcc -o wxw/mAVMMonitor.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config -toolkit=gtk2 --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.7 wxw/mAVMMonitor.cpp gcc -o wxw/mAMenuBar.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config -toolkit=gtk2 --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.7 wxw/mAMenuBar.cpp gcc -o wxw/mAConsoleMonitor.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config -toolkit=gtk2 --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.7 wxw/mAConsoleMonitor.cpp gcc -o wxw/mAConfig.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config -toolkit=gtk2 --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.7 wxw/mAConfig.cpp gcc -o wxw/mAPreferencesWindow.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config -toolkit=gtk2 --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.7 wxw/mAPreferencesWindow.cpp gcc -o wxw/mAUIElements.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config -toolkit=gtk2 --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.7 wxw/mAUIElements.cpp In file included from wxw/mAUIElements.cpp:44: /usr/local/include/wx-2.8/wx/tglbtn.h:31:32: wx/univ/tglbtn.h: No such file or directory wxw/mAUIElements.cpp: In member function `virtual void UI::mAUIElement::SetSize(wxCommandEvent&)': wxw/mAUIElements.cpp:130: warning: passing `double' for converting 1 of `void wxWindowBase::SetClientSize(int, int)' wxw/mAUIElements.cpp:130: warning: passing `double' for converting 2 of `void wxWindowBase::SetClientSize(int, int)' wxw/mAUIElements.cpp: In member function `virtual void UI::mAUIElement::SetPosition(wxCommandEvent&)': wxw/mAUIElements.cpp:137: warning: converting to `int' from `double' wxw/mAUIElements.cpp:137: warning: converting to `int' from `double' wxw/mAUIElements.cpp: In member function `virtual void UI::mAUISlider::SetSize(wxCommandEvent&)': wxw/mAUIElements.cpp:435: warning: passing `double' for converting 1 of `void wxWindowBase::SetSize(int, int)' wxw/mAUIElements.cpp:435: warning: passing `double' for converting 2 of `void wxWindowBase::SetSize(int, int)' wxw/mAUIElements.cpp:438: warning: passing `double' for converting 1 of `void wxWindowBase::Move(int, int, int)' wxw/mAUIElements.cpp:438: warning: passing `double' for converting 2 of `void wxWindowBase::Move(int, int, int)' wxw/mAUIElements.cpp:441: warning: passing `double' for converting 1 of `void wxWindowBase::SetSize(int, int)' wxw/mAUIElements.cpp:441: warning: passing `double' for converting 2 of `void wxWindowBase::SetSize(int, int)' wxw/mAUIElements.cpp:443: warning: passing `double' for converting 1 of `void wxWindowBase::Move(int, int, int)' wxw/mAUIElements.cpp:443: warning: passing `double' for converting 2 of `void wxWindowBase::Move(int, int, int)' wxw/mAUIElements.cpp:446: warning: passing `double' for converting 1 of `void wxWindowBase::SetSize(int, int)' wxw/mAUIElements.cpp:446: warning: passing `double' for converting 2 of `void wxWindowBase::SetSize(int, int)' wxw/mAUIElements.cpp:450: warning: passing `double' for converting 2 of `wxSize::wxSize(int, int)' wxw/mAUIElements.cpp:450: warning: `SetBestFittingSize' is deprecated (declared at /usr/local/include/wx-2.8/wx/window.h:1410) wxw/mAUIElements.cpp:452: warning: passing `double' for converting 1 of `void wxWindowBase::Move(int, int, int)' wxw/mAUIElements.cpp:452: warning: passing `double' for converting 2 of `void wxWindowBase::Move(int, int, int)' wxw/mAUIElements.cpp: At global scope: wxw/mAUIElements.cpp:793: error: ISO C++ forbids declaration of `wxToggleButton' with no type wxw/mAUIElements.cpp:793: error: expected `;' before '*' token wxw/mAUIElements.cpp: In constructor `UI::mAUIButton::mAUIButton()': wxw/mAUIElements.cpp:671: error: `toggle' was not declared in this scope wxw/mAUIElements.cpp: In member function `virtual void UI::mAUIButton::SetSize(wxCommandEvent&)': wxw/mAUIElements.cpp:688: warning: passing `double' for converting 1 of `void wxWindowBase::SetSize(int, int)' wxw/mAUIElements.cpp:688: warning: passing `double' for converting 2 of `void wxWindowBase::SetSize(int, int)' wxw/mAUIElements.cpp:690: warning: passing `double' for converting 1 of `void wxWindowBase::Move(int, int, int)' wxw/mAUIElements.cpp:690: warning: passing `double' for converting 2 of `void wxWindowBase::Move(int, int, int)' wxw/mAUIElements.cpp:692: warning: passing `double' for converting 1 of `void wxWindowBase::SetSize(int, int)' wxw/mAUIElements.cpp:692: warning: passing `double' for converting 2 of `void wxWindowBase::SetSize(int, int)' wxw/mAUIElements.cpp: In member function `virtual void UI::mAUIButton::SetState(wxCommandEvent&)': wxw/mAUIElements.cpp:739: error: `toggle' was not declared in this scope wxw/mAUIElements.cpp: In member function `virtual void UI::mAUIButton::SetActionType(wxCommandEvent&)': wxw/mAUIElements.cpp:748: error: `toggle' was not declared in this scope wxw/mAUIElements.cpp:773: error: `wxToggleButton' has not been declared make[1]: *** [wxw/mAUIElements.o] Error 1 make[1]: Leaving directory `/miniAudicle-0.1.3.7' make: [linux-alsa] Error 2 (ignored) root@crypto5:/miniAudicle-0.1.3.7# ---------- Forwarded Message ---------- Subject: Re: miniAudicle version 0.1.3.7 no joy... compile error... Date: Thursday 22 March 2007 22:40 From: Spencer Salazar <ssalazar(a)cs.princeton.edu> To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> Cc: Vince Werber <ka1iic(a)prexar.com> Hey Vince, No worries! Hopefully we can solve this and get it going for you soon. Thanks for trying this out so soon after the release. It looks like we got past the previous error you were having, which is good (I did include a specific fix for that in this release, so apparently it worked). It looks like you are using a wxUniversal build--this isn't explicitly supported, but only in the sense that I have never tried building miniAudicle with wxUniversal. If you also happen have wxGTK on your system, you might want to try forcing miniAudicle to use that by entering: make clean; WX_OPTIONS='--toolkit=gtk2' make linux-alsa in the miniAudicle-0.1.3.7 directory. If you don't have or don't like wxGTK, then thats okay too, as it should be pretty easy for me to whip up a quick patch to the current miniAudicle source that would be wxUniversal-compatible. Also, I've pulled this discussion over to the chuck-users list, on the sudden whim that audicle list subscribers are probably interested only in audicle specifically, whereas chuck-users subscribers are (theoretically) interested in both ChucK specifically and general ChucK issues, including miniAudicle. (Thus contradicting on my previous statement that miniAudicle problems could go to either list. I suppose it could go either way still but chuck-users is probably the preferred way to go as of now.) spencer On Mar 22, 2007, at 2:37 AM, Vince Werber wrote: > Hi all, > > No joy .... > > I'm getting to be a real pain and probably about to be voted the > 'Zippy the > Pin Head' award but here's my latest... > > Slackware Linux version 11.0 > Kernel 2.4.33.3 > GCC version 3.4.6 > > have a good day in spite of me Please ;-}> > > vince in Maine > p.s. IF THERE IS NO "Zippy' award you might want to consider it > <heh> <running > for cover> >>>-------------->X-[ I shot an arrow in the > air, it > fell to earth... oh my that smarts<heh> > > Complete compile output below: > ----------------------------------------------------------------- > > root@crypto5:/miniAudicle-0.1.3.7# clear > root@crypto5:/miniAudicle-0.1.3.7# make linux-alsa > make: Warning: File `makefile' has modification time 4.8e+03 s in > the future > make -f makefile.alsa > make[1]: Entering directory `/miniAudicle-0.1.3.7' > make[1]: Warning: File `makefile.alsa' has modification time 4.8e > +03 s in the > future > gcc -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ > `wx-config --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src - > Iwxw -I/miniAudicle-0.1.3.7 > miniAudicle.cpp > gcc -o wxw/mAParentFrame.o -D__LINUX_ALSA__ -D__LINUX__ - > D__MA_WXWIDGETS__ > `wx-config --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src - > Iwxw -I/miniAudicle-0.1.3.7 > wxw/mAParentFrame.cpp > gcc -o wxw/mADocument.o -D__LINUX_ALSA__ -D__LINUX__ - > D__MA_WXWIDGETS__ > `wx-config --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src - > Iwxw -I/miniAudicle-0.1.3.7 > wxw/mADocument.cpp > gcc -o wxw/mAView.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ > `wx-config --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src - > Iwxw -I/miniAudicle-0.1.3.7 > wxw/mAView.cpp > gcc -o wxw/mAVMMonitor.o -D__LINUX_ALSA__ -D__LINUX__ - > D__MA_WXWIDGETS__ > `wx-config --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src - > Iwxw -I/miniAudicle-0.1.3.7 > wxw/mAVMMonitor.cpp > gcc -o wxw/mAMenuBar.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ > `wx-config --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src - > Iwxw -I/miniAudicle-0.1.3.7 > wxw/mAMenuBar.cpp > gcc -o wxw/mAConsoleMonitor.o -D__LINUX_ALSA__ -D__LINUX__ - > D__MA_WXWIDGETS__ > `wx-config --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src - > Iwxw -I/miniAudicle-0.1.3.7 > wxw/mAConsoleMonitor.cpp > gcc -o wxw/mAConfig.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ > `wx-config --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src - > Iwxw -I/miniAudicle-0.1.3.7 > wxw/mAConfig.cpp > gcc -o > wxw/mAPreferencesWindow.o -D__LINUX_ALSA__ -D__LINUX__ - > D__MA_WXWIDGETS__ > `wx-config --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src - > Iwxw -I/miniAudicle-0.1.3.7 > wxw/mAPreferencesWindow.cpp > gcc -o wxw/mAUIElements.o -D__LINUX_ALSA__ -D__LINUX__ - > D__MA_WXWIDGETS__ > `wx-config --cppflags` -O3 -c -D__CK_SNDFILE_NATIVE__ -Ichuck/src - > Iwxw -I/miniAudicle-0.1.3.7 > wxw/mAUIElements.cpp > In file included from wxw/mAUIElements.cpp:44: > /usr/local/include/wx-2.8/wx/tglbtn.h:31:32: wx/univ/tglbtn.h: No > such file or > directory > wxw/mAUIElements.cpp: In member function `virtual void > UI::mAUIElement::SetSize(wxCommandEvent&)': > wxw/mAUIElements.cpp:130: warning: passing `double' for converting > 1 of `void > wxWindowBase::SetClientSize(int, int)' > wxw/mAUIElements.cpp:130: warning: passing `double' for converting > 2 of `void > wxWindowBase::SetClientSize(int, int)' > wxw/mAUIElements.cpp: In member function `virtual void > UI::mAUIElement::SetPosition(wxCommandEvent&)': > wxw/mAUIElements.cpp:137: warning: converting to `int' from `double' > wxw/mAUIElements.cpp:137: warning: converting to `int' from `double' > wxw/mAUIElements.cpp: In member function `virtual void > UI::mAUISlider::SetSize(wxCommandEvent&)': > wxw/mAUIElements.cpp:435: warning: passing `double' for converting > 1 of `void > wxWindowBase::SetSize(int, int)' > wxw/mAUIElements.cpp:435: warning: passing `double' for converting > 2 of `void > wxWindowBase::SetSize(int, int)' > wxw/mAUIElements.cpp:438: warning: passing `double' for converting > 1 of `void > wxWindowBase::Move(int, int, int)' > wxw/mAUIElements.cpp:438: warning: passing `double' for converting > 2 of `void > wxWindowBase::Move(int, int, int)' > wxw/mAUIElements.cpp:441: warning: passing `double' for converting > 1 of `void > wxWindowBase::SetSize(int, int)' > wxw/mAUIElements.cpp:441: warning: passing `double' for converting > 2 of `void > wxWindowBase::SetSize(int, int)' > wxw/mAUIElements.cpp:443: warning: passing `double' for converting > 1 of `void > wxWindowBase::Move(int, int, int)' > wxw/mAUIElements.cpp:443: warning: passing `double' for converting > 2 of `void > wxWindowBase::Move(int, int, int)' > wxw/mAUIElements.cpp:446: warning: passing `double' for converting > 1 of `void > wxWindowBase::SetSize(int, int)' > wxw/mAUIElements.cpp:446: warning: passing `double' for converting > 2 of `void > wxWindowBase::SetSize(int, int)' > wxw/mAUIElements.cpp:450: warning: passing `double' for converting > 2 of > `wxSize::wxSize(int, int)' > wxw/mAUIElements.cpp:450: warning: `SetBestFittingSize' is deprecated > (declared at /usr/local/include/wx-2.8/wx/window.h:1410) > wxw/mAUIElements.cpp:452: warning: passing `double' for converting > 1 of `void > wxWindowBase::Move(int, int, int)' > wxw/mAUIElements.cpp:452: warning: passing `double' for converting > 2 of `void > wxWindowBase::Move(int, int, int)' > wxw/mAUIElements.cpp: At global scope: > wxw/mAUIElements.cpp:793: error: ISO C++ forbids declaration of > `wxToggleButton' with no type > wxw/mAUIElements.cpp:793: error: expected `;' before '*' token > wxw/mAUIElements.cpp: In constructor `UI::mAUIButton::mAUIButton()': > wxw/mAUIElements.cpp:671: error: `toggle' was not declared in this > scope > wxw/mAUIElements.cpp: In member function `virtual void > UI::mAUIButton::SetSize(wxCommandEvent&)': > wxw/mAUIElements.cpp:688: warning: passing `double' for converting > 1 of `void > wxWindowBase::SetSize(int, int)' > wxw/mAUIElements.cpp:688: warning: passing `double' for converting > 2 of `void > wxWindowBase::SetSize(int, int)' > wxw/mAUIElements.cpp:690: warning: passing `double' for converting > 1 of `void > wxWindowBase::Move(int, int, int)' > wxw/mAUIElements.cpp:690: warning: passing `double' for converting > 2 of `void > wxWindowBase::Move(int, int, int)' > wxw/mAUIElements.cpp:692: warning: passing `double' for converting > 1 of `void > wxWindowBase::SetSize(int, int)' > wxw/mAUIElements.cpp:692: warning: passing `double' for converting > 2 of `void > wxWindowBase::SetSize(int, int)' > wxw/mAUIElements.cpp: In member function `virtual void > UI::mAUIButton::SetState(wxCommandEvent&)': > wxw/mAUIElements.cpp:739: error: `toggle' was not declared in this > scope > wxw/mAUIElements.cpp: In member function `virtual void > UI::mAUIButton::SetActionType(wxCommandEvent&)': > wxw/mAUIElements.cpp:748: error: `toggle' was not declared in this > scope > wxw/mAUIElements.cpp:773: error: `wxToggleButton' has not been > declared > make[1]: *** [wxw/mAUIElements.o] Error 1 > make[1]: Leaving directory `/miniAudicle-0.1.3.7' > make: [linux-alsa] Error 2 (ignored) > make: warning: Clock skew detected. Your build may be incomplete. > root@crypto5:/miniAudicle-0.1.3.7# > _______________________________________________ > audicle mailing list > audicle(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/audicle -------------------------------------------------------

2 3

Using LiSa w/o recording?
by Lukas Degener 24 Mar '07

24 Mar '07

Hi List, I am playing around with the LiSa ugen and I am wondering: Is there any way to get data into it other than recording it (in realtime)? E.g. by loading a wav-file, or copying an existing Buffer? Please forgive me if I am overlooking something obvious :-) I am rather new to ChucK. TIA + Kind Regards, --lu

2 3

compiling miniAudicle 0.1.3.7 on x86_64
by Lukas Degener 23 Mar '07

23 Mar '07

Hi, hope I found the right list :-) Compiling miniAudicle on my computer (ubuntu 6.10, x86_64, using jack for audio) showed me the following error: wxw/mAPreferencesWindow.cpp:830: error: cast from 'void*' to 'int' loses precision wxw/mAPreferencesWindow.cpp:839: error: cast from 'void*' to 'int' loses precision wxw/mAPreferencesWindow.cpp:848: error: cast from 'void*' to 'int' loses precision wxw/mAPreferencesWindow.cpp:857: error: cast from 'void*' to 'int' loses precision wxw/mAPreferencesWindow.cpp:866: error: cast from 'void*' to 'int' loses precision wxw/mAPreferencesWindow.cpp:875: error: cast from 'void*' to 'int' loses precision Hm... looks familiar. I changed the "int"s to "long"s and now it seems to work. But probably it would be a better idea to not hard-wire this in the first place? Some preprocessor switch maybe? Sorry, I'm not fluent with C/C++ ... Yet another hm... Chuck segfaults whenever I try to start some shred. So I guess it's just not working (yet) in a 64bit environment? Cheers, --lu

2 2