<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Hi Julien,<br><br>So, the best way to start this message is to say you are in for a world of<br>hurt. Prototype code is not likely to be fun.<br><br>You can get hold of a file below for version 0.60.0p. You should be<br>able to do the following;<br><br>./configure --disable-x11<br>make<br><br>You might get past this point - lets see. If not mail me, either onlist<br>or off, I prefer off as we will be dealing with specifics of your system<br>and my proto code. If you have issues with the interface design then <br>it should naturally be onlist as that will be interesting to more people.<br><br>You will still need X11 headers and probably libraries to build it, I <br>will work that out of the final release. The final code will not link to<br>the X11 libraries but it still builds the libbrightonX11 as well as<br>something called libbrightonC11 for command line only.<br><br>http://bristol.sf.net/files/bristol-0.60.0p.tar.gz<br><br>Assuming this actually compiles and installs then you can do the <br>following:<br><br>startBristol -cli -mini<br><br>For anybody else who wants to play with the CLI then building the<br>code WITHOUT '--disable-x11' will be able to use the CLI at the same<br>time as the GUI with the following options:<br><br>startBristol -cli -pro1 -window<br><br>Change a CLI parameter and the GUI will track it.<br><br>You will get some startup messages, then it should finally say 'Hi!'<br>on the braille. You then have the following commands:<br><br>Cursor motion keys:<br><br> Left/Right - navigate through the parameters.<br> Up/Down - change the parameter values<br><br>The value changes are VERY coarse: +/- 10%, I might make this<br>configurable but this will give you very quick changes to params<br>to hear the differences - if you like them then go for finer adjustment.<br><br>General keys:<br><br>Dont worry too much about these to start with - you have cursor keys:<br>The idea behind JK is the following: j/k is up/down for the parameter<br>value, <Shift> J/K is up/down even more. <Control> J/K is in small<br>amounts to control the parameter value. You can remap them.<br><br> CLI: h left <br> CLI: l right<br> CLI: ^k incmin<br> CLI: k inc<br> CLI: K incmax<br> CLI: ^j decmin<br> CLI: j dec<br> CLI: J decmax<br> CLI: M memUp<br> CLI: m memDown<br> CLI: r read<br> CLI: w write<br> CLI: x toggle<br> CLI: u fineup<br> CLI: d finedown<br> CLI: U up<br> CLI: D down<br> CLI: : insert<br><br>At the moment I don't handle <Shift> or <Control> on the Up/Down<br>
cursor keys but I will work that into an eventual release.<br>
<br>
Mem Up/Down should print a message to say whether the memory<br>is free or assigned.<br><br>You can remap the keys by editing the profile file for the emulator<br>if you want: for the mini it is ~/.brighton/memory/profile/mini. The<br>cursor keys are always available, they do not get put in the profile <br>file. <Control-C> and <Control-D> will quit the engine and GUI. <br>You will have to save a memory to get the above text in the profile <br>file: the above mappings are the default ones so do not appear in <br>the profile but when you save it they get placed there.<br><br>The ':' will give you an 'insert mode', a bit like readline but this <br>code is not finalised - eventually it will accept commands to search<br>for synth parameter with completion, have engine commands to <br>adjust its operation. At the moment it just has up/down edit history<br>and quit/exit to leave the app but ^d and ^c do that anyway. As with<br>'vi', every line in ':' mode will print a ':' at the start of the line. To <br>leave it type ESC.<br><br>At the moment I have only added in the parameter descriptions <br>for a few emulators, the others will give you (NULL) or empty <br>parameter descriptions:<br><br> -pro1, -mini, -b3, -juno, -axxe, -bme700<br><br>You will have to tell me if the text is a bit terse/short. If you cannot <br>understand what the parameters do then let me know.<br><br>There are a few emulators that I probably cannot convert to this <br>interface - some of the layered synths (OBXA/BIT/Jupiter/pro10) use<br>some really odd stuff in the GUI to manage the different layers of<br>the synth, they do not lend themselves well to this interface. By the<br>time the code goes out though I should be able to give you a dozen<br>emulators. You can try all of them now but they will not give you much<br>indication of the parameters you are changing.<br><br>To give you an idea of what you can expect if you even get this to<br>compile and install, here is the edited output from:<br><br>% startBristol -cli -mini<br>...<br>going operational: 9af8008, 9af8370<br>Hi nicky!<br>01 Glide : 117<br>02 Mod : 0 <br>03 Osc1 Tranpose : 3 <br>04 Osc2 Tranpose : 2 <br>05 Osc3 Tranpose : 4 <br>06 Osc2 Tuning : 489<br>07 Osc3 Tuning : 526<br>07 Osc3 Tuning : 626<br>07 Osc3 Tuning : 726<br>07 Osc3 Tuning : 826<br>07 Osc3 Tuning : 926<br>07 Osc3 Tuning : 1000<br>07 Osc3 Tuning : 1000<br><br>To get this I used 'l' to navigate to 'Osc3 Tuning' then 'k' to change <br>its value. It could have been done with the cursor keys too. The string<br>that is printed should be the current line, ie, it should not scroll off<br>of your braille display as I don't append a linefeed, it should be<br>prepended.<br><br>The values are represented a 'per mil', they are actually<br>floats and I can make them floats in the display too (perhaps another<br>config option?), it's just that with k, K and ^K you can adjust values<br>with +0.01, +0.1 and +0.001 (respectively). The concept is that <br>j/k is up down. <Shift J/K> is up/down by even more, and then<br><Control J/K> is small, controlled amounts. Made sense to me, if it<br>is not functional I can change it or you can remap the keys.<br><br>I am open to changes to the interface, the data presentation, etc.<br><br>Kind 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: Sun, 11 Apr 2010 21:41:59 +0200<br>> From: julien@c-lab.de<br>> To: nickycopeland@hotmail.com<br>> CC: lsutton@libero.it; linux-audio-dev@lists.linuxaudio.org<br>> Subject: RE: [LAD] Interface development for the blind (starting from Bristol)<br>> <br>> Hello Nick!<br>> Just got back and found a lot of mails. :-) So I'm replying in reverse <br>> order. :-)<br>> VI is fine with me. But cursor keys would be great. Reasons are obvious: We <br>> might know of VI and you seem to be used to it. But many others don't. Second <br>> minor reason: The best hand to fool around with is usually the right one, with <br>> me as well. So the keyboard is to the right of the computer. The cursor keys <br>> are farther to the right of the keyboard, so not so much stretching. And on a <br>> standard keyboard the cursor keys are easier to spot (they have their own <br>> block to themselves.<br>> But of course working with h/l and j/k is very fine to start and see how it <br>> works out. NJo problem about the X-libs having to be there. the ugliness would <br>> have been to start X. It adds overhead and loads of things I don't need, and <br>> thus don't want. :-)<br>> Onto the next mails...<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 /><hr />Hotmail: Trusted email with powerful SPAM protection. <a href='https://signup.live.com/signup.aspx?id=60969' target='_new'>Sign up now.</a></body>
</html>