On Apr 8, 2006, at 11:54 PM, Travis Siegel wrote:
It kept crashing, wouldn't unpack anything, and generally left things in a mess.
Ah, that's a different kettle of beans (does anyone say that anymore?). We've used it here for testing and development but haven't had any difficulties. My guess (and that's all it is) is that the proprietary packing is seen as the cleanest way to comply with legal obligations to protect copyrighted content without the scheme having to be implemented in third party playback software/devices.
For RFBD content, the responsibility of unpacking the content is transferred to the player developer i.e. you can't access protected RFBD content without an RFBD-enabled player.
Joe
