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: Journal2 recipe...
On Sat, Nov 29, 2008 at 09:18:12PM -0500, Michael Stone wrote: >Scott, > >This is adequate to bring up a nice journal gui but, unfortunately, >searches yield no documents, presumably because none have been indexed. > >What should I do in order to try out searching? Casual inspection of http://pinot.berlios.de/ suggested that the main 'pinot' GUI can be used to instruct the pinot-dbus-daemon to start indexing useful things like /home/olpc. In the future, it would be helpful if journal2 came with a sample ~/.pinot/config.xml or if its README instructed users to enable indexing in some other fashion. Unsurprisingly, indexing on the XO is quite slow. More interestingly, though, result retrieval and display is slow as well. Perhaps result display is blocked on result retrieval which is, perhaps, competing with an indexing thread in a single low-priority process? Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Journal2 recipe...
Scott, I've wanted to see Journal2 running on an XO for some time so I: 1. flashed 767 onto my XO and installed git. 2. checked out git://dev.laptop.org/users/cscott/journal2. * downloading and recompressing 80 MB of videos is really slow on an XO; please stick these in a submodule. 3. built myself a pinot rpm with your patches... * checkout git://dev.laptop.org/users/cscott/pinot * saved the diff from your pristine source import commit to HEAD; removed debian-specific hunks * checkout pinot from Fedora cvs and, on the F-9 branch, 'cvs up -r pinot_0_85-1_fc9 .' to return to pinot-0.85-1(f9 is on pinot-0.89) * modified the specfile to apply your cumulative patch * make mockbuild MOCKCFG=fedora-9-i386 * posted the result to http://teach.laptop.org/~mstone/pinot.rpm and installed it by 4. yum install pinot for deps, wget the patched pinot, then 'rpm -Uvh --force' updated pinot 5. as olpc, 'mkdir ~/Journal; cd journal2; python gui.py' This is adequate to bring up a nice journal gui but, unfortunately, searches yield no documents, presumably because none have been indexed. What should I do in order to try out searching? Thanks, Michael ___ 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: will there be an 8.2 update ?
On Sat, Nov 29, 2008 at 05:48:17PM -0500, Mikus Grinbergs wrote: >My reason for asking is that I have a problem with Network Manager >0.6 (ticket #8343). If there is a chance that 8.2 will be improved, >I will leave that ticket open. If 8.2's Network Manager will not be >updated, then I can close that ticket as 'wontfix', and instead >write a different ticket against the newer Network Manager. [What >Network Manager 0.7 does/does_not_do needs to be described >differently from what Network Manager 0.6 does/does_not_do.] > >Will a 'fixpack for 8.2' be released ? My rough impression is that if any point releases to 8.2 are made, they will be created at the behest of a deployment via existing country-support procedures. Therefore, I suspect your NM-0.7 ticket will appeal to a larger audience than your 0.6 ticket. However, for completeness, you should also be aware that people with Fedora CVS accounts and access to the joyride drop-boxes can supply new versions of packages for use with 'yum update' for 8.2. Therefore, while I am aware of little specific interest in releasing 8.2-bug-fixes before 9.1, it is technically feasible for interested volunteers to do so of their own accord. Does this help? Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
will there be an 8.2 update ?
Looking at the "official" http://dev.laptop.org/roadmap, it is not clear to me whether an official update to 8.2 (f9) will be released. My reason for asking is that I have a problem with Network Manager 0.6 (ticket #8343). If there is a chance that 8.2 will be improved, I will leave that ticket open. If 8.2's Network Manager will not be updated, then I can close that ticket as 'wontfix', and instead write a different ticket against the newer Network Manager. [What Network Manager 0.7 does/does_not_do needs to be described differently from what Network Manager 0.6 does/does_not_do.] Will a 'fixpack for 8.2' be released ? mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: RetroMessenger on OLPC
The provided executable links dynamically with libwx* So I installed wxGTK-2.8.9-1.fc9.i386 and wxBase-2.8.9-1.fc9.i386 on the XO. Program starts but aborts immediately with the following message: Fatal Error: Mismatch between the program and library build versions detected. The library used 2.8 (no debug, Unicode, compiler with C++ ABI 1002, wx containers, compatibe with 2.4, compatible with 2.6) and your program used 2.8 (no debug, Unicode, compiler with C++ ABI 1002, wx containers, compatibe with 2.6) - Does not sound like a real incompatibility to me. Ton van Overbeek 2008/11/29 M. Peterson <[EMAIL PROTECTED]>: > Hallo > > http://retromessenger.sf.net has a first release for wx Linux. > Kann jemand mal bitte testen, ob es auf OLPC Sugar läuft? > > FWD: >> > Homepage: > http://retromessenger.sf.net > Download: > http://sourceforge.net/project/showfiles.php?group_id=233927&package_id=299091 > Direct-Download: > http://mesh.dl.sourceforge.net/sourceforge/retromessenger/RetroMessenger_V0.02-linux.tar.bz2 > > Please test and reports issues at: > retromessenger-team # lists.sourceforge.net ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Power Management plan for December.
Chris Ball <[EMAIL PROTECTED]> wrote on 11/28/2008 04:18:11 PM: > > Bugs I plan to fix: > > * #2765 -- Need to turn off DCON after some time in idle suspend > * #3732 -- ARP broadcasts don't wake autosuspended laptops This works now and Ricardo has tested it. The remaining bugs in WOL don't affect it. B.t.w. this should be re-phrased as ARP requests for XO's own IP address. Ricardo, Can you update the trac? > * #7981 -- EC mask setting is inefficient > * #9055 -- Create 9.1 test plans for automatic power management > > Bugs I will need significant help to fix: > > * #6818 -- Make the multicast wakeup filter work with collaboration > (Ricardo Carrano?) Again, WOL works as it is supposed to be. The WOL filter wakes up the laptop when it receives a frame destined for a multicast address that the network adapter listens for. That means that as we stand right now the XOs will wake up on reception of every frame destined for the presence service. One way out of this would be to stop the presence service before going to sleep and starting it up again upon coming out of sleep. In that manner presence updates won't wake up the XO, but traffic destined to already running activities will. M.___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
