Hi all, Is it possible to select which driver for the soundcard I want to use? Like in Reason or Logic you can select the ASIO driver and change the buffersize... Any help would be appreciated! Greetings, Tom
On 31 December 2010 17:00, Tom Aizenberg
Hi all,
Is it possible to select which driver for the soundcard I want to use? Like in Reason or Logic you can select the ASIO driver and change the buffersize...
Yes, using the "--dac[n]" option, where your choices will be listed after using " chuck --probe". If you want ASIO (and if on Windows you likely will) this will be of interest; http://electro-music.com/forum/topic-18931.html&postorder=asc The second page of that topic has the latest, which is a bit out of date. Ok, it's badly out of date, being from 2008. Just for the record; the "ASIO patch" has been tested and can probably be assumed to be safe by now. The "new" RTAudio version should fix the issues there, as well as a whole series of questions about the various way of addressing audio under Linux. Kas.
Wow this is really timely, I was just looking to do the same thing to hook ChucK up to JACK. Any idea how to change the adc input? I'm trying to route audio through JACK into ChucK. Using "chuck --loop --dac[4] --adc[4]" doesn't seem to do the trick; adc is still taking mic input, but I want it to take iTunes input. If I "chuck --probe" in another window with ChucK started and seemingly connected to JACK, I get this: [chuck]: ------( chuck -- dac4 )--------------- [chuck]: device name = "Grame: JackRouter" [chuck]: probe [success] ... [chuck]: # output channels = 2 [chuck]: # input channels = 2 [chuck]: # duplex Channels = 2 [chuck]: default device = YES [chuck]: natively supported data formats: [chuck]: 8-bit int [chuck]: 16-bit int [chuck]: 24-bit int [chuck]: 32-bit int [chuck]: 32-bit float [chuck]: 64-bit float [chuck]: supported sample rates: [chuck]: 44100 Hz ChucK does appear in the JACK routing table, but if I rout iTunes through ChucK I don't seem to be getting any sound with an adc => dac stream; I still get the mic input. I thought it would be cool to be able to use ChucK scripts in conjunction with other tools and connect stuff through JACK. Anyone try this? http://jackaudio.org/ On Jan 1, 2011, at 9:28 AM, Kassen wrote:
On 31 December 2010 17:00, Tom Aizenberg
wrote: Hi all, Is it possible to select which driver for the soundcard I want to use? Like in Reason or Logic you can select the ASIO driver and change the buffersize...
Yes, using the "--dac[n]" option, where your choices will be listed after using " chuck --probe".
If you want ASIO (and if on Windows you likely will) this will be of interest; http://electro-music.com/forum/topic-18931.html&postorder=asc
The second page of that topic has the latest, which is a bit out of date.
Ok, it's badly out of date, being from 2008. Just for the record; the "ASIO patch" has been tested and can probably be assumed to be safe by now. The "new" RTAudio version should fix the issues there, as well as a whole series of questions about the various way of addressing audio under Linux.
Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
oh stupidity. No square brackes. "chuck --loop --dac4 --adc4" works fine. ChucK won't complain about it, but "chuck --loop --dac[4] --adc[4]" doesn't actually work. Yay filtering iTunes in ChucK with JACK! On Jan 1, 2011, at 12:16 PM, Jordan Orelli wrote:
Wow this is really timely, I was just looking to do the same thing to hook ChucK up to JACK. Any idea how to change the adc input? I'm trying to route audio through JACK into ChucK. Using "chuck --loop --dac[4] --adc[4]" doesn't seem to do the trick; adc is still taking mic input, but I want it to take iTunes input. If I "chuck --probe" in another window with ChucK started and seemingly connected to JACK, I get this:
[chuck]: ------( chuck -- dac4 )--------------- [chuck]: device name = "Grame: JackRouter" [chuck]: probe [success] ... [chuck]: # output channels = 2 [chuck]: # input channels = 2 [chuck]: # duplex Channels = 2 [chuck]: default device = YES [chuck]: natively supported data formats: [chuck]: 8-bit int [chuck]: 16-bit int [chuck]: 24-bit int [chuck]: 32-bit int [chuck]: 32-bit float [chuck]: 64-bit float [chuck]: supported sample rates: [chuck]: 44100 Hz
ChucK does appear in the JACK routing table, but if I rout iTunes through ChucK I don't seem to be getting any sound with an adc => dac stream; I still get the mic input.
I thought it would be cool to be able to use ChucK scripts in conjunction with other tools and connect stuff through JACK. Anyone try this? http://jackaudio.org/
On Jan 1, 2011, at 9:28 AM, Kassen wrote:
On 31 December 2010 17:00, Tom Aizenberg
wrote: Hi all, Is it possible to select which driver for the soundcard I want to use? Like in Reason or Logic you can select the ASIO driver and change the buffersize...
Yes, using the "--dac[n]" option, where your choices will be listed after using " chuck --probe".
If you want ASIO (and if on Windows you likely will) this will be of interest; http://electro-music.com/forum/topic-18931.html&postorder=asc
The second page of that topic has the latest, which is a bit out of date.
Ok, it's badly out of date, being from 2008. Just for the record; the "ASIO patch" has been tested and can probably be assumed to be safe by now. The "new" RTAudio version should fix the issues there, as well as a whole series of questions about the various way of addressing audio under Linux.
Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
2011/1/1 Jordan Orelli
oh stupidity. No square brackes.
Oops, I take the blame for that. I tried to make it clear that "n" stood for a variable and wasn't meant as a literal letter but apparently I just made it harder to read.
Yay filtering iTunes in ChucK with JACK!
Great! What's strange though is that ChucK didn't complain about getting invalid parameters like that "--adc" and "--dac" should be followed by a non-negative integer, if it isn't I'd want a error, not chuck pretending all is fine as you seem to have experienced? If it does that I'm inclined to say that's a bug. Yours, Kas.
participants (3)
-
Jordan Orelli
-
Kassen
-
Tom Aizenberg