Forum Discussion
Edge Chromium Official release seems to not work with Dishanywhere streaming
josh_bodner
Any good word yet?
Hopefully better than my outreaches to dish?
Wiesshund well, we actually got a reply from somebody over there, I'd say that's progress!
Well, it has been working fine like this
Which, considering Dish's co-operative track record, might be the best you can do
barring some time to try and reverse engineer some stuff- Yes, although that's just a workaround since we'd eventually like to fix this, but just can't prioritize the work right now.
- Ok, i disabled playready, and yes it did seem to work
So you are thinking to have edge detect dish's domain and then disable on the fly for that?
Seems like it would work Wiesshund given that we aren't any closer to either side providing an actual fix (we still aren't seeing any actual errors on the PlayReady side, so it's hard for us to verify where in the pipeline this is failing), our video team is considering disabling PlayReady on Dish specifically and just making it fall back to WideVine. Before they can do that though, we need to verify that Dish will work when PlayReady is completely disabled, so since you have a Dish account, could you disable the edge://flags/#edge-playready-drm-win10 flag and verify that Dish works as expected?
- How we looking?
Any updates yet? Wiesshund our capacity is pretty reduced right now because of the holidays, but I'll check back again in the new year!
Wiesshund You're right about number 1, even with the feedback button right there in the toolbar, most people just don't report those sort of things. For number 2 though, Dish originally made their support policy back when Edge Legacy was a thing, so some of the outreach we've been doing is to try to convince them that, now that we're functionally similar to Chrome (although not identical since we also have our own DRM that's unfortunately giving us unique problems), it should be relatively trivial for them to support Edge, especially since we can also do things on our end to help their servers treat us the same as Chrome if they want us to.
josh_bodner
Well as far as complaints received, two things1) Average user has no idea how or where to send a complaint or anything
2) When they call DISH, the CSR's tell the user that edge is not support and not a good browser
(not kidding, call them and pretend to be a customer)
and to use google chrome as DISH only supports ChromeAs far as a dish account
If you guys pm or email me, you can use mineWiesshund We've still got the issue on our backlog, but we honestly aren't hearing many other complaints about this site not working. I'm going to see if we can at least get somebody on our team with a dish account to try this out since we've just been working with bitmovin's code directly.
Wiesshund Chrome is using a different DRM provider (Widevine) than we are (PlayReady). The second issue, which doesn't have a workaround, is specific to our DRM, which is why it works in Chrome.
Well...
How is Google doing it with Chrome?
They are using the same root source for Google Chrome as Microsoft Edge Chromiumso there must be some little trick hiding in there
Wiesshund Okay, it looks like they've broken it out into two issues. One of the issues can be worked around by turning off hardware acceleration, the other can't.
Wiesshund I'll check with our engineers. Last time I asked, they were looking into a particular error they were seeing when bitmovin's code interacted with Playready.
Since Chrome and Edge use the same browser code base, seems possible to do something similar
to what ever they did in Chrome?
Course i am sure they are not exactly sharing what that thing is, but yea BitMovin, i would think, would be able to shed some light on it, it is their framework after all.Wiesshund we confirmed that they're not testing in Edge and are following up on that. In the meantime, our engineers are also looking into the issue from the bitmovin side.