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

building miniAudicla on debian "cannot find -lqscintilla2"
by Atte 12 Apr '21

12 Apr '21

Hi! I'm trying to build miniAudicle under debian but the build fails like this: /usr/bin/ld: cannot find -lqscintilla2 collect2: error: ld returned 1 exit status make[1]: *** [makefile.qt-alsa:270: miniAudicle] Error 1 make[1]: Leaving directory '/mnt/data/atte/medium/software/chuck/miniAudicle-1.3.5.2/src' make: [makefile:38: linux-alsa] Error 2 (ignored) If I try to install libqscintilla2-dev I get this: atte@pandrup:~/software/chuck/miniAudicle-1.3.5.2/src$ sudo apt-get install libqscintilla2-dev Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libqscintilla2-qt4-dev' instead of 'libqscintilla2-dev' libqscintilla2-qt4-dev is already the newest version (2.10.4+dfsg-2.1). Any pointers appreciated. -- Atte http://latestyoutube.a773.dk | http://a773.dk

2 1

PhD postion on the ERC-funded Intelligent Instruments project
by thor list 07 Apr '21

07 Apr '21

Hello ChucKers, and apologies for x-posting! We are seeking applications for the first PhD position on the ERC-funded Intelligent Instruments research project hosted at the Iceland University of the Arts. This is a three-year fully-funded scholarship. The candidate will propose their own project under the rubric of Intelligent Instruments (see advert) and work in an exciting lab in the heart of Reykjavik, Iceland. Deadline is May 17th and the start date for the project is Sept 1st, 2021. Further information here: https://www.lhi.is/en/intent <https://www.lhi.is/en/intent> Please share and forward this email or the above URL! Looking forward to hear from you - happy to answer any questions at thor.magnusson(a)lhi.is <mailto:thor.magnusson@lhi.is> All best Thor Magnusson https://thormagnusson.github.io <https://thormagnusson.github.io/>

1 0

Newbie troubleshooting Mac/Windows
by Tim Burgess 24 Mar '21

24 Mar '21

Hi, I've installed ChucK 1.4.0.1 using the provided installers on both the Mac Catalina and Windows 10 partitions of my BootCamped MacBook Pro. Booted to the Mac side of things, I created and successfully ran the first tutorial program, as far as randomizing the sine wave frequencies, so that's great. I then booted to Windows and used the same file to validate my installation but, unfortunately, I got no audio output and no error messages. Pressing Ctrl+C generates a message saying "cleaning up", but the command prompt never returns. Can anybody help out a newbie with troubleshooting tips, please? Cheers. Tim

2 13

1.4.0.2 release?
by Michael Heuer 17 Mar '21

17 Mar '21

Hello, I see commits https://github.com/ccrma/chuck/commit/c1e26a18cbcf17a0ad06bdb680200da7f385d… <https://github.com/ccrma/chuck/commit/c1e26a18cbcf17a0ad06bdb680200da7f385d…> and https://github.com/ccrma/chuck/commit/54f1bcd49edad88affd649712af097d38b4f1… <https://github.com/ccrma/chuck/commit/54f1bcd49edad88affd649712af097d38b4f1…> but I can't find a version 1.4.0.2 release version to download anywhere, nor is there a release tag on https://github.com/ccrma/chuck/releases <https://github.com/ccrma/chuck/releases>. The latest provided by download links at https://chuck.cs.princeton.edu/release/ <https://chuck.cs.princeton.edu/release/> and Homebrew is 1.4.0.1 $ which chuck /usr/local/bin/chuck $ chuck --version chuck version: 1.4.0.1 (numchucks) mac os x : intel : 64-bit http://chuck.cs.princeton.edu/ http://chuck.stanford.edu/ <http://chuck.stanford.edu/> Cheers, michael

1 0

hello
by Adam McCartney 12 Mar '21

12 Mar '21

Hello chuck users, just joined the list and wanted to say a brief hello, enjoying Chuck. Really liking the clear syntax and the emphasis on multithreading. Actually had a specific question related to a function call in linux, but it managed to answer itself in the course of writing this mail. I'm on a debian buster distro and running chuck from inside a tmux session running in bash (why not make life as difficult as possible?!) Look forward to seeing what's going on in the community and hopefully can contribute in some positive ways. Regards, Adam -- Adam McCartney | Baumgasse 52/36 A-1030 Wien | +4365 08722811 | admccartney.mur.at

1 0

Re: [chuck-users] [chuck users] Mic on Mini on Mojave+
by David Loberg Code 02 Mar '21

02 Mar '21

I have students who have encountered this general problem with mics, keyboard, and trackpads (with OSX 10.14/15 and OSX 11) Personally, I have never gotten miniAud to trigger the "wants to access" prompt yet. I use this work-around: Open the application Terminal and type the following: open /Applications/miniAudicle.app/Contents/MacOS/miniAudicle This opens miniAudicle via Terminal which allows it to inherit all of the access permissions of Terminal. The above link is assuming that your miniAudicle is located in the Applications folder on your drive. Otherwise you will need a different directory path. Santé, davd ----------------- David Loberg Code School of Music Western Michigan code(a)wmich.edu any pronouns [chuck-users] Mic on Mini on Mojave+ PC Perry Cook <prc(a)cs.princeton.edu>  Til: * chuck-users(a)lists.cs.princeton.edu Hi all, Since Mojave, MacOS has instituted increasing security restrictions on Mic (and Camera) use. One of my Mojave machines at least launched the “MiniAudicle wants access to your microphone” dialog, and Mini now shows up in the Security pane of System Preferences. BUT, opening adc with system Mic selected just ylelds zeroes. Running the very same ChucK code: adc => Gain g => blackhole; // or dac while (1) { <<< now/second, g.last() >>>; second/10 => now; } in Terminal yields the usual non-zero mic output floats on the adc channel. Running it in Mini yields zeroes. I’ve tried it with multiple mic devices (headphone External Mic) and same result, zeroes on Mini. I actually used LoopBack to stream the mic into a virtual dac in Terminal, then selected that Loopback channel as my input in MiniAudicle. That solution works, but costs $$, and of course ChucK MiniAudicle should be able to see and use the mic. Anyone run into this and have a solution? PRC While we’re at it, has anyone dealt with this yet for Processing (mic and camera don’t work, no dialog box from system)???

1 1

Mic on Mini on Mojave+
by Perry Cook 01 Mar '21

01 Mar '21

Hi all, Since Mojave, MacOS has instituted increasing security restrictions on Mic (and Camera) use. One of my Mojave machines at least launched the “MiniAudicle wants access to your microphone” dialog, and Mini now shows up in the Security pane of System Preferences. BUT, opening adc with system Mic selected just ylelds zeroes. Running the very same ChucK code: adc => Gain g => blackhole; // or dac while (1) { <<< now/second, g.last() >>>; second/10 => now; } in Terminal yields the usual non-zero mic output floats on the adc channel. Running it in Mini yields zeroes. I’ve tried it with multiple mic devices (headphone External Mic) and same result, zeroes on Mini. I actually used LoopBack to stream the mic into a virtual dac in Terminal, then selected that Loopback channel as my input in MiniAudicle. That solution works, but costs $$, and of course ChucK MiniAudicle should be able to see and use the mic. Anyone run into this and have a solution? PRC While we’re at it, has anyone dealt with this yet for Processing (mic and camera don’t work, no dialog box from system)???

1 0

Re: [chuck-users] MidiIn/MidiMsg expansion
by Mario Buoninfante 20 Jan '21

20 Jan '21

Hi, I suppose one solution could be to have a new dedicate class (ie SysexMsg) with a getSysex() method, and then tweak the various bits that deal with receiving MIDI so that if the incoming msg is a sysex we can use a SysexMsg object instead of a MidiMsg one. The end result could be something along this line: MidiIn min; MidiMsg msg; SysexMsg sysex; ... ... while (true) { min => now; while (min.recv(sysex)) do something while (min.recv(msg) do something else } cheers, Mario

1 0

MidiIn/MidiMsg expansion
by Mario Buoninfante 20 Jan '21

20 Jan '21

Hi all, As you know I was trying to add sysex support to ChucK, and there are some progress there. I managed to let sysex msg through, and I can get the first 3 bytes using the data1, data2 and data3 member variables (MidiMsg). But of course sysex messages can have any length, so I was trying to find a way to return an array containing the received sysex. It's easy enough to internally store the sysex message received (ie tweaking the MIDI callback and MidiIn and increasing the array used to store incoming MIDI msg), but then when it's time to retrieve this array, well I'm a bit lost tbh. MidiMsg in midiio_rtmidi.cpp appears to be a union, and this makes things a bit trickier since I was thinking about having a member method that returns the sysex array (ie similar to SerialIO.getytes()). Does anyone have any idea about the best way to proceed here? Any help is really appreciated :) cheers, Mario

1 0

Try out this VST instrument/effect chugin
by David Braun 11 Jan '21

11 Jan '21

I created a chugin for Windows that does VST effects and instruments all in one. https://github.com/ccrma/chugins/pull/47 Sample code: VST vst => dac; vst.loadPlugin("C:/VSTPlugIns/Serum_x64.dll"); <<< "num parameters: ", vst.getNumParameters() >>>; <<< "parameter 0 is named: ", vst.getParameterName(0) >>>; vst.loadPreset("serum_preset.fxp"); vst.setParameter(0, vst.getParameter(0)); while(true) { vst.noteOn(60, 1.); 200::ms => now; vst.noteOff(60, 0.); 250::ms => now; } Please checkout the branch (literally) and try it out! David

2 1