<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18939">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>FYI: I'm one who never took a signals course in college. I
have some basic idea of complex numbers, but really have no clue why they should
relate to sound / audio signals at all. So, digital filtering is difficult
for me to understand. I know conceptually how it works (i.e. analog equalizer),
but not sure how to work with filters etc digitally i.e. from
chuck.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I can understand the basics of chuck and how the timing model
works, and the unit generators are just objects, so I know how to use
those.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>For me, chuck is low-level - about expressing synthesis
algorithms or some new weird effect.</FONT></DIV>
<DIV><FONT size=2>A sound designer, in my opinion, would use pre-built
synthesizers, effects processors, etc to make a sound; individual synthesizers
or effects processors would look like black boxes. Want a new synthesizer
- just plug it in!</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>think the easiest way to architect this would be:</FONT></DIV>
<DIV><FONT size=2>- build a way of binding chuck classes / objects to
gui</FONT></DIV>
<DIV><FONT size=2>- define exactly what can be exposed and thus manipulated via
the gui (efrrably in code)</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>When writing the chuck classes corresponding to each synthesis
engine, effects processor, etc, mark each field to be gui-enabled.
Some magic would happen to bind each of the classes marked fields to a live
gui object like a textbox or listbox etc . </FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV> <FONT size=2>could add new low-level components (written in chuck or
any language really) to the pallet of objects.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>The real key is how to do it and keep it accessible! I'm
not aware of any sound design / processing environment which is
accessible.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I'm sure all of this has been done before...</FONT></DIV>
<DIV><FONT size=2>In fact, now that I think of it, there are plugin standards
like VST, etc which must do some of this stuff, but not sure exactly how they
work. When I use VST plugins in cakewalk (which has been made quite accessible
to those using the jaws screen reader on windows), the accessibility of each
plugin itself is completely independant of the accessibility of the host (i.e.
cakewalk). </FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>-- Rich</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=signal.automatique@gmail.com
href="mailto:signal.automatique@gmail.com">Kassen</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=chuck-users@lists.cs.princeton.edu
href="mailto:chuck-users@lists.cs.princeton.edu">ChucK Users Mailing List</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, September 01, 2010 4:33
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [chuck-users] blind
user</DIV>
<DIV><BR></DIV>Rob;<BR><BR>
<DIV class=gmail_quote>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>What attracted me to ChucK was the fact that it is NOT graphically
oriented. </DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>Me too. </DIV>
<DIV><BR></DIV>
<DIV>I often think graphical displays in music programs are distracting form
focussing on the sound itself, even.</DIV>
<DIV><BR></DIV>
<DIV>All of that aside; we could go make jabs at MAX and the like or even go
into how many modern plugins have interfaces where no amount of vision will
help you figure out how you are supposed to use them. What really interests me
though is that something like ChucK could/should be a great tool for people
who can't see or can't see that well to make electronic music.</DIV>
<DIV><BR></DIV>
<DIV>I suspect a lot of advances in interface design could be made there, not
just with support for screen-readers, but also things like interface and error
sonification that could help everyone, not just the blind. I think it's a good
thing that there's renewed interest in this.</DIV>
<DIV><BR></DIV>
<DIV>Yours,</DIV>
<DIV>Kas.</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV> </DIV></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>chuck-users mailing
list<BR>chuck-users@lists.cs.princeton.edu<BR>https://lists.cs.princeton.edu/mailman/listinfo/chuck-users<BR></BLOCKQUOTE></BODY></HTML>