Opera Developer YouTube Subscription HTML 5 videos non playable
-
avl Opera last edited by
It does seem to be related to the format of the video, as said earlier YouTube makes videos available in other encodings later (and this can take quite some time). So it looks like some format isn't playing for you.
What do you see when you go to https://www.youtube.com/html5 ? For reference, this is what it looks like in my O30 developer: http://imgur.com/6dG4F1p.
-
gregorw last edited by
After the error occurs, open opera://gpu/ and see problems detected.
Then scroll all the way down to log messages.If there are any, post them here.
You can also try if this flag makes any difference: opera://flags/#ignore-gpu-blacklist
-
Deleted User last edited by
It does seem to be related to the format of the video, as said earlier YouTube makes videos available in other encodings later (and this can take quite some time). So it looks like some format isn't playing for you.
What do you see when you go to https://www.youtube.com/html5 ? For reference, this is what it looks like in my O30 developer: http://imgur.com/6dG4F1p.I'm not sure how can it be related to that, since the same videos, played at the same time, in two different versions of Opera, have two different behaviors. One works, the other one doesn't. The HTML5 player is activated in both browsers.
The only difference I found in terms of support is that Opera 28.0.1750.51 (regular version) doesn't have support for MSE & H.264 (not sure what difference does that MSE make, since it looks like it does have support for H.264 anyway), whereas Opera Developer does have support for all. Which is awesome and all. But still doesn't answer the question: how come the browser that works ok is the one with less support (regular Opera browser)? It's pretty counter intuitive.Also, if I'm not mistaken (which I might as well be), this issue did not occur in the past, with older versions of Opera Developer. I haven't used another browser as my number one browser, in a very long time. And I wouldn't have installed the regular version if it wasn't for this issue with YouTube.
I would like to test an older version of Opera Developer, but not sure where I can get it from. Any ideas?
Not sure that's gonna make any difference. But there is only one way to find out, right?
-
Deleted User last edited by
After the error occurs, open opera://gpu/ and see problems detected.
Then scroll all the way down to log messages.
If there are any, post them here.
You can also try if this flag makes any difference: opera://flags/#ignore-gpu-blacklistLog Messages
[0417/211526:ERROR:gpu_video_decode_accelerator.cc(276)] : HW video decode not available for profile 1Enabling ignore-gpu-blacklist didn't make any difference.
-
avl Opera last edited by
I'm not sure how can it be related to that, since the same videos, played at the same time, in two different versions of Opera, have two different behaviors. One works, the other one doesn't. The HTML5 player is activated in both browsers.
The only difference I found in terms of support is that Opera 28.0.1750.51 (regular version) doesn't have support for MSE & H.264 (not sure what difference does that MSE make, since it looks like it does have support for H.264 anyway), whereas Opera Developer does have support for all. Which is awesome and all. But still doesn't answer the question: how come the browser that works ok is the one with less support (regular Opera browser)? It's pretty counter intuitive.Because to implement those things, and others, Opera now relies on different operating system APIs. Programming is never as simple as it might seem - there's no such thing as simply 'adding' MSE
So it's entirely possible that there's a problem with the new implementation on your system that didn't appear with the old one. Can you tell us more about which system you're using? Version of OS X, which Mac (you can use the description in "About This Mac" to identify the model)?
-
Deleted User last edited by
I'm not sure how can it be related to that, since the same videos, played at the same time, in two different versions of Opera, have two different behaviors. One works, the other one doesn't. The HTML5 player is activated in both browsers.
The only difference I found in terms of support is that Opera 28.0.1750.51 (regular version) doesn't have support for MSE & H.264 (not sure what difference does that MSE make, since it looks like it does have support for H.264 anyway), whereas Opera Developer does have support for all. Which is awesome and all. But still doesn't answer the question: how come the browser that works ok is the one with less support (regular Opera browser)? It's pretty counter intuitive.Because to implement those things, and others, Opera now relies on different operating system APIs. Programming is never as simple as it might seem - there's no such thing as simply 'adding' MSE
So it's entirely possible that there's a problem with the new implementation on your system that didn't appear with the old one. Can you tell us more about which system you're using? Version of OS X, which Mac (you can use the description in "About This Mac" to identify the model)?Thank you very much for your reply!
Yes, I know it's not as easy as just "adding MSE". I work in IT. And I know that, sometimes, the smallest things can have the most unpredictable results.
So, just to make sure we're on the right track here, assuming that the latest additions in HTML5 support are actually the cause of the issue, I tested the same scenario with the following versions of Opera Developer:
- 28.0.1750.5 - No MSE & H.264 support yet -> all fine in terms of functionality
- 29.0.1795.14 - No MSE & H.264 support yet -> all fine in terms of functionality
- 30.0.1812.0 - No MSE & H.264 support yet -> all fine in terms of functionality
- 30.0.1820.0 - MSE & H.264 support added -> YouTube issues.
So I was right when I said that I don't remember having this issue in the past, with Opera Developer. There were no issues cause there was no support for that MSE thing in the past to cause the issues before.
By the way, just out of curiosity, I checked the HTML5 support on the latest version of Safari. Let's just say I'm glad I chose Opera.
Also, kudos for your hard work.And I'm on Mac OSX 10.10.3.
-
-
Deleted User last edited by
Could you also tell us which Mac you're using (first line in "About This Mac") and which GPU you have ("About This Mac" -> "Displays")?
I actually tested this with two computers, just to make sure the GPU and the actual hardware doesn't have anything to do with this issue:
- a Mac computer 27-inch, Mid 2010, running OSX 10.10.2. Video card: ATI Radeon HD 5670 with 512 MB of RAM
- a custom PC running Mac OS X 10.10.3. Video card: nVidia GTX 650 with 2048 MB of RAM.
Also, additionally, I tested the same scenario on a Windows PC, which did not have this issue, despite the fact that the support for MSE & H.264 was there for this case, as well. I know that's off-topic for this thread, but just throwing it in there for comparison.
So, as you can see, the issue is not hardware related. It's software related. And it does occur with both OSX 10.10.2 and OSX 10.10.3.
Now, I'm really curious, do you guys not have this issue? Any of you? Cause I find it kind of hard to believe that I can reproduce it on two different machines, and no one can reproduce it on at least one, over there.
If you need any more information, please, let me know.
-
avl Opera last edited by
Now, I'm really curious, do you guys not have this issue? Any of you? Cause I find it kind of hard to believe that I can reproduce it on two different machines, and no one can reproduce it on at least one, over there.
Yes, that's correct - we can't reproduce this on any of the Macs we have here. The HW video decode message you get is most likely the culprit: we have no fallback when that is the case, but we had never seen a real-life Mac without this feature.
a Mac computer 27-inch, Mid 2010, running OSX 10.10.2. Video card: ATI Radeon HD 5670 with 512 MB of RAM
A 2010 iMac, we might have one of those around. Can you make sure that you get the same error message there?
a custom PC running Mac OS X 10.10.3. Video card: nVidia GTX 650 with 2048 MB of RAM.
It's obvious why HW decoding is not supported there.
-
Deleted User last edited by
Now, I'm really curious, do you guys not have this issue? Any of you? Cause I find it kind of hard to believe that I can reproduce it on two different machines, and no one can reproduce it on at least one, over there.
Yes, that's correct - we can't reproduce this on any of the Macs we have here. The HW video decode message you get is most likely the culprit: we have no fallback when that is the case, but we had never seen a real-life Mac without this feature.
a Mac computer 27-inch, Mid 2010, running OSX 10.10.2. Video card: ATI Radeon HD 5670 with 512 MB of RAM
A 2010 iMac, we might have one of those around. Can you make sure that you get the same error message there?
a custom PC running Mac OS X 10.10.3. Video card: nVidia GTX 650 with 2048 MB of RAM.
It's obvious why HW decoding is not supported there.
To be honest, it's not so obvious to me.
The nVidia GTX 650 is a lot better than the Radeon 5670 on the Mac. So....not sure about that. :))But anyway, I already went ahead and took a screenshot from the 27-inch mac, just in case you guys might want that. And yes, it's exactly the same issue. And I'm pretty sure that once you guys my figure out the reason why this happens on the regular Mac, the issue will be also fixed on the custom build, as well.
You can find it here.
-
