I’ve been testing msync for close to a month now, and I feel that I can finally say that it’s ready for release. I encountered a few bugs dealing with the efficiency of syncing multiple playlists, wildcards, and syncing albums with the same title, but I’ve fixed those errors and it is working very well now. If you’re interested, make sure you have python 2.5+ with the sqlite and PIL modules installed, and download it.
I’ve approached a point with msync where it seems to be stable enough (i.e. I can’t think of where else to go with/what else to add to the base library). I’m going to start working to test everything for everyday use by starting a library with my music collection and using it to manage my Sansa files. I’ll be sure to post again once I’ve decided to start working on the GUI frontend for it. In the meantime, I’ve attached the help information for anyone interested in seeing what it can do.
Lately I’ve been working on a new project to sync music with my Sansa e260. Unsatisfied with manually moving files on and off of the tiny flash drive, I began work on an application to manage playlists and sync them for me. I’ve gotten it to the point where it scans my music collection, allows me to create playlists, and syncs those playlists with any directory I specify. In the future, I plan on implementing removable device recognition and cover attachment and resizing. It also currently only functions as a command-line client, but there are plans to develop a GUI frontend for it once the base library is stable enough.
Anyway, the project page is available behind the link on the right (or right here).
Mokash is now an official OpenMoko.org project. I’ve just finished copying the current svn repository over to the openmoko.org repository, and that will be the new official repository. The old repository on my home server will occasionally be updated to match the openmoko.org one, but it probably won’t be very often, so don’t come here looking for it. I still need to move the current tickets and such over to the OMO tracker, but that’s not a high priority. Thanks to this, this project will have higher availability (no more monthly reboots or crashes!) and the opportunity to be seen by a larger amount of OpenMoko users.