Re: TamTam Mini Quirks In Build 56
On Sun, Dec 13, 2009 at 10:15:02PM -0800, Caryl Bigenho wrote: OK. Tried it again with build 59. This time it was different. Oh, that's unfortunate. It makes me worry about your hardware now. ;-) I played with it for about 40 mins with no problems until the sound quit! I tried it in TamTam Jam... no sound. I tried it in Speak... no sound. Rebooted... sound was fine! Okay, next time no sound happens, try Ctrl-Alt-Erase to restart Sugar ... before you try the reboot. Also check the volume control. And make sure nothing is plugged in to the green headphone socket. ;-) That's just me covering all the bases. I've not seen a no sound problem with os59 or later. I did a test yesterday with four laptops playing sound from Tam Tam Mini for about 120 minutes, and it didn't go wrong. The sound stopped each time the laptops suspended from being idle, but restarted once I woke them up. This is probably an interesting problem that isn't a problem. How many people are going to play with Tam Tam Mini for 40 minutes? Probably not many. And if they do manage to crash the sound, they can just reboot. If we can reproduce lose the sound after playing for 40 minutes, then we should fix it. I have seen kids who will sit for three hours playing with Tam Tam Mini, if allowed the time. Whether the kid is allowed the time is usually not in our control. A low occurrence frequency of the problem will change how we investigate it; what resources we will deploy for that investigation, but I still think if the problem happens we need to investigate it. Or at least understand it. So, I'll download build 60 now and see what other things I can get to crash! Great, thanks for your testing! -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
TamTam Mini Quirks In Build 56
Hi... I have been playing with Tam Tam Mini in build 56. After playing for a while it will not allow the machine to go home! You can access the Journal and go to the Activities previously opened (including Tam Tam Mini) but there is no way to get back to the home screen. You have to do a force quit with the power button. I have checked to see if this was a special occurrence but I got it to happen 3 times total and have no doubt that it will happen again. Each time, I selected a drum set and instrument. Then I just kept playing with the notes and loops for several minutes. After just a minute or 2, I could still access the home page, but after I kept playing for maybe 5 minutes or so... it would no longer go to home. I tried this on an XO-1 just to see if it was an old bug. A few funny things happened there, but I was always able to get back to the home screen on the XO-1 but not on the XO-1.5. BTW, I didn't realize that Tam Tam Mini had melodic loops available on the keys that aren't assigned to specific notes. Really cool! Lots of fun! Caryl P.S. The build 59 download just finished. I'll install it now. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam Mini Quirks In Build 56
G'day Caryl, That problem sounded interesting, so I tested it myself. I couldn't get it to happen. I was using os60, and I don't think anything relevant was changed between os56 and os60. I wondered if I was trying to do the same thing you were. Could you tell me what action you do to go home? Do you mean pressing the Home View or F3 (single green dot in solid green circle) key above the 4 key? Or Alt/Tab? Or Ctrl/Q? Was an external keyboard attached to the laptop? Were you holding down any of the modifier keys ... the ctrl, shift, fn, alt, alt gr, or shift keys? The Home View key surprisingly doesn't work if any of those are active. If you can get it to happen again, could you tell me if any of the following fixes the symptom without having to restart: 1. Alt/Tab (which should switch to the Journal or any other running activity), 2. Ctrl/Q (which should quit the Tam Tam Mini activity), 3. clicking on the Stop icon at the top right, 4. Ctrl/Alt/Erase (which should restart Sugar only without restarting the operating system), 5. pressing each of the modifier keys once and then releasing them before you try the Home View key. (this would imply a key state is incorrectly latching, something we've seen before after a resume from idle suspend, but we thought we fixed it). -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: TamTam Mini Quirks In Build 56
Hi James, I'll fill in my responses in your message. Boy! These builds come along fast. I haven't had time to test 59 yet and 60 is here already! Is there supposed to be a firmware update along with 60? It was mentioned in the email Adam forwarded, but there was no link. Caryl Date: Mon, 14 Dec 2009 14:55:43 +1100 From: qu...@laptop.org To: cbige...@hotmail.com CC: devel@lists.laptop.org; support-g...@laptop.org Subject: Re: TamTam Mini Quirks In Build 56 G'day Caryl, That problem sounded interesting, so I tested it myself. I couldn't get it to happen. I was using os60, and I don't think anything relevant was changed between os56 and os60. I wondered if I was trying to do the same thing you were. I'll try it again. Right now I have 59 installed so I'll use it. I will also time it to see how long it takes to happen. It may be longer than I thought. Could you tell me what action you do to go home? Do you mean pressing the Home View or F3 (single green dot in solid green circle) key above the 4 key? Or Alt/Tab? Or Ctrl/Q? First I clicked on the stop sign icon. That took me to the Journal. I tried the F3 key to go home. It didn't work. From the Journal I was able to get back to TamTam and to the other Activities in the Journal, but when they were closed I ended up back in the Journal. I was locked in! Was an external keyboard attached to the laptop? No, just the laptop. I hope someday a small piano-type will be able to interface with the XO. Were you holding down any of the modifier keys ... the ctrl, shift, fn, alt, alt gr, or shift keys? The Home View key surprisingly doesn't work if any of those are active. No, just the Home View key If you can get it to happen again, could you tell me if any of the following fixes the symptom without having to restart: I'll check it out and let you know one way or another what happens. 1. Alt/Tab (which should switch to the Journal or any other running activity), 2. Ctrl/Q (which should quit the Tam Tam Mini activity), 3. clicking on the Stop icon at the top right, 4. Ctrl/Alt/Erase (which should restart Sugar only without restarting the operating system), 5. pressing each of the modifier keys once and then releasing them before you try the Home View key. (this would imply a key state is incorrectly latching, something we've seen before after a resume from idle suspend, but we thought we fixed it). -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam Mini Quirks In Build 56
On Sun, Dec 13, 2009 at 08:35:24PM -0800, Caryl Bigenho wrote: Is there supposed to be a firmware update along with 60? It was mentioned in the email Adam forwarded, but there was no link. Yes, it is included in the build now, and when you next reboot with battery and external power it will be applied. First I clicked on the stop sign icon. That took me to the Journal. I tried the F3 key to go home. It didn't work. From the Journal I was able to get back to TamTam and to the other Activities in the Journal, but when they were closed I ended up back in the Journal. I was locked in! Okay, thanks, that's a better description of the symptom. Interesting. Seems to be related only to Sugar, based on the available information. I'll check it out and let you know one way or another what happens. Thanks! -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: TamTam Mini Quirks In Build 56
OK. Tried it again with build 59. This time it was different. I played with it for about 40 mins with no problems until the sound quit! I tried it in TamTam Jam... no sound. I tried it in Speak... no sound. Rebooted... sound was fine! This is probably an interesting problem that isn't a problem. How many people are going to play with Tam Tam Mini for 40 minutes? Probably not many. And if they do manage to crash the sound, they can just reboot. So, I'll download build 60 now and see what other things I can get to crash! Caryl Date: Mon, 14 Dec 2009 15:47:43 +1100 From: qu...@laptop.org To: cbige...@hotmail.com CC: devel@lists.laptop.org; support-g...@laptop.org Subject: Re: TamTam Mini Quirks In Build 56 On Sun, Dec 13, 2009 at 08:35:24PM -0800, Caryl Bigenho wrote: Is there supposed to be a firmware update along with 60? It was mentioned in the email Adam forwarded, but there was no link. Yes, it is included in the build now, and when you next reboot with battery and external power it will be applied. First I clicked on the stop sign icon. That took me to the Journal. I tried the F3 key to go home. It didn't work. From the Journal I was able to get back to TamTam and to the other Activities in the Journal, but when they were closed I ended up back in the Journal. I was locked in! Okay, thanks, that's a better description of the symptom. Interesting. Seems to be related only to Sugar, based on the available information. I'll check it out and let you know one way or another what happens. Thanks! -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam
On 26.02.2009, at 03:34, Caroline Meeks wrote: http://www.youtube.com/watch?v=31L9qaxOrp0 This is a great demo! I'm trying it on Sugar on a Stick. It works well. Except I can't find a mic button nor can I see how to get to synth through an edit button as demonstrated in the video. I'm on version 50. Any ideas? This is not actually MiniTamTam, but TamTam before it was split into separate activities. A breakup from which it has not fully recovered, yet, since Sugar discourages close coupling between activities. - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam
Why was it broken up, BTW? Can it be put back together? :) It's always been confusing to me how the parts interact. On Thu, Feb 26, 2009 at 6:38 AM, Bert Freudenberg b...@freudenbergs.dewrote: On 26.02.2009, at 03:34, Caroline Meeks wrote: http://www.youtube.com/watch?v=31L9qaxOrp0 This is a great demo! I'm trying it on Sugar on a Stick. It works well. Except I can't find a mic button nor can I see how to get to synth through an edit button as demonstrated in the video. I'm on version 50. Any ideas? This is not actually MiniTamTam, but TamTam before it was split into separate activities. A breakup from which it has not fully recovered, yet, since Sugar discourages close coupling between activities. - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
TamTam
Hi Aaron and other music enthusiasts... Aaron asked for info on how to use TamTam. Here is the MiniTamTam information in Spanish. It has a link to a demo in English on YouTube at: http://www.youtube.com/watch?v=31L9qaxOrp0 Here is one for the synthLab: http://www.youtube.com/watch?v=Nwqt8NMT-zIfeature=related All show an older version of Sugar, but you can get the idea from them. There are other videos on YouTube you might check also. We really need to do a FLOSS manual for the entire TamTam suite during the BookSprint next August. How about it? We really need someone to do the programming to interface an electronic keyboard to the XO. Shouldn't be hard to do since the XO already can recognize usb keyboards...just something that will convert the signal from the music keyboard to what it would be if the corresponding XO key were pressed. This is such a powerful program with a lot of educational potential. We really need to give it more attention. Caryl ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam
Since TamTam uses Csound internally it is actually easier to use a MIDI keyboard than the QWERTY keyboard. It shouldn't be hard to add, but who is maintaining TamTam currently (and where?). I could help with this. Cheers, Andrés 2009/2/25 Caryl Bigenho cbige...@hotmail.com: Hi Aaron and other music enthusiasts... Aaron asked for info on how to use TamTam. Here is the MiniTamTam information in Spanish. It has a link to a demo in English on YouTube at: http://www.youtube.com/watch?v=31L9qaxOrp0 Here is one for the synthLab: http://www.youtube.com/watch?v=Nwqt8NMT-zIfeature=related All show an older version of Sugar, but you can get the idea from them. There are other videos on YouTube you might check also. We really need to do a FLOSS manual for the entire TamTam suite during the BookSprint next August. How about it? We really need someone to do the programming to interface an electronic keyboard to the XO. Shouldn't be hard to do since the XO already can recognize usb keyboards...just something that will convert the signal from the music keyboard to what it would be if the corresponding XO key were pressed. This is such a powerful program with a lot of educational potential. We really need to give it more attention. Caryl ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Andrés ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam
2009/2/25 Caryl Bigenho cbige...@hotmail.com Hi Aaron and other music enthusiasts... Aaron asked for info on how to use TamTam. Here is the MiniTamTam information in Spanish. It has a link to a demo in English on YouTube at: http://www.youtube.com/watch?v=31L9qaxOrp0 This is a great demo! I'm trying it on Sugar on a Stick. It works well. Except I can't find a mic button nor can I see how to get to synth through an edit button as demonstrated in the video. I'm on version 50. Any ideas? Here is one for the synthLab: http://www.youtube.com/watch?v=Nwqt8NMT-zIfeature=related All show an older version of Sugar, but you can get the idea from them. There are other videos on YouTube you might check also. We really need to do a FLOSS manual for the entire TamTam suite during the BookSprint next August. How about it? How about Cards too! We really need someone to do the programming to interface an electronic keyboard to the XO. Shouldn't be hard to do since the XO already can recognize usb keyboards...just something that will convert the signal from the music keyboard to what it would be if the corresponding XO key were pressed. This is such a powerful program with a lot of educational potential. We really need to give it more attention. Caryl ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: Music Keyboard for TamTam?
Hi Gary, This is very exciting and I would love to help test it when it is ready for that. This idea came to mind when I noticed Mexico's OLPC activity information for TamTamMini showed the relationship of the XO keys to those of an actual music keyboard. Why not let the children experience the real thing? You can download their guide here (see page 3 in the TamTamMini instructions): http://www.mochiladigitaltelmex.com.mx/olpc/index.php/Herramientas_pedag%C3%B3gicas As a former music major and the wife of a retired instrumental music teacher, I really would love to have TamTam give students a chance to transfer their skills to music keyboards and mallet instruments. I asked on the olpc-sur list if anyone would use something like this with their students. I got only one reply, but I think it was evidence of the concerns teachers have...they thought it was a great idea except for the cost of the music keyboards. Maybe we need to start a company to make no-frills basic usb music keyboards to sell for about $20-$25 US so that schools in countries with deployments could afford to get some for their music classes. Keep me posted on your progress! Caryl CC: [EMAIL PROTECTED]; devel@lists.laptop.org From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Music Keyboard for TamTam? Date: Tue, 9 Dec 2008 01:12:59 + Hi Caryl, On 4 Dec 2008, at 07:55, Caryl Bigenho wrote: Thanks for all your efforts! 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... Will it work with all of the TamTam Activities? It does not work with any of the TamTam activities yet, but I am digging through TamTamMini to see what's the best way to add this functionality. The Python code is fairly obtuse, likely due to all the copy/paste hacking that it's been through (all 4 activities used to be one big single activity). Right now I've just tested that the standard 8.2-767 release does respond correctly to a USB MIDI keyboard by writing some simple/small CSound code. No special kernel modules, drivers, updates are needed – so it works 'out the box' but we have no current activities that listen for MIDI events just now. Is it likely that all midi keyboards would work? Yes I think so, USB MIDI keyboards being the easiest to use. I also have a MIDI to USB converter kicking around (some other folks sent you links to these), and a bunch of old school MIDI synths and devices that I plan to test function correctly. Would it be possible to put the instructions into language that the less technically inclined could easily follow to get started on this? If I can update TamTamMini the way I intend, you'd just need to plug in a MIDI keyboard and start hitting keys in a tuneful way :-) Does anything have to be changed in the software/hardware to make this easily used by teachers everywhere? New releases of the TamTam Activities (if I manage to get this working). Should just be a software update away for those already running Sugar. 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. M-Audio is what I've used. Doing a quick google, my curiosity was piqued by a roll-up USB piano (49key, velocity sensitive) - it's about £20 here in the UK, ~$40 in the US, any one got one of these? I only ask as it seems both cheap, potentially durable, easy to store, and easy to ship... Pity it doesn't come in green ;-) Could easier use of a midi keyboard be incorporated into a change in the Sugar OS (like 9.1.0)? 8.2 seems to have all the required components. A new control panel module for advance MIDI device configuration could be something for the future, but to be honest that seem like massive over kill, and a potential source of confusion. I've hacked about with keyboards for plenty of years now, and it is almost always the individual client software that deals with fancy MIDI configurations, if needed, and not the OS. Regards, --Gary Or is there an easy way to make the current set-up easier? Thanks again for your interest and efforts! Caryl Date: Mon, 1 Dec 2008 20:37:59 -0800 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Music Keyboard for TamTam? CC: [EMAIL PROTECTED]; devel@lists.laptop.org See also http://www.flickr.com/photos/curiouslee/189728345/ Walter and Simon demonstrate MIDI keyboard input into the A-TEST board Taken on July 14, 2006, uploaded July 14, 2006 On Sun, Nov 30, 2008 at 9:16 PM, Gary C Martin
Re: Music Keyboard for TamTam?
Hi Caryl, On 4 Dec 2008, at 07:55, Caryl Bigenho wrote: Thanks for all your efforts! 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... Will it work with all of the TamTam Activities? It does not work with any of the TamTam activities yet, but I am digging through TamTamMini to see what's the best way to add this functionality. The Python code is fairly obtuse, likely due to all the copy/paste hacking that it's been through (all 4 activities used to be one big single activity). Right now I've just tested that the standard 8.2-767 release does respond correctly to a USB MIDI keyboard by writing some simple/small CSound code. No special kernel modules, drivers, updates are needed – so it works 'out the box' but we have no current activities that listen for MIDI events just now. Is it likely that all midi keyboards would work? Yes I think so, USB MIDI keyboards being the easiest to use. I also have a MIDI to USB converter kicking around (some other folks sent you links to these), and a bunch of old school MIDI synths and devices that I plan to test function correctly. Would it be possible to put the instructions into language that the less technically inclined could easily follow to get started on this? If I can update TamTamMini the way I intend, you'd just need to plug in a MIDI keyboard and start hitting keys in a tuneful way :-) Does anything have to be changed in the software/hardware to make this easily used by teachers everywhere? New releases of the TamTam Activities (if I manage to get this working). Should just be a software update away for those already running Sugar. 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. M-Audio is what I've used. Doing a quick google, my curiosity was piqued by a roll-up USB piano (49key, velocity sensitive) - it's about £20 here in the UK, ~$40 in the US, any one got one of these? I only ask as it seems both cheap, potentially durable, easy to store, and easy to ship... Pity it doesn't come in green ;-) Could easier use of a midi keyboard be incorporated into a change in the Sugar OS (like 9.1.0)? 8.2 seems to have all the required components. A new control panel module for advance MIDI device configuration could be something for the future, but to be honest that seem like massive over kill, and a potential source of confusion. I've hacked about with keyboards for plenty of years now, and it is almost always the individual client software that deals with fancy MIDI configurations, if needed, and not the OS. Regards, --Gary Or is there an easy way to make the current set-up easier? Thanks again for your interest and efforts! Caryl Date: Mon, 1 Dec 2008 20:37:59 -0800 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Music Keyboard for TamTam? CC: [EMAIL PROTECTED]; devel@lists.laptop.org See also http://www.flickr.com/photos/curiouslee/189728345/ Walter and Simon demonstrate MIDI keyboard input into the A-TEST board Taken on July 14, 2006, uploaded July 14, 2006 On Sun, Nov 30, 2008 at 9:16 PM, Gary C Martin [EMAIL PROTECTED] wrote: On 1 Dec 2008, at 04:01, Gary C Martin wrote: On 30 Nov 2008, at 22:16, Erik Garrison wrote: On Sun, Nov 30, 2008 at 12:20 AM, Gary C Martin [EMAIL PROTECTED] wrote: On 30 Nov 2008, at 01:29, Erik Garrison wrote: On Mon, Nov 17, 2008 at 8:23 AM, [EMAIL PROTECTED] wrote: ignacio wrote: On Mon, 2008-11-17 at 04:24 +, Gary C Martin wrote: On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 All wontfix means is that they're waiting for someone with a stronger itch to scratch it ;) i really have no idea how such devices are normally presented to the systems, but is it possible that the keyboard is consists of more than one USB device (i.e., via a built-in hub) and that not all the drivers are present on the XO? FWIW, The M-audio systems abide by open midi specifications and are platform-independent. I don't know about the driver situation. There is a program which can be used to dump midi signals to stdout. It might be a good test as it's very simple to configure and its results are very clear, unlike the audio programs you'll want to use. ... and it's called??? Gah! ;-) Just for reference, after connecting the USB Midi keyboard
RE: Music Keyboard for TamTam?
Hello It seems that you need jack in order to connect your usb-midi keyboard to your application http://jackaudio.org/ http://sourceforge.net/projects/bristol a nice keyboard could be , I dont know if linux supports this keyboard KORG nanoKEY 25-Key USB MIDI Controller Keyboard $49.00 http://www.amazon.com/KORG-nanoKEY-25-Key-Controller-Keyboard/dp/B001H2X192/ref=pd_bbs_sr_1?ie=UTF8s=musical-instrumentsqid=1228472814sr=8-1 Fred --- On Thu, 12/4/08, Caryl Bigenho [EMAIL PROTECTED] wrote: From: Caryl Bigenho [EMAIL PROTECTED] Subject: RE: Music Keyboard for TamTam? To: Edward Cherlin OLPC [EMAIL PROTECTED], Gary Martin [EMAIL PROTECTED] Cc: Developers List devel@lists.laptop.org Date: Thursday, December 4, 2008, 8:55 AM Thanks for all your efforts! 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... Will it work with all of the TamTam Activities? Is it likely that all midi keyboards would work? Would it be possible to put the instructions into language that the less technically inclined could easily follow to get started on this? Does anything have to be changed in the software/hardware to make this easily used by teachers everywhere? 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. Could easier use of a midi keyboard be incorporated into a change in the Sugar OS (like 9.1.0)? Or is there an easy way to make the current set-up easier? Thanks again for your interest and efforts! Caryl Date: Mon, 1 Dec 2008 20:37:59 -0800 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Music Keyboard for TamTam? CC: [EMAIL PROTECTED]; devel@lists.laptop.org See also http://www.flickr.com/photos/curiouslee/189728345/ Walter and Simon demonstrate MIDI keyboard input into the A-TEST board Taken on July 14, 2006, uploaded July 14, 2006 On Sun, Nov 30, 2008 at 9:16 PM, Gary C Martin [EMAIL PROTECTED] wrote: On 1 Dec 2008, at 04:01, Gary C Martin wrote: On 30 Nov 2008, at 22:16, Erik Garrison wrote: On Sun, Nov 30, 2008 at 12:20 AM, Gary C Martin [EMAIL PROTECTED] wrote: On 30 Nov 2008, at 01:29, Erik Garrison wrote: On Mon, Nov 17, 2008 at 8:23 AM, [EMAIL PROTECTED] wrote: ignacio wrote: On Mon, 2008-11-17 at 04:24 +, Gary C Martin wrote: On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 All wontfix means is that they're waiting for someone with a stronger itch to scratch it ;) i really have no idea how such devices are normally presented to the systems, but is it possible that the keyboard is consists of more than one USB device (i.e., via a built-in hub) and that not all the drivers are present on the XO? FWIW, The M-audio systems abide by open midi specifications and are platform-independent. I don't know about the driver situation. There is a program which can be used to dump midi signals to stdout. It might be a good test as it's very simple to configure and its results are very clear, unlike the audio programs you'll want to use. ... and it's called??? Gah! ;-) Just for reference, after connecting the USB Midi keyboard amidi -l gives me: [EMAIL PROTECTED] ~]$ amidi -l Dir DeviceName IO hw:1,0,0 Keystation 49e MIDI 1 I'm not at an XO or my development machine now, but looked around the web to try to find some information to help. See: http://www.4front-tech.com/pguide/midi.html Will go read. Does the system have a /dev/midi* when you plug the device in? Yep, I get a /dev/midi1 Do you see anything interesting in the kernel logs returned with dmesg? Unfortunately our kernel configs aren't online anywhere i can find... but I'll check to see if it's enabled. My guess would be not, but perhaps I'm mistaken. I'm trying to hack my way through coding csound, but I've not had much time to play so far. A magic midi data dumping tool would be a nice shortcut to test – FWIW, I can see my M-audio correctly listed on the USB as an available MIDI input device, but not got any further yet. Perhaps cat /dev/midi* if the file(s) exist. Fab, yes, cat/dev/midi1 gives me wild ascii characters each time I press a key, looks like both note and velocity (this particular keyboard doesn't emit pressure but I have another one somewhere that does), also other
Re: Music Keyboard for TamTam?
On Wed, Dec 3, 2008 at 11:55 PM, Caryl Bigenho [EMAIL PROTECTED] wrote: Thanks for all your efforts! 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... Will it work with all of the TamTam Activities? Is it likely that all midi keyboards would work? All MIDI *USB* keyboards. Not those with only the standard MIDI connector, unless we find MIDI to USB converters cheap. Would it be possible to put the instructions into language that the less technically inclined could easily follow to get started on this? As soon as we decide on the technical solution. Plug in your USB MIDI instrument, assign it an instrumental voice in the UI, and play, should about cover it when we have everything put together. Does anything have to be changed in the software/hardware to make this easily used by teachers everywhere? It should be set up so that it Just Works. 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. Google very kindly put this ad up in Google mail next to your message. Yamaha UX16 MIDI/USB $41.99 In Stock Now Free Shipping www.kensprosound.com Could easier use of a midi keyboard be incorporated into a change in the Sugar OS (like 9.1.0)? Or is there an easy way to make the current set-up easier? I leave the rest to the developers. Thanks again for your interest and efforts! Caryl -- Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name And Children are my nation. The Cosmos is my dwelling place, The Truth my destination. http://wiki.sugarlabs.org/go/User:Mokurai ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: Music Keyboard for TamTam?
Thanks for all your efforts! 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... Will it work with all of the TamTam Activities? Is it likely that all midi keyboards would work? Would it be possible to put the instructions into language that the less technically inclined could easily follow to get started on this? Does anything have to be changed in the software/hardware to make this easily used by teachers everywhere? 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. Could easier use of a midi keyboard be incorporated into a change in the Sugar OS (like 9.1.0)? Or is there an easy way to make the current set-up easier? Thanks again for your interest and efforts! Caryl Date: Mon, 1 Dec 2008 20:37:59 -0800 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Music Keyboard for TamTam? CC: [EMAIL PROTECTED]; devel@lists.laptop.org See also http://www.flickr.com/photos/curiouslee/189728345/ Walter and Simon demonstrate MIDI keyboard input into the A-TEST board Taken on July 14, 2006, uploaded July 14, 2006 On Sun, Nov 30, 2008 at 9:16 PM, Gary C Martin [EMAIL PROTECTED] wrote: On 1 Dec 2008, at 04:01, Gary C Martin wrote: On 30 Nov 2008, at 22:16, Erik Garrison wrote: On Sun, Nov 30, 2008 at 12:20 AM, Gary C Martin [EMAIL PROTECTED] wrote: On 30 Nov 2008, at 01:29, Erik Garrison wrote: On Mon, Nov 17, 2008 at 8:23 AM, [EMAIL PROTECTED] wrote: ignacio wrote: On Mon, 2008-11-17 at 04:24 +, Gary C Martin wrote: On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 All wontfix means is that they're waiting for someone with a stronger itch to scratch it ;) i really have no idea how such devices are normally presented to the systems, but is it possible that the keyboard is consists of more than one USB device (i.e., via a built-in hub) and that not all the drivers are present on the XO? FWIW, The M-audio systems abide by open midi specifications and are platform-independent. I don't know about the driver situation. There is a program which can be used to dump midi signals to stdout. It might be a good test as it's very simple to configure and its results are very clear, unlike the audio programs you'll want to use. ... and it's called??? Gah! ;-) Just for reference, after connecting the USB Midi keyboard amidi -l gives me: [EMAIL PROTECTED] ~]$ amidi -l Dir DeviceName IO hw:1,0,0 Keystation 49e MIDI 1 I'm not at an XO or my development machine now, but looked around the web to try to find some information to help. See: http://www.4front-tech.com/pguide/midi.html Will go read. Does the system have a /dev/midi* when you plug the device in? Yep, I get a /dev/midi1 Do you see anything interesting in the kernel logs returned with dmesg? Unfortunately our kernel configs aren't online anywhere i can find... but I'll check to see if it's enabled. My guess would be not, but perhaps I'm mistaken. I'm trying to hack my way through coding csound, but I've not had much time to play so far. A magic midi data dumping tool would be a nice shortcut to test – FWIW, I can see my M-audio correctly listed on the USB as an available MIDI input device, but not got any further yet. Perhaps cat /dev/midi* if the file(s) exist. Fab, yes, cat/dev/midi1 gives me wild ascii characters each time I press a key, looks like both note and velocity (this particular keyboard doesn't emit pressure but I have another one somewhere that does), also other controls (volume, pitch blend modulation) trigger comms. I'd say the drivers are good to go, and I need to get back to reading csound documentation and try a demo to pickup the incoming midi feed. OK, really boring but working example (XO 8.2-767): 1) Plug in your USB MIDI input device 2) In terminal run amidi -l it should list something like: Dir DeviceName IO hw:1,0,0 Keystation 49e MIDI 1 3) Make a file bells.csd, it MUST be called some_such_or_other.csd, that alone wasted hours of my life :-( here's a what should go in it, the one thing to watch is the -M hw:1,0,0 as this is the option that tells csound which midi device to listen to, if amidi -l shows your MIDI device with a different reference, use that instead: CsoundSynthesizer CsOptions -odac -M hw:1,0,0 /CsOptions CsInstruments instr 1 idec = 1 iamp ampmidi
Re: Music Keyboard for TamTam?
See also http://www.flickr.com/photos/curiouslee/189728345/ Walter and Simon demonstrate MIDI keyboard input into the A-TEST board Taken on July 14, 2006, uploaded July 14, 2006 On Sun, Nov 30, 2008 at 9:16 PM, Gary C Martin [EMAIL PROTECTED] wrote: On 1 Dec 2008, at 04:01, Gary C Martin wrote: On 30 Nov 2008, at 22:16, Erik Garrison wrote: On Sun, Nov 30, 2008 at 12:20 AM, Gary C Martin [EMAIL PROTECTED] wrote: On 30 Nov 2008, at 01:29, Erik Garrison wrote: On Mon, Nov 17, 2008 at 8:23 AM, [EMAIL PROTECTED] wrote: ignacio wrote: On Mon, 2008-11-17 at 04:24 +, Gary C Martin wrote: On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 All wontfix means is that they're waiting for someone with a stronger itch to scratch it ;) i really have no idea how such devices are normally presented to the systems, but is it possible that the keyboard is consists of more than one USB device (i.e., via a built-in hub) and that not all the drivers are present on the XO? FWIW, The M-audio systems abide by open midi specifications and are platform-independent. I don't know about the driver situation. There is a program which can be used to dump midi signals to stdout. It might be a good test as it's very simple to configure and its results are very clear, unlike the audio programs you'll want to use. ... and it's called??? Gah! ;-) Just for reference, after connecting the USB Midi keyboard amidi -l gives me: [EMAIL PROTECTED] ~]$ amidi -l Dir DeviceName IO hw:1,0,0 Keystation 49e MIDI 1 I'm not at an XO or my development machine now, but looked around the web to try to find some information to help. See: http://www.4front-tech.com/pguide/midi.html Will go read. Does the system have a /dev/midi* when you plug the device in? Yep, I get a /dev/midi1 Do you see anything interesting in the kernel logs returned with dmesg? Unfortunately our kernel configs aren't online anywhere i can find... but I'll check to see if it's enabled. My guess would be not, but perhaps I'm mistaken. I'm trying to hack my way through coding csound, but I've not had much time to play so far. A magic midi data dumping tool would be a nice shortcut to test – FWIW, I can see my M-audio correctly listed on the USB as an available MIDI input device, but not got any further yet. Perhaps cat /dev/midi* if the file(s) exist. Fab, yes, cat/dev/midi1 gives me wild ascii characters each time I press a key, looks like both note and velocity (this particular keyboard doesn't emit pressure but I have another one somewhere that does), also other controls (volume, pitch blend modulation) trigger comms. I'd say the drivers are good to go, and I need to get back to reading csound documentation and try a demo to pickup the incoming midi feed. OK, really boring but working example (XO 8.2-767): 1) Plug in your USB MIDI input device 2) In terminal run amidi -l it should list something like: Dir DeviceName IO hw:1,0,0 Keystation 49e MIDI 1 3) Make a file bells.csd, it MUST be called some_such_or_other.csd, that alone wasted hours of my life :-( here's a what should go in it, the one thing to watch is the -M hw:1,0,0 as this is the option that tells csound which midi device to listen to, if amidi -l shows your MIDI device with a different reference, use that instead: CsoundSynthesizer CsOptions -odac -M hw:1,0,0 /CsOptions CsInstruments instr 1 idec = 1 iamp ampmidi 32767 kfrq cpsmidib 2 kenv expsegr 1, idec, 0.1, 0.1, 0.01 asig oscili kenv*iamp, kfrq, 1 out asig endin /CsInstruments CsScore f0 36000 f1 0 16384 10 1 /CsScore /CsoundSynthesizer 4) Then again in console run: csound bells.csd 5) Start pressing keys and make beautiful music, see I said it wasn't too exciting, but nice to get this far :-) The XO speakers don't do very well below middle C (with this instrument), but it's a start. So... hardware/kernel/driver all working in 8.2-767. MIDI input is now demoted to just ;-) a client software side feature for the TamTam activities. I'll do a little more csound reading on the python side and try to hack on TamTamMini, will ping the list if I make useful progress. Regards, --Gary Erik Many thanks, --Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name And Children are my nation. The Cosmos is my dwelling place, The Truth my destination. http://wiki.sugarlabs.org/go/User:Mokurai ___ Devel mailing list Devel@lists.laptop.org http
Re: Music Keyboard for TamTam?
2008/11/15 Caryl Bigenho [EMAIL PROTECTED]: Hi, I was wondering if there would be a way to connect a usb musical keyboard to the XO to use with the TamTam suite of Activities? The software would have to be able to recognize the input from the keyboard. A small 37-key midi keyboard by M-Audio costs about $50. http://www.fullcompass.com/product/324805.html. It supposedly works with any computer with a usb connection, but I suspect they mean any Mac or Windows based machine. With an appropriate USB MIDI driver installed. The programs in the TamTam suite are really powerful, and could appeal to older children and adults if the keyboard input was more suited to their larger hands. Any ideas? We need to add a driver from the usual sources, and we need to modify our music software to accept MIDI from USB as well as from conventional files. This being Linux, the changes required for handling a port as a file are fairly trivial internally, but we need a UI to select USB I/O and to map it to the desired instrument. Once we have this, we get not just MIDI keyboards, but drums, guitars, breath controllers, string controllers, and all the rest, and we can play any instrument from any controller. I am also looking forward to using the second touch screen on an XO-2 as a MIDI controller, with all of the graphical input possibilities that it will allow: keyboard, drums, string tablature, theremin,... I'm not on your mailing list so please just cc your answer to: [EMAIL PROTECTED] Thanks ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name And Children are my nation. The Cosmos is my dwelling place, The Truth my destination. http://wiki.sugarlabs.org/go/User:Mokurai ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Music Keyboard for TamTam?
On Sun, Nov 30, 2008 at 12:20 AM, Gary C Martin [EMAIL PROTECTED] wrote: On 30 Nov 2008, at 01:29, Erik Garrison wrote: On Mon, Nov 17, 2008 at 8:23 AM, [EMAIL PROTECTED] wrote: ignacio wrote: On Mon, 2008-11-17 at 04:24 +, Gary C Martin wrote: On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 All wontfix means is that they're waiting for someone with a stronger itch to scratch it ;) i really have no idea how such devices are normally presented to the systems, but is it possible that the keyboard is consists of more than one USB device (i.e., via a built-in hub) and that not all the drivers are present on the XO? FWIW, The M-audio systems abide by open midi specifications and are platform-independent. I don't know about the driver situation. There is a program which can be used to dump midi signals to stdout. It might be a good test as it's very simple to configure and its results are very clear, unlike the audio programs you'll want to use. ... and it's called??? Gah! ;-) I'm not at an XO or my development machine now, but looked around the web to try to find some information to help. See: http://www.4front-tech.com/pguide/midi.html Does the system have a /dev/midi* when you plug the device in? Do you see anything interesting in the kernel logs returned with dmesg? Unfortunately our kernel configs aren't online anywhere i can find... but I'll check to see if it's enabled. My guess would be not, but perhaps I'm mistaken. I'm trying to hack my way through coding csound, but I've not had much time to play so far. A magic midi data dumping tool would be a nice shortcut to test – FWIW, I can see my M-audio correctly listed on the USB as an available MIDI input device, but not got any further yet. Perhaps cat /dev/midi* if the file(s) exist. Erik ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Music Keyboard for TamTam?
On 30 Nov 2008, at 22:16, Erik Garrison wrote: On Sun, Nov 30, 2008 at 12:20 AM, Gary C Martin [EMAIL PROTECTED] wrote: On 30 Nov 2008, at 01:29, Erik Garrison wrote: On Mon, Nov 17, 2008 at 8:23 AM, [EMAIL PROTECTED] wrote: ignacio wrote: On Mon, 2008-11-17 at 04:24 +, Gary C Martin wrote: On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 All wontfix means is that they're waiting for someone with a stronger itch to scratch it ;) i really have no idea how such devices are normally presented to the systems, but is it possible that the keyboard is consists of more than one USB device (i.e., via a built-in hub) and that not all the drivers are present on the XO? FWIW, The M-audio systems abide by open midi specifications and are platform-independent. I don't know about the driver situation. There is a program which can be used to dump midi signals to stdout. It might be a good test as it's very simple to configure and its results are very clear, unlike the audio programs you'll want to use. ... and it's called??? Gah! ;-) Just for reference, after connecting the USB Midi keyboard amidi -l gives me: [EMAIL PROTECTED] ~]$ amidi -l Dir DeviceName IO hw:1,0,0 Keystation 49e MIDI 1 I'm not at an XO or my development machine now, but looked around the web to try to find some information to help. See: http://www.4front-tech.com/pguide/midi.html Will go read. Does the system have a /dev/midi* when you plug the device in? Yep, I get a /dev/midi1 Do you see anything interesting in the kernel logs returned with dmesg? Unfortunately our kernel configs aren't online anywhere i can find... but I'll check to see if it's enabled. My guess would be not, but perhaps I'm mistaken. I'm trying to hack my way through coding csound, but I've not had much time to play so far. A magic midi data dumping tool would be a nice shortcut to test – FWIW, I can see my M-audio correctly listed on the USB as an available MIDI input device, but not got any further yet. Perhaps cat /dev/midi* if the file(s) exist. Fab, yes, cat/dev/midi1 gives me wild ascii characters each time I press a key, looks like both note and velocity (this particular keyboard doesn't emit pressure but I have another one somewhere that does), also other controls (volume, pitch blend modulation) trigger comms. I'd say the drivers are good to go, and I need to get back to reading csound documentation and try a demo to pickup the incoming midi feed. Erik Many thanks, --Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Music Keyboard for TamTam?
On 1 Dec 2008, at 04:01, Gary C Martin wrote: On 30 Nov 2008, at 22:16, Erik Garrison wrote: On Sun, Nov 30, 2008 at 12:20 AM, Gary C Martin [EMAIL PROTECTED] wrote: On 30 Nov 2008, at 01:29, Erik Garrison wrote: On Mon, Nov 17, 2008 at 8:23 AM, [EMAIL PROTECTED] wrote: ignacio wrote: On Mon, 2008-11-17 at 04:24 +, Gary C Martin wrote: On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 All wontfix means is that they're waiting for someone with a stronger itch to scratch it ;) i really have no idea how such devices are normally presented to the systems, but is it possible that the keyboard is consists of more than one USB device (i.e., via a built-in hub) and that not all the drivers are present on the XO? FWIW, The M-audio systems abide by open midi specifications and are platform-independent. I don't know about the driver situation. There is a program which can be used to dump midi signals to stdout. It might be a good test as it's very simple to configure and its results are very clear, unlike the audio programs you'll want to use. ... and it's called??? Gah! ;-) Just for reference, after connecting the USB Midi keyboard amidi -l gives me: [EMAIL PROTECTED] ~]$ amidi -l Dir DeviceName IO hw:1,0,0 Keystation 49e MIDI 1 I'm not at an XO or my development machine now, but looked around the web to try to find some information to help. See: http://www.4front-tech.com/pguide/midi.html Will go read. Does the system have a /dev/midi* when you plug the device in? Yep, I get a /dev/midi1 Do you see anything interesting in the kernel logs returned with dmesg? Unfortunately our kernel configs aren't online anywhere i can find... but I'll check to see if it's enabled. My guess would be not, but perhaps I'm mistaken. I'm trying to hack my way through coding csound, but I've not had much time to play so far. A magic midi data dumping tool would be a nice shortcut to test – FWIW, I can see my M-audio correctly listed on the USB as an available MIDI input device, but not got any further yet. Perhaps cat /dev/midi* if the file(s) exist. Fab, yes, cat/dev/midi1 gives me wild ascii characters each time I press a key, looks like both note and velocity (this particular keyboard doesn't emit pressure but I have another one somewhere that does), also other controls (volume, pitch blend modulation) trigger comms. I'd say the drivers are good to go, and I need to get back to reading csound documentation and try a demo to pickup the incoming midi feed. OK, really boring but working example (XO 8.2-767): 1) Plug in your USB MIDI input device 2) In terminal run amidi -l it should list something like: Dir DeviceName IO hw:1,0,0 Keystation 49e MIDI 1 3) Make a file bells.csd, it MUST be called some_such_or_other.csd, that alone wasted hours of my life :-( here's a what should go in it, the one thing to watch is the -M hw:1,0,0 as this is the option that tells csound which midi device to listen to, if amidi -l shows your MIDI device with a different reference, use that instead: CsoundSynthesizer CsOptions -odac -M hw:1,0,0 /CsOptions CsInstruments instr 1 idec = 1 iamp ampmidi 32767 kfrq cpsmidib 2 kenv expsegr 1, idec, 0.1, 0.1, 0.01 asig oscili kenv*iamp, kfrq, 1 out asig endin /CsInstruments CsScore f0 36000 f1 0 16384 10 1 /CsScore /CsoundSynthesizer 4) Then again in console run: csound bells.csd 5) Start pressing keys and make beautiful music, see I said it wasn't too exciting, but nice to get this far :-) The XO speakers don't do very well below middle C (with this instrument), but it's a start. So... hardware/kernel/driver all working in 8.2-767. MIDI input is now demoted to just ;-) a client software side feature for the TamTam activities. I'll do a little more csound reading on the python side and try to hack on TamTamMini, will ping the list if I make useful progress. Regards, --Gary Erik Many thanks, --Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Music Keyboard for TamTam?
On Mon, Nov 17, 2008 at 8:23 AM, [EMAIL PROTECTED] wrote: ignacio wrote: On Mon, 2008-11-17 at 04:24 +, Gary C Martin wrote: On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 All wontfix means is that they're waiting for someone with a stronger itch to scratch it ;) i really have no idea how such devices are normally presented to the systems, but is it possible that the keyboard is consists of more than one USB device (i.e., via a built-in hub) and that not all the drivers are present on the XO? FWIW, The M-audio systems abide by open midi specifications and are platform-independent. I don't know about the driver situation. There is a program which can be used to dump midi signals to stdout. It might be a good test as it's very simple to configure and its results are very clear, unlike the audio programs you'll want to use. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Music Keyboard for TamTam?
On 30 Nov 2008, at 01:29, Erik Garrison wrote: On Mon, Nov 17, 2008 at 8:23 AM, [EMAIL PROTECTED] wrote: ignacio wrote: On Mon, 2008-11-17 at 04:24 +, Gary C Martin wrote: On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 All wontfix means is that they're waiting for someone with a stronger itch to scratch it ;) i really have no idea how such devices are normally presented to the systems, but is it possible that the keyboard is consists of more than one USB device (i.e., via a built-in hub) and that not all the drivers are present on the XO? FWIW, The M-audio systems abide by open midi specifications and are platform-independent. I don't know about the driver situation. There is a program which can be used to dump midi signals to stdout. It might be a good test as it's very simple to configure and its results are very clear, unlike the audio programs you'll want to use. ... and it's called??? Gah! ;-) I'm trying to hack my way through coding csound, but I've not had much time to play so far. A magic midi data dumping tool would be a nice shortcut to test – FWIW, I can see my M-audio correctly listed on the USB as an available MIDI input device, but not got any further yet. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Music Keyboard for TamTam?
ignacio wrote: On Mon, 2008-11-17 at 04:24 +, Gary C Martin wrote: On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 All wontfix means is that they're waiting for someone with a stronger itch to scratch it ;) i really have no idea how such devices are normally presented to the systems, but is it possible that the keyboard is consists of more than one USB device (i.e., via a built-in hub) and that not all the drivers are present on the XO? paul =- paul fox, [EMAIL PROTECTED] give one laptop, get one laptop --- http://www.amazon.com/xo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: Music Keyboard for TamTam?
Hi Gary, I'm glad others are interested in this possible extension of the use of the XO. I got the idea when I saw the OLPCMEXICO guide to TamTamMini. They show the correspondence of the XO keys with a standard keyboard. You don't need to know Spanish to understand what they are showing. You can download their guide here: http://www.mochiladigitaltelmex.com.mx/olpc/index.php/Herramientas_pedag%C3%B3gicas Greg Smith was the speaker at our Support-Gang conference call meeting today. He indicated that we can submit ideas for additions to the next release, 9.1.0, to come out in March. I was going to submit the keyboard input fix in his Roadmap section: http://wiki.laptop.org/go/Feature_roadmap Would you like to join me as co-champions of the idea? You can submit it and include me, or I can do it and include you, whichever you prefer. We can each go over the proposal and edit collaboratively (OLPC style!). I think the educational value is great. Children can be learning a standard keyboard as they play with the TamTam suite and it will transfer to other instruments they may want to try later in life...not just piano and organ, but mallet instruments like marimba as well. Do you have any idea how well in tune the XO is? If you play an A is it 440? If it is in tune, it can also help children develop an excellent sense of pitch that will help them all their lives (a survey of adults with perfect pitch showed they all began playing an instrument by the age of 8...my Master's Thesis many years ago!). Let's see where we can take this...it would be great to find a source of inexpensive usb keyboards too. They don't have to do anything fancy, just work for input. Caryl OLPC Support Volunteer CC: [EMAIL PROTECTED]; [EMAIL PROTECTED] From: [EMAIL PROTECTED] To: devel@lists.laptop.org Subject: Re: Music Keyboard for TamTam? Date: Mon, 17 Nov 2008 04:24:54 + On 17 Nov 2008, at 04:06, Gary C Martin wrote: I was wondering if there would be a way to connect a usb musical keyboard to the XO to use with the TamTam suite of Activities? The software would have to be able to recognize the input from the keyboard. A small 37-key midi keyboard by M-Audio costs about $50. http://www.fullcompass.com/product/324805.html. It supposedly works with any computer with a usb connection, but I suspect they mean any Mac or Windows based machine. The programs in the TamTam suite are really powerful, and could appeal to older children and adults if the keyboard input was more suited to their larger hands. Any ideas? Ooh I've been meaning to test this for a while – so I've just plugged my M-Audio 49-e into the XO (release 8.2-767), and tried each of the TamTam suite... Unfortunately it seems to have no effect :-( This was only a very quick attempt, I'll try a deeper look and see if anything obvious is borked, will likely poke about with csound in the raw and see what I can pick-up: http://wiki.laptop.org/go/CSound I'm guessing this may well work, or at least used to, as I found this flicker shot of Simon and Walter testing an early board prototype :-) http://flickr.com/photos/[EMAIL PROTECTED]/189728345/ Anyone else tried, or can point me in the right direction (is there some /dev I should look for)? OK, replying to my own email (well it is late here) – I can at least see the midi keyboard is being recognised using the terminal amidi command: amidi -l Dir DeviceName IOhw:1,0,0 Ketstation 49e MIDI 1 On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 --Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Music Keyboard for TamTam?
Hi, I was wondering if there would be a way to connect a usb musical keyboard to the XO to use with the TamTam suite of Activities? The software would have to be able to recognize the input from the keyboard. A small 37-key midi keyboard by M-Audio costs about $50. http://www.fullcompass.com/product/324805.html. It supposedly works with any computer with a usb connection, but I suspect they mean any Mac or Windows based machine. The programs in the TamTam suite are really powerful, and could appeal to older children and adults if the keyboard input was more suited to their larger hands. Any ideas? I'm not on your mailing list so please just cc your answer to: [EMAIL PROTECTED] Thanks ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Music Keyboard for TamTam?
Hi Caryl, On 16 Nov 2008, at 04:54, Caryl Bigenho wrote: Hi, I was wondering if there would be a way to connect a usb musical keyboard to the XO to use with the TamTam suite of Activities? The software would have to be able to recognize the input from the keyboard. A small 37-key midi keyboard by M-Audio costs about $50. http://www.fullcompass.com/product/324805.html. It supposedly works with any computer with a usb connection, but I suspect they mean any Mac or Windows based machine. The programs in the TamTam suite are really powerful, and could appeal to older children and adults if the keyboard input was more suited to their larger hands. Any ideas? Ooh I've been meaning to test this for a while – so I've just plugged my M-Audio 49-e into the XO (release 8.2-767), and tried each of the TamTam suite... Unfortunately it seems to have no effect :-( This was only a very quick attempt, I'll try a deeper look and see if anything obvious is borked, will likely poke about with csound in the raw and see what I can pick-up: http://wiki.laptop.org/go/CSound I'm guessing this may well work, or at least used to, as I found this flicker shot of Simon and Walter testing an early board prototype :-) http://flickr.com/photos/[EMAIL PROTECTED]/189728345/ Anyone else tried, or can point me in the right direction (is there some /dev I should look for)? I'm not on your mailing list so please just cc your answer to: [EMAIL PROTECTED] Thanks ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Music Keyboard for TamTam?
On 17 Nov 2008, at 04:06, Gary C Martin wrote: I was wondering if there would be a way to connect a usb musical keyboard to the XO to use with the TamTam suite of Activities? The software would have to be able to recognize the input from the keyboard. A small 37-key midi keyboard by M-Audio costs about $50. http://www.fullcompass.com/product/324805.html. It supposedly works with any computer with a usb connection, but I suspect they mean any Mac or Windows based machine. The programs in the TamTam suite are really powerful, and could appeal to older children and adults if the keyboard input was more suited to their larger hands. Any ideas? Ooh I've been meaning to test this for a while – so I've just plugged my M-Audio 49-e into the XO (release 8.2-767), and tried each of the TamTam suite... Unfortunately it seems to have no effect :-( This was only a very quick attempt, I'll try a deeper look and see if anything obvious is borked, will likely poke about with csound in the raw and see what I can pick-up: http://wiki.laptop.org/go/CSound I'm guessing this may well work, or at least used to, as I found this flicker shot of Simon and Walter testing an early board prototype :-) http://flickr.com/photos/[EMAIL PROTECTED]/189728345/ Anyone else tried, or can point me in the right direction (is there some /dev I should look for)? OK, replying to my own email (well it is late here) – I can at least see the midi keyboard is being recognised using the terminal amidi command: amidi -l Dir DeviceName IOhw:1,0,0 Ketstation 49e MIDI 1 On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 --Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Music Keyboard for TamTam?
On Mon, 2008-11-17 at 04:24 +, Gary C Martin wrote: On a more disappointing note I found this ticket G1G1 tamtam suite should respond to MIDI keyboard input from 10 months ago. Closed. Wont fix :-( https://dev.laptop.org/ticket/6031 All wontfix means is that they're waiting for someone with a stronger itch to scratch it ;) -- Ignacio Vazquez-Abrams [EMAIL PROTECTED] PLEASE don't CC me; I'm already subscribed signature.asc Description: This is a digitally signed message part ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Why we are about to not bother upkeeping TamTam.
C. Scott Ananian wrote: On Tue, Aug 5, 2008 at 5:57 PM, Daniel Drake [EMAIL PROTECTED] wrote: On Tue, 2008-08-05 at 16:16 -0400, jean piche wrote: If you are interested in doing this yourself, here is my approximate plan of action: 1. Test all the builds on latest joyride by installing manually 2. Read the specs about Scott's activity updater (which are on the wiki, I think), in order to fully understand the processes involved in shipping new activity versions Just keeping http://wiki.laptop.org/go/Activities updated would be a good start, and sufficient to ensure that activity updater picks it up. Look at the update_url information on [[Activity bundles]] for alternatives/more information. We only updated the fructose modules for the http://wiki.laptop.org/go/Activities page since it is easy to do and the update_url feature was not really communicated or discussed. It would be nice to communicate such features better beforehand. Best, Simon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Why we are about to not bother upkeeping TamTam.
jean piche wrote: TamTamJam v50 TamTamEdit v49 TamTamSynthLab v50 TamTamMin v48 I dont know why we even bother making new bundles with bug fixes that never get included into the builds. I mean the TamTam you are using is like 8 months old... Anyone care? Hi Jean, I understand that it is not always easy to follow the changing processes to release your software. We tried to make it clearer with the fructose process but tamtam and some other activities did not jump in. In any case it would be nice to send at least an announcement to devel/sugar that a new release has been made. If then - you lack an important part of the release process someone will likely tell you. Best, Simon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Why we are about to not bother upkeeping TamTam.
On Tue, 2008-08-05 at 16:16 -0400, jean piche wrote: TamTamJam v50 TamTamEdit v49 TamTamSynthLab v50 TamTamMin v48 I dont know why we even bother making new bundles with bug fixes that never get included into the builds. I mean the TamTam you are using is like 8 months old... OK, someone has updated the wiki and I've tested the activities on latest joyride. They work. Thanks!! The audio performance problems are still present. Myself and Deepak are working on them. If you have time and interest, your involvement would be very welcome. http://dev.laptop.org/ticket/7603 Thanks! Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Why we are about to not bother upkeeping TamTam.
TamTamJam v50 TamTamEdit v49 TamTamSynthLab v50 TamTamMin v48 I dont know why we even bother making new bundles with bug fixes that never get included into the builds. I mean the TamTam you are using is like 8 months old... Anyone care? On 08-08-05, at 15:56, Christoph Derndorfer wrote: On Tue, Aug 5, 2008 at 9:47 PM, Jean Piché [EMAIL PROTECTED] wrote: g) the oddest issue I ran into is that none of the TamTam activities worked, they all crashed when starting and took Sugar with it, a hardware-reset was needed Has the latest TamTam build been rolled into this joyride? Here's what I got: TamTamJam v48 TamTamEdit v47 TamTamSynthLab v48 TamTamMin v46 Which is also what the latest versions are according to [[Activities/ Joyride]] Christoph jp -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Why we are about to not bother upkeeping TamTam.
On Tue, Aug 05, 2008 at 04:16:32PM -0400, jean piche wrote: Anyone care? I care (random user here). They're cool. Martin pgpOu0r2oHyN4.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Why we are about to not bother upkeeping TamTam.
Where do I find the updated versions then? They're not listed on http://wiki.laptop.org/go/TamTam http://wiki.laptop.org/go/Activities http://wiki.laptop.org/go/Activities/Joyride http://tamtam4olpc.wordpress.com/ Thanks, Christoph On Tue, Aug 5, 2008 at 10:16 PM, jean piche [EMAIL PROTECTED] wrote: TamTamJam v50 TamTamEdit v49 TamTamSynthLab v50 TamTamMin v48 I dont know why we even bother making new bundles with bug fixes that never get included into the builds. I mean the TamTam you are using is like 8 months old... Anyone care? On 08-08-05, at 15:56, Christoph Derndorfer wrote: On Tue, Aug 5, 2008 at 9:47 PM, Jean Piché [EMAIL PROTECTED] wrote: g) the oddest issue I ran into is that none of the TamTam activities worked, they all crashed when starting and took Sugar with it, a hardware-reset was needed Has the latest TamTam build been rolled into this joyride? Here's what I got: TamTamJam v48 TamTamEdit v47 TamTamSynthLab v48 TamTamMin v46 Which is also what the latest versions are according to [[Activities/Joyride]] Christoph jp -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: [EMAIL PROTECTED] -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Why we are about to not bother upkeeping TamTam.
I think the reason for tam tam not opening in joyride is that it expects its files to be in /usr/share/activities/* and not in /home/olpc/activities/* Perhaps fixed in later versions? Victor - Original Message - From: jean piche To: Christoph Derndorfer Cc: devel@lists.laptop.org ; [EMAIL PROTECTED] Sent: Tuesday, August 05, 2008 9:16 PM Subject: Why we are about to not bother upkeeping TamTam. TamTamJam v50 TamTamEdit v49 TamTamSynthLab v50 TamTamMin v48 I dont know why we even bother making new bundles with bug fixes that never get included into the builds. I mean the TamTam you are using is like 8 months old... Anyone care? On 08-08-05, at 15:56, Christoph Derndorfer wrote: On Tue, Aug 5, 2008 at 9:47 PM, Jean Piché [EMAIL PROTECTED] wrote: g) the oddest issue I ran into is that none of the TamTam activities worked, they all crashed when starting and took Sugar with it, a hardware-reset was needed Has the latest TamTam build been rolled into this joyride? Here's what I got: TamTamJam v48 TamTamEdit v47 TamTamSynthLab v48 TamTamMin v46 Which is also what the latest versions are according to [[Activities/Joyride]] Christoph jp -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: [EMAIL PROTECTED] -- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Why we are about to not bother upkeeping TamTam.
In fact, if I put some symlinks in /usr/share/Activities pointing to the installed TamTam, I get it to load and run. - Original Message - From: jean piche To: Christoph Derndorfer Cc: devel@lists.laptop.org ; [EMAIL PROTECTED] Sent: Tuesday, August 05, 2008 9:16 PM Subject: Why we are about to not bother upkeeping TamTam. TamTamJam v50 TamTamEdit v49 TamTamSynthLab v50 TamTamMin v48 I dont know why we even bother making new bundles with bug fixes that never get included into the builds. I mean the TamTam you are using is like 8 months old... Anyone care? On 08-08-05, at 15:56, Christoph Derndorfer wrote: On Tue, Aug 5, 2008 at 9:47 PM, Jean Piché [EMAIL PROTECTED] wrote: g) the oddest issue I ran into is that none of the TamTam activities worked, they all crashed when starting and took Sugar with it, a hardware-reset was needed Has the latest TamTam build been rolled into this joyride? Here's what I got: TamTamJam v48 TamTamEdit v47 TamTamSynthLab v48 TamTamMin v46 Which is also what the latest versions are according to [[Activities/Joyride]] Christoph jp -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: [EMAIL PROTECTED] -- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Why we are about to not bother upkeeping TamTam.
On 5 Aug 2008, at 21:16, jean piche wrote: Anyone care? I care, these are a fab set of activities for kids! It's so sad there seems to be bad blood here :-( I guess it must down to constant shifting APIs (a huge red flag for any activity developer**) and evolving Rainbow (a good but potentially painful thing). --Gary ** Rant: I specifically kept away from _any_ vaguely 'interesting' parts of sugar (colaboration, journal, sound, video – going for just absolute basic python and GTK+ requirements, and even that's needing some triage now) for this very reason, I'm sure a bunch of other much more skilled developers than I are doing the same until there is offered some hope of stability. It's fine if you have a lot of free time to burn, rich parents, or an open minded sponsor – development of something cool is 'cheap as chips', maybe less than a week or two of hacking***. Supporting it over time in the current environment... Now that's another mater entirely. Bit rot is a horrible thing when you are just a sad leaf node. *** I don't include TamTam here, it's clearly a much larger project. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Why we are about to not bother upkeeping TamTam.
On Tue, 2008-08-05 at 16:16 -0400, jean piche wrote: I dont know why we even bother making new bundles with bug fixes that never get included into the builds. I mean the TamTam you are using is like 8 months old... Many thanks for producing the releases. Sorry for my slow response. I am planning on getting them into the builds myself, but I have been too busy with other work. If you are interested in doing this yourself, here is my approximate plan of action: 1. Test all the builds on latest joyride by installing manually 2. Read the specs about Scott's activity updater (which are on the wiki, I think), in order to fully understand the processes involved in shipping new activity versions 3. Make whatever modifcations are needed to include the newer bundles in the build I think step 3 may just be modifying a page on the wiki, but I'm not sure, which is why step 2 is there. Thanks apologies for slowness! Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Why we are about to not bother upkeeping TamTam.
On Tue, Aug 5, 2008 at 5:57 PM, Daniel Drake [EMAIL PROTECTED] wrote: On Tue, 2008-08-05 at 16:16 -0400, jean piche wrote: If you are interested in doing this yourself, here is my approximate plan of action: 1. Test all the builds on latest joyride by installing manually 2. Read the specs about Scott's activity updater (which are on the wiki, I think), in order to fully understand the processes involved in shipping new activity versions Just keeping http://wiki.laptop.org/go/Activities updated would be a good start, and sufficient to ensure that activity updater picks it up. Look at the update_url information on [[Activity bundles]] for alternatives/more information. I believe that 6673 used to prevent TamTam from playing sounds (a five month old bug), but it looks like Nat finally fixed this in TamTam git 8 days ago? --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] TamTam is broken in jhbuild.
Right now there are several issues that makes it not work. So I removed it from the mod list for now... Marco On Fri, May 30, 2008 at 8:50 PM, Eben Eliason [EMAIL PROTECTED] wrote: I'm trying to get jhbuild setup on Ubuntu. I have everything working, but the tamtam module won't build, and fails because it can't locate setup.py. The build script (scripts/bundlemodule.py) just attempts to call (within the do_build method) python setup.py build in the source directory, whereas the tamtam module has a setup.sh file which references individual setup.py files in each activity subdirectory instead. This error was introduced with the rearrangement of the modules in the following commit: http://dev.laptop.org/git?p=sugar-jhbuild;a=commitdiff;h=a742ce634d9d1a9bf5f02925097c6c9cf1bf8ccd I don't know if the fix belongs in the jhbuild scripts or in the tamtam module, but it would be nice to clear this up either way. Thanks! - Eben ___ Sugar mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/sugar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
I don't think using the aclient is the better way to make it work on Debian. This client was build very tight to save cpu cycles on the XO. The better way is to use the Python API for Csound... (with the API, don't forget to remove -n flag (no sound) in tamtamorc.csd). Maybe James can tell you more about aclient.so I did not look closely so did not realize that python-csound is not used. Anyway I'd rather keep changes from the XO version at a minimum for now and not add extra code. The goal is to get it working first. When tested on jhbuild, we've got erratic sound.Good luck! No sound at all here, not even erratic. One important issue I forgot to mention yesterday: there are no licensing headers or copyright files in the sources except in Clooper/audio.cpp which comes from ALSA. Can you when time permits add any kind of copyright notice along the source files? It is impossible to upload to either Debian or Ubuntu otherwise. Absolutely! Thanks for the warning... Can you say which license will it be until you get around to adding it to the sources so I get a head start with packaging. While adding headers to all files is a lot of work and probably preferable, adding a LICENSE file in each xo would do too. Jani ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
Perhaps the multiple apps using the soundcard are using dmix, in which
case, you might want to see if you can get csound connected to it too.
(-odac:dmix i think). However I never bothered with dmix as it is one
awkward piece of software.
insert_score_event(): invalid instrument number or name
This generated by insert_score_event() (musmon.c), in the csound
library:
i = (int) fabs((double) p[1]);
if ((unsigned int) (i - 1) = (unsigned int) csound-maxinsno ||
csound-instrtxtp[i] == NULL) {
csoundMessage(csound, Str(insert_score_event(): invalid
instrument
number or name\n));
This indicates something amiss with the CSD file, the instrument has not
been
found, 'i' is p-field 1 in the score event and and should be an index to a
valid
instrument name/number.
Not sure why, but could be something in the csd parsing. Examining the csd
tamtam generated might give us a clue.
Victor
- Original Message -
From: Jani Monoses [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, April 19, 2008 3:10 PM
Subject: Re: TamTam packaging
New packages have made into debian testing. You might want to try
those. Also remember you need to set the OPCODEDIR (OPCODEDIR64 in
your case) so the csound library can find the plugins (plugins in
csound include opcode plugins and realtime output modules).
Actually csound works from the command line iff no other app is using
the sound card.
Multiple apps can play simultaneously (flash in firefox, mpg123) but
csound is not among them.
It uses ALSA for rtaudio and gives this.
*** Cannot open device 'plughw' for audio output: Device or resource busy
So if no other apps use the sound the pippy sound examples work fine,
but tamtam activities do not work even then, with many lines such as
this one in the logs.
insert_score_event(): invalid instrument number or name
I've attached a full log of tamtam mini in case someone can help to
figure out what could be wrong.
Jani
PortMIDI real time MIDI plugin for Csound
PortAudio real-time audio module for Csound
virtual_keyboard real time MIDI plugin for Csound
0dBFS level = 32768.0
Csound version 5.08 (double samples) Apr 16 2008
libsndfile-1.0.17
UnifiedCSD:
/home/jani/Activities/TamTamMini.activity/common/Resources/tamtamorc.csd
STARTING FILE
Creating options
Creating orchestra
Creating score
orchname: /tmp/fileu5b7q9.orc
scorename: /tmp/filey4hDAb.sco
rtaudio: PortAudio module enabled ... using blocking interface
rtmidi: PortMIDI module enabled
orch compiler:
1091 lines read
opcode homeSine a kki
opcode synthGrain a aa
opcode ControlMatrice i ii
opcode SourceMatrice i i
opcode FxMatrice i i
opcode controller k ii
opcode source a ii
opcode effects a ii
instr 200
instr 5600
instr 5400
instr 5401
instr 5201
instr 5202
instr 5212
instr 6000
instr 5204
instr 5203
Token length extended to 256
instr 5000
instr 5022
instr 5023
instr 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010
instr 5101 5102 5103 5104 5105 5106 5107 5108 5109 5110
instr 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020
instr 5111 5112 5113 5114 5115 5116 5117 5118 5119 5120
instr 5021
LABELS list is full...extending to 10
LABELS list is full...extending to 15
LABELS list is full...extending to 20
LABELS list is full...extending to 25
LABELS list is full...extending to 30
sorting score ...
sread: unexpected char ,
section 1: at position 41
in line 1110 of file input
/home/jani/Activities/TamTamMini.activity/common/Resources/tamtamorc.csd
remainder of line flushed
... done
Csound version 5.08 (double samples) Apr 16 2008
displays suppressed
0dBFS level = 32768.0
orch now loaded
audio buffered in 256 sample-frame blocks
SECTION 1:
ftable 1:
ftable 2:
ftable 4:
ftable 30:
ftable 31:
ftable 32:
ftable 33:
ftable 34:
ftable 35:
ftable 36:
ftable 37:
ftable 38:
ftable 39:
ftable 41:
ftable 42:
ftable 44:
ftable 45:
ftable 5150:
ftable 6001:
ftable 6002:
ftable 6003:
ftable 6004:
new alloc for instr 200:
ALSA lib pcm.c:7075:(snd_pcm_recover) underrun occured
ALSA lib pcm.c:7075:(snd_pcm_recover) underrun occured
/usr/lib/python2.5/site-packages/sugar/graphics/window.py:135: GtkWarning:
gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) ||
widget-parent == GTK_WIDGET (container)' failed
self._vbox.remove(self.toolbox)
rtevent:T 0.304 TT 0.304 M: 0.0 0.0
ftable 5028:
deferred alloc
audio sr = 16000, monaural
opening WAV infile
/home/jani/Activities/TamTamEdit.activity/common/Resources/Sounds/drum1splash
defer length 24000
ftable 5027:
deferred alloc
audio sr = 16000, monaural
opening WAV infile
/home/jani/Activities/TamTamEdit.activity/common/Resources/Sounds/drum1crash
defer length 32000
ftable 5026:
deferred alloc
audio sr = 16000
Re: TamTam packaging
-why are the cpp sources in the MANIFEST and consequently in the xo? At the beginning we TamTam was only one activity with a welcome screen to choose which component to play with. When we were aksed to spilt the activities it was the simplest way for us to manage all activities from one git tree. But all sounds and common images are located only inside TamTamEdit. Ok. But are the c++ sources in common/Util/Clooper/ needed in the final xo? -which versions do you recommend for packaging. Latest are 48 and 49 , depending on the activity Always the latest... even though i'm on the way to make major changes in the way TamTam handle resources (mic recording, synthlab sounds...) to respect OLPC security policy. These changes will complicate once more the port to others system... I got them to build and start on Ubuntu but I have no sound The lib is acsound64 not acsound in debian/ubuntu so the link flag needed a change to rebuild the aclient.so instead of using the one in git. I don't think using the aclient is the better way to make it work on Debian. This client was build very tight to save cpu cycles on the XO. The better way is to use the Python API for Csound... (with the API, don't forget to remove -n flag (no sound) in tamtamorc.csd). Maybe James can tell you more about aclient.so I did not look closely so did not realize that python-csound is not used. Anyway I'd rather keep changes from the XO version at a minimum for now and not add extra code. The goal is to get it working first. One important issue I forgot to mention yesterday: there are no licensing headers or copyright files in the sources except in Clooper/audio.cpp which comes from ALSA. Can you when time permits add any kind of copyright notice along the source files? It is impossible to upload to either Debian or Ubuntu otherwise. thank you Jani ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
Le 08-04-17 à 02:49, Jani Monoses a écrit : -why are the cpp sources in the MANIFEST and consequently in the xo? At the beginning we TamTam was only one activity with a welcome screen to choose which component to play with. When we were aksed to spilt the activities it was the simplest way for us to manage all activities from one git tree. But all sounds and common images are located only inside TamTamEdit. Ok. But are the c++ sources in common/Util/Clooper/ needed in the final xo? No. -which versions do you recommend for packaging. Latest are 48 and 49 , depending on the activity Always the latest... even though i'm on the way to make major changes in the way TamTam handle resources (mic recording, synthlab sounds...) to respect OLPC security policy. These changes will complicate once more the port to others system... I got them to build and start on Ubuntu but I have no sound The lib is acsound64 not acsound in debian/ubuntu so the link flag needed a change to rebuild the aclient.so instead of using the one in git. I don't think using the aclient is the better way to make it work on Debian. This client was build very tight to save cpu cycles on the XO. The better way is to use the Python API for Csound... (with the API, don't forget to remove -n flag (no sound) in tamtamorc.csd). Maybe James can tell you more about aclient.so I did not look closely so did not realize that python-csound is not used. Anyway I'd rather keep changes from the XO version at a minimum for now and not add extra code. The goal is to get it working first. When tested on jhbuild, we've got erratic sound.Good luck! One important issue I forgot to mention yesterday: there are no licensing headers or copyright files in the sources except in Clooper/audio.cpp which comes from ALSA. Can you when time permits add any kind of copyright notice along the source files? It is impossible to upload to either Debian or Ubuntu otherwise. Absolutely! Thanks for the warning... thank you Jani ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
Hi Jani, On Wed, Apr 16, 2008 at 6:44 PM, Jani Monoses [EMAIL PROTECTED] wrote: The lib is acsound64 not acsound in debian/ubuntu so the link flag needed a change to rebuild the aclient.so instead of using the one in git. the lib will have a 64 if csound was built for double (64 bits) precision. Since the OLPC uses the float build it uses a different file (this setup allows a system to have both floats and doubles version of csound without conflicts). Hardcoded paths starting with /home/olpc were changed too but it still does not play any sound - the graphics are stunning though! :) The version of csound for the XO is a modified version which among other things uses the alsa output module by default. The normal version defaults to portaudio. You would need to check whether csound is actually producing sound on your machine. You can use many of the manual examples (e.g. oscil.csd), which are configured for realtime audio. If csound is producing output tamtam should too. I tried it some time ago on a debian machine, and it worked fine. csound is 5.08.0 do you know if that should be OK? yes, the current version of OLPCsound is a cvs version a little later than the official 5.08, but there should be no important changes. Minor change to get it to build with -Werror with g++ 4.2.3 (Ubuntu 8.04) Can you post the error? Cheers, Andrés ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
Hi Andres, the lib will have a 64 if csound was built for double (64 bits) precision. Since the OLPC uses the float build it uses a different file (this setup allows a system to have both floats and doubles version of csound without conflicts). Changing the makefile to link agains libcsound64.so made it build so that is fine. Are there runtime incompatibilities I should be aware of and which could make it not run on debian? Hardcoded paths starting with /home/olpc were changed too but it still does not play any sound - the graphics are stunning though! :) The version of csound for the XO is a modified version which among other things uses the alsa output module by default. The normal version defaults to portaudio. You would need to check whether csound is actually producing sound on your machine. You can use many of the manual examples (e.g. oscil.csd), which are configured for realtime audio. If csound is producing output tamtam should too. I tried it some time ago on a debian machine, and it worked fine. I tried a while ago and it worked and from pippy as well, but the latest package does not. So it is may not be a tamtam issue after all. csound is 5.08.0 do you know if that should be OK? yes, the current version of OLPCsound is a cvs version a little later than the official 5.08, but there should be no important changes. Minor change to get it to build with -Werror with g++ 4.2.3 (Ubuntu 8.04) Can you post the error? two instances of warning: deprecated conversion from string constant to ‘char*’ which are eliminated by the patch I attached yesterday Jani ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
Hi Jani, On Thu, Apr 17, 2008 at 9:43 AM, Jani Monoses [EMAIL PROTECTED] wrote: Changing the makefile to link agains libcsound64.so made it build so that is fine. Are there runtime incompatibilities I should be aware of and which could make it not run on debian? No incompatbilites as long as all the build is the same precision. I tried a while ago and it worked and from pippy as well, but the latest package does not. So it is may not be a tamtam issue after all. New packages have made into debian testing. You might want to try those. Also remember you need to set the OPCODEDIR (OPCODEDIR64 in your case) so the csound library can find the plugins (plugins in csound include opcode plugins and realtime output modules). Can you post the error? two instances of warning: deprecated conversion from string constant to 'char*' which are eliminated by the patch I attached yesterday Jani Thanks! Cheers, Andrés ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
TamTam packaging
Hi Olivier, I have a few questions regarding the .deb packaging of the four TamTam activities. -why are the cpp sources in the MANIFEST and consequently in the xo? -which versions do you recommend for packaging. Latest are 48 and 49 , depending on the activity I got them to build and start on Ubuntu but I have no sound The lib is acsound64 not acsound in debian/ubuntu so the link flag needed a change to rebuild the aclient.so instead of using the one in git. Hardcoded paths starting with /home/olpc were changed too but it still does not play any sound - the graphics are stunning though! :) csound is 5.08.0 do you know if that should be OK? Minor change to get it to build with -Werror with g++ 4.2.3 (Ubuntu 8.04) thanks Jani --- a/common/Util/Clooper/aclient.cpp +++ b/common/Util/Clooper/aclient.cpp @@ -549,8 +549,8 @@ struct TamTamSound csound = csoundCreate(NULL); int argc=3; char **argv = (char**)malloc(argc*sizeof(char*)); -argv[0] = csound; -argv[1] = -m7; +argv[0] = (char *)csound; +argv[1] = (char *)-m7; argv[2] = orc; : ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: TamTam packaging
Hi Jani, First of all, our main goal is to make TamTam runs on the XO. We didn't think yet about porting it to others system... Le 08-04-16 à 17:44, Jani Monoses a écrit : Hi Olivier, I have a few questions regarding the .deb packaging of the four TamTam activities. -why are the cpp sources in the MANIFEST and consequently in the xo? At the beginning we TamTam was only one activity with a welcome screen to choose which component to play with. When we were aksed to spilt the activities it was the simplest way for us to manage all activities from one git tree. But all sounds and common images are located only inside TamTamEdit. -which versions do you recommend for packaging. Latest are 48 and 49 , depending on the activity Always the latest... even though i'm on the way to make major changes in the way TamTam handle resources (mic recording, synthlab sounds...) to respect OLPC security policy. These changes will complicate once more the port to others system... I got them to build and start on Ubuntu but I have no sound The lib is acsound64 not acsound in debian/ubuntu so the link flag needed a change to rebuild the aclient.so instead of using the one in git. I don't think using the aclient is the better way to make it work on Debian. This client was build very tight to save cpu cycles on the XO. The better way is to use the Python API for Csound... (with the API, don't forget to remove -n flag (no sound) in tamtamorc.csd). Maybe James can tell you more about aclient.so ( [EMAIL PROTECTED] ) Hardcoded paths starting with /home/olpc were changed too but it still does not play any sound - the graphics are stunning though! :) csound is 5.08.0 do you know if that should be OK? Minor change to get it to build with -Werror with g++ 4.2.3 (Ubuntu 8.04) thanks Jani --- a/common/Util/Clooper/aclient.cpp +++ b/common/Util/Clooper/aclient.cpp @@ -549,8 +549,8 @@ struct TamTamSound csound = csoundCreate(NULL); int argc=3; char **argv = (char**)malloc(argc*sizeof(char*)); -argv[0] = csound; -argv[1] = -m7; +argv[0] = (char *)csound; +argv[1] = (char *)-m7; argv[2] = orc; : Thanks for trying to make it works on Debian! Olivier ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Handling TamTam Resources...
Hi all, I'm working on sharing resources between our 4 activities with respect to the security policy. It will be very helpfull if you have time to give me your opinion on the problem... Here is the situation: TamTamJam and TamTamSynthLab produce sounds that we want usable by any TamTam activities. Each sounds come with a little text file specifying some attributes of the sound (loop points, crossfade duration, amplitude, ...). Before security policy, all our stuff was saved in .sugar/default/tamtam and all activities was looking there for resources... that was working very well. Now, I moved all permanent saved stuff to DATA_DIR and everything work except that others TamTam activity (e.g. TamTamEdit) can't use sounds saved in TamTamJam's DATA_DIR. Is there a way to let all TamTam activities have access to a common directory? How do think this stuff should be implemented? Thank you very much! Olivier Bélanger TamTam's developer team ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Handling TamTam Resources...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Olivier Bélanger wrote: | Is there a way to let all TamTam activities have access to a common | directory? No. Activities are untrusted code. The security design assumes that every Activity is a trojan horse, unless the user specifically requests otherwise. | How do think this stuff should be implemented? The easiest solution, and the one I recommend, is to make the TamTam activities into a single activity. There is no need to have 4 distinct activities. Switching between screens within one activity seems much more reasonable than running multiple distinct TamTam activities. I cannot keep track of which one is which. If the activities must be separate, I recommend using the P_DOCUMENT_RO model. Whenever SynthLab creates a new sound, it should be added to the datastore as a new entry. TamTamEdit can then run with P_DOCUMENT_RO permission, scan the datastore for all sounds created so far, and load them all. I am not sure about the current state of datastore security; I believe it is minimal. However, if you follow this pattern, you will be appropriately future-proofed. In the Bitfrost design, P_DOCUMENT_RO is mutually exclusive with P_NETWORK by default. If you require both P_DOCUMENT_RO and P_NETWORK for a single activity, you may request this additional permission at install time. When TamTam activities are added before students receive laptops, they will be installed by customization keys, which will also set the desired permissions. - --Ben -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIBUKDUJT6e6HFtqQRAuA1AJ9aiX8cu/DK/XDsBzNc7ta5zu9jNwCfSicH JfAM7kfj6+bFj+5uwau+hqY= =hYOC -END PGP SIGNATURE- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Handling TamTam Resources...
Olivier Bélanger wrote: | Is there a way to let all TamTam activities have access to a common | directory? No. Activities are untrusted code. The security design assumes that every Activity is a trojan horse, unless the user specifically requests otherwise. | How do think this stuff should be implemented? The easiest solution, and the one I recommend, is to make the TamTam activities into a single activity. There is no need to have 4 distinct activities. Switching between screens within one activity seems much more reasonable than running multiple distinct TamTam activities. I cannot keep track of which one is which. Actually, I specifically recommend against this model, myself. The activities each focus on very different overall tasks. One is for composing, another is for performing, yet another is for constructing/editing sounds. I wholeheartedly agree that we need to make them work together as seamlessly as possible, but the do one thing and do it well mantra is one that applies here, I believe. Each interface should be as clean and intuitive as possible, without the need to shuffle around a bunch of different toolbars and views. That's the reason the activity model exists as it does, fullscreen and with identifying icons for each activity. Moreover, keeping them all together emphasizes their interoperability at the expense of generating objects that are available for use in all of sugar. I should be able to make a sound in SynthLab and import that into my Slideshow. I shoul dbe able to record a sound in the Record activity and import that into my TamTamJam session. etc. Finding the correct way to let these activities share objects is crucial to creating the environment we *need* to reach with Sugar as a whole. If the activities must be separate, I recommend using the P_DOCUMENT_RO model. Whenever SynthLab creates a new sound, it should be added to the datastore as a new entry. TamTamEdit can then run with P_DOCUMENT_RO permission, scan the datastore for all sounds created so far, and load them all. This is the method I strongly recommend as well, as it has the advantages I spoke of above. If these objects are created an placed into the Journal, then they can be shared, copied, edited, etc, with any activity that supports their type. - Eben ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Handling TamTam Resources...
Thanks for quick answers! Le 08-04-15 à 20:43, Eben Eliason a écrit : Olivier Bélanger wrote: | Is there a way to let all TamTam activities have access to a common | directory? No. Activities are untrusted code. The security design assumes that every Activity is a trojan horse, unless the user specifically requests otherwise. OK, it's clear! | How do think this stuff should be implemented? The easiest solution, and the one I recommend, is to make the TamTam activities into a single activity. There is no need to have 4 distinct activities. Switching between screens within one activity seems much more reasonable than running multiple distinct TamTam activities. I cannot keep track of which one is which. Actually, I specifically recommend against this model, myself. The activities each focus on very different overall tasks. One is for composing, another is for performing, yet another is for constructing/editing sounds. I wholeheartedly agree that we need to make them work together as seamlessly as possible, but the do one thing and do it well mantra is one that applies here, I believe. Each interface should be as clean and intuitive as possible, without the need to shuffle around a bunch of different toolbars and views. That's the reason the activity model exists as it does, fullscreen and with identifying icons for each activity. At some point in the past, TamTam was only one activity, with a welcome screen to choose which activity to play with. We were asked to split our activities and I think it was a good call. Most of our activities are now very complex and are design for different purposes. I think the split facilitates learning what each of them does... Moreover, keeping them all together emphasizes their interoperability at the expense of generating objects that are available for use in all of sugar. I should be able to make a sound in SynthLab and import that into my Slideshow. I shoul dbe able to record a sound in the Record activity and import that into my TamTamJam session. etc. Finding the correct way to let these activities share objects is crucial to creating the environment we *need* to reach with Sugar as a whole. I am agree with the example of SynthLab's sound imported into SlideShow, that makes sense... but I don't think it's a good idea to share all our resources. Some sounds will be relevent only inside TamTam environment, musical context, very stripped sound with fine tuned loop points, etc... Can we use the datastore without creating an entry in the Journal (kind of private resources)? Actually, TamTam saves tunes in ogg format in the Journal, this is the files that we really want to import in others activities! If the activities must be separate, I recommend using the P_DOCUMENT_RO model. Whenever SynthLab creates a new sound, it should be added to the datastore as a new entry. TamTamEdit can then run with P_DOCUMENT_RO permission, scan the datastore for all sounds created so far, and load them all. This is the method I strongly recommend as well, as it has the advantages I spoke of above. If these objects are created an placed into the Journal, then they can be shared, copied, edited, etc, with any activity that supports their type. OK, I will look at the P_DOCUMENT_RO model. Is there a template or an activity that does this kind of stuff where I can study the code? Olivier ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Correction: TamTam MUST be in /usr/share/activities to work.
We are working on a fix to make it work in /home/olpc. The fix is almost ready but details remain. _ http://jeanpiche.com On 27-Mar-08, at 4:14 PM, Jean Piché wrote: Bryan, You need to use the latest verisons of TamTam found here: http://mock.laptop.org/repos/local.update1/XOS/index.html and install them either in /usr/share/activities or /home/olpc/Activities Until next week, you will not be able to save .ogg files and audiofiles recorded with the mike. Journal will keep projetc normally jp _ http://jeanpiche.com On 27-Mar-08, at 11:20 AM, Bryan Berry wrote: Gary, thanks a lot. This is extremely helpful. and thanks to Bert as well On Thu, 2008-03-27 at 15:03 +, Gary C Martin wrote: On 27 Mar 2008, at 05:25, Bryan Berry wrote: Can anyone tell me how to install TamTam from scratch? Not sure if this is the official way – but hidden in the update- activities.py script from Bert Freudenberg is a very useful link to a whole bunch of .xo builds, not all of which are available on the wiki activities page (I'm not sure why). You can find .xo bundles for the TamTam** activities here: http://mock.laptop.org/repos/local.update1/XOS/index.html ** I believe the original TamTam activity is now considered old, unsupported code, and has been split out into individual activities called TamTamEdit, TamTamJam, TamTamMini, and TamTamSynthLab. Once activities are installed, the new xo_get.py script (which includes Bert's update-activities.py code), is very useful for keeping all installed activities upgraded to the latest versions available. You can download the xo-get.py file from: http://wiki.laptop.org/go/Xo-get Regards, Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: old tamtam in the wild?
On Sun, Mar 16, 2008 at 05:13:47PM -0400, Jean Piche wrote: On 15-Mar-08, at 3:28 PM, [EMAIL PROTECTED] wrote: http://mock.laptop.org/repos/local.update1/XOS/index.html There are 5 TamTam activities in the update1 collection: TamTam, TamTamMini, TamTamEdit, TamTamJam, and TamTamSynthLab. Is TamTam an obsolete version? yes. Would it be sensible to remove it from the update1 repo? Or is it there for a reason? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 694 (TamTam?)
The process for getting things into update.1 has always been defined http://wiki.laptop.org/go/Update.1_process I did a quick search and it looks like you did not follow this process when requesting update. http://dev.laptop.org/ticket/6521 seems to be the ticket requesting their inclusion Please list in it exactly the files you want included and assign to ApprovalForUpdate Dennis On Wednesday 27 February 2008, Jean Piche wrote: Hello, Why are old TamTam builds still being used for update.1 builds, thereby not including current .po files? uptodate versions (and in curent joyride) are: TamTamEdit = 47 TamTamMini = 46 TamTamSynthLab = 48 TamTamJam = 48 according build.log, versions in last build (694) are: TamTamEdit = 45 TamTamMini = 44 TamTamSynthLab = 46 TamTamJam = 46 Weren't the requests from Jim to rebuild for inclusion of new .po files? jp (ethrop) On 26-Feb-08, at 5:40 PM, Build Announcer v2 wrote: http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build694 Changes in build 694 from build: 693 Size delta: 0.26M -etoys 2.3.1894-1 +etoys 2.3.1894-2 -telepathy-salut 0.2.2-1.olpc2 +telepathy-salut 0.2.2-3.olpc2 -Read 41 +Read 44 --- Changes for etoys 2.3.1894-2 from 2.3.1894-1 --- + respin rpm, previous etoys.image was broken (#6548) --- Changes for telepathy-salut 0.2.2-3.olpc2 from 0.2.2-1.olpc2 --- + dev.laptop.org #6483 for stream tube flushing (patch really applied) + dev.laptop.org #6483 for stream tube flushing (patch applied) --- Changes for Read 44 from 41 --- + fix unused_download_tubes problem, #6540 (gdesmott) + Pickup translations + Add mimetypes for djvu/tiff -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/update.1-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: new FRS blocker 4418 - no sound in tamtam
It would appear that nothing's able to play sounds; see my latest followup: https://dev.laptop.org/ticket/4418 On Tue, 23 Oct 2007 22:23:23 -0400 Walter Bender [EMAIL PROTECTED] wrote: Is pippy able to play sounds? -walter On 10/23/07, Andres Salomon [EMAIL PROTECTED] wrote: On Wed, 24 Oct 2007 02:54:56 +0200 Marco Pesenti Gritti [EMAIL PROTECTED] wrote: On 10/24/07, Andres Salomon [EMAIL PROTECTED] wrote: I've noticed this as well; note that the MIC LED comes on *after* X starts, while sugar is being initialized. We also see the following message on the console: [ 91.166430] snd-malloc: invalid device type 0 I'm not sure what userspace is doing yet to trigger that, but if the sugar folks could isolate it, that'd be helpful. Strace FTW? I suspect the sugar startup sound because it went on git master and not on the trial-3 branch. I'm unable to test on a XO right now but it should be easy to verify by deleting the sound file: /usr/share/sugar/data/startup.flac Marco Well, the sugar startup sound is what's triggering it (moving startup.flac out of the way causes the MIC LED to not come on).. However, tamtam still appears to be broken (and the MIC LED comes on when we start tamtam). ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: new FRS blocker 4418 - no sound in tamtam
Hi Jean, We are finished with Trial-3 branch. I need to let cscott send out the details of the new build system since I'm not very familiar with. For the next few days I'll assume issues like this bug (sound not working) are probably caused by something in the build process. So changing owner to jg or cscott is appropriate. Thanks, Kim On 10/23/07, Jean Piché [EMAIL PROTECTED] wrote: Hello, We develop almost entirely on the machine itself or in jhbuild. What does the joyride build entail and why would TamTam fail in it? Does sound work otherwise? Does csound work otherwise? A wiki search on joyride brings up almost no information. jp On 23-Oct-07, at 3:45 PM, Kim Quirk wrote: Latest joyride build, 81. Also, I recommend putting notes in the Test Group Release Notes page to help others decide whether they want to load a particular build.: http://wiki.laptop.org/go/Test_Group_Release_Notes ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: new FRS blocker 4418 - no sound in tamtam
FYI, sound doesn't work for lots of activities on joyride-81 (pippy for example). I doubt the problem is TamTam specific. Note that the microphone is on (or at least the LED indicator) by default. This suggests that perhaps alsa is not being initialized properly in the build. -walter On 10/23/07, Kim Quirk [EMAIL PROTECTED] wrote: Hi Jean, We are finished with Trial-3 branch. I need to let cscott send out the details of the new build system since I'm not very familiar with. For the next few days I'll assume issues like this bug (sound not working) are probably caused by something in the build process. So changing owner to jg or cscott is appropriate. Thanks, Kim On 10/23/07, Jean Piché [EMAIL PROTECTED] wrote: Hello, We develop almost entirely on the machine itself or in jhbuild. What does the joyride build entail and why would TamTam fail in it? Does sound work otherwise? Does csound work otherwise? A wiki search on joyride brings up almost no information. jp On 23-Oct-07, at 3:45 PM, Kim Quirk wrote: Latest joyride build, 81. Also, I recommend putting notes in the Test Group Release Notes page to help others decide whether they want to load a particular build.: http://wiki.laptop.org/go/Test_Group_Release_Notes ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Walter Bender One Laptop per Child http://laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: new FRS blocker 4418 - no sound in tamtam
On 10/24/07, Andres Salomon [EMAIL PROTECTED] wrote: I've noticed this as well; note that the MIC LED comes on *after* X starts, while sugar is being initialized. We also see the following message on the console: [ 91.166430] snd-malloc: invalid device type 0 I'm not sure what userspace is doing yet to trigger that, but if the sugar folks could isolate it, that'd be helpful. Strace FTW? I suspect the sugar startup sound because it went on git master and not on the trial-3 branch. I'm unable to test on a XO right now but it should be easy to verify by deleting the sound file: /usr/share/sugar/data/startup.flac Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: new FRS blocker 4418 - no sound in tamtam
On Wed, 24 Oct 2007 02:54:56 +0200 Marco Pesenti Gritti [EMAIL PROTECTED] wrote: On 10/24/07, Andres Salomon [EMAIL PROTECTED] wrote: I've noticed this as well; note that the MIC LED comes on *after* X starts, while sugar is being initialized. We also see the following message on the console: [ 91.166430] snd-malloc: invalid device type 0 I'm not sure what userspace is doing yet to trigger that, but if the sugar folks could isolate it, that'd be helpful. Strace FTW? I suspect the sugar startup sound because it went on git master and not on the trial-3 branch. I'm unable to test on a XO right now but it should be easy to verify by deleting the sound file: /usr/share/sugar/data/startup.flac Marco Well, the sugar startup sound is what's triggering it (moving startup.flac out of the way causes the MIC LED to not come on).. However, tamtam still appears to be broken (and the MIC LED comes on when we start tamtam). ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: new FRS blocker 4418 - no sound in tamtam
Is pippy able to play sounds? -walter On 10/23/07, Andres Salomon [EMAIL PROTECTED] wrote: On Wed, 24 Oct 2007 02:54:56 +0200 Marco Pesenti Gritti [EMAIL PROTECTED] wrote: On 10/24/07, Andres Salomon [EMAIL PROTECTED] wrote: I've noticed this as well; note that the MIC LED comes on *after* X starts, while sugar is being initialized. We also see the following message on the console: [ 91.166430] snd-malloc: invalid device type 0 I'm not sure what userspace is doing yet to trigger that, but if the sugar folks could isolate it, that'd be helpful. Strace FTW? I suspect the sugar startup sound because it went on git master and not on the trial-3 branch. I'm unable to test on a XO right now but it should be easy to verify by deleting the sound file: /usr/share/sugar/data/startup.flac Marco Well, the sugar startup sound is what's triggering it (moving startup.flac out of the way causes the MIC LED to not come on).. However, tamtam still appears to be broken (and the MIC LED comes on when we start tamtam). -- Walter Bender One Laptop per Child http://laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: #2633 NORM Trial-3: TamTam needs R/W access to home directory, not included in Rainbow
On Wed, 2007-08-15 at 20:28 -0400, Owen Williams wrote: What's the best way to implement this change and maintain compatibility? If SUGAR_ACTIVITY_ROOT exists, use it, but if not, use HOME? Well, SUGAR_ACTIVITY_ROOT should always exist when your activity is ran inside Sugar, regardless of rainbow. If you want to maintain compatibility with older versions of Sugar, I think you could just make a dir like ~/.sugar/[SUGAR_PROFILE]/[my_activity_service_name] and save your data in there. Regards, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: #2633 NORM Trial-3: TamTam needs R/W access to home directory, not included in Rainbow
What's the best way to implement this change and maintain compatibility? If SUGAR_ACTIVITY_ROOT exists, use it, but if not, use HOME? owen On Wed, 2007-08-15 at 22:49 +, Zarro Boogs per Child wrote: #2633: TamTam needs R/W access to home directory, not included in Rainbow ---+ Reporter: mburns| Owner: mburns Type: task | Status: assigned Priority: normal| Milestone: Trial-3 Component: security | Version: Build 239 Resolution:|Keywords: Verified: 0 | ---+ Comment (by mburns): The Rainbow RPMs are now in Fedora. Using the environment variable SUGAR_ACTIVITY_ROOT, we add both the 'conf' and the 'data' directories for persistent files. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] TamTam for Trial-2
Hi, On Mon, 2007-07-02 at 11:10 -0400, Jean Piché wrote: The following features will depend on Mesh and Journal stability/ usability over the next few days: Network synchronisation for TamTamJam (many machines can improvise/ play together on a shared pulse) Some Journal functionality to save and load TamTam tunes Regarding the journal support, if you can write to and read from a file on the fs (from python), then adding journal support will be trivial. Thanks, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
