grace mustang (nintendo and etc) created by dunewulff
Description

GIF version of apparently junk original c:

  • Comments
  • GIF version of original.

    Yeah, I deleted the original as inferior. Please learn to do encodes properly.

  • Reply
  • |
  • -9
  • Mairo said:
    Yeah, I deleted the original as inferior. Please learn to do encodes properly.

    Enlighten me then, please. Tell me how to do it properly instead of just throwing it under the bus.

  • Reply
  • |
  • 4
  • DuneWulff said:
    Enlighten me then, please. Tell me how to do it properly instead of just throwing it under the bus.

    The main problem with this is always that I have no idea about everyone elses workflow, so I cannot give much of hints what to do with software you are already using and tools I'm using are command line based like ffmpeg. There is general information I wrote long while ago now in my profile bio under "converting" and some basic WebM encoding information which should apply to all converters to some degree can be found here: https://trac.ffmpeg.org/wiki/Encode/VP9

    1. Always use the actual project resolution and framerate. For some reason the video version was lower resolution (quarter of the gif!), but aspect ratio was also wrong, which added additional pillarboxing. Posts here are handled by visuals, text and audio are usually irrelevance.
    2. Always minimize the steps between origin and last export and work with lossless material between. Not sure if it was because of downscale, but background did look noticeabely more compressed compared to this gif, which could be because origin -> mp4 -> random online converter, instead of preferred origin -> webm, which I do not know because I don't know your workflow.
    3. Try to use constant quality mode and VP9 to minimize visual compression and to avoid bloated filesizes. I can actually easily manage to create gifs resolution and higher visual quality with 2/3 of the bitrate: https://puu.sh/CaTiv/f4a685c30a.webm
    With audio, Opus with 96-128kbps should be good enough, instead of overkill 320kbps with Vorbis used on your post, especially when the audio is already noisy and also not sure what's purpose of forcing stereo when it's mono audio

    As for sound with loop, soundless webm files do usually loop extremely seamlessly at least with chrome and MPC-HC, however I have not been able to get seamless loop when including audio, so that is what it is. You can make it appear more seamless by having the loop 2-3 times when the loop is ~1 second only.

  • Reply
  • |
  • 0
  • Mairo said:
    The main problem with this is always that I have no idea about everyone elses workflow, so I cannot give much of hints what to do with software you are already using and tools I'm using are command line based like ffmpeg. There is general information I wrote long while ago now in my profile bio under "converting" and some basic WebM encoding information which should apply to all converters to some degree can be found here: https://trac.ffmpeg.org/wiki/Encode/VP9

    1. Always use the actual project resolution and framerate. For some reason the video version was lower resolution (quarter of the gif!), but aspect ratio was also wrong, which added additional pillarboxing. Posts here are handled by visuals, text and audio are usually irrelevance.
    2. Always minimize the steps between origin and last export and work with lossless material between. Not sure if it was because of downscale, but background did look noticeabely more compressed compared to this gif, which could be because origin -> mp4 -> random online converter, instead of preferred origin -> webm, which I do not know because I don't know your workflow.
    3. Try to use constant quality mode and VP9 to minimize visual compression and to avoid bloated filesizes. I can actually easily manage to create gifs resolution and higher visual quality with 2/3 of the bitrate: https://puu.sh/CaTiv/f4a685c30a.webm
    With audio, Opus with 96-128kbps should be good enough, instead of overkill 320kbps with Vorbis used on your post, especially when the audio is already noisy and also not sure what's purpose of forcing stereo when it's mono audio

    As for sound with loop, soundless webm files do usually loop extremely seamlessly at least with chrome and MPC-HC, however I have not been able to get seamless loop when including audio, so that is what it is. You can make it appear more seamless by having the loop 2-3 times when the loop is ~1 second only.

    Mate I'm no sound engineer.
    I used Krita, exported to MP4, then opened it premiere and added sound.
    Krita doesn't natively support sound in the build I use, so I have to add sound afterwards with premiere.
    I can add a WebM extension to Premiere, but whether or not that'd help anything I don't know.

  • Reply
  • |
  • 1
  • DuneWulff said:
    Mate I'm no sound engineer.
    I used Krita, exported to MP4, then opened it premiere and added sound.
    Krita doesn't natively support sound in the build I use, so I have to add sound afterwards with premiere.
    I can add a WebM extension to Premiere, but whether or not that'd help anything I don't know.

    OK, this helps a bit. This is exactly what I was saying when I said I don't know your workflow :p

    Don't export as MP4, export as PNG image sequence (or lossless AVI). PNG image sequence is lossless and can be handled with premiere, ffmpeg, sony vegas, etc. with ease and into any desired end format. PNG image sequence is also what I always ask if someone requests me to encode something like this for them. MP4 h264 is fine if you are uploading the animation like that, but you aren't, instead you are converting it into gif and editing it in premiere which is not ideal.

    If you have to or want to use premiere, then yes, having webm extension to export into webm directly is preferred. If you don't want to do this, then export as lossless AVI instead to handle with your webm converter like ffmpeg, webm for retards (that's the actual name), xmedia recode, etc.

    I do not use Krita nor Premiere myself so I cannot give step-by-steps sadly. Just make sure that project resolution and framerate stays identical with all the steps. Tools like ffmpeg simply take the resolution from input, but something like premiere is higher end video editing tool and doesn't assume anything and has seperate options for project settings and export settings which can default to something like 480p.

  • Reply
  • |
  • 3