<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
So it is back on list, good.<br><br>Something I can make available for bristol in the short term is a VI like interface<br>navigate left/right through the synth parameters with h/l and change their values<br>down/up with j/k (with shift key accelerators and control key decelerators).<br><br>The nice thing about the interface is that the parameter control can be done quickly<br>with one hand whilst the other one plays the piano. A readline interface might need <br>both hands on the QWERTY to change a value. <br><br>Each change in these keys results in a short line of text output giving parameter<br>name/value and the audible signal output from the synth. I have this operational already<br>for bristol although I would give it a couple of days to clean up some pretty gruesome<br>edges (you need to use two terminal, one for GUI one for engine at the moment to get<br>it to work for example) but I can clean them up a lot for sometime next week. The<br>code does not need X11 to be active to work but it does still need X11-dev to compile<br>and X11 run time libraries to operate. It kind of cheats and presents a totally dummy<br>window to the GUI - it thinks it has a window open which I need because of the<br>signal paths used to set parameters in the GUI into the engine.<br><br>Of course, if you don't like VI this is going to be a bit of a pain in the butt - I love it<br>which is why I took it as a starting point. Medium term I can have a mapping file for <br>the keys you want to use.<br><br>I am not sure I could code another audible tone to represent the value of a parameter,<br>the issue is that audio comes from the engine emulator but the GUI or CLI interface<br>is to brighton. To present an audible signal of the parameter value I would have to <br>rework the engine as well. It is possible, but not in the short term.<br><br>This can be a prototype for people to test next week, after that we can work on the<br>necessary refinements. The code is only for the Prophet-1 emulator at the moment.<br>It can have memory save/load options operational. If people really object to VI I can<br>work more on the arrow navigation keys but I would have to configure a very raw <br>interface to get that.<br><br>Regards, nick,.<br><br>"we have to make sure the old choice [Windows] doesn't disappear”.<br>Jim Wong, president of IT products, Acer<br><br><br><br><br>> Date: Fri, 9 Apr 2010 11:54:34 +0200<br>> From: julien@c-lab.de<br>> To: lsutton@libero.it<br>> CC: linux-audio-dev@lists.linuxaudio.org<br>> Subject: Re: [LAD] Interface development for the blind (starting from Bristol)<br>> <br>> Hello Lorenzo!<br>> Using custom tones to mimic movement of sliders or marking the access of an <br>> element (button, list, etc.) is not completely off. I mean graphical apps use <br>> a lot of signalling sounds, so do some text based apps. Yet in the context of <br>> audio software I think it's not very feasable, as my ears would be atuned to <br>> the audio I'm working on, and in any case a realtime app should perform some <br>> change, when I change a slider, push a button.<br>> I hope that helps<br>> Kindly yours<br>> Julien<br>> <br>> --------<br>> Music was my first love and it will be my last (John Miles)<br>> <br>> ======== FIND MY WEB-PROJECT AT: ========<br>> http://ltsb.sourceforge.net<br>> the Linux TextBased Studio guide<br>> ======= AND MY PERSONAL PAGES AT: =======<br>> http://www.juliencoder.de<br>> _______________________________________________<br>> Linux-audio-dev mailing list<br>> Linux-audio-dev@lists.linuxaudio.org<br>> http://lists.linuxaudio.org/listinfo/linux-audio-dev<br> <br /><hr />Hotmail: Trusted email with Microsoft’s powerful SPAM protection. <a href='https://signup.live.com/signup.aspx?id=60969' target='_new'>Sign up now.</a></body>
</html>