Re: HOWTO: Install and use the latest FFmpeg and x264

Here's the thing I find odd- I used to able to download videos from Y T (or other sources) in mp4 format and put them on my iPod. Now, after upgrading to iTunes 10.5 and re-installing XP most mp4's need some sort of conversion before they can play perfectly on my iPod. It's a pain-in-the-neck and I'm sick of it.

As I said some other place Linux just doesn't have an easy program that'll manage music for iPod and that's why I'm stuck with that stupid Windows/iTunes stuff.

Re: HOWTO: Install and use the latest FFmpeg and x264

Originally Posted by PDA1

Here's the thing I find odd- I used to able to download videos from Y T (or other sources) in mp4 format and put them on my iPod. Now, after upgrading to iTunes 10.5 and re-installing XP most mp4's need some sort of conversion before they can play perfectly on my iPod. It's a pain-in-the-neck and I'm sick of it.

As I said some other place Linux just doesn't have an easy program that'll manage music for iPod and that's why I'm stuck with that stupid Windows/iTunes stuff.

well thats apple for you changing all sorts of things on your device behind your back, LOL, that's why people today are preferring to buy ARM/NEON dual and quad core Devices this year with a nice Linux OS installed and ready for ARM x264/ffmpeg encoding (Yes ARM with NEON SIMD devices can run "x264/ffmpeg directly" unless their default locked as standard like apple)

well try that sample i made for you and see if it plays fine on the pod, i can give you a windows bat script that will convert all your files to that format if it plays fine i dont know bash shell script so someone else can convert that for linux use later perhaps...

Re: HOWTO: Install and use the latest FFmpeg and x264

Originally Posted by FakeOutdoorsman

I consider FFmpeg from Git to be stable (for my purposes) on most occasions, but others have disagreed with me. Of couse a project with such active development will encounter issues, but most of the time they are fixed in a timely manner. Once again, others have disagreed with me on this point.

If you don't feel comfortable using the bleeding-edge, then you can try a recent release version. For a typical user a release version probably won't have any advantages over FFmpeg from Git other than they are called a "release" to ease any anxiety from stability concerns.

Compiling and installing a release version is fairly similar to using FFmpeg from Git as shown in the guide. Just download your desired release version from the FFmpeg download page, extract the archive file, and then continue with the guide starting with the appropriate ./configure line.

As for x264, there is a stable branch. x264 updates are usually pushed in one big dump every month or two. This includes fixes and other non-fix updates. The stable branch will include the most recent fixes, but the other non-fix updates won't be included in stable until the next set of updates. This allows the developers to catch any unforseen bugs that can be fixed before the next push to stable, and therefore hopefully decreasing the number of bugs encountered by the user. That's the idea at least, as I understand it, but I don't know how many bugs have actually been avoided in stable. To switch to the stable branch for x264, enter the following command before the x264 ./configure command:

Code:

git checkout stable

I have succeeded in solving the git problem and moved up to the final 7th step. That's where my next problem occured. Apparently libfaac is not found (although I checked synaptic and there is an item called "libfaac0" but it's already istalled! So I've bumped into another odd problem, namely: I don't even know what the problem is

I went to synaptic and noticed that I wasn't able to install the files and to me the problem seems to be that there is a version discrepancy in my system. I tried to see where that came from and my suspicion is that I use certain "ppa"s or "builds" of a couple of programs including Pulseaudio. That version incompatibility seems to be the root cause of the problem so far as I can see but as I'm not expert I can't prove that. Why else is it possible that there are stuff in the repository yet I can't install them?!?!

Re: HOWTO: Install and use the latest FFmpeg and x264

That's the most PPAs I've ever seen anyone use (I generally avoid them myself). You need to track down which one(s) is causing your problems. mc4man is usually good at navigating issues like this. Maybe he can help pinpoint which repository is to blame.

Re: HOWTO: Install and use the latest FFmpeg and x264

Originally Posted by Jerriy

^ That's not solving it

I went back and re-read the results and noticed something I overlooked before: that during step 2 things were not exactly going on as planned
libvorbis-dev: Depends: libvorbis0a (= 1.2.3-3ubuntu1) but 1.3.1-1ubuntu1~ppa1~lucid1 is to be installed
Depends: libvorbisenc2 (= 1.2.3-3ubuntu1) but 1.3.1-1ubuntu1~ppa1~lucid1 is to be installed
Depends: libvorbisfile3 (= 1.2.3-3ubuntu1) but 1.3.1-1ubuntu1~ppa1~lucid1 is to be installed
[/CODE]I went to synaptic and noticed that I wasn't able to install the files and to me the problem seems to be that there is a version discrepancy in my system. I tried to see where that came from and my suspicion is that I use certain "ppa"s or "builds" of a couple of programs including Pulseaudio. That version incompatibility seems to be the root cause of the problem so far as I can see but as I'm not expert I can't prove that. Why else is it possible that there are stuff in the repository yet I can't install them?!?!

So as it stands you'd need to add either ppa to your sources, then you could install libvorbis-dev OR just go one of the pages, click on "View package details", expand the vorbis entry & download & install libvorbis-dev, it's the same in either ppa

As far as libpulse-dev, who knows..., search out pulse in synaptic & post the complete name of your installed libpulse packages - if you highlight it, > properties you can see & maybe some additional info

Additionally -
In synaptic - click on the "Origin" tab on left side, this will list all your current sources & packages available & installed from - you should be able to figure some things out by highlighting the various ppa's & then seeing what you have installed from them

If you used lucidbleed experimental to upgrade packages previously then you'd probably be better off re-enabling that ppa depending on what you installed from there.

Overall the amount of ppa's you have enabled is fairly ripe ground for trouble, particularly if you've just done 'blanket updates', & not paid attention to what packages may have been replaced.