#17415 closed update (fixed)
ffmpeg port update r15943
Reported by: | anddam (Andrea D'Amore) | Owned by: | dbevans (David B. Evans) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.7.0 |
Keywords: | port update | Cc: | |
Port: | ffmpeg |
Description (last modified by andrea.damore@…)
I updated the ffmpeg port to have alac encoding support in m4a files, I dropped the default variants as liba52 is not supported anymore by configure script, ffmpeg has its own library now. Fixing this ticket could probably close #17310 too.
I didn't create patchfile, you should just change
- revision to 13
- svn revision variables to:
set svn_rev 15943 set swscale_svn_rev 27970
- and the libwscale line in fetch phase to:
system "svn co -r${swscale_svn_rev} svn://svn.mplayerhq.hu/mplayer/trunk/libswscale ${distpath}/${svn_rev}/trunk/libswscale"
Change History (6)
comment:1 Changed 16 years ago by andrea.damore@…
Description: | modified (diff) |
---|
comment:2 Changed 16 years ago by dbevans (David B. Evans)
Keywords: | ffmpeg removed |
---|
comment:3 Changed 16 years ago by dbevans (David B. Evans)
Owner: | changed from acho@… to devans@… |
---|---|
Status: | new → assigned |
comment:4 Changed 16 years ago by dbevans (David B. Evans)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Have committed a new port ffmpeg-devel in r46033 which implements the suggestions above. This port reflects ongoing API/ABI changes in ffmpeg trunk. Lots of new codecs but for the adventurous only as the new API is not backwardly compatible (and probably not stable yet either).
Sorry this has taken so long.
comment:5 Changed 16 years ago by jmroot (Joshua Root)
Type: | enhancement → update |
---|
Note: See
TracTickets for help on using
tickets.
Leaving as is for now as updating to this svn revision breaks the previous API (libavcodec version 51) used by many other applications. SVN revision 15261 is the last revision that is API compatible. See http://www.ffmpeg.org/ for warning dated 9/9/2008.
This should be revisited when the dependent applications have been identified and verified compatible with the newer API.