<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Thanks for all your efforts!<br><br>The last time I used a midi keyboard with a Mac (it was a G3) it had to have a special "midi interface" and then was just "plug and play" from there using Finale as a program. In looking over your discussion below, it looks like you did manage to get a midi keyboard to work with the XO, but with great difficulty. Some questions...<br><br>Will it work with all of the TamTam Activities?<br><br>Is it likely that all midi keyboards would work?<br><br>Would it be possible to put the instructions into language that the less technically inclined could easily follow to get started on this?<br><br>Does anything have to be changed in the software/hardware to make this easily used by teachers everywhere?<br><br>Do you know of any source of very simple, inexpensive midi keyboards? No bells and whistles needed, they are already in the XO in the TamTam Activities.<br><br>Could easier use of a midi keyboard be incorporated into a change in the Sugar OS (like 9.1.0)?<br><br>Or is there an easy way to make the current set-up easier?<br><br>Thanks again for your interest and efforts!<br><br>Caryl<br><br><br><br>> Date: Mon, 1 Dec 2008 20:37:59 -0800<br>> From: echerlin@gmail.com<br>> To: gary@garycmartin.com<br>> Subject: Re: Music Keyboard for TamTam?<br>> CC: cbigenho@hotmail.com; devel@lists.laptop.org<br>> <br>> See also<br>> <br>> http://www.flickr.com/photos/curiouslee/189728345/<br>> <br>> Walter and Simon demonstrate MIDI keyboard input into the A-TEST board<br>> Taken on July 14, 2006, uploaded July 14, 2006<br>> <br>> On Sun, Nov 30, 2008 at 9:16 PM, Gary C Martin <gary@garycmartin.com> wrote:<br>> > On 1 Dec 2008, at 04:01, Gary C Martin wrote:<br>> ><br>> >> On 30 Nov 2008, at 22:16, Erik Garrison wrote:<br>> >><br>> >>> On Sun, Nov 30, 2008 at 12:20 AM, Gary C Martin<br>> >>> <gary@garycmartin.com> wrote:<br>> >>>> On 30 Nov 2008, at 01:29, Erik Garrison wrote:<br>> >>>><br>> >>>>> On Mon, Nov 17, 2008 at 8:23 AM, <pgf@laptop.org> wrote:<br>> >>>>>><br>> >>>>>> ignacio wrote:<br>> >>>>>>><br>> >>>>>>> On Mon, 2008-11-17 at 04:24 +0000, Gary C Martin wrote:<br>> >>>>>>>><br>> >>>>>>>> On a more disappointing note I found this ticket "G1G1 tamtam<br>> >>>>>>>> suite<br>> >>>>>>>> should respond to MIDI keyboard input" from 10 months ago.<br>> >>>>>>>> Closed.<br>> >>>>>>>> Wont fix :-(<br>> >>>>>>>><br>> >>>>>>>> https://dev.laptop.org/ticket/6031<br>> >>>>>>><br>> >>>>>>> All "wontfix" means is that they're waiting for someone with a<br>> >>>>>>> stronger<br>> >>>>>>> itch to scratch it ;)<br>> >>>>>><br>> >>>>>> i really have no idea how such devices are normally presented to<br>> >>>>>> the systems, but is it possible that the keyboard is consists of<br>> >>>>>> more than one USB device (i.e., via a built-in hub) and that not<br>> >>>>>> all the drivers are present on the XO?<br>> >>>>>><br>> >>>>><br>> >>>>> FWIW, The M-audio systems abide by open midi specifications and are<br>> >>>>> platform-independent. I don't know about the driver situation.<br>> >>>>><br>> >>>>> There is a program which can be used to dump midi signals to<br>> >>>>> stdout.<br>> >>>>> It might be a good test as it's very simple to configure and its<br>> >>>>> results are very clear, unlike the audio programs you'll want to<br>> >>>>> use.<br>> >>>><br>> >>>> ... and it's called??? Gah! ;-)<br>> >><br>> >> Just for reference, after connecting the USB Midi keyboard amidi -l<br>> >> gives me:<br>> >><br>> >> [olpc@xo-0C-E6-BB ~]$ amidi -l<br>> >> Dir Device Name<br>> >> IO hw:1,0,0 Keystation 49e MIDI 1<br>> >><br>> >>> I'm not at an XO or my development machine now, but looked around the<br>> >>> web to try to find some information to help.<br>> >>><br>> >>> See: http://www.4front-tech.com/pguide/midi.html<br>> >><br>> >> Will go read.<br>> >><br>> >>> Does the system have a /dev/midi* when you plug the device in?<br>> >><br>> >> Yep, I get a /dev/midi1<br>> >><br>> >>> Do you see anything interesting in the kernel logs returned with<br>> >>> dmesg?<br>> >>><br>> >>> Unfortunately our kernel configs aren't online anywhere i can find...<br>> >>> but I'll check to see if it's enabled. My guess would be not, but<br>> >>> perhaps I'm mistaken.<br>> >>><br>> >>>> I'm trying to hack my way through coding csound, but I've not had<br>> >>>> much time<br>> >>>> to play so far. A magic midi data dumping tool would be a nice<br>> >>>> shortcut to<br>> >>>> test – FWIW, I can see my M-audio correctly listed on the USB as an<br>> >>>> available MIDI input device, but not got any further yet.<br>> >>><br>> >>> Perhaps cat /dev/midi* if the file(s) exist.<br>> >><br>> >> Fab, yes, cat/dev/midi1 gives me wild ascii characters each time I<br>> >> press a key, looks like both note and velocity (this particular<br>> >> keyboard doesn't emit pressure but I have another one somewhere that<br>> >> does), also other controls (volume, pitch blend & modulation) trigger<br>> >> comms.<br>> >><br>> >> I'd say the drivers are good to go, and I need to get back to reading<br>> >> csound documentation and try a demo to pickup the incoming midi feed.<br>> ><br>> > OK, really boring but working example (XO 8.2-767):<br>> ><br>> > 1) Plug in your USB MIDI input device<br>> ><br>> > 2) In terminal run "amidi -l" it should list something like:<br>> ><br>> > Dir Device Name<br>> > IO hw:1,0,0 Keystation 49e MIDI 1<br>> ><br>> > 3) Make a file bells.csd, it MUST be called <some_such_or_other>.csd,<br>> > that alone wasted hours of my life :-( here's a what should go in it,<br>> > the one thing to watch is the -M hw:1,0,0 as this is the option that<br>> > tells csound which midi device to listen to, if "amidi -l" shows your<br>> > MIDI device with a different reference, use that instead:<br>> ><br>> > <CsoundSynthesizer><br>> > <CsOptions><br>> > -odac -M hw:1,0,0<br>> > </CsOptions><br>> > <CsInstruments><br>> > instr 1<br>> > idec = 1<br>> > iamp ampmidi 32767<br>> > kfrq cpsmidib 2<br>> > kenv expsegr 1, idec, 0.1, 0.1, 0.01<br>> > asig oscili kenv*iamp, kfrq, 1<br>> > out asig<br>> > endin<br>> > </CsInstruments><br>> > <CsScore><br>> > f0 36000<br>> > f1 0 16384 10 1<br>> > </CsScore><br>> > </CsoundSynthesizer><br>> ><br>> > 4) Then again in console run:<br>> ><br>> > csound bells.csd<br>> ><br>> > 5) Start pressing keys and make beautiful music, see I said it wasn't<br>> > too exciting, but nice to get this far :-) The XO speakers don't do<br>> > very well below middle C (with this instrument), but it's a start.<br>> ><br>> > So... hardware/kernel/driver all working in 8.2-767. MIDI input is now<br>> > demoted to just ;-) a client software side feature for the TamTam<br>> > activities. I'll do a little more csound reading on the python side<br>> > and try to hack on TamTamMini, will ping the list if I make useful<br>> > progress.<br>> ><br>> > Regards,<br>> > --Gary<br>> ><br>> >>> Erik<br>> >><br>> >> Many thanks,<br>> >> --Gary<br>> >> _______________________________________________<br>> >> Devel mailing list<br>> >> Devel@lists.laptop.org<br>> >> http://lists.laptop.org/listinfo/devel<br>> ><br>> > _______________________________________________<br>> > Devel mailing list<br>> > Devel@lists.laptop.org<br>> > http://lists.laptop.org/listinfo/devel<br>> ><br>> <br>> <br>> <br>> -- <br>> Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name<br>> And Children are my nation.<br>> The Cosmos is my dwelling place, The Truth my destination.<br>> http://wiki.sugarlabs.org/go/User:Mokurai<br></body>
</html>