Do more on the web, with a fast and secure browser!

Download Opera browser with:

  • built-in ad blocker
  • battery saver
  • free VPN
Download Opera

Stories in instagram

  • Do not open video stories in instagram

  • I can't tell - is that a warning (telling people not to open videos in Instagram) or a bug report? The latter would say "Does not" rather than "Do not" ...

  • If you are trying to report a problem, please see https://forums.opera.com/topic/23068/instructions-on-posting-about-problems-in-opera-for-computers

    By the way, I can watch Instagram stories without problems here.

  • The problem is still relevant. It does not work ONLY playing video in instagram STORIES. The sound is heard, the timeline of the story goes, but the image is frozen. Videos in user profiles are played correctly. Boomerang video works too. Help me please.

    alt text

  • Hey @sgunhouse and @leocg ,
    I faced the same issue, and after some experiments I found out that videos with more than 1090 (1092) height aren't playing in Opera, but with 1088 height they're playing fine for me.
    I tested with same file encoded:
    Encoding settings for 1088:

    1088
    When opened in opera, video and audio work fine.
    What Media Internals says:

    Media Internals

    But when encoded with 1092 height, video doesn't work in Opera, just audio:

    Player no video
    Encoding settings for 1092:

    1092
    Everything is the same, just different height.
    What Media Internals says:

    Media Internals

    found_video_stream	false
    

    Uploaded both files here
    https://drive.google.com/drive/folders/12-ZBIRLCwumCbnoAkrR8X2omDUjOyZP5?usp=sharing

    Opera Version: 62.0.3331.116 and 63.0.3368.66
    OS: Windows 7 64-bit
    Video card: Nvidia GeForce GTX 1070 with 382.33 driver

    Bug exists in incognito mode (no extensions), and on different monitors (1080p, 1440p)
    So it's not about codec/specific website, but about height of each particular video.
    Also, in Chrome any height works fine for me.

    Can you please confirm this bug?

    Thanks!

  • 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:

    gpu.png

  • @ulkoalex said in Stories in instagram:

    Opera Version: 62.0.3331.116 and 63.0.3368.66

    Same with Opera 65?

  • @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:

    gpu_x264.png

    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:

    acceleration.png

    And it didn't fix the bug and 1092p video still didn't play.

  • @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.

  • @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

    h264_win7.png

  • @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.

  • @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.

  • @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):

      opera_gpu_Video acceleration.png

    @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.

  • @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:

    https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/2b052b4e-b239-459d-9dac-a197593df7db/how-to-play-highres-h264-video-asf-in-wmp-on-windows-7

    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.

  • @burnout426 so should I report this issue using Bug Report Wizard, or devs already informed about it?

  • @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.

  • 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 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.

  • @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.

    😭

  • 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-angle and chrome://flags/#d3d11-video-decoder too if you haven't.

Log in to reply