Live data from Hacker News

FFmpeg 5.0

github.com

21–30 of 31 posts

Re: FFmpeg 5.0

#21
post #12

So... what is so much different about it from 4.x?

Did you click the link?

I did, but none of those lines in the changelog mean anything to me, none look like important or major, because I'm not a specialist of this project, so from this link I don't know what makes the change from 4.x to 5.0, but I'd like to know, I use FFmpeg from time to time, and I'm genuinely curious

Could you explain what you did see in that link in a few simple words?

Re: FFmpeg 5.0

#22

In 2003 or 2004 I had a job doing video installations with Linux systems in a variety of museums. That was the first time I learned about FFMpeg. Used it for everything, still one of the first things I install on any system, and whenever I need to do anything with video conversion or resizing or taking a slice out, I use FFMpeg. It is awesome. Although, after all these years I still have to look up every single incan…

Wish it was easier to get Nvidia's encoder working with it. Too often it maxes out my CPU and the GPU is idle.

Re: FFmpeg 5.0

#24
What are the highlights that made this a new major release? The changelog just mentions which codecs, muxers etc. got added and I'd appreciate if someone can explain what the important additions are

Re: FFmpeg 5.0

#25

So... what is so much different about it from 4.x?

Looks like a lot of new codecs and filters, but no breaking changes?

I'm not sure if ffmpeg follows semver at all. I thought their API was pretty stable after the big change from "next_video_frame" (or whatever it was called) to the send/receive packet/frame model.

Re: FFmpeg 5.0

#26
post #18
post #11

Earlier quoted context omitted.

Elitist approach to bug reporting is wrong, at least that's my opinion. Unless project maintainers indeed don't care about bug reports and just do whatever. But then it's more arrogance than actual benefit to the user. I think more projects suffer from under reporting of bugs than from too many bugs reported. And if no one is fixing bugs, then the above doesn't matter anyway.

You're being really ungenerous here, saying their bug tracking system is "broken", their use of it is "elitist", they "don't care about bug reports" and they're guilty of "arrogance". I don't think you can substantiate any of this just from the fact that they use Trac. You (well, maybe not you, but one) can also imagine all kinds of counter-arguments (not that I know if any of these are true or not): - Devs would rat…

To clarify, I'm not saying it's arrogance in this particular case, but answering the above comment which claims there is no need for better bug reporting experience. That kind of attitude is arrogance I think.

All projects can have practical limitations and migrating the bug tracker is still work of course. But ignoring or even denying the fact that current experience is far from perfect is wrong.

Re: FFmpeg 5.0

#27
post #15
post #14

Earlier quoted context omitted.

They can choose whatever priorities of course, but I'd disagree that it's not impacting anyone besides a small portion of the users. Discouraging bug reports reduces quality for everyone. Those who report bugs might be a smaller portion, but projects need them I'd argue way more than those who use and never report anything to them.

I'd encourage browsing their Trac for context.. the handful of regular contributors definitely don't need any extra bug reporters

This kind of argument is exactly what I described above as an arrogant attitude. Not sure if developers actually use that in this case, but if some projects do - it's not a good thing at all.

Re: FFmpeg 5.0

#28
I use ffmpeg to slice up and convert video.

I just looked at the new features for 5.0.

Does anyone have a more detailed description on what these are?

Re: FFmpeg 5.0

#29
post #16
post #12

Earlier quoted context omitted.

Did you click the link?

Not the parent but the link is quite opaque. I'd really like it if someone more familiar with the project could explain what these changes mean, which ones are exciting and why and whether there were any interesting challenges that were overcome.

Something like that: http://www.jbkempf.com/blog/post/2022/FFmpeg-5.0

Re: FFmpeg 5.0

#30

In 2003 or 2004 I had a job doing video installations with Linux systems in a variety of museums. That was the first time I learned about FFMpeg. Used it for everything, still one of the first things I install on any system, and whenever I need to do anything with video conversion or resizing or taking a slice out, I use FFMpeg. It is awesome. Although, after all these years I still have to look up every single incan…

Wish it was easier to get Nvidia's encoder working with it. Too often it maxes out my CPU and the GPU is idle.

On most Linux package managers these days, FFmpeg is built with support for hardware encode, decode, and filtering out of the box.
Post reply on HN