[chuck] Re: Re: Audicle presentation award / video (oliver oli)

Jeffrey Treviño jtrevino at stanford.edu
Mon Feb 7 12:45:43 EST 2005

> From: oliver oli <smoerk at gmail.com>
> Date: February 6, 2005 3:04:00 PM PST
> To: "Mailing list for programming language 'ChucK'" 
> <chuck at lists.cs.princeton.edu>
> Subject: Re: [chuck] Audicle presentation award / video
> Reply-To: Mailing list for programming language 'ChucK' 
> <chuck at lists.cs.princeton.edu>
> I don't know much about Audicle, I only watched the video. It's mainly 
> a visualization of what is going on inside of ChucK. How many shreds 
> are running and when they get activated, etc... There is also an 
> editor which some nifty user interface, which I guess is based on 
> OpenGL, too.

 From the performance standpoint, I can say that the Audicle is much 
more than a fancy editor / visualization.  We have to keep in mind that 
this language aims to facilitate on-the-fly programming.  The Audicle 
interface substantially changes how a performer might interact with 
Chuck in realtime, because it fundamentally changes the characteristics 
of the performance interface.

> But this stuff is completely optional, you can also do everything with 
> plain chuck and an editor of your choice.

Except that you can do it more quickly and in different ways using 
Audicle.  Plus our plain editors are way less interesting to audience 
members than are fancy visualizations.

> I don't think it makes any sense to try to make Audicle more screen 
> reader friendly, because it's mainly 2D and 3D visualization. I guess 
> it's possible to magnify everything in Audicle as it's based on 
> OpenGL.
> But maybe it's possible to make the command line interface of chuck 
> more accessible? Have you tried to run chuck? Is there anything which 
> could be improved for a screen reader...?

As a composer/performer, I personally prefer virtual instrument GUIs of 
some kind (even if they're dynamically defined) over command line 
interfaces for performance.  We need to get away from the suspicion 
that your new music laptop performer is in fact checking his e-mailing 
during the performance you're watching, and projecting 
visualizations--especially visualizations like this that are integrated 
with the code editor and are apparently effecting the way in which the 
performer makes musical decisions--has a lot of potential as a cure.

--Jeff Treviño, Stanford University Computer Center for Research in 
Music and Acoustics (CCRMA)
> Rich Caloggero wrote:
>> Somewhat dumb question here -- what exactly is
>> Audicle ? I assume its some kind of GUI, with Chuck on the back end 
>> doing
>> the heavy lifting. My question is really - is it a win32 app or will 
>> it only
>> run on X-windows. I'm a blind musician and have always wanted an 
>> accessible
>> synthesizer, something I can actually tweak fairly easily. Most (all)
>> stand-alone boxes have incredibly difficult interfaces which can only 
>> be
>> operated by sighted people. Software solutions are worse - completely
>> inaccessible GUI.  Might there be any hope for audicle in this sense? 
>>  I'm
>> certainly no expert in win32 programming or GUI building in general, 
>> but if
>> Cakewalk/Sonar can be made reasonably accessible, then why not 
>> audicle?
>> For good models of how to create accessible interfaces, ones which can
>> expose their state to adaptive tech. like screen readers and 
>> magnification
>> software, look at the gnome project, and Java Swing, both of which are
>> attempting to do this.
>> -- Rich Caloggero, MIT Adaptive Tech. for Info. and Computing
> _______________________________________________
> chuck mailing list
> chuck at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 3897 bytes
Desc: not available
Url : http://lists.cs.princeton.edu/pipermail/chuck/attachments/20050207/b81e82ef/attachment.bin

More information about the chuck mailing list