Explicit versions for ffmpeg and mplayer?

[stuckless]

Hey Jeff, do you happen to know the explicit version for ffmpeg and mplayer? And/or, are there any modifications to these sources? ie, I'd like to compare the originals to the modified to see what was modified for SageTV (if any).

Also are there any instructions on how to upgrade ffmpeg/mplayer (or is that even possible).

I'm currently attempting to do a full rebuild under linux and I uncovered a a few things, mostly dev packages that need to be installed in addition to what you've listed. I've finally got it to build and create .deb packages, so that's a good sign I'll create a pull request for the README updates, or I can send you changes directly, whatever you want.

[Fuzzy]

This might have some insight:

http://www.sagetv.com/pubcode/

[stuckless]

Originally Posted by Fuzzy

This might have some insight:

http://www.sagetv.com/pubcode/

Still no explicit versions (for ffmpeg and mplayer) just versionless tars.

UNLESS these are versions that were used BEFORE modifications were made??

[SHS]

Dose this help stuckless
FFMpeg version 0.5
MPlayer version 1.0 rc2

[stuckless]

Originally Posted by SHS

Dose this help stuckless
FFMpeg version 0.5
MPlayer version 1.0 rc2

Thanks... That should be good.

[Fuzzy]

Originally Posted by SHS

Dose this help stuckless
FFMpeg version 0.5
MPlayer version 1.0 rc2

except I don't think that's entirely correct. The CHANGELOG in the v7 ffmpeg source, for instance, shows the <next> version after 0.6, which make me think that it was based off of at least 0.6+ something.

[Fuzzy]

running them each shows
MPlayer dev-SVN-rUNKNOWN-4.2.4
and
FFmpeg version SVN-r93

[SHS]

Originally Posted by Fuzzy

running them each shows
MPlayer dev-SVN-rUNKNOWN-4.2.4
and
FFmpeg version SVN-r93

The third_party dir
MPlayer ChangeLog show 1.0 rc2
FFmpeg ChangeLog was miss version but it eazy to check by looking at ChangeLog

[stuckless]

Originally Posted by SHS

The third_party dir
MPlayer ChangeLog show 1.0 rc2
FFmpeg ChangeLog was miss version but it eazy to check by looking at ChangeLog

Yeah, I first checked the ffmpeg Changelog but it just said Version <next>

Thanks again... this helps.

Sean.

[KJake]

Would love to see these updated, especially on the extenders.

[tmiranda]

Originally Posted by stuckless

I'm currently attempting to do a full rebuild under linux and I uncovered a a few things, mostly dev packages that need to be installed in addition to what you've listed. I've finally got it to build and create .deb packages, so that's a good sign I'll create a pull request for the README updates, or I can send you changes directly, whatever you want.

Can you post a list of the steps that need to be taken to do the linux build?

[Narflex]

The ffmpeg/mplayer versions in SageTV have a fair amount of modifications done to them. It's not really a trivial task to upgrade them...some of the changes were bug fixes, some feature adds for metadata output or placeshifting rate control, and some of other various features (like optimizing thumbnail selection).

I did have to update it awhile ago at Google for security reasons...and spent a bunch of time finding the original code it branched from (for ffmpeg). It was basically a binary search process until I found the one with the least diffs...I don't know the exact version; but it was a variant of ffmpeg 0.5 (and likely the release one).

It would be great to get it back up to speed with the current versions of each...but that is going to be a lot of work for someone with lots of potential for breakage relating to SageTV (it does expect specific formatting of data when using ffmpeg to parse non-mpeg media files or extract their metadata).

[Fuzzy]

I'm wondering how many of the tweaks would not be needed in the newer ffmpeg builds due to bugfixes. Some architectural changes might work well to get rid of some of the mods as well. Placeshifter could go to a segmented approach similar (or exactly like) HTTP Live Streaming, for instance, so instead of ffmpeg changing it's bitrate on the fly, it simply encodes the next segments at the different bitrate. If we can get to a point where ffmpeg needs NO changes, and everything is worked around core ffmpeg features, we can have a much better time keeping tech up to date.

[stuckless]

Originally Posted by tmiranda

Can you post a list of the steps that need to be taken to do the linux build?

Ubuntu 15.x

# export JDK_HOME=/usr/lib/jvm/java-8-oracle/
# sudo apt-get install libx11-dev libxt-dev libraw1394-dev libavc1394-dev libiec61883-dev libfreetype6-dev yasm autoconf libtool build-essential

You can use whatever java you want, java-8 was the version I had installed, so I used it.

[tmiranda]

Originally Posted by stuckless

Ubuntu 15.x

# export JDK_HOME=/usr/lib/jvm/java-8-oracle/
# sudo apt-get install libx11-dev libxt-dev libraw1394-dev libavc1394-dev libiec61883-dev libfreetype6-dev yasm autoconf libtool build-essential

You can use whatever java you want, java-8 was the version I had installed, so I used it.

Thanks. I could also use a GitHub primer. How do you get the code from GitHub to your local machine?

[jreichen]

Download a git command line client or gui client and use it to clone from https://github.com/google/sagetv

[stuckless]

Originally Posted by tmiranda

Thanks. I could also use a GitHub primer. How do you get the code from GitHub to your local machine?

Here.. I setup a simple primer here...
http://forums.sagetv.com/forums/show...066#post575066

[tmiranda]

Originally Posted by stuckless

Here.. I setup a simple primer here...
http://forums.sagetv.com/forums/show...066#post575066

Thank you. Just what I was looking for.

I think it's worth mentioning in the guide that you can build the Sage.jar file in Linux and then use it in a Windows install. I believe this will end up being a fairly common thing to do as a lot of the functionality is in Sage.jar and there is currently no way to build under Windows.

[Narflex]

Originally Posted by tmiranda

Thank you. Just what I was looking for.

I think it's worth mentioning in the guide that you can build the Sage.jar file in Linux and then use it in a Windows install. I believe this will end up being a fairly common thing to do as a lot of the functionality is in Sage.jar and there is currently no way to build under Windows.

Yes! Great point. You can easily upgrade from SageTV 7 to the open source version by doing just 2 things.

1. Replace the Sage.jar with the one built from the OS code
2. Put the lucene-core-3.6.0.jar file in your JARs folder

You can download the lucene file from here:

https://github.com/google/sagetv/blo...core-3.6.0.jar

And then click on the RAW button to get it to actually download the file for you.

[nyplayer]

Originally Posted by Narflex

Yes! Great point. You can easily upgrade from SageTV 7 to the open source version by doing just 2 things.

1. Replace the Sage.jar with the one built from the OS code
2. Put the lucene-core-3.6.0.jar file in your JARs folder

You can download the lucene file from here:

https://github.com/google/sagetv/blo...core-3.6.0.jar

And then click on the RAW button to get it to actually download the file for you.

So if I just want to check out the features you posted in Windows here this is all I have to do?