Re: [chuck-users] web integration (fao Jack Atherton)

10 times more expensive than what Spencer suggested, but I think worth checking this out anyway https://www.blokas.io/pisound/ I've been using it on my RaspPi 3 with ChucK in the last 3 months, and is great. I'm using they're Patchbox OS, and that is great as well. Cheers, Mario -- electronic musician, sound artist, creative coder, QA engineer https://vimeo.com/creativecodingsalerno http://mbuoninfante.tumblr.com https://github.com/mariobuoninfante https://bitbucket.org/mariobuoninfanteOn 27 Jul 2020 01:00, Spencer Salazar wrote:

Hey Michael,

For sure, feel free to use my course notes here, though they are a little old. If anything meaningful has changed Im happy to update and eventually migrate to a more accessible medium.  https://www.dropbox.com/s/923z4px4ztccm1b/basic-rpi.pdf?dl=0

If youre looking for simple 1/8" stereo out Ive had a lot of success with inexpensive (<$10 USD) USB sound interfaces from Amazon/etc. Search for "raspberry pi soundcard" or look for "class compliant" in the description. They don't require any extra software to be installed on the Pi. This option is a quick way to easily get better audio quality from the Pi- in my experience the built-in sound card is unacceptably noisy for most musical purposes. The difference in quality between $10 USB audio and the fancier GPIO shields is much less drastic, and to me never justified the extra expense and baroque custom driver setup of the latter. 

Spencer

On Thu, Jul 23, 2020 at 12:47 PM Michael Heuer wrote:

...

Spencer wrote:

...

 (Ive done a lot of work with native ChucK + Raspberry Pi so can fill in any details if needed). 

If you might be able to write a blog post or other walkthrough documentation on this, I would appreciate it!

Last I tried I couldn't get the cheapo USB sound card I was using to work, and I've never gotten as far as setting ChucK up to run automatically on startup.

Thanks!

   michael

...

On Jul 23, 2020, at 2:17 PM, Mícheál Ó Catháin wrote:

Jack Thanks very much for the pointers on web chuck! I've got a very basic setup working here https://michealocathain.com/av/webchuck-test/.

Note I'm loading Chrome from the cli on a mac as follows: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --autoplay-policy=no-user-gesture-required

It loads /chuck/micheal2.ck, which in plays aah.wav using a sndbuf ugen.

Chrome takes about 3 sec to load chuckscript.wasm, and about 2 sec to load aah.wav.  This with an empty cache.  It's quicker to reload after the first load, but it made me realise that there will possibly be a practical limit on the size of .wav files loaded.

Has there been any best practice developed on how to (pre)load .wav files longer than 5 seconds or so?  I'm interested in sampling from several ca. 5 min tracks I have recorded at 24bit, ie ca 100mb. This could be way beyond the normal user-case for webchuck!! 

I'm also curious to know if there is any variant of sndbuf which can handle mp3's or other compressed formats?

Have done a scan of the chuck-users archive - apologies if I have missed previous answers to my queries !!

Warm regards micheal

On Wed, 22 Jul 2020 at 18:23, Mícheál Ó Catháin wrote:

...

Spencer

Thanks a lot for your suggestions.  Yes, I'm definitely considering OSC between peer-peer connect Raspberry Pi's.  Still in testing mode with web chuck for now, and will see if it is the right setup for a low latency AV installation. 

Ideally I'd love to be able to load .ck files within javascript, driving visualisations