July 2019 - 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

HPF | having issues with 'set' method
by mario buoninfante 28 Jul '19

28 Jul '19

Hi, I just noticed that the 'set' method doesn't seem to work properly with HPF. the following code shows the difference between using 'set' and 'freq' Noise noise => HPF filter => dac; 100 => float f; filter.Q(1); while( true ) { f + 100 => f; if( f > 5000 ) { 100 => f; } // swap between filter.freq and filter.set to check the difference filter.freq(f); //filter.set( f, 1 ); 0.1::second => now; } I'll report this on github 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

ChucK + Launchpad
by Mario Buoninfante 27 Jul '19

27 Jul '19

Hi Raul, At the moment only LP Pro is supported, but the plan is to support all of them. I've already received several responses form others who own the standard launchpad, so probably I'll re-prioritize the thing and work on supporting them first. Which LP have you got exactly? Cheers, Mario

3 2

chuck versions and release schedule
by Forrest Cahoon 26 Jul '19

26 Jul '19

I'm putting the finishing touches on my chuck vscode extension, to which I've added syntax checking and a vscode command to have chuck play the currently open file. Since the --syntax switch the checker relies on is currently only in the git master branch, and not currently available in any prepackaged release, I'm using a boolean config param and have this feature turned off by default. I'm struggling with how I should explain this in the README. I guess it's reasonable that _most_ vscode users are programmer types who would not have a problem building chuck from github sources, but I think I have a nice environment with this extension for people who are not that sort of geek. I'd like to say, build from source or wait for version _x_, where _x_ is what I'm trying to figure out. I see that there was a simultaneous release of 1.3.6 and 1.4.0, (but no git tags for either of those?) Would I be correct to guess that the next release will be 1.4.1? Are there any plans to make another release soon? It looks like it's been a year and a half ... might it be time? The --syntax switch surely can't be the only thing that people who aren't building from source are missing. Forrest

1 0

ChucK + Launchpad
by Mario Buoninfante 25 Jul '19

25 Jul '19

Hi, is there anyone who owns a Novation Launchpad Pro and wants to be a beta tester for a new open source project that involves ChucK+Launchpad? Cheers, Mario

2 1

faust2ck | stereo to mono Chugins
by Mario Buoninfante 21 Jul '19

21 Jul '19

Hi, I've been working on some new Chugins using faust2ck (that I got working with ChucK 1.4.0.0 - https://github.com/mariobuoninfante/faust2ck), and it seems that when a Chugin has a stereo input, then will automatically have a stereo output as well. For example, I've created a "sample and hold" that in Faust has 2 inputs and 1 output, but in ChucK I have 2 inputs and 2 outputs as well. I've also tried creating a simple Chugin that in Faust looks like: process = _ <: _,_; a simple mono to stereo UGen. The same, in ChucK I have 2 ins and 2 outs. Is there any reason why this happens? am I missing something? Cheers, Mario

1 0

Re: [chuck-users] Miniaudicle preferences error (saurec asks)
by Perry Cook 16 Jul '19

16 Jul '19

This means that MiniAudicle isn’t currently connected to a dac (at least none with inputs). Go into MA Preferences, Audio, and make sure you’re connected to some dac. That should fix it. You might need to relaunch Mini just to make sure it takes. If that doesn’t work, try command line: chuck --probe which will show you which devices that chuck can see. Try chuck <yourfile.ck> in the command line. That should connect to some valid dac device and work. PRC > On Jul 16, 2019, 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. Re: Miniaudicle preferences error (sarerac) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 16 Jul 2019 12:55:25 +0200 > From: sarerac <sarerac(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] Miniaudicle preferences error > Message-ID: <117DEDF1-31F8-4774-82C0-1F56CC764CF5(a)gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello there > > I am doing ?classes? and ?objects? and i ?ve the next problem > > in the code : > > > // Simple example of sound making class > class Simple > { > //sound chain > Impulse imp => ResonZ filt => dac; > > // some default settings > 100.0 => filt.Q => filt.gain; > 1000.0 => filt.freq; > > fun void freq(float f) > { > f => filt.freq; > > } > > fun void setQ(float Q) > { > > Q => filt.Q => filt.gain; > > } > > fun void setGain(float g) > > { > g => imp.gain; > > } > > fun void noteOn (float volume) > { > volume => imp.next; > } > > > } > > Simple s; > > while(true) > { > > > Math.random2f(1100.0, 1200.0) => s.freq; > Math.random2(1,200) => s.setQ; > Math.random2f(.2,.8) => s.setGain; > // play note > 1 => s.noteOn; > .1::second => now; > } > > > > > > My console monitor return: > > [Untitled]:line(3): ugen's of type 'DAC' have no input - cannot => from another ugen... > [simple_class]:line(5): ugen's of type 'DAC' have no input - cannot => from another ugen... > > > > > Someone knows what is happening > Thank you >

1 0

Miniaudicle preferences error
by sarerac 16 Jul '19

16 Jul '19

Hi ! I am using miniAudicle [version 1.4.0.0 (gidora) git: 1aa2cf5, 64-bit] on an Macbook [OS X 10.14.3 2,9 GHz Intel Core i7 16 GB 1600 MHz DDR3], and I get the following "Assertion failure" when I select the miniAudicle > Preferences menu : 2019-03-18 18:06:20.513 miniAudicle[984:112442] *** Assertion failure in -[NSMenuItem initWithTitle:action:keyEquivalent:], /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1671.20.108/Menus.subproj/NSMenuItem.m:423 I can’t open Miniaudicle’s preference menu. Is there something obvious that I should do? Thanks. Enviado desde mi iPad

3 5

Expanding MIDI support
by mario buoninfante 07 Jul '19

07 Jul '19

I suppose trying to use the latest version of RtMidi would require more work than simply address the issue I've reported. But, we could at least fix the problem on Linux where you cannot send 1 and 2 bytes messages (program changes, real-time and aftertouch), that seems a big one to me. What I've done here (https://github.com/ccrma/chuck/issues/130) is obviously a workaround, but it would be great if someone could have a look at it and see whether or not this makes sense and is actually harmless with no side-effects. It could take "no time" to a C++ person (not sure actually, but I'm trying :) ). 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

Expanding MIDI support
by Mario Buoninfante 05 Jul '19

05 Jul '19

Hi everybody, One month ago I got started with an Open Source project whose goal is to support some hardware on various platforms/environments/programming languages (Pd, SC, Processing, Lua, Python, JS, etc.) and of course my goal is to have ChucK on board as well (hopefully I'll share more info about the project in the next months). The only issue I've got at the moment is that I need to talk SysEx with these gears, and as you know ChucK doesn't deal with SysEx. I really care a lot about this project, mainly because it's open source and because will involve different communities (Pd, SC, JS, etc.) and would really love to include ChucK in this since is the tool I'm mainly using to experiment and make music and I truly believe has got something more than other languages/environments. Thus, since I'm not a C++ person, I decided I'll ask a colleague of mine (a C++ programmer) to help out with this, also because he'll get involved in the project for other reasons anyway. But before doing this I wanted to ask the developers and all those who are involved in maintaining ChucK, if there's any particular reason why SysEx messages are not currently supported. >From what I can see in the code (and after running few experiments) with the current architecture SysEx messages could be sent out (3 bytes at time though) but with a lot of limitations (didn't manage to receive SysEx messages though). Also, I think RtMidi doesn't gate us from doing that (there's just a flag used to 'turn on/off' SysEx communication). But it seems like there's nothing in place that allows to deal with MIDI messages bigger than 3 bytes and, from a "non-C++ person", it seems one way to fix this could potentially be to add a SysExIn/SysExOut and a SysExMsg classes that deal with these kind of MIDI messages. Of course there could be a lot of things I'm missing here, and that's why I'm asking you for some help, even before asking for other help :) Just to make sure there's nothing that prevents people from adding this functionality. Then, last but not the least, ChucK is an open source project and I love it. There are a lot of people working with it, and I was wondering whether or not this would be a feature people are after. Basically I'd like to hear from the community before even getting started with this. I hope this makes sense. Looking forward to hearing from you guys :) Cheers, Mario

5 8