Well, I'm new to uploading videos, just yesterday I uploaded a couple of them, and in doing so I have respected the amount of MB allowed, even less than the allowed limit.

However, they have been erased for not meeting the minimum quality standards, and the truth is, I don't understand much about the matter.

The WebM file is well compressed to be less than 100 MB, but the message says that the encoding or compression is not supported, and I don't know what that would be like or how to fix it for future publications.

Can anyone teach me how to do it?

You should take a look at Mairo's profile if you want to know about thst kind of stuff.

https://e621.net/users/38571

I, and many others, recommend learning to use ffmpeg, it is a very powerful tool and yet very light.

I really often replace posts where transcodes could be improved by a lot while doing approvals and usually there's one or two every day, but this artists has specifically dmailed me and told me not to upload their material to "boost my janitor role" so I won't, but I did also tell them that if subpar encodes are posted I will delete them as such.
This artists material is really lenghty, high resolution and tons of noise filters which does make it a nightmare to fit it into 100MB and every bit counts.

azero said:
You should take a look at Mairo's profile if you want to know about thst kind of stuff.

https://e621.net/users/38571

I, and many others, recommend learning to use ffmpeg, it is a very powerful tool and yet very light.

My profile is years out of date, so refer to proper documentation: https://trac.ffmpeg.org/wiki/Encode/VP9

mairo said:
I really often replace posts where transcodes could be improved by a lot while doing approvals and usually there's one or two every day, but this artists has specifically dmailed me and told me not to upload their material to "boost my janitor role" so I won't, but I did also tell them that if subpar encodes are posted I will delete them as such.
This artists material is really lenghty, high resolution and tons of noise filters which does make it a nightmare to fit it into 100MB and every bit counts.

My profile is years out of date, so refer to proper documentation: https://trac.ffmpeg.org/wiki/Encode/VP9

Thank you very much for your help!

I am trying to learn how to use the program, but my question is the following: We already know what is the MB limit that a video can have as a weight, that is, 100 MB.
But what is the limit of the other aspects? I mean, what's the bitrate limit for this page and stuff?
So I know specifically what I have to limit to work on this page and not overdo it.

I tried to modify the bitrate for the video that had been previously deleted but I can't make it less than 100 MB, and although I did last time, they told me that the video didn't match the encoding standards.

israel199 said:
Thank you very much for your help!

I am trying to learn how to use the program, but my question is the following: We already know what is the MB limit that a video can have as a weight, that is, 100 MB.
But what is the limit of the other aspects? I mean, what's the bitrate limit for this page and stuff?
So I know specifically what I have to limit to work on this page and not overdo it.

I tried to modify the bitrate for the video that had been previously deleted but I can't make it less than 100 MB, and although I did last time, they told me that the video didn't match the encoding standards.

Bitrate = bits per amount of time.
Filesize = amount of bits on the file.
So you basically need to calculate based around the time of the video and filesize target what is the maximum amount of bitrate you are allowed to have.

Also you want to work with variable/avarage bitrate (doc says to use constant quality instead for better consistancy, but it is near impossible to shoot for specific filesizes and bitrates with that mode) so that the bits are distributed for the scenes that actually require them, but then you also have to use much slower encoding settings and two pass so that the encoder has the time to work on most efficient way of encoding possible and increase the quality for the same bitrate. Also if you have audio, Opus by default uses variable bitrate so it can become lower/higher from target at the end, so you need to use constrained variable bitrate instead so that you are over/undershooting.

If the filesize turns hundreds of kilobytes over or under the filesize target, then simply copying the already encoded video track and re-doing the audio encoding you can fine tune the file to take full advantage of the filesize limit.

Something like post #2686526 and post #2407672 start to be at the absolute limit of what you can fit into the filesize and on the line of what's bearly acceptable.
However alternatives would be downscaling which further significantly would decrease the quality or cutting the video in several seqments which cannot be done with many videos. post #2555100 I was actually thinking to be able to upload full lenght, but new site actually has one hour limit for video uploads, so it had to be cut regardless and 20 minutes start to make bitrate so low (703kbps video/audio combined! Much lower from twitters bitrate for 720p h264 videos) that there is quality advantage on downscaling the video to half the dimensions (1080p->540p).

I guess I could techncally just encode these into 100MB VP9 files and just accidentally drop them somewhere at which point I wasn't the one to upload them here and artists can't be mad about it.

EDIT: also just realized you also lowered the framerate to 25 from 60. Please don't do that, that's messing up the frame pacing completely, if you have to lower the framerate do it by twos. Also used VP8/Vorbis.... Also artist uses goddamn winx hd video converter deluxe to do their MP4 files which would explain why they already look so compressed... This whole situation is a goddamn mess.
https://cdn.discordapp.com/attachments/666421129027518474/910031754914594857/1636476342_oppOYt6rYWt17z9Xr_Source.mp4_snapshot_00.21.616.png

EDIT2:

ffmpeg -y -i 1617359857_9jl7mFk78lTZj49oJ_Source.mp4 -row-mt 1 -pass 1 -quality best -c:v libvpx-vp9 -pix_fmt yuv420p -b:v 2504496 -b:a 64k -vbr constrained -f webm TEMP.TMP
ffmpeg -i 1617359857_9jl7mFk78lTZj49oJ_Source.mp4 -row-mt 1 -pass 2 -metadata title="Blaziken_Defeat, Kx2-SFM" -metadata url="https://ecchi.iwara.tv/videos/9jl7mfk78ltzj49oj?language=en" -quality best -c:v libvpx-vp9 -pix_fmt yuv420p -b:v 2504496 -b:a 64k -vbr constrained 1617359857_9jl7mFk78lTZj49oJ_Source.webm

https://mega.nz/file/1B401KJL#r9Spn0Y5l3eqBtLHD9K3PMyqIogYdeDmR9CsyAIM5ks
MD5: 226932B85DF801B31EEFE0C338465065

ffmpeg -y -i 1636476342_oppOYt6rYWt17z9Xr_Source.mp4 -row-mt 1 -pass 1 -quality best -c:v libvpx-vp9 -pix_fmt yuv420p -b:v 1863327 -b:a 64k -vbr constrained -f webm TEMP.TMP
ffmpeg -i 1636476342_oppOYt6rYWt17z9Xr_Source.mp4 -row-mt 1 -pass 2 -metadata title="【SFM】MouseTrap, Kx2-SFM" -metadata url="https://ecchi.iwara.tv/videos/oppoyt6rywt17z9xr?language=en" -quality best -c:v libvpx-vp9 -pix_fmt yuv420p -b:v 1863327 -b:a 64k -vbr constrained 1636476342_oppOYt6rYWt17z9Xr_Source.webm

https://mega.nz/file/BF5gXS5J#Z6kWuLYxlvsWsiVzQgJVp0ZVXxDMbv1SrDKhvyBjJ7Y
MD5: 0E451C5CC1BA0551474A31C633865CBD

mairo said:
Bitrate = bits per amount of time.
Filesize = amount of bits on the file.
So you basically need to calculate based around the time of the video and filesize target what is the maximum amount of bitrate you are allowed to have.

Also you want to work with variable/avarage bitrate (doc says to use constant quality instead for better consistancy, but it is near impossible to shoot for specific filesizes and bitrates with that mode) so that the bits are distributed for the scenes that actually require them, but then you also have to use much slower encoding settings and two pass so that the encoder has the time to work on most efficient way of encoding possible and increase the quality for the same bitrate. Also if you have audio, Opus by default uses variable bitrate so it can become lower/higher from target at the end, so you need to use constrained variable bitrate instead so that you are over/undershooting.

If the filesize turns hundreds of kilobytes over or under the filesize target, then simply copying the already encoded video track and re-doing the audio encoding you can fine tune the file to take full advantage of the filesize limit.

Something like post #2686526 and post #2407672 start to be at the absolute limit of what you can fit into the filesize and on the line of what's bearly acceptable.
However alternatives would be downscaling which further significantly would decrease the quality or cutting the video in several seqments which cannot be done with many videos. post #2555100 I was actually thinking to be able to upload full lenght, but new site actually has one hour limit for video uploads, so it had to be cut regardless and 20 minutes start to make bitrate so low (703kbps video/audio combined! Much lower from twitters bitrate for 720p h264 videos) that there is quality advantage on downscaling the video to half the dimensions (1080p->540p).

I guess I could techncally just encode these into 100MB VP9 files and just accidentally drop them somewhere at which point I wasn't the one to upload them here and artists can't be mad about it.

EDIT: also just realized you also lowered the framerate to 25 from 60. Please don't do that, that's messing up the frame pacing completely, if you have to lower the framerate do it by twos. Also used VP8/Vorbis.... Also artist uses goddamn winx hd video converter deluxe to do their MP4 files which would explain why they already look so compressed... This whole situation is a goddamn mess.
https://cdn.discordapp.com/attachments/666421129027518474/910031754914594857/1636476342_oppOYt6rYWt17z9Xr_Source.mp4_snapshot_00.21.616.png

EDIT2:

ffmpeg -y -i 1617359857_9jl7mFk78lTZj49oJ_Source.mp4 -row-mt 1 -pass 1 -quality best -c:v libvpx-vp9 -pix_fmt yuv420p -b:v 2504496 -b:a 64k -vbr constrained -f webm TEMP.TMP
ffmpeg -i 1617359857_9jl7mFk78lTZj49oJ_Source.mp4 -row-mt 1 -pass 2 -metadata title="Blaziken_Defeat, Kx2-SFM" -metadata url="https://ecchi.iwara.tv/videos/9jl7mfk78ltzj49oj?language=en" -quality best -c:v libvpx-vp9 -pix_fmt yuv420p -b:v 2504496 -b:a 64k -vbr constrained 1617359857_9jl7mFk78lTZj49oJ_Source.webm

https://mega.nz/file/1B401KJL#r9Spn0Y5l3eqBtLHD9K3PMyqIogYdeDmR9CsyAIM5ks
MD5: 226932B85DF801B31EEFE0C338465065

ffmpeg -y -i 1636476342_oppOYt6rYWt17z9Xr_Source.mp4 -row-mt 1 -pass 1 -quality best -c:v libvpx-vp9 -pix_fmt yuv420p -b:v 1863327 -b:a 64k -vbr constrained -f webm TEMP.TMP
ffmpeg -i 1636476342_oppOYt6rYWt17z9Xr_Source.mp4 -row-mt 1 -pass 2 -metadata title="【SFM】MouseTrap, Kx2-SFM" -metadata url="https://ecchi.iwara.tv/videos/oppoyt6rywt17z9xr?language=en" -quality best -c:v libvpx-vp9 -pix_fmt yuv420p -b:v 1863327 -b:a 64k -vbr constrained 1636476342_oppOYt6rYWt17z9Xr_Source.webm

https://mega.nz/file/BF5gXS5J#Z6kWuLYxlvsWsiVzQgJVp0ZVXxDMbv1SrDKhvyBjJ7Y
MD5: 0E451C5CC1BA0551474A31C633865CBD

Thank you very much for your prompt reply.

And I didn't know that in my previous publication I lowered the framerate, actually, I had converted it using Freemake Video Converter, converting the original video to HTML5 and downloading as much as I could the MB it should weigh, and thus I managed to make it have exactly 100MB, but I didn't know what affected the quality of the video itself.

Just before you answered me, I achieved a conversion very similar to what you have shown me in these links.
I mean, I used this combination:

ffmpeg -i MouseTrap.mp4 -c:v libvpx-vp9 -pix_fmt yuv420p -crf 16 -b:v 1900K -b:a 96K MouseTrap.webm

I tried various amounts of bitrate until just that was just the right one for it to be the right weight, and the quality looked more or less decent, but the audio sounds pretty bad.
And it's true, as you say, all of this is a disaster.

Although I have seen a post here by the same artist in case you are interested in seeing it: post #2840328
I don't know how they managed to make it look good and the audio sounds great and fits in almost 100MB, and it's a video of almost the same length.
How is it possible?

israel199 said:
Thank you very much for your prompt reply.

And I didn't know that in my previous publication I lowered the framerate, actually, I had converted it using Freemake Video Converter, converting the original video to HTML5 and downloading as much as I could the MB it should weigh, and thus I managed to make it have exactly 100MB, but I didn't know what affected the quality of the video itself.

Just before you answered me, I achieved a conversion very similar to what you have shown me in these links.
I mean, I used this combination:

ffmpeg -i MouseTrap.mp4 -c:v libvpx-vp9 -pix_fmt yuv420p -crf 16 -b:v 1900K -b:a 96K MouseTrap.webm

I tried various amounts of bitrate until just that was just the right one for it to be the right weight, and the quality looked more or less decent, but the audio sounds pretty bad.
And it's true, as you say, all of this is a disaster.

Although I have seen a post here by the same artist in case you are interested in seeing it: post #2840328
I don't know how they managed to make it look good and the audio sounds great and fits in almost 100MB, and it's a video of almost the same length.
How is it possible?

I have zero experience with shareware/freeware video encoders/transcoders and most of them are kinda shitty or have bigger or smaller problems when it comes down to workloads like on the site, they might work just fine for avarage user needing filetype converted right now. Only ones I have personally used are FFmpeg and Handbrake.

Yeah, that command is fine, it's constrained quality. How that command works is that the encoder tries to encode at CRF 16 quality which is good, but if the bitrate is exceeding that specified limit, then it just uses that bitrate instead of quality. e621 sampling uses this so that the sample videos are relatively good quality, but if someone uploads extremely complex video then the filesizes won't become ridiculous. Basically really good method for automated/bulk stuff, not the most ideal on single file optimization. Main issue most likely is that you are either going below the bitrate target and just getting much smaller filesize or constantly hitting the bitrate target at which point it's the same as just using proper bitrate from getgo.

post #2840328 is exactly identical situation to this one, user Izen uploaded it as much lower resolution and more compressed at post #2832961, I deleted it for being bad, they dmailed me, I gave them examples and link to file I encoded which they then uploaded. So the file on that post is also one I encoded.

This is also getting ridiculous when even the artist themselves cannot manage the encodes of their own material, on iwara or here, yet I'm still the one managing their content to be here :|
https://puu.sh/IpD6a/371c5cadef.png
Kx2_SFM