(large text = quite a lot of characters) something like this from yesterday
Yes. Being a licensed Blu-ray player means a *LOT* of draconian things. I can't believe the audiophile crowd would even suggest integrated, native BD playback for that simple reason. Let's take a look at some of the things a licensed player is forced to do:
-First and foremost, it needs to support AACS decryption in a way that prevents the player key from being lifted from memory.
That means debuggers need to be trapped, memory needs to be wiped clean, and all kind of other nasty nonsense that could, and probably would, introduce instability in MC15.
-Next up you have BD+. This is another whole new ballgame and requires a BD+ machine implementation that is also secure from hacking. And as new titles make use of more and more BD+ functions (there are a lot), the player will most likely have to be tweaked to handle it. And since ArcSoft didn't even seem to get a heads up with the new Avatar BD+ protection was released, I suspect JRiver would also be forced to play catch up when the BD+ protection is changed. Playing catch up is never a good place to be in when you're a developer and customers are clamoring for a fix for their new Blu-ray.
-For you audiophiles in the house, we have bitstreaming and non-downsampled decoded LPCM. This is a really fun topic. For bitstreaming, a Protected Audio Path is required. JRiver would in fact be required to implement each and every vendor's interpretation of PAP. What I mean is, nVidia does PAP one way, ATI does it another way, Realtek does it another way, ASUS Xonar does it yet another way. You will be writing code to support each and every new card that comes out in order to support PAP for bitstreaming. That also applies to non-downsampled LPCM for those that couldn't care less about bitstreaming. No PAP....no non-downsampling. There is a strange use case exemption that seems to be out there, but, that use case isn't fully understood yet so discussion it here is premature at best.
-For videophiles, HDCP is also required to be supported by the player. IOW, more DRM code that doesn't achieve anything for the end user but a headache that the developers will have to focus on.
Why do I bring all this up? All of that coding equals an ENORMOUS amount of time and effort. That's time and effort that will NOT be spent improving other areas of MC15.
We need to remember that developer resources for a company the size of JRiver are not infinite. If they're working on DRM requirements to not get their AACS LA provided license revoked, they're not working on other areas of the code. If they were to hire developers specifically for the purpose of doing all the DRM coding, the cost would have to go up because they still need to cover the AACS LA license fee, PLUS pay the developers working on the code. And let's not even get into the exponential cost of testing.
The in house hardware requirements alone aren't cheap as you need to test on a wide variety of hardware to make sure the DRM plays nice. I'm not pointing all this out to be negative. I'm pointing it out to clearly define the reality behind such an endeavor. It's not cheap from a labor or monetary standpoint. And other areas of the code would likely suffer as a result.
Just look at PowerDVD for a prime example of that. I just want everyone to have a clear picture of what would be needed to provide licensed, official BD support. BTW, did I mention the work necessary to create the video and audio codecs? Those aren't provided. As an AACS LA licensee, you get the spec. You're on your own as to how to implement it. That's 3 video codecs (already handled so no problem there) and 3 audio codecs. DTS-HD MA being the most obvious one that would need to be written from scratch. I think TrueHD could be handled by what's already out there depending on how the license is written. Otherwise they may be forced to write their own codec for it. Awesome....
this work ok in MC 14 not in MC 15
maybe auto correct spelling is a thief here ? but that does not explain the lag in the action window or ?
Author
Topic: MC 15 Lags a lot when entering/editing (large) text (Read 1671 times)