FFmpeg 1.0 MultiMedia Library Released 82
An anonymous reader writes "The free software FFmpeg multi-media library that's used by VLC, MPlayer, Chrome, and many other software projects has reached version 1.0 after being in development since 2000. The 1.0 release incorporates new filters/decoders and other A/V enhancements. The code is available from FFmpeg.org."
Re: (Score:3, Funny)
FFmpeg Frosty First edition?
MPEG-LA (Score:3, Interesting)
Re:MPEG-LA (Score:4, Informative)
No. ffmpeg people don't distribute binaries and our mostly outside the US. MPEG-LA has repeatedly affirmed that source code alone is fine with them. This had been affirmed by Ryan Rodriguez of MPEG-LA that shipping source code is not a product.
http://forum.doom9.org/showthread.php?p=1431854#post1431854 [doom9.org]
There's plenty reasons to dislike MPEG-LA without making shit up.
Re: (Score:1)
MPEG-LA probably _loves_ FFMPEG. A huge chunk of media products are based on it, and all MPEG-LA has to do is detect the FFMPEG bits by signature then pursue license fees. Because they can see the source, and can probably tell which bits are compiled in, they'll know which patents are involved right off the bat.
It could hardly get any better for them...
Re: (Score:3)
There are a LOT of commercial projects that use FFmpeg but pay for licensing for the particular codecs enabled. MPEG-LA, VIA (AAC), and Thomson (MP3) have no problem with that or where the codec implementation came from so long as the client the client is paying.
My bigger complaint is an oddity of their H.264 licensing that requires *every* H.263 decoder installed to be paid for separately. This means the H.264 decoder in OSP Flash, the H.264 decoder in the Gstreamer plugin and the H.264 decoder in FFmpeg
Re: (Score:2)
that requires *every* H.263 decoder
should read
that requires *every* H.264 decoder
Re: (Score:1)
Only if they were in the United States and shipping binaries. FFmpeg only distributes source and let's others ship the binaries. Third parties in the US who compile and ship FFmpeg without a license would have an issue.
Re: (Score:2)
Re:Now that's how to use version numbers (Score:4, Insightful)
Re: (Score:3)
Re: (Score:2)
Alpha and Beta don't even need to be part of the stable release version. Like having Build 1, 2, 3... for releases, you can simplify it as Build 2 Alpha 3, or Build 5 Beta 2.
Re: (Score:2)
Re: (Score:2)
Ok, so you're more in favor of
Chrome ButteryFly Sandwich
Followed by
Chrome Unripe Egg
Followed by
Chrome Lantern of Medicraty
Followed by
Chrome Furry Enchilada
ect...
Re: (Score:2)
Re: (Score:2)
It "means something" to go to 1.0 after over a decade of development, and after being in production use in innumerable places?
It means what, exactly?
Video orientation (Score:1)
I wonder if they've finally managed to integrate correct video orientation handling when dealing with QuickTime movies. Lack of support was the reason VLC was unable to show QuickTime videos recorded using an iPhone.
Re:Video orientation (Score:5, Funny)
using an iPhone.
Found your problem
Re:Video orientation (Score:5, Funny)
I wonder if they've finally managed to integrate correct video orientation handling when dealing with QuickTime movies. Lack of support was the reason VLC was unable to show QuickTime videos recorded using an iPhone.
You're holding it wrong.
Re: (Score:3)
You're holding it wrong.
Just tell him to let go, there's no need to post about it
Does it support Intel's Quick Sync? (Score:1)
I overheard they had some ideological(?) issues with that in the past.
As a consumer I really want this feature, even if a kitten suffers somewhere because of this feature.
Re:Does it support Intel's Quick Sync? (Score:4, Interesting)
Unless I'm gravely confused, ffmpeg seems like a curious place for Quick Sync support. Quick Sync is an independent, comparatively inflexible(though fast), h.264 hardware encoder and decoder, not a set of instructions or an architectural feature that would speed up a software decoder. Why would a tool that is largely a collection of highly flexible software encoders and decoders be interested?
I can see how some of the video player programs that use ffmpeg might have reason to also have the option to use quick sync, on supported platforms; but that would really be up to them...
Re: (Score:2)
Nice story, but I really don't see the connection with reality.
Your original post got two answers: one saying that it wouldn't make sense to add the feature you want, and another saying that Intel should provide documentation.
You, on the other hand, imply that the reasons given by the ffmpeg authors for not implementing the feature you want are "Saint Stallman does not approve it" and "The Balance of The Force will be tipped in a wrong way", and you give no evidence of that at all.
Better luck on your future
Re: (Score:2)
That's nice, how about replying to the relevant post [slashdot.org]?
Intel should develop or get it developed (Score:2)
Sounds like you're getting ahead of yourself there. Before you ask if ffmpeg supports quicksync, maybe you should ask if Intel supports quicksync yet. Anyone have an URL of a page at intel.com (or whereever), where Intel says how to do it (e.g. op codes)?
If a feature is important to a cpu vendor, it is up to them to code an initial, up to ffmpeg coding standards patch and invite the community to progress it, with a good donation to the project.
ffmpeg being free and opensource doesn't mean they should waste precious development time to code a non portable enhancement.
Re:Which binary is 1.0? (Score:4, Informative)
http://ffmpeg.org/download.html#releases [ffmpeg.org]
Out of beta? (Score:1)
It's interesting how so many projects that were in beta for so long (though widely used and considered essentially stable) are finally getting the 1.0 treatment.
Re:Out of beta? (Score:5, Insightful)
Re: (Score:2)
That's a good point. "Here's our software. It should be stable, but it's beta, so don't rely on it too much." beats "Hey, we're out of beta! What? Bugs? We'll take care of that in 1.1!"
Re:Out of beta? (Score:5, Interesting)
The good news for us, is that they allow the community to help ironing out the bugs, which for many don't show up until long repeated usage. The more people there are to report failures, the better.
compared this with commerical software. Especially microsoft. They release
OpenSSL spent 15 years before a 1.0 release. Noveau almost 10.
I think its a sign of many long standing projects maturing, and that linux is ready for prime time.
Re: (Score:2)
It's interesting how so many projects that were in beta for so long (though widely used and considered essentially stable) are finally getting the 1.0 treatment.
When I write code I initially set the version of my code to 1.0 which basically means it could crash or do horrible things to the environment. In other words not to be used by anyone not encased in flame and bullet proof armour. There are many who prefer using 0.0 to designate the first version of their software however to the average person who would use that software (ie. the majority) versions starting at 1.1 or preferably 1.2 and above is much more preferred than 0.1 or 0.2. Still it is not wrong to sta
Big thanks to the developers (Score:5, Informative)
For all their ardous work!
FFMpeg donations page is here:
http://ffmpeg.org/donations.html [ffmpeg.org]
Re:Big thanks to the developers (Score:4, Funny)
Re:Big thanks to the developers (Score:5, Informative)
PayPal es del Diablo.
Re: (Score:1)
For all their ardous work!
FFMpeg donations page is here:
http://ffmpeg.org/donations.html [ffmpeg.org]
I really wonder how many software and hardware vendors which rely on it hit that donation button. Half of media apps I use and paid for has ffmpeg embedded.
Could be none.
Re: (Score:1)
Re: (Score:3, Informative)
Libav is a fork of ffmpeg, even if its developers, who are former ffmpeg develeopers, claim otherwise.
Libav proponents argue [multimedia.cx] that theirs is the better fork.
Others say [blog.pkh.me] the opposite.
Trying to decide which fork to use, I read these two accounts and concluded that both(!) were saying "stick with ffmpeg". If you are interested in the issue, read these two references and decide for yourself.
Re: (Score:2)
Last I heard, libav had managed to piss off a fairly large chunk of the developer base too through the really disruptive way they handled their fork.
Lots of great pro features! (Score:5, Insightful)
ffmpeg supports both Avid DNxHD and Apple ProRes codecs, REDCODE decode, EXR, DPX, and all the best unencumbered formats as well. This means that most pro video and film production can integrate into OSS with much more ease than ever before. It also means that proprietary data lock-in is on the way out.
Way to go ffmpeg!
Re: (Score:2)
Homebrew Install (Score:1)
12 years to release version 1 ?? (Score:3, Funny)
Stop slacking guys! Take a look at Firefox. Work as hard as they do and in 8 years you too can have a version 16 !
Branching in Matroska files? (Score:3)
This would make my day, I understand they refuse to do it though. Really sucks when you want to have both Theater AND Director's cut releases of BluRay...
Re: (Score:2)
It seems no patch has been adequate. Either the FFMpeg architecture cannot deal with it, or people who patch don't understand FFMpeg enough to submit a clean patch. Sample:
http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2008-August/041721.html [mplayerhq.hu]
They refuse to apply terrible patches. Another question is why don't they work on it themselves, to fix an obvious deficiency? I don't have an answer to that.
Re: (Score:2)
I had been told it wasn't being done for "security reasons" although I've yet to find that actually stated but this was relayed to me by an XBMC dev so I put some weight to it. The XBMC guys won't touch this until the ffmpeg guys do it. I note that the message you linked was from 2008 - 4 years ago! This has obviously been an issue for awhile and honestly it sucks. I understand the Anime community wants this because they like to slice off the start and endings of shows and only store them once, I want it
Fabrice Bellard? (Score:2)
How come neither the article nor the official site (ffmpeg.org) does not mention Fabrice Bellard [wikipedia.org], the original author?
ffmbc (Score:5, Informative)
If you're in broadcast, check out ffmbc [google.com] a broadcast-oriented ffmpeg fork. My dabbling has been with producing IMX (SMTPE D10) as an archival format for video and film archive digitiziation and although you can cook it up with ffmpeg, ffmbc makes it a doddle. The hard work has been done by the ffmpeg folks, and it's a wonderful tool.
I used ffmpeg for producing a side-by-side video of a reference uncompressed YUV vs samples of MJPEG2000 & MPEG2 at various compression ratios for a double-blind subjective quality assessment together with overlaid captions - took me a day or so going from never having used it before. Think of it as ImageMagick for video, rather than just a transcoding library.
Whilst I'm here, can I give a shout out for mediainfo(Hi Jerome!) as a technical metadata extraction tool for Video (if you're using it in an archival repository, use the mpeg7 or pbcore xml output - almost hidden features). Don't be fooled by the home page screenshot - the linux command line version is where it's at.
Re: (Score:2)
But can it make decent MP4 containers yet? (Score:3)
Re: (Score:1)
That's actually mencoder's fault. It has problems muxing to basically anything but AVI. If you use ffmpeg directly, you can make MP4 files just fine. For mencoder, it's unlikely that the situation will change, as it is basically no longer maintained.