foo. bar. baz. quux.
Schemep3
From WikiBazQuux
(Difference between revisions)
| Revision as of 20:13, 23 May 2008 Cwbowron (Talk | contribs) ← Previous diff |
Revision as of 20:14, 23 May 2008 Cwbowron (Talk | contribs) Next diff → |
||
| Line 1: | Line 1: | ||
| '''Schemep3''' is a mp3 and flac playback system and database. | '''Schemep3''' is a mp3 and flac playback system and database. | ||
| + | |||
| + | schemep3 is written in MzScheme and uses the MrEd GUI toolkit. | ||
| It is built on top of Jay McCarthy's sqlite module. It uses a slave mplayer process for audio playback. | It is built on top of Jay McCarthy's sqlite module. It uses a slave mplayer process for audio playback. | ||
Revision as of 20:14, 23 May 2008
Schemep3 is a mp3 and flac playback system and database.
schemep3 is written in MzScheme and uses the MrEd GUI toolkit.
It is built on top of Jay McCarthy's sqlite module. It uses a slave mplayer process for audio playback.
If you are interested in the code, please email me at chris SQUIGGLE bowron dizzot us.
Features
- flac
- tags reader
- duration calculation
- parse playback length
- mp3
- id3v1 tag reader
- id3v2 tag reader
- estimates playback length (hacky)
- SQLite Database
- Playlist that accepts dropped files or results from database query
- mplayer wrapper for playback.
- configurable playlist format
- playback order not depend on focus item
- UI for changing ratings
- mark the current playing file in the playlist
- export to m3u (playlist context menu)
- update play count and last played
- album art (folder.jpg)
- playlist ordering (meta-up, meta-down)
- save / restore playlist
- progress bar (implies more communication with mplayer)
- store preferences in db ( scrobbler username, password )
- play next, add to queue
- last.fm submission
- keyboard controls
- enter -> play
- space -> pause
- n,N -> next
To Do
in no partcular order
- database updates from file (add currently works)
- dropping item on playlist adds to the database
- dropping an m3u loads all the files contained in it
- multiple playlists
- better playlist abstraction
- playlist tree?
- switch to using media table index rather than filenames
- store / restore queries
