HOWTO: Install and use the latest FFmpeg and x264

[sportspool7]

I have tried to follow this way but still can not use. When I convert songs, application of this state 'FFPlay' not found. How do I solve this problem?

I using Ubuntu 9.10

[mc4man]

...application of this state 'FFPlay' not found.

If you followed the guide exactly then ffplay (and ffmpeg) would have been installed to /usr/local/bin

At the risk of misunderstanding your question if some app is saying it can't find ffplay then see if you can adjust the path in it's config or prefs.

[mc4man]

me issues building FFmpeg over the last 12 hours? A variety of errors I suspect linked to the new build process...

no problem here either - have done 3 different builds, (for vlc, xine-libs, and in general

The terminal output is different than previously (similar to vlc 1.1), the verbose part is mainly relegated to warnings or errors, - a make distclean just does it - no output.

[qyot27]

Seems that you can use PKG_CONFIG_PATH on x264, too (although I distinctly remember it failing...idk).

Finally figured it all out. FFMS2 isn't picky about where PKG_CONFIG_PATH is declared, but x264 is. I'd been trying with PKG_CONFIG_PATH declared at the end, but x264 only accepts it if it's before ./configure. FFMS2 has no issue with it placed at the end of the command. Doing so means x264 picks up both LAVF and FFMS2 from the custom prefix.

I'll edit the steps I posted before to reflect this now.

[FakeOutdoorsman]

I have tried to follow this way but still can not use. When I convert songs, application of this state 'FFPlay' not found. How do I solve this problem?

I using Ubuntu 9.10

Are you using WinFF?

[andrew.46]

Hi mc4man,

no problem here either - have done 3 different builds, (for vlc, xine-libs, and in general

Looks like I left out the vital information that I build shared libraries only . This was in fact broken for a brief time but fortunately it has been resolved in r22280 and now compiles cleanly with --enable-shared --disable-static.

Andrew

[mc4man]

This was in fact broken for a brief time

There seems to have been some changes of late including some significant ones to dsputil.h (finally rendering the asm_64 patch I had unusable for the moment


On another note, saw this in lucid which pretty much sets in stone what ffmpeg will be - the 0.5.1 release

fmpeg (4:0.5.1-1) unstable; urgency=low

* new upstream release:
- clarifies documentation on metadata, Closes: #570050, LP: #501729
- further security backports, Closes: #570713
* adapt to new versioning scheme
* use '<<' instead of '<' relationship for internal shlib file
* merge changes from ubuntu packaging
* drop wmapro backport again as discussed with upstream. The unrelated
changes seem too risky for a stable release.

-- Reinhard Tartler <siretart@tauware.de> Wed, 03 Mar 2010 22:28:24 +0100

ffmpeg (4:0.5+svn20090706-6) unstable; urgency=low

At least now ffmpeg is shown for what is is - 0.5.1, not +svn20090706-6 (-r19352) as karmic incorrectly reports

I guess one gives the benefit of doubt to "unrelated changes", the source itself has no issues being patched (had to use a wmapro patch from late last march) and works fairly well, though the current included support has advanced quite a bit from that patch.

FFplay version SVN-r19352-4:0.5+svn20090706-2ubuntu2, Copyright (c) 2003-2009 Fabrice Bellard, et al.
configuration: --extra-version=4:0.5+svn20090706-2ubuntu2 --prefix=/usr --enable-avfilter --enable-avfilter-lavf --enable-vdpau --enable-bzlib --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-pthreads --enable-zlib --disable-stripping --disable-vhook --enable-libmp3lame --enable-libmp3lame --enable-libfaac --enable-nonfree --enable-gpl --enable-postproc --enable-swscale --enable-x11grab --enable-libfaad --enable-libxvid --enable-libdc1394 --enable-shared --disable-static
libavutil 49.15. 0 / 49.15. 0
libavcodec 52.20. 0 / 52.20. 0
libavformat 52.31. 0 / 52.31. 0
libavdevice 52. 1. 0 / 52. 1. 0
libavfilter 0. 4. 0 / 0. 4. 0
libswscale 0. 7. 1 / 0. 7. 1
libpostproc 51. 2. 0 / 51. 2. 0
built on Mar 7 2010 00:18:48, gcc: 4.4.1
[wmapro @ 0x912c4b0][18] [0] [3] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [e0] [0] [0] [0]
[wmapro @ 0x912c4b0] ed sample bit depth = 16
[wmapro @ 0x912c4b0] ed decode flags = e0
[wmapro @ 0x912c4b0] samples per frame = 2048
[wmapro @ 0x912c4b0] log2 frame size = 18
[wmapro @ 0x912c4b0] max num subframes = 16
[wmapro @ 0x912c4b0] len prefix = 1
[wmapro @ 0x912c4b0] num channels = 2
[wmapro @ 0x912c4b0] lossless = 0

Blue shows clearly that karmic is not using -r19352

[andrew.46]

Hi mc4man,

There seems to have been some changes of late including some significant ones to dsputil.h (finally rendering the asm_64 patch I had unusable for the moment

I am a little heartened that I chose to remain with an older revision of FFmpeg for my vlc-git guide that patches cleanly... It would be very nice if no patch were required at all but I am not clear if the FFmpeg devs or the vlc devs should be approached, in the meantime I am waiting further developments .

On another note, saw this in lucid which pretty much sets in stone what ffmpeg will be - the 0.5.1 release

By virtue of the timing of the lucid release just missing out on the upcoming .6 release.

Andrew

[mc4man]

out on the upcoming .6 release.

That doesn't seem to be too far away, I do remember some comments by Reinhard Tartler that no ffmpeg upgrade would be considered short of a release (0.6).
I suppose there's a chance though most likely 10.10

Overall I think they've done a very commendable job multimedia wise with lucid - (except for mplayer, though there is a good guide around here somewhere...

On the 64 bit deal - I was just creating new xine-lib 1.18 package sets for karmic and lucid (fixes some flac issues, has wmapro support) and ran into a similar issue when doing the 64 bit ones.
Except in this case it was with x264 instead of ffmpeg - would not accept a static x264 (w/fPIC) at all.
(easily resolved though

So it's not just vlc that can have some issues when doing builds with static linking in 64 bit

[andrew.46]

Hi mc4man,

On another note, saw this in lucid which pretty much sets in stone what ffmpeg will be - the 0.5.1 release

I am not running lucid yet, but I guess amr support is still not included despite the free libraries now available?

Andrew