Linked by Thom Holwerda on Wed 8th May 2013 14:22 UTC
BeOS & Derivatives This is one of those news items that's fun to write, fun to read, fun to comment on, and where no one will be able to say anything unkind. It's all just one big ball of awesome fluffiness. TuneTracker, the BeOS radio automation software, has just released something very special: TuneTracker System 5, the first version designed entirely and specifically for Haiku. In fact, it actually includes Haiku in the software package. Better yet, TuneTracker also unveiled several system-in-a-box products - which have Haiku and TuneTracker pre-installed.
Permalink for comment 561015
To read all comments associated with this story, please click here.
RE[2]: Comment by BBAP
by pysiak on Thu 9th May 2013 07:12 UTC in reply to "RE: Comment by BBAP"
pysiak
Member since:
2008-01-01

1. Use file attributes to store all the metadata on the media (instead of having to use sqlite/mysql like xbmc does). It seems like a perfect fit for Haiku (probably the reason TuneTracker is still a BeOS app).

I see the benefits in storing meta data in the file system, instead of a database, but I have a few doubts:

1) can you easily and *efficiently* do a query on metadata? e.g. SELECT AUTHOR, FILENAME FROM /home/user/mp3/ WHERE TITLE LIKE '%RED%'; ?
2) would that query result be cached by the file system cache or would you want to traverse the whole library? Would you need to write your own cache mechanism? Would you want to preserve the state of the cache between runs?
3) Do all copy methods ensure file attributes are preserved? I would think that cp works differently than a copy routine coded in an application and, say, something along sendfile(). That opens the risk of losing precious meta data.

Not to mention confining yourself to one file system.

Reply Parent Score: 2