The flip side to that is that the technology needed to make a player is eerily similar to the technology needed to make CloneBD. So they aren't working at cross purposes. The underlying technology is applicable to both. A player is nothing more than outputting streams to an audio and video renderer. CloneBD is going to output streams to a new file structure. The theme here is that they need to be able to read and process the streams in the first place. That's where the huge effort is. I've said this many many times before and I'll keep repeating it until people understand this concept:
A blu-ray consists of a video stream that can be MPEG2, h.264, or VC-1, and audio stream that can be TrueHD, DTS-HD MA, PCM (and the core variants), and subtitles. The open source community has all this taken care of from bitstreaming to decoding. A blu-ray also consists of a menu system that can potentially be java. (See Source Code for a primer on why this sucks). A proper player will need to be able to parse through the menu. That is *NOT* taken care of by the open source community, and isn't likely to any time soon. However, CloneBD is going to need to be able to do that and so presumably SlyPlayer will, as well. However, we have no information as to what it will include at release. Nonetheless, the benefit of SlyPlayer is that if it can handle menu support, then it'll be a step above the current open source solutions. That's where the real meat of this project is. The OSS community has the rest already handled. Menus, however, are a pretty vital piece of the puzzle.
This was my presumption of the state of mythtv blu playback ... if I gave it the .m2ts I wanted it would play it back fine (and with VDPAU acceleration on an atom zbox hiding behind my monitor on the wall too boot). But that it would barf if I gave it a folder structure or some other thing.
So what I need is either clonebd that will give me the .m2ts I want ... or a slyplayer that I can call from a mythfe ...
The delay is OK; I'm sort of waiting on 4TB spindles (and some sort of track record on reliability ... the 1.5GB seagates I'm using are an RMA nightmare) before I really start to transition our library to blu.