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.
Thread beginning with comment 560986
To read all comments associated with this story, please click here.
Comment by BBAP
by Bringbackanonposting on Wed 8th May 2013 23:29 UTC
Bringbackanonposting
Member since:
2005-11-16

Maybe there is spin off for an in-car entertainment system. Or run XBMC or something custom on Haiku for lounge room media centres...

Reply Score: 3

RE: Comment by BBAP
by Morgan on Thu 9th May 2013 02:51 in reply to "Comment by BBAP"
Morgan Member since:
2005-06-29

Maybe there is spin off for an in-car entertainment system.


This is something I've been wanting to do with BeOS (and later Haiku) for many years now. The problem is, I'm a crappy programmer. I can build an interface in a visual IDE, and I can code simple scripts in scripting languages, but anything lower level than Python, Javascript, Tcl/Tk, PHP or Bash is beyond my abilities.

Hell, it took me three days to make a custom MP3 player in VisualBasic 6 back in college, that would have taken your average high schooler less than two hours. Granted, a solid day was wasted fine-tuning the custom graphical buttons and controls (I was all about skeuomorphism in 2001), but a true ICE interface with all the bells and whistles is far beyond my abilities.

Still, I would love to see one of the big car audio companies embrace Haiku the way the TuneTracker folks have. I think Haiku is the perfect platform for any multimedia-heavy project, and given its open source nature it is much easier from a licensing standpoint.

Reply Parent Score: 4

RE: Comment by BBAP
by galvanash on Thu 9th May 2013 03:18 in reply to "Comment by BBAP"
galvanash Member since:
2006-01-25

Maybe there is spin off for an in-car entertainment system. Or run XBMC or something custom on Haiku for lounge room media centres...


+1!!!

What I would like to see is something very much LIKE xbmc written for Haiku... For the following reasons I think it would be an excellent project for the community to work on:

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).

2. Use it as an excuse to focus more attention on Media Kit. Work has been done on it but its not close to optimal yet. My hope is to see Media Kit get good enough that a good full featured media center type application could be written using it (instead of having to implement everything internally like xbmc does).

3. Its not an easy task, but it isn't that hard either. Im pretty familiar with XBMC (did some development on it here and there), and if Media Kit was doing all the playback work and the filesystem was doing all the metadata indexing, all you have left is doing a good UI, a scanner, and a plugin architecture. I doubt you would want to get as fancy as xbmc with the state of OpenGL on Haiku at the moment, but I think you could do something decent using webkit/blink to do the rendering.

4. Thread the hell out of the media scanner! XBMC is like 100X faster than it used to be when scanning items into the library, even still I have 350 lines or so of naive code (written in node.js no less) that can outperform it by a few orders of magnitude - and that is on Windows... It is the perfect problem to attack with Haiku's exceptional threading, its all network latency bound.

5. It sounds like fun. Developers like fun projects ;)

Edited 2013-05-09 03:26 UTC

Reply Parent Score: 3

RE[2]: Comment by BBAP
by pysiak on Thu 9th May 2013 07:12 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

RE: Comment by BBAP
by BlueofRainbow on Thu 9th May 2013 14:00 in reply to "Comment by BBAP"
BlueofRainbow Member since:
2009-01-06

I believe SkyOS toyed with the concept of XBMC.

Given that SkyOS used OpenBeFS as its base file system, maybe it could be possible to bring this over to Haiku - if ever the code for SkyOS becomes open sourced.

Reply Parent Score: 1