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

Using ADSR as a P(itch)envelope
by herman verbaeten 04 Mar '20

04 Mar '20

Hi, I was hoping to use an ADSR as a pichenvelope But Chuck doesn't want to accept it. Is there another way to achieve this? SndBuf buf => dac; ADSR Penv => buf.rate; Kind regards, herman

3 3

Re: [chuck-users] adc in terminal (RoHam responds to PRC's wisdom)
by Hamilton, Rob 03 Mar '20

03 Mar '20

Thanks PRC. I'm sure that's it but I'm still missing something. So I'm going to ramble on here, subjecting the list to my failures. - I did have Blackhole installed; I uninstalled it and rebooted but still no dice. Haven't used Airplay recently but I do remember its annoying propensity to show up as default. Here's my probe: hamilr4-mbp15:Desktop hamilr4$ chuck --probe [chuck]: found 2 device(s) ... [chuck]: ------( audio device: 1 )--------------- [chuck]: device name = "Apple Inc.: MacBook Pro Microphone" [chuck]: probe [success] ... [chuck]: # output channels = 0 [chuck]: # input channels = 1 [chuck]: # duplex Channels = 0 [chuck]: default output = NO [chuck]: default input = YES [chuck]: natively supported data formats: [chuck]: 32-bit float [chuck]: supported sample rates: [chuck]: 44100 Hz [chuck]: 48000 Hz [chuck]: 88200 Hz [chuck]: 96000 Hz [chuck]: [chuck]: ------( audio device: 2 )--------------- [chuck]: device name = "Apple Inc.: MacBook Pro Speakers" [chuck]: probe [success] ... [chuck]: # output channels = 2 [chuck]: # input channels = 0 [chuck]: # duplex Channels = 0 [chuck]: default output = YES [chuck]: default input = NO [chuck]: natively supported data formats: [chuck]: 32-bit float [chuck]: supported sample rates: [chuck]: 44100 Hz [chuck]: 48000 Hz [chuck]: 88200 Hz [chuck]: 96000 Hz So if I run the pitch-track.ck example (timeless) and print out target_freq near the end of the main while loop, I'll see fluctuating output as expected when run in mini-audicle. Nothing in terminal. I'm trying: chuck --adc0 --in1 pitch-track.ck or chuck --adc:0 --in:1 --srate:48000 pitch-track.ck or to be more explicit... chuck --adc:0 --in:1 --dac:0 --out:2 --srate:48000 pitch-track.ck (both should work right? i.e. colon or no-colon) and just get a wall of: 0.000000 :(float) 0.000000 :(float) 0.000000 :(float) 0.000000 :(float) from Terminal, vs. the expected: 46.875000 :(float) 93.750000 :(float) 46.875000 :(float) 93.750000 :(float) 93.750000 :(float) plus sweet sine-waves in MiniAudicle. Interestingly enough, MiniAudicle only shows my output devices under Device Browser > Audio Interfaces (i.e. MacBook Pro Speakers here). Can't remember if it always only showed output and not input?

2 1

Re: [chuck-users] adc in terminal (Rob Hamilton asks)
by Perry Cook 03 Mar '20

03 Mar '20

Do a —probe to see how many adcs (and dacs) are there. Then try command line forcing to that adc. I find that if I’ve recently airplayed, or forget I have soundsource enabled, or sound flower, or some other real/virtual adc/dac, sometimes those are sticky in system audio and ChucK defaults to that instead of what you want. Prc Sent from my iPhone >> On Mar 3, 2020, at 9:15 AM, Hamilton, Rob <hamilr4(a)rpi.edu> wrote: >> >> TLDR: I'm seeing a strange behavior with adc not working in Terminal. >> >> OS X 10.14.5 Mojave >> 2019 MBPro >> chuck 1.4.0.0 numchucks >> >> Simple adc patches not working at all when run from Terminal. No error but no audio either. Same patches work in MiniAudicle (yay Spencer). >> >> Both built-in laptop mic or external interface give no sound. >> >> I can't find existing bugs for this. Anyone else see similar behaviors? >> >> I'm not dying to upgrade to OS X 10.15 this week but will if that fixes things. >> >> >> ----------------- >> rob hamilton, phd >> assistant professor of music and media >> rensselaer polytechnic institute >> west hall, 114 >> >> e: hamilr4(a)rpi.edu <mailto:hamilr4@rpi.edu> >> w: http://robhamilton.io <http://robhamilton.io/> >> t: @robertkhamilton >> _______________________________________________ >> chuck-users mailing list >> chuck-users(a)lists.cs.princeton.edu <mailto:chuck-users@lists.cs.princeton.edu> >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users <https://lists.cs.princeton.edu/mailman/listinfo/chuck-users> >

1 0

adc not recognized in terminal
by Hamilton, Rob 03 Mar '20

03 Mar '20

TLDR: I'm seeing a strange behavior with adc not working in Terminal. OS X 10.14.5 Mojave 2019 MBPro chuck 1.4.0.0 numchucks Simple adc patches not working at all when run from Terminal. No error but no audio either. Same patches work in MiniAudicle (yay Spencer). Both built-in laptop mic or external interface give no sound. I can't find existing bugs for this. Anyone else see similar behaviors? I'm not dying to upgrade to OS X 10.15 this week but will if that fixes things. ----------------- rob hamilton, phd assistant professor of music and media rensselaer polytechnic institute west hall, 114 e: hamilr4(a)rpi.edu w: http://robhamilton.io t: @robertkhamilton

2 1

smoothing and scaling RMS data
by Andrew Telichan Phillips 29 Feb '20

29 Feb '20

Hello, I'm wanting to capture the amplitude envelope from a live source and generate feedback loops... I'm starting by obtaining RMS values, as per the examples on the home site: https://chuck.cs.princeton.edu/doc/examples/analysis/features/rms.ck First, does anyone have a preferred way of filtering the data that effectively captures transients and smoothes the decay? Second, is there a way to scale the range of this smoothed data - that is, map it onto a defined range to use as a parametric control for another UGen? While I'm at it, does ChucK have a filter for DC leak? I'm new to ChucK and am used to work, so I appreciate any help (and patience).

2 2

ChucK as LV2 or AudioUnit v3 plugin?
by Mario Buoninfante 29 Feb '20

29 Feb '20

+1 LV2 & Linux :)

1 0