Oh that sounds great! Thank you. I can write a script to create a single-file "minified" version of the LiCK library to use.
michael > On Jul 20, 2020, at 12:08 PM, Jack Atherton <l...@ccrma.stanford.edu> wrote: > > Hi Michael, > > You can deploy a page in a way that loads a bunch of files into the file > system and runs them when the VM is initialized. See preloadfiles.js and > theChuckReady.then() (in host.js) below. One problem you might hit -- if I > remember correctly, creating subdirectories in the ChucK virtual file system > is broken. So, all your virtualFilenames will likely need to be at the top > level of the directory. > > https://ccrma.stanford.edu/~lja/timbre-library/ > <https://ccrma.stanford.edu/~lja/timbre-library/> > https://ccrma.stanford.edu/~lja/timbre-library/js/preloadfiles.js > <https://ccrma.stanford.edu/~lja/timbre-library/js/preloadfiles.js> > https://ccrma.stanford.edu/~lja/timbre-library/js/host.js > <https://ccrma.stanford.edu/~lja/timbre-library/js/host.js> > > (For an example of the directory shenanigans:) > { > serverFilename: './chuck/voicebank/intqueue.ck > <http://intqueue.ck/>', // hierarchy ok on your webserver > virtualFilename: 'intqueue.ck <http://intqueue.ck/>' > // hierarchy not ok in the virtual file system > }, > > ~Jack > > On Mon, Jul 20, 2020 at 9:20 AM Michael Heuer <heue...@gmail.com > <mailto:heue...@gmail.com>> wrote: > Hello Jack, > > WebChucK is very cool! > > Is there some way I could deploy a version of this with the LiCK library (a > bunch of .ck files and an import.ck <http://import.ck/> file that > Machine.adds all of them) included in the virtual file system, or better yet > loaded at ChucK VM initialization? > > Thank you, > > michael > > >> On Jul 20, 2020, at 10:06 AM, Jack Atherton <l...@ccrma.stanford.edu >> <mailto:l...@ccrma.stanford.edu>> wrote: >> >> Web ChucK has existed since last September, but only in Chrome: >> https://ccrma.stanford.edu/~lja/webchuck/ >> <https://ccrma.stanford.edu/~lja/webchuck/> >> For a while, Chrome was the only browser that had implemented the WebAudio >> Worklet standard. >> >> It seems like Firefox has implemented the standard in May ( >> https://hacks.mozilla.org/2020/05/high-performance-web-audio-with-audioworklet-in-firefox/ >> >> <https://hacks.mozilla.org/2020/05/high-performance-web-audio-with-audioworklet-in-firefox/> >> ), but WebChucK hasn't started working in Firefox as a result of those >> changes. It's possible the implementation is subtly different and more >> development will need to happen for WebChucK to work in Firefox. >> >> ~Jack >> >> On Mon, Jul 20, 2020 at 7:58 AM Mícheál Ó Catháin >> <micheal.ocath...@gmail.com <mailto:micheal.ocath...@gmail.com>> wrote: >> hi >> I'm developing an audiovisual installation to tour a number of arts centres >> in Ireland. I want to use ChucK to drive the audio elements, linking >> raspberry pi devices (up to 4) connected via hdmi to screens. The visuals I >> want to use browsers - probably firefox run off the RPi's. Each screen then >> displaying a different page from a javascript application run from one of >> the RPi's. >> >> I've done some initial check online of running ChucK wrapped in javascript, >> and this github page is the latest activity I can find >> https://github.com/aknuds1/chuck <https://github.com/aknuds1/chuck>. >> >> I thought it best to check with the user community if >> 1) there are further developments on running ChucK in the browser >> 2) if the av setup I'm considering has been done before so I could perhaps >> link in and learn from others >> 3) if there are better setups that I should be following... >> >> >> Thanks and kind wishes >> micheal >> >> michealocathain.com <http://michealocathain.com/> >> _______________________________________________ >> chuck-users mailing list >> chuck-users@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> >> _______________________________________________ >> chuck-users mailing list >> chuck-users@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> > > _______________________________________________ > chuck-users mailing list > chuck-users@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> > _______________________________________________ > chuck-users mailing list > chuck-users@lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
