October 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

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

data sonification with Chuck?
by Panos Amelidis 25 Oct '18

25 Oct '18

Hello All I want to explore data sonification in the context of making music pieces and/or sound installations. At the moment I am going through reading the Sonification Handbook and find it quite fascinating. I have no experience whatsoever on DS and to be honest I find it to be quite a difficult task. But, I am... determined to get a result… If any of you would like to share some thoughts, directions or examples that would be much appreciated. I have some experience with Chuck but I used to work a lot with MaxMSP (and some supercollider experience as well, mainly using it for audio files manipulation). I am willing to improve my competence in Chuck though. Thank you all in advance for the help! best ~panos

1 0

SinOsc UGen
by mario buoninfante 24 Oct '18

24 Oct '18

Hi, I ran the same simple test on my Linux machine (Asus i5-6198DU 2.30 GHz, 8 Gb RAM - Ubuntu Studio 16.04) and here I've got different results: SndBuf x 50 - 15.3% CPU usage SinOsc x 50 - 15.7% CPU usage What could explain this? cheers, Mario

1 0

Chunity v1.0.1 released + VSCode Syntax Highlighting Plugin!
by Jack Atherton 24 Oct '18

24 Oct '18

Dear all, Chunity version 1.0.1 is now up on the Unity Asset Store. This version contains internal bugfixes and also implements a retry system if you get your requests for global variables slightly out of order. http://u3d.as/1bvM or download the unitypackage directly from http://chuck.stanford.edu/chunity/files/Chunity_v101.unitypackage Also, I'm happy to announce that there is now a Chunity plugin for VSCode! You can install this to modify the definition of the C# language in VSCode to do embedded ChucK syntax highlighting every time you use the Chunity function RunCode(). Example: https://i.imgur.com/GdBilc1.png https://marketplace.visualstudio.com/items?itemName=jatherton.chunity Many thanks to Forrest Cahoon, who wrote the original ChucK VSCode plugin, which is a dependency for the Chunity plugin. https://marketplace.visualstudio.com/items?itemName=forrcaho.chuck As always, happy ChucKing!! Best, Jack + the ChucK team Music:Computing:Design @ CCRMA

2 1

SinOsc UGen
by Mario Buoninfante 24 Oct '18

24 Oct '18

Hi, I tried using SndBuf instead of SinOsc (both on Rasp Pi and a MacBookPro), but SinOsc seems to offer better performances. On the Mac (2.7 GHz Intel Core i5, 16 GB 1867 MHz DDR3, MacOS Sierra 10.12.6), running the code you'll find below, I've got this CPU usage (I used top from terminal to check the CPU usage): SndBuf x 50 - CPU usage 24.0% SinOsc x 50 - CPU usage 16.4% the same seems to happen on Rasp Pi 3, despite I had to use 25 oscillators to avoid glitches. here's my code ------------SinOsc Version------------ SinOsc s[50]; for(0 => int c; c<s.size(); c++) { s[c].gain( (1/( s.size()) $ float) * 0.25); s[c] => dac; } while(true) { for(0=>int c; c<s.size(); c++) { Math.random2f(300, 500) => s[c].freq; } 200::ms => now; } ------------SndBuf Version------------ SndBuf s[50]; for(0 => int c; c<s.size(); c++) { s[c].read(me.dir() + "/sine_1024.wav"); s[c].pos(0); s[c].loop(1); s[c].gain( (1/( s.size()) $ float) * 0.25); s[c] => dac; } while(true) { for(0=>int c; c<s.size(); c++) { Math.random2f(300, 500) => s[c].freq; } 200::ms => now; } ------------------- cheers, Mario

1 0

SinOsc UGen
by Mario Buoninfante 24 Oct '18

24 Oct '18

Hi, As already pointed out by someone else here, I noticed we've got the SinOsc UGen that doesn't use a wavetable but instead uses the sin function. I don't know what the reason behind this decision, but I was wondering whether it would be possible to also have a variant that uses wavetable as well. I presume that would help a bit in terms of performances, and I think it would be useful in scenarios where ChucK runs on platforms like Raspberry Pi. cheers, Mario

2 2

Re: [chuck-users] Sine Wavetable (Mario B.)
by Perry Cook 23 Oct '18

23 Oct '18

I’ve done this a lot. Just make a nicely oversampled single-cycle sine .wav file and use SndBuf. You’ll need a .freq function that does the right thing based on how many samples are in your wavetable. I think you can also use GenX to do it. Prc Sent from my iPhone > On Oct 23, 2018, at 9: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. SinOsc UGen (Mario Buoninfante) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 23 Oct 2018 15:28:30 +0100 > From: Mario Buoninfante <mario.buoninfante(a)gmail.com> > To: ChucK <chuck-users(a)lists.cs.princeton.edu> > Subject: [chuck-users] SinOsc UGen > Message-ID: > <CAHs=M8T3TLYV9CZUVtpoueYg9+-4MLEdA-6sq73WPSAJjaWoVg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > > As already pointed out by someone else here, I noticed we've got the SinOsc > UGen that doesn't use a wavetable but instead uses the sin function. I > don't know what the reason behind this decision, but I was wondering > whether it would be possible to also have a variant that uses wavetable as > well. I presume that would help a bit in terms of performances, and I think > it would be useful in scenarios where ChucK runs on platforms like > Raspberry Pi. > > cheers, > Mario >

1 0

outputing stereo Gain to different dac output?
by henrique matias 15 Oct '18

15 Oct '18

Hello i have a soundcard with multiple outputs ( 32 ) when i use normal Gain g => dac; I get a stereo signal, but if i do: Gain g => dac.chanel(31) i get sound only on 31 and not on 31 and 32. What's the right way of patching "stereo" out of a different pair on the dac? sorry for such basic question, when i looked for "Gain" on the documentation i could not find anything about patching it "stereo", perhaps i looked on the wrong place? Thank You -- *time's not passing, you are.* ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁ ❂ ❁

2 2