- chuck-users - lists.cs.princeton.edu

Loading Chugins
by mario buoninfante 04 Mar '18

04 Mar '18

Hi Jesse, after I installed ChucK 1.4.0.0 I was in the same situation. I wasn't able to load any chugin. so I just installed them from scratch and add the path from the terminal (chuck --chugin-path:/usr/local/lib/chuck/) and this worked for me. I noticed that chuck looks int /usr/lib/chuck/ by default, but my chugins are in /usr/local/lib/chuck/ . hope this helps. cheers, Mario

1 0

miniAudicle source - chuck folder is empty
by mario buoninfante 03 Mar '18

03 Mar '18

Hi all, I downloaded miniAudicle source code (miniAudicle github <https://github.com/ccrma/miniAudicle/tree/master/notes>) and I noticed that the ChucK folder (miniAudicle-master/src/chuck/) is empty. am I doing something wrong? cheers, Mario

2 2

ChucK Floss manual
by mario buoninfante 03 Mar '18

03 Mar '18

Hi all, ChucK Floss manual has been ported here: ChucK FLOSS <https://omnibook.pro/chuck/_full/> we're testing this new writing system, that I have to say at the first sight looks more advanced that the one used on the old website (FLOSS <http://floss.booktype.pro>). of course nothing changes in terms of contents, I'm just slowly updating some of them and collecting ideas. I'll keep the mailing list posted. cheers, Mario

1 0

ChucK Floss manual
by mario buoninfante 28 Feb '18

28 Feb '18

Hi all, I know it's only a start, but now ChucK manual is online again (there was an issue with 2 chapters sharing the same name). I also updated the /Installation/ chapter, now the /Linux building and dependencies/ paragraph has been refers to Ubuntu 16.04, the latest LTS version. I'm not a Fedora user, so if there's anyone who use it, please feel free to have a look and update it ;) apart from that it's worth saying that I've been asked by Mick Chesterman (chesterman_floss <http://write.flossmanuals.net/accounts/mick.chesterman/>) to try a new writing system for this work omnibook <https://omnibook.pro/>. so I asked some info more about it. cheers, Mario

1 0

Experiences running Chuck on ARM computers?
by Pietari Seppänen 28 Feb '18

28 Feb '18

Hi! I'm having a lot of trouble running Chuck on my Orange Pi Zero. I'm hoping to make a little hardware looper on one of these tiny and cheap single board computers. Does anyone have any success stories for running Chuck on ARM computers? I know the LoopPi2 project uses Raspberry Pi 3, but I'd prefer a single board computer I could use without an external sound card. My Orange Pi Zero effort was tiny and cheap, if it only worked... I don't know what the problem is, because it's quite beefy despite its size, a lot quicker than the original Raspberry Pi and that runs Chuck. Maybe the problem lies in the audio codec, but it seems to play and record files just fine. Here's my original post on electro-music forum: "PostPosted: Yesterday, at 2:00 am Post subject: Anyone running Chuck on Orange Pi? Reply with quote Edit/Delete this post Mark this post and the followings unread Hi! I'm trying to copy the functionality of LoopPi2 (https://github.com/szymonkaliski/LoopPI2) on Orange Pi Zero. The advantage of OPi Zero is that it is very inexpensive and has an audio codec built-in, which makes it even less expensive. I have the audio side of things working ok on both the recording side and the playback side, however all Chuck scripts work very slowly. The computer has a 1.2 GHz processor and 512 megabytes of memory, which is not much but today's standards, but you would think it's enough for some audio work. Observations: 1. Setting the rate to 8000 helps some, but it's still choppy. 2. At least looking at 'top', Chuck doesn't ever use more than half of the CPU. There's nothing else on that would use it, I don't even have a graphical UI of any kind. I'm using Armbian Debian Jessie with kernel 3.4.113 because I had some trouble with MIDI on the mainline kernel. I compiled Chuck myself from the 1.4 sources. I don't know if I missed some optimization step. Chuck runs on the original Raspberry Pi, which is a lot less powerful and otherwise quite similar, so I don't understand where the trouble comes from. " Regards, Pietari Seppänen

1 0

ChucK Floss manual
by mario buoninfante 24 Feb '18

24 Feb '18

Hi everybody, I had a quick look at the FLOSS manual (http://write.flossmanuals.net/chuck/introduction/) and I noticed the link is broken. since I'm discovering a lot of hidden stuff in the source code (Teabox, CNoise, DelayP, etc.), stuff not documented anywhere, I thought it would be great to update the manual. is there anyone interested in helping out? cheers, Mario

5 6

IFC-18: 2nd Call for Papers - International Faust Conference - Deadline Extended!
by Romain Michon 22 Feb '18

22 Feb '18

[Apologies for cross posting, please circulate widely.] *New submission deadline: March 26, 2018* 1st International Faust Conference - Johannes Gutenberg University, Mainz (Germany), July 17-18, 2018 The International Faust Conference (IFC-18: http://www.ifc18.uni-mainz.de) will take place at the Johannes Gutenberg University <http://www.uni-mainz.de/> of Mainz (Germany) on July 17-18, 2018. It aims at gathering developers and users of the Faust programming language <http://faust.grame.fr/> to present current projects and discuss future directions for Faust and its community. Participants will be able to share their work through paper presentations. A series of round tables on various topics will serve as a platform to brainstorm on Faust's features, semantics, tools, applications, etc. to determine future directions for this language. Open spaces for demos and workshops will be available for participants to openly share their ongoing projects with the rest of the community. As a special event, the winner of GRAME's Faust Open-Source Software Competition will be announced during IFC-18. IFC-18 is free and everyone is welcome to attend! *Call for Papers* We welcome submissions from academic, professional, independent programmers, artists, etc. We solicit original papers centered around the Faustprogramming language <http://faust.grame.fr/> in the following categories: - Original research - Technology tutorial - Artistic project report (e.g., installation, composition, etc.) Paper should be up to 14 pages in length, non anonymous, and formatted according to this template <http://www.ifc18.uni-mainz.de/misc/IFC-18-templates.zip>. *Submissions should be carried out via our EasyChair portal <https://easychair.org/conferences/?conf=ifc18>*. All submissions are subject to peer review. Acceptance may be conditional upon changes being made to the paper as directed by reviewers. Accepted papers will be published on-line as well as in the IFC-18 proceedings paper version. They will be presented by their author(s) at IFC-18 as 15 minutes presentations (+ 5 minutes for questions). Feel free to contact us if you have any question. *Important Dates* - Papers submission deadline: March 26, 2018 March 2, 2018 - Notification of Acceptance: May 5, 2018 May 1, 2018 - Camera-Ready Version: June 1, 2018 *Call for Round Table Topics* A series of round tables on the following themes will take place both afternoons of IFC-18: - Faust Tools (e.g., Architectures, IDE, Faust Code Generator, On-Line Services, etc.) - DSP in Faust and Faust Libraries (e.g., New Algorithms, New Libraries, Missing Functions, etc.) - Faust Compiler and Semantics - Other Topics/Open Session We solicit topic suggestions from the Faust community for each of these themes. Topics can be submitted by means of this Google form <https://goo.gl/forms/0fBYxk28jlRdtqRM2>. They will be introduced during the round tables by the session chair. *Contact* Please, address your questions to: ifc18(a)muwiinfa.geschichte.uni-mainz.de Conference website: http://www.ifc18.uni-mainz.de

1 0

Sysex (again, I Know ;) )
by mario buoninfante 18 Feb '18

18 Feb '18

Hi, still experimenting with sysex, I noticed that on MacOS it is possible to send sysex with a length not multiple of 3 will fill, while on Linux I cannot do the same. does anyone know why this happens? I suspect the "issue" is ALSA, can anyone confirm that? cheers, Mario

1 1

Re: [chuck-users] chuck-1.4.0.0 (numchucks) released
by mario.buoninfante 10 Feb '18

10 Feb '18

Yap, you're perfectly right, of course I also read the version notes...just it looks like I didn't do it properly :) Cheers, Mario Sent from my Wiko ROBBYOn Feb 8, 2018 13:24, Casper Schipper <casper.schipper(a)gmail.com> wrote: > > Dear Mario, > > that is the same new version I think, see the notes: >> >> NOTE: 1.4.0.0 is a simultaneous release with 1.3.6.0;* >> >> * the two are identical except 1.3.6.0 also supports * >> >> * earlier version of OS X before 10.9 (back to 10.5). * > > > > best, > Casper > On 8 Feb 2018, at 13:53, mario.buoninfante <mario.buoninfante(a)gmail.com> wrote: > >> Hi, >> >> I just noticed that on the Princeton website there's still the previous version 1.3.6.0 >> >> Cheers, >> Mario >> >> Sent from my Wiko ROBBYOn Feb 6, 2018 05:58, Ge Wang <ge(a)ccrma.stanford.edu> wrote: >>> >>> >>> Dear all, >>> >>> >>> Greetings! chuck-1.4.0.0 (numchucks) is available: >>> >>> >>> http://chuck.stanford.edu/ >>> >>> http://chuck.cs.princeton.edu/ >>> >>> >>> This is a major release of ChucK, and is mostly a massive code >>> >>> refactor -- huge thanks to Jack Atherton for months of groundwork. >>> >>> It is now... >>> >>> >>> 1) ...much easier to embed ChucK as a lib/module/component into >>> >>> other host systems (e.g., Unity... more on that in the coming >>> >>> weeks); (developers looking to embed chuck: the core engine >>> >>> can be found in src/core/; the command line host is now in >>> >>> src/host/ -- also as an example for new hosts) >>> >>> >>> 2) ...possible to support any number of ChucK/VM instances in >>> >>> the same address space (hence "numchucks") >>> >>> >>> Please see the release notes at the end of this email and, as >>> >>> usual, thank you and happy ChucKin! >>> >>> >>> Best, >>> >>> Spencer, Jack, Ge and the chuck team >>> >>> >>> >>> 1.4.0.0 >>> >>> --- >>> >>> **************************************************** >>> >>> * MAJOR SOURCE REFACTOR!!!!!!!!!!!!!!!!!!!!!!!!!!!!* >>> >>> * (Thanks Jack Atherton for months of groundwork!) * >>> >>> **************************************************** >>> >>> ******************************************************** >>> >>> * NOTE: 1.4.0.0 is a simultaneous release with 1.3.6.0;* >>> >>> *

3 2

Re: [chuck-users] chuck-1.4.0.0 (numchucks) released
by mario.buoninfante 08 Feb '18

08 Feb '18

Hi, I just noticed that on the Princeton website there's still the previous version 1.3.6.0 Cheers, Mario Sent from my Wiko ROBBYOn Feb 6, 2018 05:58, Ge Wang <ge(a)ccrma.stanford.edu> wrote: > > Dear all, > > Greetings! chuck-1.4.0.0 (numchucks) is available: > > http://chuck.stanford.edu/ > http://chuck.cs.princeton.edu/ > > This is a major release of ChucK, and is mostly a massive code > refactor -- huge thanks to Jack Atherton for months of groundwork. > It is now... > > 1) ...much easier to embed ChucK as a lib/module/component into > other host systems (e.g., Unity... more on that in the coming > weeks); (developers looking to embed chuck: the core engine > can be found in src/core/; the command line host is now in > src/host/ -- also as an example for new hosts) > > 2) ...possible to support any number of ChucK/VM instances in > the same address space (hence "numchucks") > > Please see the release notes at the end of this email and, as > usual, thank you and happy ChucKin! > > Best, > Spencer, Jack, Ge and the chuck team > > > 1.4.0.0 > --- > **************************************************** > * MAJOR SOURCE REFACTOR!!!!!!!!!!!!!!!!!!!!!!!!!!!!* > * (Thanks Jack Atherton for months of groundwork!) * > **************************************************** > ******************************************************** > * NOTE: 1.4.0.0 is a simultaneous release with 1.3.6.0;* > * the two are identical except 1.3.6.0 also supports * > * earlier version of OS X before 10.9 (back to 10.5). * > ******************************************************** > - (added) support for 64-bit on windows > - (added) Chuck_External API for including and running ChucK from > elsewhere in C++ > - specify the sample rate > - optionally specify the directory that me.dir() should > evaluate to; this dir will also be scanned for chugins > - optionally use custom callbacks for out and err messages > from ChucK > - (added) external keyword - for communicating variable values to > and from C++ code using Chuck_External API > - (developer) ChucK "core" as library, independent of external > system audio I/O; now much easier to embed ChucK as a > component in other hosts (e.g., command line, plugins, Unity, etc.) > - (developer) ChucK "host" (command line app) > - (developer) SOURCE: code support for multiple ChucK/VM instances > - (developer) SOURCE: one file to include them all (chuck.h) > - (developer) c_str() method for Chuck_Strings, so that chugins with a > different definition of std::string can still construct their own > string > - (developer) API for chugin API calls > - now API variable must be passed > - SHRED variable must also occasionally be passed > - (internal) refactored Chuck_String representation to be immutable > - (internal) refactored to eliminate global VM, compiler, and env > variables > - compiler stores a reference to env > - compiler stores a reference to vm > - vm stores a reference to env > - env stores its own top-level types; no more global type > variables > - DL_Query stores a reference to compiler > - (internal) refactored all print statements to use new macros > > _______________________________________________ > chuck-users mailing list > chuck-users(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

2 1