You can not view this image.

This post was deleted or flagged for the following reasons:

  • [DELETION] Unapproved in 30 days - auto moderator -
Description

I apologize for the broken video.
Here is the video in normal quality: https://mega.nz/file/rmIBSLYA#eGa1-tOVhW_MiyccnTdz7TJtULs2FO7j-k1qs5RbeEk

Blacklisted
  • Comments
  • iceblazewinters said:
    just because 1 person has an issue loading the video, is not grounds to flag it

    the video works perfectly fine for all 8 seconds

    It's probably because it works on my PC, NOT on my mobile.

  • Reply
  • |
  • 4
  • aps said:
    It's probably because it works on my PC, NOT on my mobile.

    welcome to the webm format

    its like a 50% chance for a webm to load properly on my phone if im directly on e621.
    and it will never work if its embeded anywhere else (mainly discord).

    im pretty sure this is just a iphone problem, no idea for others since iv never owned a different brand of phone

  • Reply
  • |
  • 0
  • I don't really know or understand why there's so many artists who use like 8K level resolutions, but at the same time keep compression so high that it doesn't really matter.
    Main quality dial for lossy videos is bitrate, not video resolution. What happens if you dial up resolution without dialing up bitrate, is a lot of compression artifacts all over the place. This is why I'm big fan of constant quality mode in modern encoders as it will dial the bitrate for you to upkeep perceived quality instead of you needing to figure out that you needed 30mbps instead of 5mbps.

    For here example, bottom character clearly has pants with texture on them, but majority of the texture gets into blotchy mess. If you pause the video and look at any high contrast edges, it's full of artifacts both ways like some bad JPG.
    So even if resolution is absurdly high, this isn't any better from some video shared on and transcoded into really bad quality MP4 on X (or previous twitter because nobody will know what X means without specifically noting that it is the X that used to be twitter).

    iceblazewinters said:
    just because 1 person has an issue loading the video, is not grounds to flag it

    the video works perfectly fine for all 8 seconds

    aps said:
    It's probably because it works on my PC, NOT on my mobile.

    tbf, it is sometimes pretty hard to tell why something isn't working, especially as e621 automatically scales content to fit your browser either horizontally or vertically (or for newer users just use 720p sample).

  • Reply
  • |
  • 3
  • mairo said:
    I don't really know or understand why there's so many artists who use like 8K level resolutions, but at the same time keep compression so high that it doesn't really matter.
    Main quality dial for lossy videos is bitrate, not video resolution. What happens if you dial up resolution without dialing up bitrate, is a lot of compression artifacts all over the place. This is why I'm big fan of constant quality mode in modern encoders as it will dial the bitrate for you to upkeep perceived quality instead of you needing to figure out that you needed 30mbps instead of 5mbps.

    For here example, bottom character clearly has pants with texture on them, but majority of the texture gets into blotchy mess. If you pause the video and look at any high contrast edges, it's full of artifacts both ways like some bad JPG.
    So even if resolution is absurdly high, this isn't any better from some video shared on and transcoded into really bad quality MP4 on X (or previous twitter because nobody will know what X means without specifically noting that it is the X that used to be twitter).

    tbf, it is sometimes pretty hard to tell why something isn't working, especially as e621 automatically scales content to fit your browser either horizontally or vertically (or for newer users just use 720p sample).

    Pretty much the first thing I do to test if something is actually working is use the samples. If it's actually broken it shouldn't work there either.

  • Reply
  • |
  • 0