Spencer Salazar wrote:

That's a pretty baffling issue. Could you perhaps forward the console log output when starting the virtual machine in miniAudicle?

Sure. Seems clean to me... [chuck]:(2:SYSTEM): setting log level to: 2 (SYSTEM)... [chuck]:(2:SYSTEM): -------( Sat Nov 4 19:04:03 2006 )------- [chuck]:(2:SYSTEM): starting chuck virtual machine... [chuck]:(2:SYSTEM): | initializing virtual machine... [chuck]:(2:SYSTEM): | | behavior: LOOP [chuck]:(2:SYSTEM): | | allocating shreduler... [chuck]:(2:SYSTEM): | | allocating messaging buffers... [chuck]:(2:SYSTEM): | | real-time audio: YES [chuck]:(2:SYSTEM): | | mode: CALLBACK [chuck]:(2:SYSTEM): | | sample rate: 48000 [chuck]:(2:SYSTEM): | | buffer size: 512 [chuck]:(2:SYSTEM): | | num buffers: 8 [chuck]:(2:SYSTEM): | | devices adc: 0 dac: 0 (default 0) [chuck]:(2:SYSTEM): | | channels in: 2 out: 2 [chuck]:(2:SYSTEM): | initializing compiler... [chuck]:(2:SYSTEM): | type dependency resolution: MANUAL [chuck]:(2:SYSTEM): | initializing synthesis engine... [chuck]:(2:SYSTEM): | | initializing 'real-time' audio... [chuck]:(2:SYSTEM): running virtual machine... Another finding in blit.ck: If I remove the line ".5 => s.gain;" I get sound but no reverb. Maybe that's an additional clue to knowledgeable people... -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

Atte, Sincerest apologies on not getting back to you sooner... us princeton- ites were pretty swamped with ICMC madness this past week. To be honest, Im stumped. I guess it would be good to be absolutely certain that the exact same chuck that miniAudicle links to does not produce the same bugs. Additionally, try playing around with buffer sizes if you haven't already (miniAudicle accepts most of the same command line arguments as chuck, including --bufsize###). Also, do the same bugs pop up when you write the output to a file with WvOut? If it comes down to it I would be willing to do a remote debugging session to get a closer look at what might be going wrong, if you are up for that. spencer On Nov 12, 2006, at 2:25 AM, Atte André Jensen wrote:

Atte André Jensen wrote:

...

Spencer Salazar wrote:

...

That's a pretty baffling issue. Could you perhaps forward the console log output when starting the virtual machine in miniAudicle?

Sure. Seems clean to me...

Another finding in blit.ck: If I remove the line ".5 => s.gain;" I get sound but no reverb. Maybe that's an additional clue to knowledgeable people...

Any idea on this? Things I should try out?

-- peace, love & harmony Atte

http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/ compositions _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

Atte André Jensen wrote:

...

I guess it would be good to be absolutely certain that the exact same chuck that miniAudicle links to does not produce the same bugs.

It doesn't!

...

Additionally, try playing around with buffer sizes if you haven't already (miniAudicle accepts most of the same command line arguments as chuck, including --bufsize###). Also, do the same bugs pop up when you write the output to a file with WvOut?

I know I promised this before, but hopefully I'll find some time over the weekend to try out your suggestions. Right now I'm trying to prepare my first 100% chuck live gig sunday :-) -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

Hi, I compiled miniAudicle on Linux a few days ago and ran into the same issue (I think). I found a really weird problem: It seems that float numbers are truncated into integers in miniAudicle. I wrote a small program: SinOsc o => dac; 333 => o.freq; 0.9 => o.gain; <<>>; 1::second => now; 1 => o.gain; <<>>; 1::second => now; It works correct in chuck, the output is: i@Imre ~]/Depot/Install/miniAudicle-0.1.3.6/chuck/src/chuck --srate=48000 --bufsize=512 ./Temp/gain.ck 0.900000 :(float) 1.000000 :(float) But in miniAudicle console monitor I get: [chuck](VM): sporking incoming shred: 1 (gain.ck)... 0,000000 :(float) 1,000000 :(float) (and also I don't hear the first 1 second :) ) Buffer size and sample rate were the same as in the chuck command. I tried it also with the precompiled Windows version and there it is working correct. I hope this brings us closer to the solution! Imre 2006/11/18, Atte André Jensen :

Atte André Jensen wrote:

...

...

I guess it would be good to be absolutely certain that the exact same chuck that miniAudicle links to does not produce the same bugs.

It doesn't!

...

...

Additionally, try playing around with buffer sizes if you haven't already (miniAudicle accepts most of the same command line arguments as chuck, including --bufsize###). Also, do the same bugs pop up when you write the output to a file with WvOut?

I know I promised this before, but hopefully I'll find some time over the weekend to try out your suggestions. Right now I'm trying to prepare my first 100% chuck live gig sunday :-)

-- peace, love & harmony Atte

http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

Spencer Salazar wrote:

First apply the attached patch (cd miniAudicle-0.1.3.6; patch

Shouldn't this be a part of miniAudicle in the future? Seems like a cool feature to me...

Recompile. Then try adding shreds through command line chuck. Whether or not the ChucK program runs as expected will helps us determine where the problem lies.

Well everything looks just fine, both in the console... [chuck]:(2:SYSTEM): setting log level to: 2 (SYSTEM)... [chuck]:(2:SYSTEM): -------( Tue Nov 21 09:44:54 2006 )------- [chuck]:(2:SYSTEM): starting chuck virtual machine... [chuck]:(2:SYSTEM): | initializing virtual machine... [chuck]:(2:SYSTEM): | | behavior: LOOP [chuck]:(2:SYSTEM): | | allocating shreduler... [chuck]:(2:SYSTEM): | | allocating messaging buffers... [chuck]:(2:SYSTEM): | | real-time audio: YES [chuck]:(2:SYSTEM): | | mode: CALLBACK [chuck]:(2:SYSTEM): | | sample rate: 48000 [chuck]:(2:SYSTEM): | | buffer size: 512 [chuck]:(2:SYSTEM): | | num buffers: 8 [chuck]:(2:SYSTEM): | | devices adc: 0 dac: 0 (default 0) [chuck]:(2:SYSTEM): | | channels in: 2 out: 2 [chuck]:(2:SYSTEM): | initializing compiler... [chuck]:(2:SYSTEM): | type dependency resolution: MANUAL [chuck]:(2:SYSTEM): | initializing synthesis engine... [chuck]:(2:SYSTEM): | | initializing 'real-time' audio... [chuck]:(2:SYSTEM): running virtual machine... [chuck](VM): sporking incoming shred: 1 (blit.ck)... [chuck](VM): sporking incoming shred: 2 (wind.ck)... [chuck](VM): sporking incoming shred: 3 (larry.ck)... [chuck](VM): sporking incoming shred: 4 (larry++.ck)... [chuck](VM): sporking incoming shred: 5 (tick.ck)... tick: 94,581333 seconds tick: 95,581333 seconds tick: 96,581333 seconds tick: 97,581333 seconds tick: 98,581333 seconds tick: 99,581333 seconds tick: 100,581333 seconds tick: 101,581333 seconds tick: 102,581333 seconds tick: 103,581333 seconds [chuck](VM): sporking incoming shred: 6 (fm2.ck)... tick: 104,581333 seconds tick: 105,581333 seconds tick: 106,581333 seconds tick: 107,581333 seconds tick: 108,581333 seconds tick: 109,581333 seconds ...and no error messages from chuck. However of the above, only fm2.ck actually made any sound... -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

Hi, I use the linux-oss target, but tried to apply the same change also in makefile.oss (change order of -l flags) and recompiled (only rebuilt the miniAudicle executable). It seems it doesn't make any difference (on my machine). Now I tried the following program: 1.9 => float d; d * 2.0 => float c; <<<d>>>; <<<c>>>; The output is in the console monitor: [chuck](VM): sporking incoming shred: 1 (floatv.ck)... 1,000000 :(float) 2,000000 :(float) This means digits after the decimal point get lost before (or at) the ChucK operator, but not during the printout. How is this possible??? Imre 2006/11/22, Spencer Salazar :

Hi Atte, Thanks for trying this out.

On Nov 21, 2006, at 3:59 AM, Atte André Jensen wrote:

...

Spencer Salazar wrote:

...

First apply the attached patch (cd miniAudicle-0.1.3.6; patch

Shouldn't this be a part of miniAudicle in the future? Seems like a cool feature to me...

Yep, definitely. Actually it was a part of miniAudicle in the past, but it was disabled until we could introduce an easy way of turning it on and off (as it could present a security threat to one's system if they don't know its there).

...

...

Recompile. Then try adding shreds through command line chuck. Whether or not the ChucK program runs as expected will helps us determine where the problem lies.

Well everything looks just fine, both in the console...

[...]

...and no error messages from chuck. However of the above, only fm2.ck actually made any sound...

Okay. That narrows it down a little bit, now I can see that its a problem with the chuck side of miniAudicle rather than the miniAudicle side (of miniAudicle). Just as a hunch, please try the attached patch + recompile if you have the opportunity. Ill investigate further to see what I can turn up.

thanks, spencer

...

-- peace, love & harmony Atte

http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/ compositions _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

Atte, Imre, Argh, I am terribly sorry that you guys have been afflicted with these problems. Here is my line of thought. Since miniAudicle is using the exact same chuck source as command line chuck, the problem is probably not with the source. Maybe its a problem with the linked libraries. The only difference between chuck's libraries and miniAudicle's libraries is the `wx-config --libs stc,adv,core,base` part. So a next step would be to append `wx-config --libs stc,adv,core,base` to the LIBS line of makefile.oss/makefile.alsa in chuck, and see if that messes up chuck like miniAudicle. If it does mess chuck up, the next step is to figure out what part of `wx-config --libs stc,adv,core,base` is causing the problem. Just executing wx-config --libs stc,adv,core,base should print out whatever linker directives wxWidgets is having us invoke. Taking each one individually, appending it to the LIBS line of the appropriate chuck makefile, and testing the resulting chuck binary should eventually lead to the problematic linker directive. Anyways, if you haven't completely given up on this, those are some more ideas to try. thanks, spencer On Nov 22, 2006, at 4:59 PM, Atte André Jensen wrote:

Spencer Salazar wrote:

...

Just as a hunch, please try the attached patch + recompile if you have the opportunity.

It doesn't seem to behave any different than before. fm2.ck sounds most others not. Doesn't matter if added from commandline (chuck + bla.ck) or from within miniaudicle...

-- peace, love & harmony Atte

http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/ compositions _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

Imre Kéri wrote:

This has to do with some "locale" stuff! I just typed "export LC_ALL="C"" in the terminal before starting miniAudicle and this way it is working! I think that some code in wxWidgets or miniAudicle does mess around with the locale setting of chuck and makes the lex parser think that the decimal separator is "," and not ".".

Sounds very promissing. What do you say Spencer, do you still need me to try your suggestion?? -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

Spencer Salazar wrote:

Atte, if this patch and/or export LC_ALL="C" fix the problem for you, you probably don't need to try my other suggestion.

It works! I now have sound in all the examples I tried that didn't work before. Will report back when I've been using it some more. Thanks both Imre and Spencer! -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

Hi, This patch (masl.patch) also works for me. Imre Atte André Jensen wrote:

...

It works!

To be more clear: miniAudicle now produces sound when I have the "listen for incomming sporks" (just applied it because I like the feature) + the latest "masl.patch" applied. Didn't change anything related to locales on my system...

Yes, definitely, I actually just committed it to the CVS repository a few minutes ago. spencer On Dec 1, 2006, at 5:11 PM, Atte André Jensen wrote:

Atte André Jensen wrote:

...

Atte André Jensen wrote:

...

It works!

I take it that this patch (masl.patch) is integrated into the future source of miniAudicle?

-- peace, love & harmony Atte

http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/ compositions _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users