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

Re: [chuck-users] Synth for use with guitar hex pickup
by Julius Smith 24 Mar '13

24 Mar '13

1 0

Synth for use with guitar hex pickup
by Stefan Blixt 24 Mar '13

24 Mar '13

This is pretty basic stuff, but it still worked well enough that I think it may be worth posting, for any ChucK addict with a hex pickup and hex/MIDI converter (yeah, maybe not that many) hasn't tried this yet. Also to anyone is making polyponic synths: include an omni mode that supports this kind of setup! So basically this is a simple polyphonic synth using a single BlitSaw for sound. It listen on six channels, treating each channel as its own mono synth, which suits the output from my Roland VG99 perfectly. /Stefan

4 9

1. Re: Synth for use with guitar hex pickup (Stefan Blixt)
by Perry Cook 24 Mar '13

24 Mar '13

I don't know about Gossett, but Dex and I did this on our Cook-Morrill trumpet interface, and I think the CNMAT/Gibson/Zeta project did this as well. On ours, we fired a noisy attack on one MIDI channel as soon as we detected playing over a threshold. Then we waited a fixed time (like 100 ms) and collected pitch info from many sources (valve info, lip tension, and acoustic features from two mics). Then we fired a best- guess pitched noteon on a different channel, and updated that with bend messages. We sent a note off on the attack channel. There was no perceived latency, but there was occasional monkey business on the pitch update side. Prc Ref: http://quod.lib.umich.edu/cgi/p/pod/dod-idx/midi-control-and-performance-sy… Sent from my iPad :-) On Mar 24, 2013, at 9:00 AM, chuck-users-request(a)lists.cs.princeton.edu wrote:

1 0

retrieving shred id when calling chuck from command line
by Szabolcs Horvát 15 Mar '13

15 Mar '13

Hello, I am a chuck novice, so please be gentle :-) (actually just started learning today) I would like to call chuck from another program and add/remove shreds, as well as control some parameters. Adding shreds is easy, just chuck + shed.ck, but to remove them I need the shred id. So the first question is, how can I retrieve the shred id when adding new shreds? I know that the listener process prints the shred id, but to parse the output of the listener, weed out errors, and catch the shred id only is very messy. Is there a better way? How does miniAudicle do this (since it has to do practically the same thing)? The other question is about how to control all shreds with global parameters. I found a way, but since I'm new to ChucK, I'm looking for some reassurance that this is the correct and the simplest way. I created a class like this: public class MyState { static int freq; } 500 => MyState.freq; Then I read/set the parameter MyState.freq from various shreds. Is this the correct way? Thank you for any help in advance, Szabolcs

2 2

Funded PhD studentship at University of Brighton
by thor 15 Mar '13

15 Mar '13

Hi all This might be of interest to some members of this list: The doctoral college at the University of Brighton is offering PhD studentships for eight set projects starting next academic year. Full details can be found at: http://www.brighton.ac.uk/researchstudy/2013studentships/arts-and-humanitie… Feel free to contact me off list on my Brighton addresse if you have any questions. Best Thor Magnusson

1 0

escaped backslash in string
by Joel Matthys 09 Mar '13

09 Mar '13

Hi all. I'm working on a project that requires me to send a backslash character via OSC. This construct is typical of C family languages: "\\hello" -------> prints: \hello but ChucK doesn't seem to let me escape a backslash. Instead I get [unrecognized escape sequence: '\h']. Same when I try to use octal: "\134hello" Setting aside the crazy fact that I have to send a backslash over OSC (it's for Guido music notation in InScore), does anyone know how to get a backslash in a ChucK string? Thanks, Joel

2 2

Chuck support for virtual MIDI devices
by Dany 06 Mar '13

06 Mar '13

Hi. Does chuck support input from virtual MIDI devices on Mac OS X 10.8.2? It seems that every time I try to open a MidiIn to a virtual device using the gomidi example, I get the following error: [gomidi.ck]: MidiIn: couldn't open MIDI port 0... `chuck --probe` reveals the following: [chuck]: ------( chuck -- 1 MIDI inputs )------ [chuck]: [0] : " mah midi source" [chuck]: [chuck]: ------( chuck -- 0 MIDI outputs )----- [chuck]: When I route my virtual device into Ableton, my virtual device works as expected. I tried swapping my virtual device with another one from the open source project VMPK (http://vmpk.sourceforge.net/). Chuck would open neither my virtual device nor VMPK. This could be a bug in chuck, but I'm not sure. Anyone have any ideas? Thanks, --Dany.

1 0

embedding ChucK, and Windows8, ARM, etc.
by Rob Fielding 02 Mar '13

02 Mar '13

I am using ChucK on an x86 based Windows8 large multitouch screen; as nothing more than a way to create a multi-voice OSC synth that I can describe to users how to install (at minimal cost) and get setup (with little expertise on their part). But Windows store apps (ARM, sandboxed - like on iOS), forces generally conspire to have you try to embed everything into a monolithic process. So: 1) The GPL licensing (SuperCollider as well as ChucK) seems to be an issue for anyone trying to host ChucK embedded into a controller process. Is this an actual problem, given that we are generally just linking in unmodified build of the sources? 2) What is going on with the future of ChucK? After tinkering around with the options for making an OSC synth to match my controller: 1) visual spaghetti code (Pd), 2) An ugly language in wide use (SuperCollider) 3) Hard (CSound) 4) Nice but not well known (ChucK). 3) Performance. I saw Ge Wang say that performance isn't a priority for ChucK, but have no idea what the practical implications are. Will there be (and do there need to be) target specific optimizations to take advantage of SIMD, and other ways of meeting performance goals, especially in the more constrained ARM environments? I haven't tried to do an ARM build of ChucK and get it installed onto Surface, but I read that you can't in general freely communicate between processes on localhost for store apps anyway (ie: OSC over UDP localhost); so that leads back to the problem hosting ChucK as an embedded library. -- http://www.youtube.com/rrr00bb http://rfieldin.appspot.com http://rrr00bb.blogspot.com

5 12

Re: [chuck-users] chuck --probe output: not stdout
by N. Cameron Britt 01 Mar '13

01 Mar '13

FWIW, I have piped chuck's output to stdout and used grep to remove messages that I didn't want displayed in the terminal window. Probably not smart for debugging, but it worked fine in performance. Cameron

1 0

chuck --probe output: not stdout
by mike clemow 01 Mar '13

01 Mar '13

Hi Chuckists, system: mac 10.7.3, chuck 1.3.1.3 (64 bit) So, when I type `chuck --probe` I get the usual output to the console. Now, this has always been the case, however, I'm just now asking about it; chuck does not seem to be sending that output to stdout. I can't access it that way. In fact, if I want it in a file, I have to use script. Where is that console output going? Why is it not going to stdout? Sorry if this question has been answered before. Best, Mike http://michaelclemow.com http://semiotech.org

5 6