This is something a GPT would do way better.
Ffmprovisr – Making FFmpeg Easier
91–100 of 106 posts
Re: Ffmprovisr – Making FFmpeg Easier
#92Earlier quoted context omitted.
Can you share what you chose as your points and what convinced them at the end?
One argument I made was sponsoring a project, especially buys you support / developer relations. For example, we replaced a commercial PKZIP license with 7-zip. Was able to use the fact that one of the project we donated to, 7-zip, implemented a feature request that helped in this transition. That combined with the fact that these donations relative to our proprietary software costs were insignificant, made it an eas…
Thanks forr the reply.
When you have a direct involevment in the project it surely helps.
And thanks for supporting 7z, from a guy who use it dayly! *cheers*
Re: Ffmprovisr – Making FFmpeg Easier
#93Earlier quoted context omitted.
What likely works better in conservative environments, are not donations, but (generous) support contracts. This is something buisness people can understand.
While I'm sure you are right, I can't help but to be irked by this strange environment we live in where we have to treat business people like infants who need things mashed and mushed into something they can digest and understand. Nobody had to explain to me the concept of donating to support somebody working on something my business relies on, it's just common sense. If I was really reliant on books documenting toll…
Have you spent much time around business people? I’ve spent years around them and open source software truly confuses them. Why would you ever use your time to make something and then give it away? I once suggested we make a donation and they laughed at me. Their response was if people are dumb enough to make something and give it away for free, then they get nothing.
Re: Ffmprovisr – Making FFmpeg Easier
#94Re: Ffmprovisr – Making FFmpeg Easier
#95Earlier quoted context omitted.
What's more confounding about this than translating between any other two formats?
GIF is a terrible format for video
But it's the only common video format that can be treated like a static image in most cases. Like any other format, it's got its ideal use case.
Re: Ffmprovisr – Making FFmpeg Easier
#96[flagged]
Conversely, I do not know any developers that use AI instead of google. And considering the horrific garbage it has given me the few times I tried, I’d be worried about what you’re doing with it.
To be fair, googling so many things nowadays will lead you to dogshit blog sites with a million CTA modals and needless prose
Re: Ffmprovisr – Making FFmpeg Easier
#97Earlier quoted context omitted.
GIF is a terrible format for video
But it's the only common video format that can be treated like a static image in most cases. Like any other format, it's got its ideal use case.
Animated webp is commonly supported at least on he web these days.
Of course, it too is a horrible video format, which is impressive considering it is based on a not nearly as horrible video format. If only browsers would support silent looping video in and CSS image contexts...
Re: Ffmprovisr – Making FFmpeg Easier
#98Earlier quoted context omitted.
Why?
Perhaps it's a form of hipster irony, since by and large all GIF sites and social media sites now convert source GIFs to mp4.
There are still plenty of contexts where you can embed images but not videos (or at least not with automatic looping playback) - forums, github README.md, other markdown-based comment/post systems.
Gif compression limitations also encourage you to cut down to the essential parts - too many videos waste the viewers time with delays and irrelevant bits.
Re: Ffmprovisr – Making FFmpeg Easier
#99Earlier quoted context omitted.
But it's the only common video format that can be treated like a static image in most cases. Like any other format, it's got its ideal use case.
Animated webp is commonly supported at least on he web these days. Of course, it too is a horrible video format, which is impressive considering it is based on a not nearly as horrible video format. If only browsers would support silent looping video in and CSS image contexts...
> Animated webp is commonly supported at least on he web these days.
Sure-- if it's a) a website that b) you're making. Tons of websites that allow user uploads only allow common static image formats-- jpg, gif... maybe png, maybe bmp, etc. I can't imagine anywhere that allows users to upload profile pictures, for example, would allow them to upload a webp, but I could imagine users wanting an animated profile picture. I've done it myself.
The whole point is that there are instances where using an animated gif is the only option if you want an animated image, and people want to convert videos to animated gif because of that. That's why FFmpeg does it. I'm not really sure why people find this so weird.
Re: Ffmprovisr – Making FFmpeg Easier
#100This guide recommends "yadif" as a deinterlacing filter. I find "w3fdif" looks better. Like yadif, it does not do motion tracking, so it's reasonably fast and avoids the distracting artifacts that motion tracking sometimes causes (I'd rather have consistently mediocre results than sometimes great and sometimes bad), but it considers three fields at a time instead of yadif's two, which lets it hide the interlacing art…
As previously suggested, w3fdif has mostly been supplanted by bwdif. w3fdif can produce shimmering, whereas yadif does not, which is why bwdif operates like yadif but uses the better field matching of w3fdif.