Stories in instagram
-
ulkoalex last edited by ulkoalex
PS also tried cropping and padding video width a bit, and it had no effect on the issue, only height affected.
But then I tried large width, and it had same bug - threshold is 2048px (works fine), and 2050px didn't play.
Also, GPU tab for Opera is almost the same as for Chrome, but in latest any video width/height work fine:
-
burnout426 Volunteer last edited by
@ulkoalex said in Stories in instagram:
Opera Version: 62.0.3331.116 and 63.0.3368.66
Same with Opera 65?
-
ulkoalex last edited by ulkoalex
@burnout426 said in Stories in instagram:
Same with Opera 65?
Yep, checked 65.0.3425.0, same.
Also, just found this info on opera://gpu page:
1920 don't match my measured threshold of 2048, but 1088 matches exactly.
There's the same Video Acceleration info in Chrome, where any width/height work fine,
But anyway tried to disable all hardware accelerations in Opera, both in advanced settings and in flags:
And it didn't fix the bug and 1092p video still didn't play.
-
burnout426 Volunteer last edited by
@ulkoalex Can you check in Firefox and Edge (non-Chromium Edge) please? Check in Vivaldi too.
Opera uses the Windows Media Foundation to play proprietary codecs. The resolution might not be supported for GPU acceleration in those cases using WMF where Chrome gets away with it because of its full ffmpeg support. Chrome might switch to software decoding for those resolutions where Opera might not be able to. Firefox, Edge, and Vivaldi might behave the same as Opera.
It'd be interesting to see what others have in opera://gpu for the decode baseline under the Video Acceleration section. An Opera dev has higher values his machine. I know you have a GTX 1070 though.
-
ulkoalex last edited by ulkoalex
@burnout426 said in Stories in instagram:
@ulkoalex Can you check in Firefox and Edge (non-Chromium Edge) please? Check in Vivaldi too.
Checked Firefox 68.0, 69.0 (64-bit) - played all resolutions.
Vivaldi 2.7.1628.30 (Stable channel) (64-bit) - same as opera (doesn't play above 2048w or 1088h), and same Video Acceleration Information on vivaldi://gpu page.
Regarding non-Chromium Edge - are you sure it's available on win7? I only found Chromium-based one for win7.
Tried Chromium Edge, 77.0.235.17 (Official build) beta (64-bit) - played everything.Also, do you know what should affect those Video Acceleration Information params? Like available video RAM/video driver/installed codecs/screen resolution etc
PS nvm, found this article https://docs.microsoft.com/en-us/windows/win32/medfound/h-264-video-decoder
-
burnout426 Volunteer last edited by
@ulkoalex said in Stories in instagram:
Regarding non-Chromium Edge - are you sure it's available on win7? I only found Chromium-based one for win7
Sorry about that. I forgot you had Win7.
-
burnout426 Volunteer last edited by
@ulkoalex said in Stories in instagram:
Also, do you know what should affect those Video Acceleration Information params? Like available video RAM/video driver/installed codecs/screen resolution etc
Not sure at the moment. Will try to find out. Since it works in other Chromium browsers (I guess you could check Brave too), and in Firefox (which is supposed to use some WMF stuff too), perhaps Opera and Vivaldi can improve things.
-
A Former User last edited by A Former User
@burnout426 said in Stories in instagram:
It'd be interesting to see what others have in opera://gpu for the decode baseline under the Video Acceleration section. An Opera dev has higher values his machine. I know you have a GTX 1070 though.
- Opera 63.03368.66 (stable channel, 64-bit)
- OS: Windows 10 Pro 1903 (build 18362.295, 64-bit)
- Video card: NVIDIA GeForce 210 (1 GB RAM)
- Monitor: Eizo EV-Series (Full HD; currently connected to the computer via VGA instead of via HDMI, for a specific reason):
@ulkoalex said in Stories in instagram:
Also, do you know what should affect those Video Acceleration Information params? Like available video RAM/video driver/installed codecs/screen resolution etc
I've been thinking about those questions, too.
-
ulkoalex last edited by ulkoalex
@burnout426 said in Stories in instagram:
Not sure at the moment. Will try to find out. Since it works in other Chromium browsers (I guess you could check Brave too), and in Firefox (which is supposed to use some WMF stuff too), perhaps Opera and Vivaldi can improve things.
Checked Brave 0.68.132 Chromium: 76.0.3809.132 (Official Build) (64-bit) - plays all resolutions, and it has exactly the same entire brave://gpu/ page as Vivaldi, except for timestamps (and command line)
https://www.diffchecker.com/PNiYzXbv
Also, found similar issue with h264 decoding here:
WMF has no way of discovering that the decoder is not suitable until too late, it would be up to WMP to check the limitations of the decoder
So in this case browser should check the video before using decoder and, as you said, switch to software decoding for resolutions unsupported by WMF.
-
ulkoalex last edited by
@burnout426 so should I report this issue using Bug Report Wizard, or devs already informed about it?
-
burnout426 Volunteer last edited by burnout426
@ulkoalex said in Stories in instagram:
@burnout426 so should I report this issue using Bug Report Wizard, or devs already informed about it?
They're informed about it, but please file a bug so it can be analyzed, and include all the details etc. you can. Also, include a link to this forum thread for good measure. Also, after you've submitted, please post the bug number here. Thanks.
-
burnout426 Volunteer last edited by burnout426
For Vivaldi, I submitted VB-56881 (more of an FYI) and pointed to this thread. In https://forum.vivaldi.net/topic/27450/what-is-the-status-of-vb-already-reported-bug-issue, you can ask what the status of it is. I just submitted it, so I'd wait a while before asking.
-
burnout426 Volunteer last edited by burnout426
@burnout426 said in Stories in instagram:
@ulkoalex said in Stories in instagram:
Also, do you know what should affect those Video Acceleration Information params? Like available video RAM/video driver/installed codecs/screen resolution etc
Not sure at the moment. Will try to find out.
Dev/QA that was testing just has a GTX 1050 on Win 10 and 4GB of ram actually. Max Decode resolution for him is 4096x2304 and 2304x4096.
So, I'm thinking you need Win10 + a fairly-new and decent GPU to get the most out of things at the moment.
-
ulkoalex last edited by
@burnout426 said in Stories in instagram:
They're informed about it, but please file a bug so it can be analyzed, and include all the details etc. you can. Also, include a link to this forum thread for good measure. Also, after you've submitted, please post the bug number here. Thanks.
Submitted the bug, ID: DNAWIZ-71786
Dev/QA that was testing just has a GTX 1050 on Win 10 and 4GB of ram actually. Max Decode resolution for him is 4096x2304 and 2304x4096.
So, I'm thinking you need Win10 + a fairly-new and decent GPU to get the most out of things at the moment.
I see, thanks. Yeah, need win 10 at least, as win 7 has resolution limit no matter what GPU you have:
In Windows 7, the maximum supported resolution is 1920 × 1088 pixels for both software and DXVA decoding.
-
burnout426 Volunteer last edited by
Just for kicks, try launching Opera with --disable-gpu or just --disable-accelerated-video-decode to see if it does some software stuff with better supported resolutions. It's a long shot, but you can try it.
Try messing with
opera://flags/#use-angleandchrome://flags/#d3d11-video-decodertoo if you haven't. -
ulkoalex last edited by
@burnout426 hey, appears it was some kind of glitch with my system - now Opera plays all resolutions, as well as Vivaldi (Video Acceleration Information or any other params didn't change).
I'm trying to reproduce the issue again, but for now it just started working lol (and I didn't even reboot this time)
My apologies for taking your time, and thanks for your input on the issue. I'll write back if I have more info.
