Spandex superheroes, giants, fighting bug men, armored heroes, and kaiju are all welcome.Image limit was hit, previous thread >>6005060
>>6030352
>>6030352you forgot to put tokusatsu in the op
>>6030352>>6030241Was the fire gotchard video meant to be soundless? Was that part of the summer graduation movie or the daybreak one?
>>6030370I've been listening to this furry sax on loop for half an hour now
>>6030473
>>6030487
bump
>>6030352>>6030370gay
>>6031795Hey Moose, what settings do you use for your webms?
>>6031985What Boram defaults to as I've found it gives by far the cleanest output out of anything I've used including standalone FFMPEG commands. I was recommended this on /v/ I think a few years back and I haven't looked back since. It also gets around the issue Webm for Retards/Lazies has where it sometimes has the subtitles go off sync, audio doesn't sync correctly, or outright refuses to open a video past a few minutes even though the file is fine.https://github.com/Kagami/boramI set up the start and end times before I do anything as this tells me how long the webm is going to be.Second I set the filesize limit to 4 or 6 MB (Don't do this in Webm for Retards or standalone FFMPEG as it cuts off the video to fit the filesize). This gives me a baseline bitrate to work with in the modifiable command lone below it.If I am going 6 MB with sound I then choose either 128, 196, or 256 audio bitrate depending on how long the webm will be and how badly the visual bitrate suffers. Generally 196 is my starting point and I go to 256 if I'm seeing a fairly high bitrate or 128 if it's super low. Anything longer than a minute I usually stick to 128 unless I can afford it.I then adjust the window size based on what I see in the bitrate. Generally it's>200 or lower you don't go past 320p.>210-300ish you stick to 360p.>300-450ish you stick to 854 x 480p.>450ish to 800 you stick to 540p.>900-1300 is when 720p stops looking like garbage.>1500+ is 1080p.>Never had to convert 4k but if I had to guess I'd say around 3000+ would be fine.Once you get your window size then manually change the bitrate in the text input below to anywhere from 30-100+ higher than what it says based on the video length and framerate.Keep in mind that when you compile a webm like this it takes a minimum of 2-5 minutes per compilation so typically a webm with corrections to the bitrate (Because I either under or overshot) takes me anywhere from 5-20 minutes to make per webm.
>>6031995Thanks.
>>6031995When I tried boram the output webm had variable framerate instead of keeping the original 24fps or 60fps, don't know why.
>>6032032No idea what the problem is there as it's always been consistent for me. It does mention it fixes SAR if you slap the modern Blade encodes in there for example and you can deinterlace, but I've use 24 FPS and 60 FPS stuff without issues before. Maybe update FFMPEG?
>>6032035>Frame rate mode : Variable>Frame rate : 282.014 FPSReplaced the ffmpeg, left the setting in codecs on default only, set the mb limit, no idea why boram does this for me.
>>6032112Well, if it's causing you trouble you could always go to Webm for Lazies since it's the updated Webm for Retards and see if you get the same issue there. The only problem is you'll have to wing it on the bitrate until you get the right filesize.
>>6031995>Generally 196 is my starting point and I go to 256 if I'm seeing a fairly high bitrateWhat's a high bitrate in this case?
>>6032778nta but bitrate is calculatable. It directly corresponds to file size and so the question is just how long you're willing to make the webm before it degrades too much in quality.https://chameleon-ai.github.io/webm-guide/#quick-reference
>>6032783I know what bitrate is, I just wanna know what Moose considers a high enough video bitrate to aim for 256 kb for audio.
>>6032778>>6033183It's entirely relative to the file you are creating and the circumstances surrounding it. So let's say you have a 540p webm that's 700ish bitrate when you slap 196 audio bitrate onto it. You're not gonna hit your 720p threshold of bitrate and your visual quality is not going to be massively affected by a 30-40 bitrate loss, so that's when you can justify going to 256.Generally something in the 320p-360p range you want to stick to 128 unless you really want to try to hit 196, but once you get past that you can start messing around with 196 and 256. I would leave worrying about audio bitrate for last. Always try to opt for better visual quality over the audio quality since 128 is still pretty good overall and 196 is more than fine.
Spandex supreheroes normalized the homosexuality
>>6033183But what I'm trying to say is that it's all a calculation. Say you choose 256k audio, that results in a specific size and you spend the rest of the bits you have on video. Then you do a calculation or heuristic to determine what resolution you pick for that bitrate.It's not so much "what's a high enough bitrate" as much as what fits into the target file size. It's not guesswork.
