- chuck-dev - lists.cs.princeton.edu

OpenBSD
by Cédric Krier 24 Jun '15

24 Jun '15

Hi, Just to say that I updated the OpenBSD patch to the latest version of ChucK: http://www.b2ck.com/~ced/chuck-1.3.5.1-openbsd.patch It uses the OSS API but it is still missing the midi and hid support. Regards, -- Cédric Krier

1 0

Where is the stack depth of user-defined functions determined?
by Arve Knudsen 22 Sep '14

22 Sep '14

Hi I need to determine where the stack depth of user defined functions (i.e. Chuck_VM_Code::stack_depth) is determined, but haven't succeeded in doing so myself yet. Could someone please point it out for me? Thanks, Arve

1 1

Re: [chuck-dev] Fwd: Porting ChucK to JavaScript with Emscripten
by Arve Knudsen 18 Sep '14

18 Sep '14

Hi Phill! First of all, you might want to check out the fruits of my existing efforts, if you haven't already: ChucKJS (https://github.com/aknuds1/chuckjs) and ChucK Demos (http://chuckdemos.com, this is based on ChucKJS). Second, I have a fork of ChucK which I linked to in my original email: https://github.com/aknuds1/chuck/tree/emscripten. The work goes on in the emscripten branch. To build this, you must have sourced the Emscripten SDK (the whole thing is a bit ramshackle for now, sorry about that) and type "make emscripten". Sure you're welcome to help out! Can you write C++? The project is C++ driven, since the idea is to transform ChucK sources (in C++) to JavaScript automatically. Right now, I mainly need to write Emscripten shims (emulations) of ChucK dependencies such as the audio driver (I'm currently thinking we should emulate ASIO). Otherwise, we will probably need some JavaScript ("unit") tests down the line to verify that e.g. the shims do what they're supposed to. Best, Arve On Sep 11, 2014 11:43 AM, "Phill" <phillip.hermans(a)gmail.com> wrote: > Howdy, > > I am a huge fan of ChucK and am just not getting seriously involved with > JS. > > Mainly I'd like to say that have chuck available in JS is a great idea, as > far as how to implement I defer to your judgment. > > Basically I want to give you kudos and also offer any help I may be able > to give as a code monkey in this regard. > > Have you started a new GitHub for this version? > > thanks, > pmh > https://github.com/cheesymoo > ---------- Forwarded message ---------- > From: Arve Knudsen <arve.knudsen(a)gmail.com> > Date: Wed, Sep 10, 2014 at 9:10 PM > Subject: [chuck-dev] Porting ChucK to JavaScript with Emscripten > To: ChucK Developer Mailing List <chuck-dev(a)lists.cs.princeton.edu> > > > Hi guys > > I've re-directed my focus from manually porting ChucK to JavaScript (i.e., > ChucKJS) to an automatic port with the help of the Emscripten tool ( > http://emscripten.org/): https://github.com/aknuds1/chuck/tree/emscripten. > I don't know yet how this'll pan out, but I'm thinking it should be more > future proof than having to maintain an independent JavaScript version of > ChucK. Also, it ought to be much more performant, since Emscripten > generates asm.js rather than vanilla JavaScript. > > The status of the port is that I am currently able to generate a > JavaScript library, chuck.js, which can be invoked, but I need to write > shims for dependencies such as the audio driver to actually do anything > useful. > > Arve > > _______________________________________________ > chuck-dev mailing list > chuck-dev(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev > > >

1 3

Where does the Chuck_VM_Shreduler::now_system attribute get incremented?
by Arve Knudsen 16 Sep '14

16 Sep '14

Hi In trying to auto-port ChucK to JavaScript through Emscripten, I am experiencing that the JavaScript version of ChucK's system clock (i.e., Chuck_VM_Shreduler::now_system), gets incremented by two seconds (i.e. 88200) for some reason I don't yet understand. Only 4096 samples have been processed at that point. Could someone be so kind as to point out in which parts of ChucK now_system gets incremented, to help me debug this issue? Thanks! Arve

2 2

Porting ChucK to JavaScript with Emscripten
by Arve Knudsen 10 Sep '14

10 Sep '14

Hi guys I've re-directed my focus from manually porting ChucK to JavaScript (i.e., ChucKJS) to an automatic port with the help of the Emscripten tool ( http://emscripten.org/): https://github.com/aknuds1/chuck/tree/emscripten. I don't know yet how this'll pan out, but I'm thinking it should be more future proof than having to maintain an independent JavaScript version of ChucK. Also, it ought to be much more performant, since Emscripten generates asm.js rather than vanilla JavaScript. The status of the port is that I am currently able to generate a JavaScript library, chuck.js, which can be invoked, but I need to write shims for dependencies such as the audio driver to actually do anything useful. Arve

1 0

ChucK meets unit testing
by Mark Cerqueira 10 Jul '14

10 Jul '14

Hi all, In between some intense StarCrafting, Spencer and I set up ChucK to be continuously integrated on Travis CI. This means every commit/change to ChucK ensures ChucK compiles on Mac (10.9.2) and Linux (Ubuntu 12.04), as well as running a bunch of unit tests on both platforms. https://travis-ci.org/ccrma/chuck/builds This was spurred by the recent 147th shred removal causing a segmentation fault, given we could easily test (and even further stress test) ChucK automatically. Tests are currently in the src/test folder of the ChucK repo on GitHub, including tests like Michael Heuer's 147 spork (and one with over 9000 shreds) removal code in the 04-Stress folder: https://github.com/ccrma/chuck/tree/master/src/test Want to contribute? Feel free to fork the ChucK repo, add tests, and send a pull request. We're not quite sure how we want to organize the tests yet so put them in whatever folder you want. Once your tests are pulled in, they'll be run every time a new commit is pushed to ChucK. We're hoping this will make ChucK more stable as well as decreasing the chance for regressing bugs. -Mark

2 1

Register-based VM
by Arve Knudsen 03 Jun '14

03 Jun '14

Hi guys Have you ever considered swapping the stack-based VM in ChucK for a register-based one like the one in Lua 5 ( http://en.wikipedia.org/wiki/Lua_(programming_language)#Internals)? I switched to this design in ChucKJS, and it improved performance a great deal. I think it's much nicer to work with as well. I was thinking it might also ease eventual auto-porting of ChucK to JavaScript via Emscripten. Best, Arve

1 0

ChucK porting and license
by Arve Knudsen 06 May '14

06 May '14

Hi Is it correct to assume that a port of ChucK, i.e. ChucKJS<https://github.com/aknuds1/chuckjs>, will need to mirror ChucK's own license: GPL? I'd find an MIT style license ideal personally, but if we are tied to GPL I'll stick to that. Thanks, Arve

1 0

Making website of the ChucK code examples
by Arve Knudsen 19 Mar '14

19 Mar '14

Hi guys As part of my work on ChucKJS <https://github.com/aknuds1/chuckjs> I wish to create a website with examples<https://github.com/spencersalazar/chuck/tree/master/src/examples>from the ChucK source tree, where the examples are executable inside the browser (thanks to ChucKJS). Is this OK with the ChucK project, considering that the examples would come directly from the ChucK source tree, or would there be any licensing concerns? I have already written an initial version of the website with a few examples, so I can publish it immediately once I get the thumbs up :) Best, Arve

2 3

ChucK as part of a debian package
by Stuart McDonald 05 Mar '14

05 Mar '14

Hi, I don't know if this is the best place to discuss; if not let me know to whom I should address this :) I've built a simple Raspberry Pi-based Chuck system, which loads and plays random wave files, applying random filters to them. The system currently runs the program on boot, making the Pi a single purpose sound box. I did this as a sound art project using my own field recordings, and achieved that goal, but now I'm thinking the sound box idea is something others might be interested in, and to that end I'm considering making the program available as a Raspbian package. My first question is: are the Chuck maintainers ok with this? Note that I don't intend to sell the software (although see the bit about KickStarter below) and will make the source chuck files available. My second question is around distributing ChucK itself with the package, since the current ChucK debian package does not run on the Pi. Is it acceptable if I include ChucK with the package? Finally, I am currently considering running this project on KickStarter. I don't really want to go to this effort unless there's sufficient interest, so am looking to set the project's viability at a threshold of 100 interested people contributing a token amount of $1 or $2. My final question is: any objections to me running a kickstarter project based on a ChucK program? Thanks Stuart

3 2