Jake Hawkes
2002-02-01 22:40:11 UTC
The filesystem database is a great, easy way to to do it.
Since this is open source, how hard would it be to have a generic interface so that we can develop
interfaces for anything.
Once we start thinking about DBs, it important to realise that everyone is going to want to do it
differently, and some (or most) may have already got a database. That said, it would be up to the
user to develop an interface to their database, or use the existing (implied) filesystem method.
I'm thinking of some way to translate between how the simp3 thinks about tracks to play (filenames
really) and tracks to select (a menu system).
Would the slimp3 still navigate the menu and controll the input etc, but simply display a menu
created by another module? The default would be to have a file system module that hash-ed and
cached filenames from a directory (or directories) and passed (using XML maybe) a menu structure
to the slimp3 to display. Then one could write a module to interface to anything and again
present a menu structure to display.
It would be important to make the slimp work straight of the box, but it would also then be easier
to plug it in to existing systems.
Just my two cents. When I break my leg this saturday skiing I will have alot of time to do this
:)
---
Jacob Hawkes, B. Eng (CSE)
Programmer / Analyst
Metso Automation
jacob.hawkes-***@public.gmane.org
jakehawkes2001-/***@public.gmane.org (while onsite in Venezuela)
__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions!
http://auctions.yahoo.com
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Sponsored by VeriSign - The Value of Trust
Secure all your Web servers now - with a proven 5-part
strategy. The FREE Server Security Guide shows you how.
http://us.click.yahoo.com/iWSNbC/VdiDAA/yigFAA/rIp0lB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, send an email to:
slimp3-dev-unsubscribe-***@public.gmane.org
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Since this is open source, how hard would it be to have a generic interface so that we can develop
interfaces for anything.
Once we start thinking about DBs, it important to realise that everyone is going to want to do it
differently, and some (or most) may have already got a database. That said, it would be up to the
user to develop an interface to their database, or use the existing (implied) filesystem method.
I'm thinking of some way to translate between how the simp3 thinks about tracks to play (filenames
really) and tracks to select (a menu system).
Would the slimp3 still navigate the menu and controll the input etc, but simply display a menu
created by another module? The default would be to have a file system module that hash-ed and
cached filenames from a directory (or directories) and passed (using XML maybe) a menu structure
to the slimp3 to display. Then one could write a module to interface to anything and again
present a menu structure to display.
It would be important to make the slimp work straight of the box, but it would also then be easier
to plug it in to existing systems.
Just my two cents. When I break my leg this saturday skiing I will have alot of time to do this
:)
I've learned two things from building my pre-SliMP3 mp3 system for my
1. The information in the ID3 tags from CDDB is so bad that it's
nearly useless. Nearly every CD I ripped needed to have its ID3
information edited in a major way.
2. Everybody has a different idea of how to organize and categorize
their music.
1. Ignore the ID3 information and use the file name as the song name.
2. Put every song for a given album in its own directory, name that
directory the same as the album.
3. Put every album for a given artist in its own directory and name
that directory for the artist.
4. Create a directory of category directories, each of which contains
artist directories which each contain symlinks to existing album
directories.
I change the categories for a given album by creating and deleting
symlinks, and I can have albums in multiple categories. I can change
the titles of songs/albums/artists by simply renaming files. When
you think of the file system as a particular kind of database, you
realize that it works pretty good.
That said, I think that if we do intend on creating
mood/genre/categories in SliMP3 (and I think we should) we should do
it separately from the organization of the files and store the
information in a simple SliMP3-only database. (Sean: here's a chance
for us to use DBMs like you've always dreamed!) I'd like to avoid
moving or changing the existing MP3 files if at all possible.
NB: I'm a little scared of using MySQL or some other "real" database
because the complexity of it. If someone can cobble together a
demonstration of a database that can maintain our cross-platform
capabilities and be easy to install and invisible to maintain, then
I'd love to be able to use it with SliMP3. Otherwise, let's just
keep on keeping it simple.
-dean
ID3v2 - yes, it is a string
In ID3v1 you could always use the Comments field. Only 30 chars though.
See www.id3.org for full ID3 specs. Note that the MP3::Info module that we
are using may or may not support all the ID3v2 tags desired. Of course that
is just incentive to hack it up to make it better (and send the changes to
the maintainer).
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
=====1. The information in the ID3 tags from CDDB is so bad that it's
nearly useless. Nearly every CD I ripped needed to have its ID3
information edited in a major way.
2. Everybody has a different idea of how to organize and categorize
their music.
1. Ignore the ID3 information and use the file name as the song name.
2. Put every song for a given album in its own directory, name that
directory the same as the album.
3. Put every album for a given artist in its own directory and name
that directory for the artist.
4. Create a directory of category directories, each of which contains
artist directories which each contain symlinks to existing album
directories.
I change the categories for a given album by creating and deleting
symlinks, and I can have albums in multiple categories. I can change
the titles of songs/albums/artists by simply renaming files. When
you think of the file system as a particular kind of database, you
realize that it works pretty good.
That said, I think that if we do intend on creating
mood/genre/categories in SliMP3 (and I think we should) we should do
it separately from the organization of the files and store the
information in a simple SliMP3-only database. (Sean: here's a chance
for us to use DBMs like you've always dreamed!) I'd like to avoid
moving or changing the existing MP3 files if at all possible.
NB: I'm a little scared of using MySQL or some other "real" database
because the complexity of it. If someone can cobble together a
demonstration of a database that can maintain our cross-platform
capabilities and be easy to install and invisible to maintain, then
I'd love to be able to use it with SliMP3. Otherwise, let's just
keep on keeping it simple.
-dean
Can the ID3 Genre be set to an arbitrary string?
ID3v1 - no, it is a one byte numberID3v2 - yes, it is a string
Is there room in the ID3 tags for such a "mood" descriptor?
In ID3v2 there is a Mood tag (TMOO)In ID3v1 you could always use the Comments field. Only 30 chars though.
See www.id3.org for full ID3 specs. Note that the MP3::Info module that we
are using may or may not support all the ID3v2 tags desired. Of course that
is just incentive to hack it up to make it better (and send the changes to
the maintainer).
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
---
Jacob Hawkes, B. Eng (CSE)
Programmer / Analyst
Metso Automation
jacob.hawkes-***@public.gmane.org
jakehawkes2001-/***@public.gmane.org (while onsite in Venezuela)
__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions!
http://auctions.yahoo.com
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Sponsored by VeriSign - The Value of Trust
Secure all your Web servers now - with a proven 5-part
strategy. The FREE Server Security Guide shows you how.
http://us.click.yahoo.com/iWSNbC/VdiDAA/yigFAA/rIp0lB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, send an email to:
slimp3-dev-unsubscribe-***@public.gmane.org
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/