<p dir="ltr">10 times more expensive than what Spencer suggested, but I think worth checking this out anyway</p>
<p dir="ltr"><a href="https://www.blokas.io/pisound">https://www.blokas.io/pisound</a>/</p>
<p dir="ltr">I've been using it on my RaspPi 3 with ChucK in the last 3 months, and is great.<br>
I'm using they're Patchbox OS, and that is great as well.</p>
<p dir="ltr">Cheers,<br>
Mario<br><br></p>
<p dir="ltr">-- <br>
electronic musician, sound artist, creative coder, QA engineer<br>
<a href="https://vimeo.com/creativecodingsalerno">https://vimeo.com/creativecodingsalerno</a> <a href="http://mbuoninfante.tumblr.com">http://mbuoninfante.tumblr.com</a> <a href="https://github.com/mariobuoninfante">https://github.com/mariobuoninfante</a> <a href="https://bitbucket.org/mariobuoninfante">https://bitbucket.org/mariobuoninfante</a></p>
<div class="quote">On 27 Jul 2020 01:00, Spencer Salazar <spencer.salazar@gmail.com> wrote:<br type='attribution'><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hey Michael,<div><br /></div><div>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. </div><div><a href="https://www.dropbox.com/s/923z4px4ztccm1b/basic-rpi.pdf?dl=0">https://www.dropbox.com/s/923z4px4ztccm1b/basic-rpi.pdf?dl=0</a><br /></div><div><br /></div><div>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. </div><div><br /></div><div>Spencer</div><div><br /></div></div></div></div><br /><div class="elided-text"><div dir="ltr">On Thu, Jul 23, 2020 at 12:47 PM Michael Heuer <<a href="mailto:heuermh@gmail.com">heuermh@gmail.com</a>> wrote:<br /></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb( 204 , 204 , 204 );padding-left:1ex"><div style="word-wrap:break-word">Spencer wrote:<div><br /></div><div>> (Ive done a lot of work with native ChucK + Raspberry Pi so can fill in any details if needed). </div><div><br /><div>If you might be able to write a blog post or other walkthrough documentation on this, I would appreciate it!</div><div><br /></div><div>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.</div><div><br /></div><div>Thanks!</div><div><br /></div><div> michael</div><div><br /></div><div><br /><blockquote><div>On Jul 23, 2020, at 2:17 PM, Mícheál Ó Catháin <<a href="mailto:micheal.ocathain@gmail.com">micheal.ocathain@gmail.com</a>> wrote:</div><br /><div><div dir="ltr"><div>Jack</div><div>Thanks very much for the pointers on web chuck!</div><div>I've got a very basic setup working here <a href="https://michealocathain.com/av/webchuck-test/">https://michealocathain.com/av/webchuck-test/</a>.</div><div><br /></div><div>Note I'm loading Chrome from the cli on a mac as follows:</div><div>/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome
--autoplay-policy=no-user-gesture-required</div><div><br /></div><div>It loads /chuck/<a href="http://micheal2.ck/">micheal2.ck</a>, which in plays aah.wav using a sndbuf ugen.<br /></div><div><br /></div><div>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. <br /></div><div><br /></div><div>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!! <br /></div><div><br /></div><div>I'm also curious to know if there is any variant of sndbuf which can handle mp3's or other compressed formats?</div><div><br /></div><div><br /></div><div>Have done a scan of the chuck-users archive - apologies if I have missed previous answers to my queries !! <br /></div><div><br /></div><div><br /></div><div>Warm regards</div><div>micheal<br /></div><div><br /></div><div class="elided-text"><div dir="ltr">On Wed, 22 Jul 2020 at 18:23, Mícheál Ó Catháin <<a href="mailto:micheal.ocathain@gmail.com">micheal.ocathain@gmail.com</a>> wrote:<br /></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb( 204 , 204 , 204 );padding-left:1ex"><div dir="ltr"><div>Spencer</div><div><br /></div><div>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. <br /></div><div><br /></div><div>Ideally I'd love to be able to load .ck files within javascript, driving visualisations</div></div></blockquote></div></div></div></blockquote></div></div></div></blockquote></div></blockquote></div>