Apple ProRes codec reverse engineered
git.videolan.org
Apple ProRes codec reverse engineered
1–10 of 27 posts
Re: Apple ProRes codec reverse engineered
#2ProRes 422 is a standard-definition and high-definition lossy video compression format developed by Apple Inc. for use in post production. It was introduced in 2007 with Final Cut Studio 2 [1] and is comparable to Avid's DNxHD codec which has the same purpose and uses similar bit rates.
Re: Apple ProRes codec reverse engineered
#3Re: Apple ProRes codec reverse engineered
#4This is a great development for decoding ProRes with non-OSX OSes. What are the legal implications? Will ffmpeg need to pay to license the ProRes codec from Apple? Does Apple even offer a license for the codec?
However, it's nice that they have it built into ffmpeg now.
Re: Apple ProRes codec reverse engineered
#5This is a great development for decoding ProRes with non-OSX OSes. What are the legal implications? Will ffmpeg need to pay to license the ProRes codec from Apple? Does Apple even offer a license for the codec?
Haven't they had this for a while (Post Date: August 28, 2008). http://support.apple.com/downloads/Apple_ProRes_QuickTime_De... However, it's nice that they have it built into ffmpeg now.
Re: Apple ProRes codec reverse engineered
#6From http://en.wikipedia.org/wiki/ProRes_422 : ProRes 422 is a standard-definition and high-definition lossy video compression format developed by Apple Inc. for use in post production. It was introduced in 2007 with Final Cut Studio 2 [1] and is comparable to Avid's DNxHD codec which has the same purpose and uses similar bit rates.
Re: Apple ProRes codec reverse engineered
#7This is a great development for decoding ProRes with non-OSX OSes. What are the legal implications? Will ffmpeg need to pay to license the ProRes codec from Apple? Does Apple even offer a license for the codec?
Re: Apple ProRes codec reverse engineered
#8Re: Apple ProRes codec reverse engineered
#9Re: Apple ProRes codec reverse engineered
#10This code makes me feel like I'm not even a real software engineer, I'm just a guy playing with kiddie languages working on kiddie problems. Anyone else think that after reading it?