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

FaucK compilation/installation problem?
by Marc Lavallée 26 Jan '19

26 Jan '19

Hello Chuck users (and gurus). This is my first message to the list. I'm a complete newbie, but I think I would enjoy using miniAudicle with the Faust chugin (FaucK). So It could be a question for developers. I'm an experienced Linux user. I compiled ChucK 1.4.0.0, the latest and greatest Faust, all the chugins (including FaucK) and miniAudicle. Unfortunately, FaucK give me this error (on the command line and with miniAudicle): chuck examples/flute.ck [flute.ck]:line(5): undefined type 'Faust'... [flute.ck]:line(5): ... in declaration ... Any pointer would be appreciated. Marc N.B. I first sent this message to the chuck announcement list, so please ignore.

1 0

error message
by Charlie 05 Jan '19

05 Jan '19

Hi folks, when running the code linked below I get this error message: [chuck](via STK): DelayL: setDelay(1173.42) too big! FYI here's the code: https://github.com/charliekramer/ChucK/blob/master/WIP%20call%20and%20respo… It's weird because I'm not using DelayL in my code (but I guess it's in one of the STK models--I'm using Saxofony and Bowed). The message seems innocuous--it seems to continue running fine. It doesn't occur right away but after the code's been running for a little while. Just curious if I'm doing something weird. I'm running it on a MacBook Air with Mojave 10.14.2. Thanks! Charlie

2 1

Why is my code doing this?
by Forrest Cahoon 04 Jan '19

04 Jan '19

Sorry, I tried to come up with a more hello-world example of the problem I'm experiencing, but I really don't know what's going on so I have to post something a bit complex. My ChucK code is here: https://gist.github.com/forrcaho/21acdb25e05a8620f56dba591cd52ed5 I have a class called AdditivePartial and one called Additive which contains an array of AdditivePartial objects. The Additive objects play method sporks the play method for all its partials. The first Additive object I create appears to ignore the noteAmplitude I have set; it is pegged and clipping. That is, until the second Additive object is sporked, at which point the first object suddenly "remembers" it's noteAmplitude. I've looked at the output in Sonic Visualiser and that confirmed this is what's happening, at least on my linux machine. Can anyone reproduce this behavior, or does it work for you? If you can reproduce it, what the heck is going on? Forrest

3 4

running() doesn't return status of the shred
by mario buoninfante 03 Jan '19

03 Jan '19

Hi, I found out that running() always return the value 0, doesn't matter if the shred is actually running or not. done() instead seems to work fine. I tried on my Linux machine running Ubuntu Studio 16.04 using ChucK 1.4.0.0. Here's a little script that shows the issue: 0 => int c; spork ~ loop() @=> Shred parallel; //---------MAIN--------- while( c < 5 ) { <<< "running(): " + parallel.running() + "\t||\t " + "done(): " + parallel.done() >>>; if( c == 2 ) { <<< "exiting the shred" >>>; parallel.exit(); } c++; 0.5::second => now; } //-------FUNCTIONS-------- function void loop() { while( true ) { 333::ms => now; } } 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

Newbie having audio issue
by Theo B. 02 Jan '19

02 Jan '19

Hi all, I'm new to Chuck and very excited about it. I've been trying to work in miniAudicle today, but have had an issue. When I try to use my AirPods, the VM crashes. Any advice? Happy New Year!Theo

1 0

SysExIn and SysExOut classes
by Mario Buoninfante 19 Dec '18

19 Dec '18

Hi, I made 2 simple classes that allow to send/receive SysEx messages on ChucK: https://bitbucket.org/mariobuoninfante/sysex/src/master/ All they do it's basically sending/receiving messages via OSC to/from Pure Data that deals with actual SysEx messages. It seems to work fine, but I didn't do any 'stress test'. Of course having to convert from/to OSC is a kind of a bottleneck, so I'd expect some 'performance issues' when dealing with big SysEx messages (ie firmware updates) , but I think it's fine for general purpose SysEx transmissions. I'd like to see, one day, these 2 classes (SysExIn and SysExOut) being part of the ChucK source code as members of the MIDI classes family. Let me know if you have any question. Cheers, Mario

1 0

Gen10 issue with coefficients
by mario buoninfante 08 Dec '18

08 Dec '18

Hi, I'm working with the Gen10 UGen and it seems like once I set up the coefficients, I can't change them on the fly anymore. To be more precise I can only add new sines to the table but I can't get rid of the ones that are already there. Here's an example where I try to remove the fundamental, but I can't Phasor phasor => Gen10 g10 => Gain volume => dac; volume.gain(0.1); g10.coefs([1.]); 0 => int c; while(true) { if(c==3) { g10.coefs([0., 0.,0.,0.,1.]); <<< "table update" >>>; } Math.random2f(500,700) => phasor.freq; c++; second => now; } When I update the table, instead of removing the 1st partial and add the 5th, I end up having both 1st and 5th. I had a quick look at the source code (ugen_osc.cpp, row 1469) and the possibility of having a coefficient equal to 0 is not considered. Would it be better if we could remove partials? 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

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

Is the sample rate available in ChucK code?
by Forrest Cahoon 05 Dec '18

05 Dec '18

I've found that I can compute the sample rate as a float inside of chuck code by using 1::second/1::samp but I'm wondering if it might be available in some other way, like a global variable. I was thinking, if something doesn't already exist, maybe it could be a variable belonging to the Machine class library. It is a property of the Virtual Machine, right?

1 0

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