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

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

Problems with qubes
by Luca Sangiacomo 19 Feb '16

19 Feb '16

Hi there, I'm having trouble installing chuck and with miniAudicle. I'm using Qubes os, so I'm running the code in a VM. miniAudicle can see the audio interfaces, but it freeze a couple of seconds after I start the chuck vm. Chuck doesn't output any sound and or warning. I have tried to compile with linux-pulse. Compiling with linux-alsa doesn't solve the problem. The sound is working fine (tested playing a wav by shell) Tnx.

1 0

MOOC of interest to ChucK users: Machine Learning for Musicians and Artists
by Rebecca Fiebrink 03 Feb '16

03 Feb '16

Hi everyone! I am teaching a MOOC (online class) called "Machine learning for musicians and artists,” and it has just opened: https://www.kadenze.com/courses/machine-learning-for-musicians-and-artists/… <https://www.kadenze.com/courses/machine-learning-for-musicians-and-artists/…> This class grew out of work that I've done with a number of computer music composers and music technology students, many of whom are ChucK users, and I hope it will be helpful to you. If you’re interested in machine learning for building new musical instruments or other real-time creative interactions, please sign up. No prior machine learning knowledge or mathematical background is necessary. The course is probably most interesting for people who can already program in some environment, because it allows you to connect code you write in languages like ChucK to machine learning algorithms as well as sensors, other software and hardware, etc. But the class should still be accessible to people who don’t program. I’m thrilled to be joined by two guest lecturers, music technology researcher Baptiste Caramiaux and composer/instrument builder/performer Laetitia Sonami. You can watch the lectures and access all the course content for free, or pay a small monthly subscription to also submit & get feedback on assignments. (FYI many familiar ChucK faces have been involved in Kadenze, including Spencer Salazar and Perry Cook, and Perry has a sound synthesis class there as well.) Please share widely with interested friends/colleagues/students! Best, Rebecca

1 0

Announcing MIDIFlower
by Gregory Newsome 07 Jan '16

07 Jan '16

Hi chuck-users, I’d like to announce the release of MIDIFlower, a lightweight MIDI input framework for ChucK. MIDIFlower listens for and routes incoming MIDI data to your ChucK instruments. It’s particularly useful for those who use ChucK with a MIDI controller. With MIDIFlower, you’ll focus more on your instrument code, and less (or not at all) on MIDI input boilerplate. https://github.com/GLN/MIDIFlower Feedback welcome! GLN — Gregory Lee Newsome Lecturer, Digital Composition Faculty of Music University of Toronto greg.newsome(a)utoronto.ca<mailto:greg.newsome@utoronto.ca> http://gregoryleenewsome.ca/

2 1