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

Chunity (ChucK for Unity): Release!
by Jack Atherton 29 Jul '22

29 Jul '22

Dear all, Hello! I'm happy to announce the initial official release of Chunity (ChucK for Unity)! http://chuck.stanford.edu/chunity/ http://u3d.as/1bvM Chunity is the integration of ChucK in Unity. (For those of you not familiar with the Unity game engine, Chunity gives you the ability to do realtime sound + music generation natively in Unity, tightly coupled to interactions with graphical objects.) You can use most (possibly all?) ChucK features, run new ChucK code on-the-fly at any time, and communicate between Unity and ChucK using "global" (new keyword!) ints, floats, strings, Events, and 1D int and float arrays. (More types to come!) You can even run multiple VMs that share the same strong timing! Check out this video of things people have already made with Chunity: https://vimeo.com/263613454 And check out the original description of Chunity in this NIME paper: http://chuck.stanford.edu/chunity/files/2018-nime-chunity.pdf We want to know what you all do with this! Please feel free to send works in progress, bug reports, feature requests, finished works, etc. to the chuck-users mailing list! We are also planning to send a sparse series of follow-up emails covering tutorials, new features, and cool projects that people in the community have created. Please see the tutorials, documentation, etc. at the official Chunity website: http://chuck.stanford.edu/chunity/ Thank you and happy ChucKing!! Best, Jack + the ChucK team Music:Computing:Design @ CCRMA

1 2

LAC 2019 : Call for Papers / Posters / Workshops/ Demos / Music / Multimedia Installations
by Romain Michon 05 Dec '18

05 Dec '18

Dear all, It is our pleasure to announce the 17th Linux Audio Conference (LAC-19). We look forward to see you at Stanford this Spring (see details below)! Cheers, [Apologies for cross posting, please circulate widely.] *17th Linux Audio Conference - CCRMA, Stanford University (USA), March 23-26, 2019* After seven years outside of the United States, Linux Audio Conference (LAC) <https://lac.linuxaudio.org/> is coming back to Stanford University <http://stanford.edu/> on March 23-26, 2019 for its 17th edition! LAC is the international conference about Free/Open-Source Software for music, sound, and other media with GNU/Linux as the main platform. More information about this event can be found on the conference website: https://lac.linuxaudio.org/2019/ *Call for Papers / Posters / Workshops* LAC 2019 invites submissions of papers, posters, and workshops addressing all areas of audio processing based on Linux and open source software. All submissions and presentations are in English. Submitted papers are expected to respect academic standards and must be complete (*a simple abstract is not enough*). Submissions can focus on technical, artistic, and/or scientific issues and can target developers and/or users. This includes (but is not limited to) the following categories: - Audio and Music Languages - Audio Hardware Support - Audio Plugins - Drivers, System and Sound Architecture - Education and E-Learning - Games - Interactive Art - Interface Design - Live Coding - Live Performance - Media Art - MIDI, OSC... - Mobile Audio - Music Composition - Music Production - Networked Audio - Physical Computing - Projects Realized using Linux Audio - Realtime Kernel and Linux Distributions - Signal Processing and Sound Synthesis - Sound Spatialization - Standards and Protocols - Video - Etc. *Full Papers* Full papers must be written and presented in English. The length of papers is 4 to 8 pages, with up to 5 keywords, including an abstract of up to 200 words. The abstract will be published on the conference website once the paper has been accepted. The full paper will be available on the website during and after the conference. All papers are peer reviewed by a committee of experts from different disciplines. Reviewers may suggest improvements to the author(s), or require changes in order to accept the submission. The duration of the presentation is 25 minute followed by a 5 minute discussion. *Poster Papers* Poster papers must be written in English, should be 2-4 pages, with up to 5 keywords, including an abstract of up to 150 words. The abstract will be published on the conference website once the poster has been accepted. All posters are peer reviewed by a committee of experts in different disciplines. Reviewers may suggest improvements to the author(s), or require changes in order for the poster to be accepted. *Demos* Demos are informal project (e.g., plug-in, software, interface, idea, etc.) presentations that will be carried out in parallel with poster presentations. Demos can be submitted through this online form <https://lac.linuxaudio.org/2019/submissions.html> to be added to the conference program. *Workshops* Workshop presentations (max duration of 2h) should be 1-4 pages, with up to 5 keywords, including an abstract of up to 150 words to be published on the conference website. Make sure that your proposal indicates if participants are expected to have a specific level, if there are prerequisites, if you'd like to limit the number of participants, etc. Workshops will take place in the CCRMA classroom (which can host approximately 30 people). A projector and a 4 channels sound system will be available in this space. Submit a brief description of the workshop including a URL (if available). *How to Submit Papers / Posters / Workshops?* - Use the online submission tool <http://submissions.html/> - Choose the relevant submission type (paper, poster, or workshop) in addition to your 5 categories - The required file format is PDF. Authors must use the provided templates <https://lac.linuxaudio.org/2019/doc/LAC-19-templates.zip> for paper formatting. - Please let us know if you need a special technical setup for your presentation. *Call for Music / Multimedia Installations* LAC 2019 also invites submissions of musical works involving the use of technology/open source software and multimedia installations. A jury will select the compositions and installations to be included in the conference program according to artistic merit and technical feasibility. Please be prepared to perform your work yourself and make sure that you have all resources needed to perform your piece (e.g., instruments, props, other performers, etc.). LAC 2019 cannot pay for any expenses related to a performance (e.g., performers, travel, accommodation, special equipment, etc.). SCLOrk <https://www.scu.edu/cas/music/ensembles/sclork/> will be available to perform new (or old) laptop orchestra compositions, so this type of submission is encouraged this year! SCLOrk <https://www.scu.edu/cas/music/ensembles/sclork/> is the Santa Clara Laptop Orchestra and uses exclusively Linux computers. Musical works and installations can address all areas of digital audio and audiovisual art. This includes (but is not limited to) the following categories: - Electronic Music - Electroacoustic Music - Mixed Music - Acoustic Music - Sound Installation - Interactive Art - Audiovisual Installation - Game in art - Web and Connected Art *Available Setups* For concerts, LAC will provide the following equipment: - CCRMA Stage: 56.8 full 3d sound system (up to 6th order Ambisonics) - CCRMA Listening Room: 22.4 sound system (up to 3d order Ambisonics) - SCLOrk <https://www.scu.edu/cas/music/ensembles/sclork/> (the Santa Clara Laptop Orchestra). Pieces accepted for a performance with SCLOrk will be added to the rehearsal schedule of the corresponding SCU <https://www.scu.edu/> class. - Additional requests can be made but are not be guaranteed. *How to Submit Music / Multimedia Installations?* - Use the online submission tool <https://lac.linuxaudio.org/2019/submissions.html> - Select the submission type (performance) - The required file format is PDF, formatted for Letter paper size. Submissions should include: - Description of the project program notes - Link to video or audio demonstration of the project - Technical rider of the work *Important Dates* - *Submission Deadline:* December 7, 2018 (11:59pm PST) - *Notification of Acceptance:* January 18, 2019 - *Camera-ready Version Due:* February 15, 2019 - *Conference Dates:* March 23-26, 2019 *Contact* - lac(a)linuxaudio.org Additional information about LAC-19 can be found on the conference website: https://lac.linuxaudio.org/2019/

1 2

TCP protocol
by Mario Buoninfante 04 Dec '18

04 Dec '18

Hi, Does anyone know if it's possible to use TCP instead of UDP in ChucK? Cheers, Mario

7 11

Chunity - RunCode() vs RunFile() affecting the stereo image
by Luis Bergmann 27 Nov '18

27 Nov '18

Hello all, I've been making a demo using Chunity to create music and sound for the Unity demo Space Shooter. I think Chunity is great and open up lots of possibilities, not only regarding procedural synthesis but also implementing features commonly found in game audio middlewares like Fmod and Wwise. One particularly odd issue that I've found is that when using RunFile the audio plays in mono only. That doesn't happen when using RunCode() or with Machine.add(), as the stereo image using Pan2 or SndBuf2 is not affected using these methods. Does anyone notice that, or maybe I am missing something? Best regards, Luis -- Luis Bergmann | +55 11 94284 0574 Twitter: @_luisbergmann

2 2

Biweekly appointment with ChucK on the Facebook group
by mario buoninfante 07 Nov '18

07 Nov '18

Hi everybody, Sorry in advance for the spam, I simply wanted to let you guys know that we're organizing a biweekly appointment with ChucK on the Facebook group. It's just an occasion to share works made with ChucK, focusing on sound and music, without getting lost in technicalities. The idea is to "force" us to do something creative, artistic, without worrying too much about the way the goal has been accomplished. If you feel like you want to take part, please give us a shout: https://www.facebook.com/groups/1593843507578422/ Happy ChucKing, Mario -- Electronic Musician, Creative Coder, QA Engineer https://vimeo.com/creativecodingsalerno http://mbuoninfante.tumblr.com/ https://github.com/mariobuoninfante https://bitbucket.org/mariobuoninfante/

7 8

ChucK scripting language for Audio/MIDI testing
by mario buoninfante 05 Nov '18

05 Nov '18

Hi, Has anyone ever used ChucK for audio/MIDI testing? I personally used it in more than a couple of occasions, and I found it really useful. Nowadays, also for audio and MIDI, Python is pretty much the standard language for testing. Actually it is quite powerful, especially considering the number of libraries available, but despite its versatility and easy of use, I found it a bit annoying for audio/MIDI testing. It seems to me that languages like ChucK and Pure Data are better candidates for this kind of job. I've been using Pd for testing for almost 2 years now (from regression to semi-automated tests), and I'm really happy with it. No need to configure anything more than the essential, pretty stable and reliable, multi-platform, etc. Then, recently I started doing the same with ChucK, that of course has some advantages being a "text-based" language rather than a graphical one. In the specific I've been using it to talk with a CLI via Serial (hardware testing). Perfect, stable, reliable, the possibility to easily manage events... in short, brilliant! I think it would be perfect for test automation as well! The only missing thing is a full MIDI implementation (I know, I said that something like 5 billions times here on the mailing list, and I'm sorry I'm being "a bit" boring). But, SysEx messages are crucial nowadays. A lot of gears use it for basically everything from data transmission (patches, bootloader/firmware updates, etc.) to parameters control (from DX7 till the most recent Korg Volca series), plus internal functionalities. I think this is the real bottleneck at the moment, and I hope one day it will get "fixed". Anyway, I'm saying this for 2 reasons. First, I'd like to get some feedback from you guys and see if anyone else has been doing similar things. Second, I think start using ChucK for audio/MIDI testing could be really good for ChucK itself and its community. I don't know, maybe that's just me thinking about stupid things, but I suppose if people (and when I say people I also mean companies) start using ChucK for work reason, the amount of support increases as well. There will be more users for sure, that means more beta testing, and probably more support in developing it as well. cheers, Mario -- Electronic Musician, Creative Coder, QA Engineer https://vimeo.com/creativecodingsalerno http://mbuoninfante.tumblr.com/ https://github.com/mariobuoninfante https://bitbucket.org/mariobuoninfante/

1 0