Universal Media Server

[SubJunk]

First of all, thanks for these builds, it's really great what you're doing

I'm a developer of Universal Media Server, which has supported FFmpeg since its first version but we're looking to use newer builds and add better support/features for FFmpeg.

The problem is that between the March 19th and March 25th releases of FFmpeg something changed to break seeking.
There are some things I can do to investigate it still but I just wanted to quickly ask if you changed anything in the build environment between those dates that would account for this change?

Cheers!

[rogerdpack]

The build environment "probably" hasn't caused any breaks, but I'm no expert there

[Zeranoe]

Can you be more specific on the issues your having? Open new threads for the issues.

[SubJunk]

I've fixed this now. In case anyone was interested, it was caused by FFmpeg ccfa8aa26f666372f47d69bc49e420a9b4239626 which enabled reordering of UDP packets by default.

[rogerdpack]

So this is fixed in newer builds of ffmpeg, now?

[SubJunk]

Sorry, I should have been more specific.
That revision was the cause of the "bug" (not sure if it is a bug or a feature that just happens to be incompatible with UMS) and in the next release of UMS (either 1.3.1 or 1.4) we will be getting around that revision by passing "-max_delay 0" to FFmpeg.

[rogerdpack]

If you can get a reproducible test case then I'd inquire about it, to make sure they didn't introduce a bug...
-r

[SubJunk]

I was wrong about which revision it was. I've done some digging now and found that it was 967facb that caused FFmpeg to sometimes output files that are incompatible with PS3 and other renderers.
Unfortunately that commit isn't easy to reverse since it was the introduction of the encode2() function which was widespread.

Files are only incompatible if they seek to certain points, for example using "-ss 2" may be compatible while "-ss 3" may be incompatible. I suspect it has something to do with proximity to keyframes.

I'm trying to make a patch for it now.

[rogerdpack]

Yes you may want to bring this up on ffmpeg-devel or ffmpeg-users and see if they have any ideas too, and to alert them of the problem.
Thanks for looking into this.
=r

[SubJunk]

Thanks, rogerdpack. I just made an issue report here.