Hi,
I work with Flowplayer OY, manufactures of the Flowplayer HTML5 video player.
We test our software with all available browsers which can play html5 video and older ones where the player falls back to Flash.
So far it worked perfectly for us with the IE11 / Win 8.1 test VM as well as about a dozen live systems ranging from older laptops with integrated graphics to two month-old high-end octacore systems with a Geforce Titan-X.
Apparently it also works for thousands of IE11 site visitors, as we did not get complaints so far, except one two years ago (concerning an older build of IE11 and an older version of Flowplayer), another one seeing the same problmes in April 2015, and one from a user a week ago.
They presented screenshots showing that the implemenation on their site does not play the video but produces a "html5 file not found" error for the clip, which is a slightly customized message referring to either a 404 error for a file, or an aborted network request.
This concerns a single video embed on the site, and according to them also simple demos like http://demos.flowplayer.org/basics/minimal.html .
We checked their site in all our IE11 setups without seeing any error, as well as in IE10 and Edge. When trying to narrow down the issue we asked them to test with a simple <video> tag, namely on
http://demos.flowplayer.org/videotest/mp4.html
and they said that would not work either. Our assumption was that something in their IE setups , settings or build must be wrong, or that they experience symtopms like the missing codecs for K/KN versions of Windows 7 or on Server 2008, as described in https://msdn.microsoft.com/en-us/ie/ff959805.aspx .
A similar problem has also been described (for an older IE11 build)in
https://connect.microsoft.com/IE/feedback/details/805982/html5-video-playback-problem-ie-11-windows-8-1-invalid-source but seems to be rarely reproducible.
The videos are delivered with standard byte-range requests with video/MP4 MIME typde from Cloudfront or MaxCDN
The user now claimed the following which we judge as unlikely but would like to get third-party opinions on. They say that the information in for example
https://msdn.microsoft.com/en-us/magazine/hh561710.aspx?f=255&MSPPError=-2147217396
https://msdn.microsoft.com/en-us/library/hh924821(v=vs.85).aspx
https://msdn.microsoft.com/en-us/library/ff975073(v=vs.85).aspx
regarding the standard <video> tag has been silently invalidated by Microsoft due to a content-protection strategy which disables html5 video for pure tag implementations (which usually allow right-click downloading of the source) on some computers.
They also claim that this would be enforced by US-American "politics" and therefore not be visible here in Europe.
So I'd like to ask the valued community if
a) anyone experienced similar issues with a html5 video player, and knows about a specific bug, setting or feature in IE11 which could cause the problem
b) anyone who finds the time to check the demos on http://demos.flowplayer.org/basics/minimal.html etc can reproduce the error
c) anyone can comment the claims above
Thank you for your time.
I work with Flowplayer OY, manufactures of the Flowplayer HTML5 video player.
We test our software with all available browsers which can play html5 video and older ones where the player falls back to Flash.
So far it worked perfectly for us with the IE11 / Win 8.1 test VM as well as about a dozen live systems ranging from older laptops with integrated graphics to two month-old high-end octacore systems with a Geforce Titan-X.
Apparently it also works for thousands of IE11 site visitors, as we did not get complaints so far, except one two years ago (concerning an older build of IE11 and an older version of Flowplayer), another one seeing the same problmes in April 2015, and one from a user a week ago.
They presented screenshots showing that the implemenation on their site does not play the video but produces a "html5 file not found" error for the clip, which is a slightly customized message referring to either a 404 error for a file, or an aborted network request.
This concerns a single video embed on the site, and according to them also simple demos like http://demos.flowplayer.org/basics/minimal.html .
We checked their site in all our IE11 setups without seeing any error, as well as in IE10 and Edge. When trying to narrow down the issue we asked them to test with a simple <video> tag, namely on
http://demos.flowplayer.org/videotest/mp4.html
and they said that would not work either. Our assumption was that something in their IE setups , settings or build must be wrong, or that they experience symtopms like the missing codecs for K/KN versions of Windows 7 or on Server 2008, as described in https://msdn.microsoft.com/en-us/ie/ff959805.aspx .
A similar problem has also been described (for an older IE11 build)in
https://connect.microsoft.com/IE/feedback/details/805982/html5-video-playback-problem-ie-11-windows-8-1-invalid-source but seems to be rarely reproducible.
The videos are delivered with standard byte-range requests with video/MP4 MIME typde from Cloudfront or MaxCDN
The user now claimed the following which we judge as unlikely but would like to get third-party opinions on. They say that the information in for example
https://msdn.microsoft.com/en-us/magazine/hh561710.aspx?f=255&MSPPError=-2147217396
https://msdn.microsoft.com/en-us/library/hh924821(v=vs.85).aspx
https://msdn.microsoft.com/en-us/library/ff975073(v=vs.85).aspx
regarding the standard <video> tag has been silently invalidated by Microsoft due to a content-protection strategy which disables html5 video for pure tag implementations (which usually allow right-click downloading of the source) on some computers.
They also claim that this would be enforced by US-American "politics" and therefore not be visible here in Europe.
So I'd like to ask the valued community if
a) anyone experienced similar issues with a html5 video player, and knows about a specific bug, setting or feature in IE11 which could cause the problem
b) anyone who finds the time to check the demos on http://demos.flowplayer.org/basics/minimal.html etc can reproduce the error
c) anyone can comment the claims above
Thank you for your time.