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

Re: [chuck-users] Raspberry pi and ChucK and performance
by Stuart McDonald 30 Jan '14

30 Jan '14

For anyone heading pi-wards in future, I tried out Perry's advice and found dropping to 32khz as well as smarter resource management means I can run three concurrent SndBufs (with pans) and a three effect fx chain (including a mighty JCReverb!) simultaneously. It's modest, but enough for me to achieve the ambient driftyness I wanted. YMMV! Cheers Stuart From: Perry Cook <prc(a)CS.Princeton.EDU> > Thoughts from the battlefield: > > One nice thing about the Pi is that it supports many > sample rates. So if you can run at 22.05k or even > 16k or less, then you'll get much more bang for > your buck. > > Also, you might look into using WvIn (non looping) > or WavLoop (looping), rather than SndBuf, because > I think I remember that these are slightly more > efficient. > > Look into using some long delay lines (non-interpolating), > with feedback. These can really fatten up a texture without > requiring much CPU. > > Also be judicious about your efx, some will take more > CPU than others. > > Finally, if a wave is not playing sound, unchuck it at the > end of the chain, and it won't use any CPU while muted. > Keeping track of what's actually sounding, and muting > the rest (by unchuck) can really help. > > Prc >

2 1

Re: [chuck-users] chuck-users Digest, Vol 102, Issue 6
by Anthony Bowyer-Lowe 28 Jan '14

28 Jan '14

I don't know if it's an option for you, Leonard, but in this situation and with these requirements I'd personally be tempted to modify the ChucK source to support something like a --capture command line option which records all output and then auto-closes the audio output file when all shreds have finished. > The problem here is that the duration has to be known beforehand. The > batch conversion can't know how long these scripts are, and the > scripts themselves shouldn't be rigged to put that information > somewhere else. I'm amazed how difficult that appears to realize. I > went through the docs and I can find nothing of use. >

1 0

Fwd: Automated batch conversion of ck files to WAV
by Leonard Ritter 23 Jan '14

23 Jan '14

Hi there, I wrote this to Ge Wang on Twitter before but he's not been there since October, so I thought I'd better write here. I've used ChucK a few years ago and had quite some fun with it. I would like to use it as part of the game we are currently developing. The goal is to allow sounds to be customized to individual installations of the game, where they would then be played back by OpenAL to provide for positional 3D audio. As part of my prototyping, I wanted to write a simple Python script that is able to batch convert a stack of ck files to WAV, ideally sample precise (no leading or trailing silence). I thought that rec.ck would be perfect for achieving that but it seems I can't figure out a way to have recording end precisely when the main script is done playing, instead of recording indefinitely and waiting for abortion via the Ctrl+C key. Is there such a method? I'd be very thankful for advice. Cheers, Leonard -- Leonard und Sylvia Ritter, Duangle, GbR Ritter Altpieschen 9, 01127 Dresden Leonard.Ritter(a)duangle.com www.duangle.com Geschäftsführung: Sylvia Ritter, Leonard Ritter

5 6

Re: [chuck-users] Raspberry pi and ChucK and performance
by Perry Cook 11 Jan '14

11 Jan '14

Thoughts from the battlefield: One nice thing about the Pi is that it supports many sample rates. So if you can run at 22.05k or even 16k or less, then you'll get much more bang for your buck. Also, you might look into using WvIn (non looping) or WavLoop (looping), rather than SndBuf, because I think I remember that these are slightly more efficient. Look into using some long delay lines (non-interpolating), with feedback. These can really fatten up a texture without requiring much CPU. Also be judicious about your efx, some will take more CPU than others. Finally, if a wave is not playing sound, unchuck it at the end of the chain, and it won't use any CPU while muted. Keeping track of what's actually sounding, and muting the rest (by unchuck) can really help. Prc Sent from my iPad :-) > On Jan 11, 2014, at 3:03 PM, chuck-users-request(a)lists.cs.princeton.edu wrote: > > Raspberry pi and ChucK and performance

1 0

Raspberry pi and ChucK and performance
by Stuart McDonald 11 Jan '14

11 Jan '14

I've written a ChucK script to concurrently instantiate samples with their own effects chains with the aim of creating a kind of kaleidoscopic music box that randomly plays filtered longish samples (say up to two minutes). The box bit is intended to be a raspberry pi. Running on a pi the program maxes out at two concurrent samples and a modest effects chain for each. Ideally I'd prefer to double or even triple that so clearly I need to scale back my resource-intensive intentions, along with attempting to improve the pi's performance (overclocking, for example). There are concrete steps to take on both these fronts, but I have two concerns I'd be keen to get advice on: 1. Is ChucK the best electronic music platform to be doing processor-intensive tasks on a low-power processor? 2. Is building a processor-intensive composition on a raspberry pi (as opposed to building a hardware controller-related application) bordering on folly? I realise the second question is more open-ended and philosophical, but I'd be interested to hear other perspectives :) Many thanks Stuart

1 0

Serial/Arduino & ChucK example
by Alan Brooker 06 Jan '14

06 Jan '14

Hi there I am using ChucK 1.3.2.0 (Chimera) with miniAudicle 1.3.0a on Ubuntu 12.04- I think the latest version can communicate with Arduino directly? Cant seem to find any examples so any advice or example code would be much appreciated. I am trying to build a simple step sequencer with *x5 potentiometer*s that send values to an arduino board and then into ChucK hopefully. Was hoping I could do this without OSC- thanks for helping this noob! Al

5 9

language feature requests
by Michael Heuer 03 Jan '14

03 Jan '14

All, I added several language feature requests and bugs to the issue tracker on github at https://github.com/spencersalazar/chuck/issues Allow => from a UGen into a field/parameter #34 Add namespaces and import statements #33 Add constrain and lerp methods to Std or Math #32 Add constructors to class definitions #31 Order of class definitions in a file matters sometimes #30 Allow a class to implement more than one interface or extend more than one class #29 Add abstract and final class and method modifiers #28 now returns 0.0 from Chugen #27 These nudge the ChucK language towards Java in a lot of ways, perhaps not surprising given my background. I'm curious to know what others think. Cheers, michael

1 0