I'd be very interessted to help with beta-testing the audicle, as I am also aiming to apply the principles of ChucK in my Live-Performing work here in the UK. So I will have a go with it in actually applying it. Keep me up to date please. Regards, Favio

--- Ursprüngliche Nachricht --- Von: Ge Wang An: ChucK Users Mailing List Betreff: Re: [chuck-users] audicle Datum: Mon, 17 Oct 2005 14:02:42 -0400

...

whats the current status of this project?

The Audicle release is tentatively planned for Christmas 2049... uh I mean 2005. There are several key features/bugs to remove/implement, respectively. The current set of things being worked on:

http://wiki.cs.princeton.edu/index.php/Audicle_DoThisNow

If anyone is willing to beta-test the audicle, that would be excellent. We hope to start that next month.

...

oh and the 1.2.0.1 release of chuck is very neat.

Thanks - we are glad to hear that! 1.2.0.2 has just been released. Announcement/release notes will go out on the main 'chuck' mailing list soon. If you aren't on that list and want to sign up for marginally more spam:

http://chuck.cs.princeton.edu/community.html

Best, Ge!

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- Favio Masulli y Becker Contact: 07840 185 746 MSN : protoolz@hotmail.co.uk

Hi Favio!

1. In your ChucK Tutorial, you write as follows... "Given any number of source files that uses the timing mechanism above,...."

The mechanism here is one that simply chucks a duration to 'now': // advance time by 100 ms 100::ms => now; Time in the language specification: http://chuck.cs.princeton.edu/doc/language/time.html The idea is that as long as each individual program component deals with its own time, chuck can automatically run them concurrently and with sample- synchronous precision. There are other ways of advancing time, such as with events: http://chuck.cs.princeton.edu/doc/language/event.html

2. Is it possible to trigger ChucK with MIDI?

It sure is - in the new 1.2.0.2 release, check out gomidi.ck and gomidi2.ck in the examples/midi/ folder. They only print out the messages, but it is very straightforward to add code to control synthesis and other parameters with them. Also, fire up polyfony.ck and polyfony2.ck, which takes notein messages, such as from a keyboard. The only "trick" to running them is that you must specify the midi device to open - and you can find this number using chuck --probe. For example, in polyfony.ck: // device to open (see: chuck --probe) 1 => int device; If you see that the device you want to use (chuck --probe) is 3, then change the 1 to 3, save the file, and run it. Quite a few folks here have been using MIDI in ChucK. They can likely provide more and better usage examples. Hope this helps. Best, Ge! ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

Hi,

2. Is it possible to trigger ChucK with MIDI? I get the MIDI ports listed under the --probe. And would it be also possible to sync ChucK with another MIDI aplication, say MTC or something like that? Did anyone already write a ck for that?

As far as I am aware ChucK does not deal with sysex, timing or active sensing. ChucK uses the RtMidi library and by default those functions are turned off and I can't find anywhere in the source where they are turned back on. Ge? So, for syncing to another app it depends how you do that. You could send midi messages from your other program and have chuck wait on those events. You could trigger samples or patches or events or whatever you want. That is the power of ChucK! Without knowing what it is you are trying to sync with or what you want to do, that is my first suggestion. Let us know how you are using ChucK :) I hope this answers your question. a