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

FLOSS manual new paragraphs
by mario buoninfante 17 Mar '18

17 Mar '18

Hi, as I mentioned few weeks ago I started updating the ChucK FLOSS manual (ChucK_FLOSS <https://omnibook.pro/chuck>). today I also added a new paragraph (Synthesis Basics - Part I <https://omnibook.pro/chuck/_full/#synthesis-basics-part-i>). the idea is to expand the tutorial chapter offering a gentle introduction to ChucK, that covers several aspects. it would be great if you guys could have a look at it, and give me some feedback. I apologize in advance for my bad English. of course this is a FLOSS manual, so please feel free to contribute :) cheers, Mario

1 0

CCRMA Summer Workshops Announced!
by Romain Michon 07 Mar '18

07 Mar '18

Hi all, CCRMA summer workshops have been announced! Join us in California this summer! Cheers, Romain [Apologies for cross posting, please circulate widely.] Greetings! Wow, do we have an exciting summer of workshops lined up for the computer/audio enthusiast! Check out the schedule below, and find details on specific workshops and registration at the CCRMA Workshop site <https://ccrma.stanford.edu/workshops>. Feel free to forward this to anyone who may be interested! Questions or comments, please reach out to Nette Worthey: nette(a)ccrma.stanford.edu *CCRMA SUMMER WORKSHOPS* The Center for Computer Research in Music and Acoustics offers intensive programs where top educators and researchers from the fields of music, engineering, and computer science will present a detailed study of specialized subjects. Each workshop is one week long. The workshops are open to the public. *6/18 – 6/22* Perceptual Audio Coding: Marina Bosi, Rich Goldberg Electronic Arts Ensemble: Constantin Basica, Alex Chechile Motion Capture and Analysis of Music Performance: Takako Fujioka, Madeline Huberth *6/25 – 6/29* Music Information Retrieval: Brian McFee, Meinard Müller, Steve Tjoa *7/1 – 7/6* Deep Learning for MIR I: How do Neural Networks Learn Music?: Irán Román, Kitty Shi *7/9 – 7/13* Deep Learning for MIR II: State-of-the-art Algorithms: Irán Román, Kitty Shi *7/16 – 7/20* Digital Audio Effects: A Digital Signal Processing Primer for Musicians and Audio Engineers: Elliot Canfield-Dafilou, Mark Rau SpaceCamp: Ambisonics and Multi-channel Sound Experiments: Christopher Jette, Fernando Lopez-Lezcano *7/30 – 8/3* Formalized Score Control: Using Python and Abjad in Music Composition: Trevor Baca, Josiah Oberholtzer, Jeffrey Treviño *8/6 – 8/10* Aspects of Sound in Art: Elaine Buckholtz, Christopher Jette SuperCollider: Fernando Lopez-Lezcano, Bruno Ruviaro *8/13 – 8/17* Max/MSP/Jitter 1: Safe and Friendly introduction to Max: Christopher Jette, Matt Wright *8/18 – 8/22* Max/MSP/Jitter 2: Really Understanding Max: Christopher Jette, Matt Wright Designing Musical Games::Gaming Musical Design: Rob Hamilton, Chris Platz *8/27 – 8/31* Augmented Mobile Instruments: John Granzow, Romain Michon Algorithmic Composition with Max/MSP and Open Music: Davor Vincze, Andrew Watts

1 0

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

Re: [chuck-users] chuck-users Digest, Vol 150, Issue 1
by Jeff Snyder 06 Feb '18

06 Feb '18

Congratulations, guys! This looks excellent :) -Jeff Snyder Director of Electronic Music Princeton University

1 0

Chuck m4L plugins
by pat pagano 06 Feb '18

06 Feb '18

Hi Folks long time lurkere here i am looking for a set of Chuck M4L devices -- i had them working in Ableton and there was some ridiculous number of them like 10+ different ones does someone recall what they were called? I know there are chuck racks but i think they were prior to that any help would be grand Patrick On Tue, Feb 6, 2018 at 12:58 AM, 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 > -- *Patrick Pagano B.S, M.F.A* Assistant Professor in Residence University of Connecticut *Stamford, Connecticut* *(352)226-2016*

1 0

chuck-1.4.0.0 (numchucks) released
by Ge Wang 06 Feb '18

06 Feb '18

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

3 2

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

06 Feb '18

That sounds amazing! Looking forward to hearing about Unity :) 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

1 0

static strings and the future
by Atte 25 Jan '18

25 Jan '18

Hi I've been away for a long time and surprised that activity seems to have slowed down a lot, both on the development of new releases chuck and the life of this list. Am I looking at the wrong places? What's the status of chuck development now and in the future? I really like chuck (mostly the timing and sporking including Machine.add()), should I look other places for a language that will privide a more secure future? I'm on linux and looked at Csound, Super Collider and PD, each has it's challenges in how I work (realtime generative and algorithmic MIDI), python seems to have realtime problems (garbage collection at random points). Any idea what former chuck users have switched to now? Back to chuck! A problem that I never been able to solve, static strings: public class A { "b" @=> static string B; public static void C(){ <<<B>>>; } } That throws an error, how would I go about what I'm trying to do? Cheers -- Atte http://atte.dk http://a773.dk

9 8

Re: [chuck-users] [chuck-users new user: silly questions
by Casper Schipper 21 Jan '18

21 Jan '18

Dear Sheri, I think the basic documentation "ChucK_manual.pdf" that one gets when you download chuck is actually rather good, for me, the clarity of that manual is what actually got me hooked many years ago. My 2 cents regarding the future of ChucK: I still run it every day. For playing around with experimental DSP that includes compositional ideas, I think it is still really cool (I've tried Faust, but find it a bit to focused on DSP). I also know ChucK was used at Sonology institute in The Hague for teaching (some of the) DSP classes. I have to say that I am running into its limitations (especially that code can get very verbose, because of its similarity to Java). I noticed some of my live-coded programs got unreadable/uneditable because of it. I especially miss functional programming syntax, which is why I now use a translation script written in Python: https://github.com/casperschipper/cisp, which takes a scheme like syntax and translates it into chuck. Since the syntax of that is very different from chuck, I could imagine it someday 'compiles' to another (more efficient) language, but for now, ChucK is ok. Regarding performance, I sometimes schedule supercollider events through OSC with chuck, this gives me the nice strong-timing syntax of chuck and the efficiency of supercollider server, but I guess for beginners this is a bit messy construction. Best, Casper On Mon, Jan 15, 2018 at 10:42 AM, Sheri W-J <Sheri(a)wells-jensen.net> wrote: > Hello, Folks, > Can someone tell me where to find the YouAreReasonablySmartButHavingTroubleGettingStarted > documentation? I'm having trouble getting past the initial steps: I've done > some Perl programming but I could use maybe ... I guess if I knew exactly > what I needed, then I wouldn't need it! > Is the book I see advertised on the Check homepage my answer? If it is, is > that book available electronically anywhere? I'm blind, so purchasing a > hard copy would mean running it through OCR which would introduce pesky > errors. > Thanks for any tips. > Best, > Sheri > > > > On Jan 14, 2018, at 1:12 PM, Stuart Roland <stuartroland(a)gmail.com> wrote: > > I can't speak to the future of ChucK itself, but recently I have been > giving a lot of thought to MY future with Chuck. First off, I love ChucK > and all the cool stuff it let's me create. I find it much more intuitive > than any other audio programming language/environment I have used and I can > usually create something along the lines of what I set out to create with > it. My problem with it is that I really want to be able to create stand > alone apps and plugins with it, which I have not found any way of doing. I > would like for my software to be usable by the average musician, not just > by programmer-musicians who can read ChucK code (though we are a cool > bunch). I know ChucK Racks were just released (for Macs,which I don't use) > but as I understand, this just let's you run ChucK scripts as a plugin, and > does not provide a way to wrap up the code in any UI to distribute to > musicians who are used to sliders, knobs, presets etc. > > So I guess I have a few questions for everyone/anyone here: is there a way > to use ChucK in a mobile or desktop app? Is there a way to connect ChucK to > a GUI that is simple enough that non-programmers could use it? If not, is > there another language / libraries for another language like python, for > example, that has some of the great, intuitive design as ChucK? Is ChucK > more of an educational tool at this point and less of a tool for developers? > > Thanks for taking the time to read. Happy audio/music making! > > Stuart > > On Jan 14, 2018 11:00 AM, <chuck-users-request(a)lists.cs.princeton.edu> > wrote: > >> Send chuck-users mailing list submissions to >> chuck-users(a)lists.cs.princeton.edu >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >> or, via email, send a message with subject or body 'help' to >> chuck-users-request(a)lists.cs.princeton.edu >> >> You can reach the person managing the list at >> chuck-users-owner(a)lists.cs.princeton.edu >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of chuck-users digest..." >> >> Today's Topics: >> >> 1. Re: static strings and the future (JP Yepez) >> >> >> ---------- Forwarded message ---------- >> From: JP Yepez <jpyepezimc(a)gmail.com> >> To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> >> Cc: >> Bcc: >> Date: Sun, 14 Jan 2018 15:53:30 +1300 >> Subject: Re: [chuck-users] static strings and the future >> Hello all, >> >> I can't say much about the development part itself, but in my experience >> I've noticed that ChucK is still being used widely at an academic level. I >> understand it's being used in a few universities that include creative >> technology programs and computer orchestra courses in their curriculums, >> including CalArts, Stanford, and VUW (New Zealand). Like Mario mentioned, >> it is a core part of a few Kadenze courses; I've been involved as a >> producer/teaching assistant in a couple of them and it seems like it's a >> popular language among students who are just learning how to code, and >> musicians who would like to develop more advanced projects. Also, ChucK >> Racks popped up a couple of months ago, which was pretty exciting. So yeah, >> I think there's quite a bit going on, but it certainly would be nice to >> have a more active community (I'm hoping to contribute, and hopefully I'll >> get to it before too long). >> >> About the *static strings* issue, I think they're kind of in a shady >> spot. Like Gonzalo mentioned, you can't have static non-primitives in your >> code, but there is a workaround to this by declaring objects as a reference >> and then initializing them outside of the class. However, if you try to do >> this with strings, it will tell you that they're a primitive type and it >> throws an error. The best hack I've found for this is through arrays (even >> if the size of the array is 1 in many cases). Here's an example: >> >> >> public class Container { >> >> >> static string staticString[]; >> >> >> >> public static void init() { >> >> new string[1] @=> staticString; >> >> "Hello World" @=> staticString[0]; >> >> } >> >> >> >> public static void print(){ >> >> <<< staticString[0] >>>; >> >> } >> >> } >> >> >> Container.init(); >> >> Container.print(); >> >> >> >> You don't really need an init() function, and you can initialize the >> array on the actual script, but I usually end up with much larger classes, >> which is why I like to keep things clean. >> Hope this helps! >> >> Best, >> >> JP >> >> >> *JP Yepez* >> New Media Artist - Musician - Researcher >> Website: http://www.jpyepez.com/ >> Email: jpyepezimc(a)gmail.com >> -------------------------------------------------------- >> <https://www.instagram.com/jpyepez/> <https://twitter.com/jpyepezmusic> >> <https://www.linkedin.com/in/jp-yepez-063928123/> >> >> >> On Sun, Jan 14, 2018 at 12:19 AM, mario buoninfante < >> mario.buoninfante(a)gmail.com> wrote: >> >>> Hi, >>> >>> I'd like to ask the same question about the development status. >>> >>> the only thing I can say is that also if the development seems to be a >>> bit stuck, on the other side I noticed that they're pushing on the >>> educational side (see Kadenze courses), and if you look at the github >>> repository, there's been some update in the last 2 years. >>> >>> but as you guys said, it's important to know what's the plan ;) >>> >>> it's a couple of years I'm really diving into ChucK and I strongly >>> believe that is a good programming language which opens up a lot of >>> possibilities that other languages don't. >>> >>> but at the same time I feel like it's been a bit abandoned (maybe that's >>> a huge word, let's say put aside ;) ) and of course using a "tool" which >>> has an "uncertain future" it's not the best thing. >>> >>> I wish I was able to offer my contribution to the development, but >>> unfortunately I'm not really into C/C++, I'm more a "scripting language >>> guy" :) >>> >>> btw, it would be nice to hear what developers and/or other users have to >>> say about it. >>> >>> >>> cheers, >>> >>> Mario >>> >>> >>> >>> On 12/01/18 22:14, Gonzalo wrote: >>> >>>> Yes, I'm wondering the same thing. There's a Facebook group ( >>>> https://www.facebook.com/groups/1593843507578422/) but it doesn't look >>>> super active either. >>>> >>>> As far as static strings: I'm pretty sure you just can't have static >>>> non-primitives. What are you trying to achieve? >>>> >>>> Cheers, >>>> Gonzalo >>>> >>>> >>>> On 13.01.18 00:20, Atte wrote: >>>> >>>>> Hi >>>>> >>>>> I've been away for a long time and surprised that activity seems to >>>>> have slowed down a lot, both on the development of new releases chuck and >>>>> the life of this list. Am I looking at the wrong places? What's the status >>>>> of chuck development now and in the future? >>>>> >>>>> I really like chuck (mostly the timing and sporking including >>>>> Machine.add()), should I look other places for a language that will privide >>>>> a more secure future? I'm on linux and looked at Csound, Super Collider and >>>>> PD, each has it's challenges in how I work (realtime generative and >>>>> algorithmic MIDI), python seems to have realtime problems (garbage >>>>> collection at random points). Any idea what former chuck users have >>>>> switched to now? >>>>> >>>>> Back to chuck! A problem that I never been able to solve, static >>>>> strings: >>>>> >>>>> public class A { >>>>> "b" @=> static string B; >>>>> >>>>> public static void C(){ >>>>> <<<B>>>; >>>>> } >>>>> } >>>>> >>>>> That throws an error, how would I go about what I'm trying to do? >>>>> >>>>> Cheers >>>>> >>>>> >>>> >>> _______________________________________________ >>> chuck-users mailing list >>> chuck-users(a)lists.cs.princeton.edu >>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >>> >> >> >> _______________________________________________ >> chuck-users mailing list >> chuck-users(a)lists.cs.princeton.edu >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >> >> _______________________________________________ > chuck-users mailing list > chuck-users(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > > _______________________________________________ > chuck-users mailing list > chuck-users(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > -- Casper Schipper casper.schipper(a)gmail.com +31 6 52 322 590

5 7

Re: [chuck-users] future of ChucK
by Stuart Roland 16 Jan '18

16 Jan '18

I can't speak to the future of ChucK itself, but recently I have been giving a lot of thought to MY future with Chuck. First off, I love ChucK and all the cool stuff it let's me create. I find it much more intuitive than any other audio programming language/environment I have used and I can usually create something along the lines of what I set out to create with it. My problem with it is that I really want to be able to create stand alone apps and plugins with it, which I have not found any way of doing. I would like for my software to be usable by the average musician, not just by programmer-musicians who can read ChucK code (though we are a cool bunch). I know ChucK Racks were just released (for Macs,which I don't use) but as I understand, this just let's you run ChucK scripts as a plugin, and does not provide a way to wrap up the code in any UI to distribute to musicians who are used to sliders, knobs, presets etc. So I guess I have a few questions for everyone/anyone here: is there a way to use ChucK in a mobile or desktop app? Is there a way to connect ChucK to a GUI that is simple enough that non-programmers could use it? If not, is there another language / libraries for another language like python, for example, that has some of the great, intuitive design as ChucK? Is ChucK more of an educational tool at this point and less of a tool for developers? Thanks for taking the time to read. Happy audio/music making! Stuart On Jan 14, 2018 11:00 AM, <chuck-users-request(a)lists.cs.princeton.edu> wrote: > Send chuck-users mailing list submissions to > chuck-users(a)lists.cs.princeton.edu > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > or, via email, send a message with subject or body 'help' to > chuck-users-request(a)lists.cs.princeton.edu > > You can reach the person managing the list at > chuck-users-owner(a)lists.cs.princeton.edu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chuck-users digest..." > > Today's Topics: > > 1. Re: static strings and the future (JP Yepez) > > > ---------- Forwarded message ---------- > From: JP Yepez <jpyepezimc(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Cc: > Bcc: > Date: Sun, 14 Jan 2018 15:53:30 +1300 > Subject: Re: [chuck-users] static strings and the future > Hello all, > > I can't say much about the development part itself, but in my experience > I've noticed that ChucK is still being used widely at an academic level. I > understand it's being used in a few universities that include creative > technology programs and computer orchestra courses in their curriculums, > including CalArts, Stanford, and VUW (New Zealand). Like Mario mentioned, > it is a core part of a few Kadenze courses; I've been involved as a > producer/teaching assistant in a couple of them and it seems like it's a > popular language among students who are just learning how to code, and > musicians who would like to develop more advanced projects. Also, ChucK > Racks popped up a couple of months ago, which was pretty exciting. So yeah, > I think there's quite a bit going on, but it certainly would be nice to > have a more active community (I'm hoping to contribute, and hopefully I'll > get to it before too long). > > About the *static strings* issue, I think they're kind of in a shady > spot. Like Gonzalo mentioned, you can't have static non-primitives in your > code, but there is a workaround to this by declaring objects as a reference > and then initializing them outside of the class. However, if you try to do > this with strings, it will tell you that they're a primitive type and it > throws an error. The best hack I've found for this is through arrays (even > if the size of the array is 1 in many cases). Here's an example: > > > public class Container { > > > static string staticString[]; > > > > public static void init() { > > new string[1] @=> staticString; > > "Hello World" @=> staticString[0]; > > } > > > > public static void print(){ > > <<< staticString[0] >>>; > > } > > } > > > Container.init(); > > Container.print(); > > > > You don't really need an init() function, and you can initialize the array > on the actual script, but I usually end up with much larger classes, which > is why I like to keep things clean. > Hope this helps! > > Best, > > JP > > > *JP Yepez* > New Media Artist - Musician - Researcher > Website: http://www.jpyepez.com/ > Email: jpyepezimc(a)gmail.com > -------------------------------------------------------- > <https://www.instagram.com/jpyepez/> <https://twitter.com/jpyepezmusic> > <https://www.linkedin.com/in/jp-yepez-063928123/> > > > On Sun, Jan 14, 2018 at 12:19 AM, mario buoninfante < > mario.buoninfante(a)gmail.com> wrote: > >> Hi, >> >> I'd like to ask the same question about the development status. >> >> the only thing I can say is that also if the development seems to be a >> bit stuck, on the other side I noticed that they're pushing on the >> educational side (see Kadenze courses), and if you look at the github >> repository, there's been some update in the last 2 years. >> >> but as you guys said, it's important to know what's the plan ;) >> >> it's a couple of years I'm really diving into ChucK and I strongly >> believe that is a good programming language which opens up a lot of >> possibilities that other languages don't. >> >> but at the same time I feel like it's been a bit abandoned (maybe that's >> a huge word, let's say put aside ;) ) and of course using a "tool" which >> has an "uncertain future" it's not the best thing. >> >> I wish I was able to offer my contribution to the development, but >> unfortunately I'm not really into C/C++, I'm more a "scripting language >> guy" :) >> >> btw, it would be nice to hear what developers and/or other users have to >> say about it. >> >> >> cheers, >> >> Mario >> >> >> >> On 12/01/18 22:14, Gonzalo wrote: >> >>> Yes, I'm wondering the same thing. There's a Facebook group ( >>> https://www.facebook.com/groups/1593843507578422/) but it doesn't look >>> super active either. >>> >>> As far as static strings: I'm pretty sure you just can't have static >>> non-primitives. What are you trying to achieve? >>> >>> Cheers, >>> Gonzalo >>> >>> >>> On 13.01.18 00:20, Atte wrote: >>> >>>> Hi >>>> >>>> I've been away for a long time and surprised that activity seems to >>>> have slowed down a lot, both on the development of new releases chuck and >>>> the life of this list. Am I looking at the wrong places? What's the status >>>> of chuck development now and in the future? >>>> >>>> I really like chuck (mostly the timing and sporking including >>>> Machine.add()), should I look other places for a language that will privide >>>> a more secure future? I'm on linux and looked at Csound, Super Collider and >>>> PD, each has it's challenges in how I work (realtime generative and >>>> algorithmic MIDI), python seems to have realtime problems (garbage >>>> collection at random points). Any idea what former chuck users have >>>> switched to now? >>>> >>>> Back to chuck! A problem that I never been able to solve, static >>>> strings: >>>> >>>> public class A { >>>> "b" @=> static string B; >>>> >>>> public static void C(){ >>>> <<<B>>>; >>>> } >>>> } >>>> >>>> That throws an error, how would I go about what I'm trying to do? >>>> >>>> Cheers >>>> >>>> >>> >> _______________________________________________ >> chuck-users mailing list >> chuck-users(a)lists.cs.princeton.edu >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >> > > > _______________________________________________ > chuck-users mailing list > chuck-users(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > >

5 4

ChucK Getting Started (RE to Sheri W-J)
by Perry Cook 15 Jan '18

15 Jan '18

Hey Sheri, The book is available in EBook form from the publisher (Manning) here: https://www.manning.com/books/programming-for-musicians-and-digital-artists There is also an intro to programming in ChucK video course on Kadenze here: https://www.kadenze.com/courses/introduction-to-programming-for-musicians-a… Hope this helps, PRC > Date: Mon, 15 Jan 2018 04:42:12 -0500 > From: Sheri W-J <Sheri(a)wells-jensen.net> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] [chuck-users new user: silly questions > Message-ID: <8C078E78-EA41-4A6C-94E2-A9C55DD513FB(a)Wells-Jensen.net> > Content-Type: text/plain; charset="us-ascii" > > Hello, Folks, > Can someone tell me where to find the YouAreReasonablySmartButHavingTroubleGettingStarted documentation? I'm having trouble getting past the initial steps: I've done some Perl programming but I could use maybe ... I guess if I knew exactly what I needed, then I wouldn't need it! > Is the book I see advertised on the Check homepage my answer? If it is, is that book available electronically anywhere? I'm blind, so purchasing a hard copy would mean running it through OCR which would introduce pesky errors. > Thanks for any tips. > Best, > Sheri

1 0

Critter & Guitari Organelle OS3
by mario.buoninfante 10 Jan '18

10 Jan '18

Hi Everybody, I just read an article about the new Organelle OS by Critter & Guitari, and it seems like they will support "all kind of patch formats", not only Pure Data. On their website the mentioned SuperCollider. Does anybody know if ChucK will get involved too? Cheers, Mario Sent from my Wiko ROBBY

3 2

Organelle OS3
by mario buoninfante 01 Jan '18

01 Jan '18

Hi everybody, I just read about Organelle OS 3 release by Critter and Guitari (https://www.critterandguitari.com/blogs/news/organelle-os-3), where they say, I quote: /The Organelle is no longer for only Pd patches and will load patches written in other languages (e.g. SuperCollider)/ I was wondering if they will include ChucK too, that would be great :D Does anybody know anything about that? cheers, Mario

1 0

Save the date: Linux Audio Conference 2018
by Henrik von Coler 22 Dec '17

22 Dec '17

[Apologies for cross-postings] [Please distribute] *Save the date: Linux Audio Conference 2018* The 2018 Linux Audio Conference will take place at *c-base, Berlin* *7th -11th June 2018* The LAC 2018 will feature a full program of talks, workshops and music. Theofficial call for papers and works will be sent shortly after the winter break - so use the quiet of the holidays to think about possible submissions. All relevant information will be made availableon: http://lac.linuxaudio.org/2018/ All the best, the LAC 2018 Organizing Team -- Henrik von Coler Elektronisches Studio, Fachgebiet Audiokommunikation Electronic Music Studio, Audio Communication Group Technische Universität Berlin Fakultät I Geistes- und Bildungswissenschaften Institut für Sprache und Kommunikation Faculty I Humanities Institute of Speech and Communication Einsteinufer 17c, Sekr. EN 8, 10587 Berlin Germany Tel: +49 (0)30 314 22327 Fax: +49 (0)30 314 21143 voncoler(a)tu-berlin.de www.ak.tu-berlin.de

1 0

Fwd: Re: polyphony with MIDI
by mario buoninfante 11 Dec '17

11 Dec '17

-------- Forwarded Message -------- Subject: Re: [chuck-users] polyphony with MIDI Date: Mon, 11 Dec 2017 20:54:30 +0000 From: mario.buoninfante <mario.buoninfante(a)gmail.com> To: Michael <heuermh(a)gmail.com> Hi Michael, There should be a really good script in the examples folder. You can access to them directly from miniAudicle. Cheers, Mario Sent from my Wiko ROBBY On Dec 11, 2017 20:02, Michael Heuer <heuermh(a)gmail.com> wrote: All, I mostly play guitar and single-finger bass lines, but now my sons are starting to play keys for reals and so I'm curious what the typical patterns for implementing polyphony with MIDI might be? Thanks in advance, michael

1 0

polyphony with MIDI
by Michael Heuer 11 Dec '17

11 Dec '17

All, I mostly play guitar and single-finger bass lines, but now my sons are starting to play keys for reals and so I'm curious what the typical patterns for implementing polyphony with MIDI might be? Thanks in advance, michael

3 2