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

Re: [chuck-users] Set adc sampling rate
by Perry Cook 14 May '16

14 May '16

In miniAudicle, it’s in the Preferences window. In terminal, the --srate switch sets sample rate: > chuck --srate8000 MyChucK.ck But both ADC and DAC must run at same rate. AND there has to be supporting hardware there to run at that sample rate. So native Mac coreaudio won’t allow for 8k. You could use the —silent switch, but then you lose the real timebase because ChucK then just runs as fast as it possibly can. You could plug in an iMic or other USB audio device that does support 8k, then it would all work. Use > chuck --probe to find out what sample rates are available. PRC > Message: 2 > Date: Sat, 14 May 2016 17:40:06 +0200 > From: Guille Elias Alonso <guille_elias_alonso(a)hotmail.com> > To: "chuck-users(a)lists.cs.princeton.edu" > <chuck-users(a)lists.cs.princeton.edu> > Subject: [chuck-users] Set adc sampling rate > Message-ID: <DUB125-W53FA6DD2238309A38920E9B3750(a)phx.gbl> > Content-Type: text/plain; charset="iso-8859-1" > > Hi guys! > I'm trying to make some analysis of the micro input and to do so I have to take my micro input with a sampling rate of 8000 Hz. I've checked my micro supports that (with chuck --probe) but in the doc I haven't found how to set the sampling rate of adc. Does someone know how to do that? Or does someone know where I can find some kind of API doc where everything is listed? In the ChucK language specification or in the Unit Generators Reference I cannot find much info about it. > Thanks!Guille >

1 0

Re: [chuck-users] Communicate with a C++ programme (Guille Elias Alonso)
by Perry Cook 13 May '16

13 May '16

It’s pretty old-school, but often my solution for this is to pipe text output of ChucK into stdin of the Cxx program in a terminal. You need to be sure to send to chout and not just use the <<< “PRINT THIS” >>>; form, because the latter prints to stderr, not stdout. Here’s a simple ChucK program that writes a random number to stdout every 16 ms. Below that is a very simple C program to read and report. You’d need to have your C++ program read from stdin and use the argument(s) accordingly. You’d invoke the whole thing like this: > chuck MyChucK.ck | myCProgram where myCProgram is your compiled C++ executable. // MyChucK.ck ChucK Program to write random numbers to stdout while (true) { 16::ms => now; chout <= Std.ftoa(Math.random2f(0.0,3.14159),4); // 4 decimal places chout <= "\n"; // newline chout.flush(); // be sure and do this!! } // END OF CHUCK PROGRAM TO WRITE FLOATS // myCProgram.c a C Program to read single floats from Stdin #include <stdlib.h> #include <stdio.h> #include <string.h> int main() { char inString[256]; float inVal; while (1) { fgets(inString,256,stdin); // read standard input inVal = atof(inString); // peel off float value inString[strlen(inString)-1] = 0; // kill the newline printf("Got it!! %s, %f\n", inString, inVal); // report!! } return 1; } // END C PROGRAM TO READ FLOATS > On May 10, 2016, at 2:09 PM, chuck-users-request(a)lists.cs.princeton.edu wrote: > > 1. Communicate with a C++ programme (Guille Elias Alonso) > 2. Re: Communicate with a C++ programme (Stephen D Beck) > 3. Re: Communicate with a C++ programme (Guille Elias Alonso) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 10 May 2016 22:53:48 +0200 > From: Guille Elias Alonso <guille_elias_alonso(a)hotmail.com> > To: "chuck-users(a)lists.cs.princeton.edu" > <chuck-users(a)lists.cs.princeton.edu> > Subject: [chuck-users] Communicate with a C++ programme > Message-ID: <DUB125-W7866DF5CBF0938708FB36CB3710(a)phx.gbl> > Content-Type: text/plain; charset="iso-8859-1" > > Hello guys, > I'm writing a programme that analyses the micro input and makes some actions according to the analysis. Everything about the analysis is written in Chuck. The analysis of the micro signal gives a single number every 16 ms, and this number has to be sent to the C++ programme but I don't know how I can connect the two parts. This application is highly time-sensitive so I need a fast way of communicating. > I had read about these OSC events but it seems it's only for Chuck programmes receiving input from the outside and I want just the opposite. I've also thought about some mechanism of shared memory between the Chuck programme and the C++ programme but I don't see anywhere some way of implementing that with Chuck. Do you have any ideas? > Thanks,Guillermo >

2 1

ICLI 2016 - Registration open
by thor 12 May '16

12 May '16

3rd International Conference on Live Interfaces School of Media, Film and Music - University of Sussex, Brighton. Dates: June 28th - July 2nd, 2016. Website: www.liveinterfaces.org Registration is now open for the International Conference on Live Interfaces in Brighton this summer. This biennial conference brings together people working with live interfaces in the performing arts, including music, the visual arts, dance, puppetry, robotics or games. The conference scope is highly interdisciplinary but with a focus on interface technologies of expression in the area of performance. Topics of liveness, immediacy, presence (and tele-presence), mediation, collaboration and timing or flow are engaged with and questioned in order to gain a deeper understanding of the role contemporary media technologies play in human expression. The conference consists of paper presentations, performances, interactive installations, poster demonstrations, a doctoral colloquium and workshops. Works engaging with the principles and assumptions governing interaction design, including perspectives from art, philosophy, product design and engineering are specially invited. Keynotes: - Stuart Nolan (magician) - Kristina Andersen (instrument maker) - Roman Paska (puppeteer) Workshops: - Magnetic Resonator Piano (Andrew McPherson) - The halldorophone (Halldor Ulfarsson) - Sound and Space: Performing Music for Organ and Electronics (Lauren Redhead and Alistair Zaldua) - A Practical and Theoretical Introduction to Chaotic Musical Systems (Tristan Clutterbuck, Tom Mudd and Dario Sanfilippo) - Making High-Performance Embedded Instruments with Bela and Pure Data (Giulio Moro, Astrid Bin, Robert Jack, Christian Heinrichs and Andrew McPherson) - Distributed Agency in Performance (Paul Stapleton, Simon Waters, Owen Green and Nicholas Ward) - Interfacing the Txalaparta Workshop (Enrike Hurtado) The conference, including performances and installations, will take place at the newly renovated Attenborough Centre for the Creative Arts. We will publish final performance, installations and paper programme when closer in time. There is a doctoral colloquium on Wednesday 29th of June and a Brighton Modular Meet on Sunday, 3rd of July. We look forward to welcome you to the University of Sussex for the ICLI conference this summer. Best, Thor --- Thor Magnusson Department of Music School of Media, Film and Music University of Sussex http://www.sussex.ac.uk/profiles/164902 http://www.ixi-audio.net https://twitter.com/thormagnusson ---

1 0

print absolute time in chuck
by Chiel ten Brinke 12 May '16

12 May '16

I would like to figure out the source of latency from chuck interacting with another application via OSC. To do that, I want to print timestamps of messages sent and received and compare these. But here's the thing: How do I print the absolute current time in chuck? The variable `now` only seems to hold the time from the start of the process.

4 10

Communicate with a C++ programme
by Guille Elias Alonso 10 May '16

10 May '16

Hello guys, I'm writing a programme that analyses the micro input and makes some actions according to the analysis. Everything about the analysis is written in Chuck. The analysis of the micro signal gives a single number every 16 ms, and this number has to be sent to the C++ programme but I don't know how I can connect the two parts. This application is highly time-sensitive so I need a fast way of communicating. I had read about these OSC events but it seems it's only for Chuck programmes receiving input from the outside and I want just the opposite. I've also thought about some mechanism of shared memory between the Chuck programme and the C++ programme but I don't see anywhere some way of implementing that with Chuck. Do you have any ideas? Thanks,Guillermo

2 2

OSC messages from a python-osc client are not picked up by ChucK server
by Chiel ten Brinke 23 Apr '16

23 Apr '16

I'm trying to set up OSC communication between chuck and python-osc. It appears that the messages we send from the python side do not arrive at the chuck side. All other combinations, i.e. python to python, chuck to chuck and chuck to python are working fine though. I'm running python 3.4.4 on windows 7. What could be going wrong here? Here are the four files with the client/server implementations I'm using for testing. ### chuck_client.py: OscSend xmit; xmit.setHost("localhost", 5005); <<<"Sending">>>; xmit.startMsg("/debug"); ### chuck_server.py: OscRecv orec; 5005 => orec.port; orec.listen(); orec.event("/debug") @=> OscEvent e; <<<"Waiting">>>; e => now; <<<"Received">>>; ### python_client.py: from pythonosc import osc_message_builder from pythonosc import udp_client client = udp_client.UDPClient('localhost', 5005) msg = osc_message_builder.OscMessageBuilder(address="/debug") msg = msg.build() print('Sending') client.send(msg) ### python_server.py: from pythonosc import dispatcher from pythonosc import osc_server dispatcher = dispatcher.Dispatcher() dispatcher.map("/debug", lambda _: print('Received')) print('Waiting') server = osc_server.ThreadingOSCUDPServer( ('localhost', 5005), dispatcher) print("Serving on {}".format(server.server_address)) server.serve_forever() This issue can also be viewed on github: https://github.com/ccrma/chuck/issues/54#issuecomment-213495106

1 0

Seeking ChucK => programmer
by MediMuse 07 Mar '16

07 Mar '16

Seeking ChucK => programmer For bio-metric data Sonification project. Please state your interest in this effort and provide ChucK dev and/or UI history to: medimuse(a)alumni.stanford.edu

2 1

Re: [chuck-users] MIDI devices (more)
by Perry Cook 03 Mar '16

03 Mar '16

You can also check the device name to make sure you’re opening what you want, or iterate through midi device numbers until you find the device you want. Something like: for(0 => int i; true ; i++){ if (!midin.open(i)) me.exit(); if (midin.name() == "Intern in") break; } I think there’s also a capability to open by Device name (as printed out by chuck —probe). I’ve never used it, but I think Spencer put it in fairly recently. PRC > On Mar 3, 2016, 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: not receiving midi messages (Daniel Chapiro) (Perry Cook) > 2. Re: not receiving midi messages (Daniel Chapiro) (Daniel Chapiro) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 2 Mar 2016 14:50:23 -0800 > From: Perry Cook <prc(a)CS.Princeton.EDU> > To: chuck-users(a)lists.cs.princeton.edu > Subject: Re: [chuck-users] not receiving midi messages (Daniel > Chapiro) > Message-ID: <CE790EAF-FEAB-45C7-A2A7-38648331B0AA(a)cs.princeton.edu> > Content-Type: text/plain; charset=utf-8 > > Whenever this happens to me, It almost invariable has to do with > some other MIDI device getting loaded and bumping the number > of the actual device I want around. Make sure you?ve only got one > MIDI device available, or if multiple, make sure that you?re explicitly > opening the one you want. miniAudicle will show the devices, and > also try running: > > chuck --probe > > in a terminal/shell/dosbox, and see what it prints out for MIDI devices. > > That?s my best guess. Also try another MIDI device, a basic keyboard > or other, and make sure messages from it are getting received. > > PRC > > >> On Mar 1, 2016, 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. not receiving midi messages (Daniel Chapiro) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 29 Feb 2016 18:03:48 -0800 >> From: Daniel Chapiro <dchapiro(a)gmail.com> >> To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> >> Subject: [chuck-users] not receiving midi messages >> Message-ID: <C3FE748A-D746-484F-B420-916DBDA98890(a)gmail.com> >> Content-Type: text/plain; charset="us-ascii" >> >> Hi - I have beeen using the same version of Chuck (1.3.5.2-beta-2) on OSX Lion (10.7.5) for over a year, without any changes or problems. However something strange happened, and I'm stuck: >> >> All versions of my Chuck-based software stopped working with my WX-5 (including those that I had frozen and worked fine) >> I tried the WX-5 with GB+Wivi, and it works fine, so I know the hardware is ok, and OSX is passing the midi events to the applications. >> As one more check, I ran "MIDI Monitor.app", and it reports correctly all the Note on/off and CC events I'm sending with the WX-5. >> So I tried MiniAudicle->File->examples->gomidi. It opens succesfully Midi dev 0, and then it blocks forever at min.recv(msg) ... >> >> Can anybody give me a suggestion of what could make Chuck not see the Midi events, or what I can try next? >> >> Thanks! >> Daniel >>

3 2

Re: [chuck-users] not receiving midi messages (Daniel Chapiro)
by Perry Cook 02 Mar '16

02 Mar '16

Whenever this happens to me, It almost invariable has to do with some other MIDI device getting loaded and bumping the number of the actual device I want around. Make sure you’ve only got one MIDI device available, or if multiple, make sure that you’re explicitly opening the one you want. miniAudicle will show the devices, and also try running: chuck --probe in a terminal/shell/dosbox, and see what it prints out for MIDI devices. That’s my best guess. Also try another MIDI device, a basic keyboard or other, and make sure messages from it are getting received. PRC > On Mar 1, 2016, 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. not receiving midi messages (Daniel Chapiro) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 29 Feb 2016 18:03:48 -0800 > From: Daniel Chapiro <dchapiro(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: [chuck-users] not receiving midi messages > Message-ID: <C3FE748A-D746-484F-B420-916DBDA98890(a)gmail.com> > Content-Type: text/plain; charset="us-ascii" > > Hi - I have beeen using the same version of Chuck (1.3.5.2-beta-2) on OSX Lion (10.7.5) for over a year, without any changes or problems. However something strange happened, and I'm stuck: > > All versions of my Chuck-based software stopped working with my WX-5 (including those that I had frozen and worked fine) > I tried the WX-5 with GB+Wivi, and it works fine, so I know the hardware is ok, and OSX is passing the midi events to the applications. > As one more check, I ran "MIDI Monitor.app", and it reports correctly all the Note on/off and CC events I'm sending with the WX-5. > So I tried MiniAudicle->File->examples->gomidi. It opens succesfully Midi dev 0, and then it blocks forever at min.recv(msg) ... > > Can anybody give me a suggestion of what could make Chuck not see the Midi events, or what I can try next? > > Thanks! > Daniel >

2 1

not receiving midi messages
by Daniel Chapiro 29 Feb '16

29 Feb '16

Hi - I have beeen using the same version of Chuck (1.3.5.2-beta-2) on OSX Lion (10.7.5) for over a year, without any changes or problems. However something strange happened, and I'm stuck: All versions of my Chuck-based software stopped working with my WX-5 (including those that I had frozen and worked fine) I tried the WX-5 with GB+Wivi, and it works fine, so I know the hardware is ok, and OSX is passing the midi events to the applications. As one more check, I ran "MIDI Monitor.app", and it reports correctly all the Note on/off and CC events I'm sending with the WX-5. So I tried MiniAudicle->File->examples->gomidi. It opens succesfully Midi dev 0, and then it blocks forever at min.recv(msg) ... Can anybody give me a suggestion of what could make Chuck not see the Midi events, or what I can try next? Thanks! Daniel

1 0