Re: [chuck-users] Multi-channel weirdness (mike clew)
what does chuck —probe print out? Maybe you’re connecting to the wrong dac?? For reference, here’s an invocation script I used last time I did a multichannel performance: chuck -c8 -bufsize2048 -in2 --dac1 --adc0 INIT.ck That would have been an older version of chuck, but it worked then. PRC
From: mike clemow
To: ChucK Users Mailing List Hi folks,
Been a while, hope everyone is safe.
I'm experiencing something very strange and feel I must be doing something wrong. (MacOS 10.14.6)
Running chuck on command line like this:
$ chuck --dac7 --out7 --channels4 --srate48000 --verbose --loop
Then I run this file to test outputs:
SinOsc s0 => dac.chan(0); SinOsc s1 => dac.chan(1); SinOsc s2 => dac.chan(2); SinOsc s3 => dac.chan(3); 1::second => now;
Yields this error:
[chuck](VM): NullPointerException: (UGen link) on line[3] in shred[id=1: speaker_tester.ck]
Note: "line[3]"... it only thinks there are two dac channels. Indeed, I can only get sound out of dac.chan(0) and dac.chan(1).
I get the same behavior in chuck versions 1.4.0.1, 1.4.0.0, & 1.3.6.0 I get the same behavior in different sound cards with 4+ channels out.
BUT... the code works with 4 channels in miniAudicle!
What is going on? What am I doing wrong?
All best, Mike
-- Michael Clemow Artist/Composer/Sound Designer http://michaelclemow.com (he/him)
Hey Perry,
Thanks for the reply! I figured it out late last night and it's
embarrassing: I wasn't adding the file to the running vm with
$ chuck + my_file.ck
but rather executing
$ chuck my_file.ck
which, of course, asked the dac to change to the default sample rate of
44.1k and also the default number of channels (2) so... it wasn't my
incantation or setup at all but the way in which I was running the file.
[facepalm] That's why it worked in miniAudicle but not command line chuck.
It wasn't until I had tried it with JACK as the interface and JACK crashed
complaining that the sample rate changed that I noticed! JACK is picky
about that and became an unwitting debugging tool, haha.
Very best,
Mike
--
Michael Clemow
Artist/Composer/Sound Designer
http://michaelclemow.com
(he/him)
On Thu, May 14, 2020 at 12:27 PM Perry Cook
what does
chuck —probe
print out? Maybe you’re connecting to the wrong dac??
For reference, here’s an invocation script I used last time I did a multichannel performance:
chuck -c8 -bufsize2048 -in2 --dac1 --adc0 INIT.ck
That would have been an older version of chuck, but it worked then.
PRC
From: mike clemow
To: ChucK Users Mailing List Hi folks,
Been a while, hope everyone is safe.
I'm experiencing something very strange and feel I must be doing something wrong. (MacOS 10.14.6)
Running chuck on command line like this:
$ chuck --dac7 --out7 --channels4 --srate48000 --verbose --loop
Then I run this file to test outputs:
SinOsc s0 => dac.chan(0); SinOsc s1 => dac.chan(1); SinOsc s2 => dac.chan(2); SinOsc s3 => dac.chan(3); 1::second => now;
Yields this error:
[chuck](VM): NullPointerException: (UGen link) on line[3] in shred[id=1: speaker_tester.ck]
Note: "line[3]"... it only thinks there are two dac channels. Indeed, I can only get sound out of dac.chan(0) and dac.chan(1).
I get the same behavior in chuck versions 1.4.0.1, 1.4.0.0, & 1.3.6.0 I get the same behavior in different sound cards with 4+ channels out.
BUT... the code works with 4 channels in miniAudicle!
What is going on? What am I doing wrong?
All best, Mike
-- Michael Clemow Artist/Composer/Sound Designer http://michaelclemow.com (he/him)
participants (2)
-
mike clemow
-
Perry Cook