>>48092890>isn't that only /gif/ anyway that allows sound?On 4chan, yes. There's also liveboards that generally run a more advanced/filetype friendly system which are a consideration of mine.
libopus defaults to 96kbps, but the purpose of "lazy" is that it's lazy and shouldn't really considered a viable option for true archiving. However, I see your point. I should definitely put more thought into it (and the Archival quality version) to be quicker and as lossless as possible.
>Crop then scaleYeah, that should be addressed by making the help info tailored to the actual FFprobe input data.
>Padding inaccuracyMy main focus is mitigation of I/P/B-frame data causing either smear glitches or frozen frames, not actually mistiming of start/stop times. By doing an encoding copy rather than a re-encode you run the risk of those problems, so the thought is to give enough padding to securely avoid starting during a smear/frozen frame while also keeping the process relatively quick.
>Quality flagsI think this can be easier mitigated by the help stuff. You're right since we're approaching different philosophies it's causing a bit of an intent issue and maybe the code should offer best of both worlds. Maybe it should also catch you on making very long clips and check filesize at the end to see if it's even postable.
>>48093394Yeah, seems like help/error handling should be priority 1 in making these scripts more hootie-friendly.