Live player is not working in the Edge browser on a fully updated Windows 10 machine. I just tried watching the GBE Playdate and no controls were loading for me to start the video.
Keep in mind, html5 support on Edge is terrible, at best. I'd guess that you have issues with html5 videos on many other sites as well. Reading through microsoft support threads from the last 30 days shows a ton of issues related to usage of html5 video in edge, which, should be a surprise to no one.
Secondarily, check security settings. Windows firewall, and security settings often block files that are required. Try turning your security settings down to test.
Further, it's important that you run Windows Update. It could be that you have denied a required pack previously, which could be causing issues: https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/windows-10-n-media-feature-pack-not-working-after/953d600b-badd-4fdb-8756-6eb3b740d02e You need the windows 10 media feature pack. Depending on your upgrade path, you might have missed this pack at some point.
Good luck! My advice to you would be to use Chrome or Firefox if you want the latest video tech...
This breakage started out of the blue this week. Videos played fine yesterday and are broken today. Additionally, the fact its affecting multiple Win10/Edge users suggests its kinda unlikely that it's something specific on our computers? Also, the Youtube URL you posted works fine (as does literally every other non-GB video I've tried today). As far as the video player issues, opening up the Console shows a myriad of issues, specifically around Access-Control-Allow-Origin header issues.
As far as browser/OS details, here's mine:
Microsoft Edge 40.15063.0.0
Microsoft EdgeHTML 15.15063
Windows 10 Creators Update (build 15063.250)
The video @jslack linked works fine for me as well. Giantbomb is the only site where I have problems with video content. And like wise to @fish_face_mcgee this problem appeared for me suddenly last week. Just noticed that I couldn't post on the forums with Edge either, after clicking reply button page did load up but my reply apparently disappeared into ether.
Microsoft Edge 38.14393.1066.0
Microsoft EdgeHTML 14.14393
Win 10 ver 1607 build 14393.1066
I've been unable to load videos on Edge on Xbox One since Wednesday/Thursday, and the site won't keep me logged in either. I think the issues started when the membership sale went live (and the page headers changed).
Using the unofficial video player app on Xbox One is working fine, for the time being.
This is the 3rd time posting this already, it is nice when you just want to watch and not be part of some video player beta (no offense GB programmers, but the video player has issues): "You can do this: "before it will be fixed... it is easy to watch any (premium) video by (on the page of the video) clicking on Download -> On the Resolution you want Right mouse click -> Open in new tab. And you'll use the in browser player to get the stream directly. Which is nice."
I almost would not mind using my browser to open Giant Bomb as the new normal, but one thing it does not allow me to do is skip ahead in videos. I still (premium stuff) have to dl for that. Plus I know, the problem has to be figured out. Otherwise the work around has done me okay, for the time being.
I'm unable to view any videos in edge. The player button nor settings comes up. Comments aren't loading either. I'm running Windows 10 x64 1703 (creators update.)
I'm pretty sure this worked with 1703, but it isn't working now. (IE still works)
I'm also unable to "Post Reply" from Edge either. I had to load up IE for this to work.
Microsoft Edge 40.15063.0.0
Microsoft EdgeHTML 15.15.063
@wcarle, I think there's still some lingering issues. On video pages, while the player operates correctly now, the comments don't auto-load like they used to, and the Podcasts don't show run time/current progress when the audio file is playing. Also, possibly un-related, but there's some JS code that's infinitely trying to manipulate a DOM element that doesn't exist, making it incredibly difficult to view accurate error info the console.
Please Log In to post.
Log in to comment