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

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

how to use MIDI clock in ChucK
by Michael Heuer 02 Jul '19

02 Jul '19

All, I'm curious how to use MIDI clock effectively in ChucK, in two main use cases: From a sample-rate-based timer in ChucK, how should I send out MIDI clock? while (true) { 10::ms => now; // send MIDI clock } or TimeSignature.common(120) @=> TimeSignature ts; while (true) { ts.e => now; // send MIDI clock } or (this one allows the caller to modify the tempo later) TimeSignature.common(120) @=> TimeSignature ts; ts.eighthProvider() @=> EighthProvider e; while (true) { e.evaluate() => now; // send MIDI clock } From receiving MIDI clock messages from an external source, how should one adjust the BPM in ChucK? MidiIn min; MidiMsg msg; TimeSignature.common(120) @=> TimeSignature ts; while (min.recv(msg)) { // if is clock … { /* new BPM */ => ts.tempo; } } I would imagine I would want to window over the last n clock messages to average? Thanks in advance, michael

2 3

Looking for people from BR and South America
by Ana Paula Kelm Soares 02 Jul '19

02 Jul '19

Hi My name is Ana Paula, I'm from Brazil, and i just finished the kadenze course (in which I want to congratulate who made it, it's amazing). I'm an engineer but now I'm studying music production, and I'm really interested in using chuck. I'd like to ask if there are brasilians arround that use chuck, or even people from south america that have interest in making contact. People can e-mail me directly by anapaula.ksoares(a)gmail.com Thanks

1 0

showing your screen during live coding
by Charlie 01 Jul '19

01 Jul '19

hey there, for those of you performing live, how do you show your screens? do you just project the screen with the audible? grateful for any tips! Charlie (NorthWoods) NorthWoods on Facebook <https://www.facebook.com/NorthWoods-live-codingelectronicaambient-230770441…>

1 0

Working on the next version of my ChucK vscode extension
by Forrest Cahoon 28 Jun '19

28 Jun '19

I'm working on a new version of my vscode extension for chuck that will run chuck to check for diagnostic errors. I've got a basically working but not ready for prime time version in the syntax-checker branch of my github repo: https://github.com/forrcaho/vscode-chuck/tree/syntax-checker Note that this will require a chuck built from the latest sources at https://github.com/ccrma/chuck because I'm using the new `--syntax` switch which was just added to run chuck just for syntax checking. If you are interested in taking a look (and maybe helping out), please do so. This is my first vscode extension, so I'm still just figuring things out. Forrest

1 0

Mini Audicle build error
by Ranjith Hegde 20 Jun '19

20 Jun '19

Greetings, I am new to ChuCK and miniaudicle. I joined the course on Kadenze to learn. I use linux laptop. The build is Ubuntu Studio 19.04. I was able to build chuck without errors using the tutorial from the website. I, however, encounter the following error when I try to build miniaudicle. I understand that it does not support qt5 which is why I replaced it with qt4 and qt4-dev. I still get the following error. " sudo make linux-jack make -f makefile.qt-jack make[1]: Entering directory '/home/ranjith/Softwares/miniAudicle-1.3.5.2/src' g++ -c -pipe -D__LINUX_JACK__ -D__UNIX_JACK__ -D__CK_SNDFILE_NATIVE__ -D__LINUX__ -D__PLATFORM_LINUX__ -Ichuck/src -DHAVE_CONFIG_H -O3 -w -D_REENTRANT -fPIC -DHAVE_CONFIG_H -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -Ibuild -isystem /usr/include/libdrm -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o build/moc_mAMainWindow.o build/moc_mAMainWindow.cpp In file included from build/moc_mAMainWindow.cpp:9: build/../qt/mAMainWindow.h:28:10: fatal error: QMainWindow: No such file or directory #include <QMainWindow> ^~~~~~~~~~~~~ compilation terminated. make[1]: *** [makefile.qt-jack:1630: build/moc_mAMainWindow.o] Error 1 make[1]: Leaving directory '/home/ranjith/Softwares/miniAudicle-1.3.5.2/src' make: [makefile:32: linux-jack] Error 2 (ignored) " Would anyone be able to help me out? Thank you -- Regards, *Ranjith Hegde*

1 0