[chuck-users] adc in terminal (RoHam responds to PRC's wisdom)

Scott Smallwood ssmallwo at ualberta.ca
Tue Mar 3 23:31:32 EST 2020


Hey y’all,

This reminds me:  Does anyone know how to change the resolution of what WavOut writes when using command-line chuck?  It seems to default to 16 bit.  What about 24 or 32 float?  


—ss

[ - ]  Scott Smallwood <http://www.scott-smallwood.com/> - Associate Professor - University of Alberta  [ - ]

> On Mar 3, 2020, at 7:59 PM, Hamilton, Rob <hamilr4 at rpi.edu> wrote:
> 
> 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?
> 
> 
> 
> 
> 
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu <mailto:chuck-users at lists.cs.princeton.edu>
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users <https://lists.cs.princeton.edu/mailman/listinfo/chuck-users>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20200303/48c5b4a6/attachment-0001.html>


More information about the chuck-users mailing list