[x264-devel] multi-process encoding problem

[David Wolstencroft]

At a quick glance, It looks like there are some frames repeating
themselves around the late 14 second mark second mark. Check that the
stream is being sectioned properly.

Using:

ffmpeg -fdebug ts (options to decode to /dev/null), I get:

[flv @ 0x101007c00] av_read_frame_internal stream=0, pts=14880,
dts=14800, size=9037, duration=0, flags=1
[flv @ 0x101007c00] av_read_frame_internal stream=0, pts=14920,
dts=14840, size=24, duration=0, flags=0
[flv @ 0x101007c00] av_read_frame_internal stream=0, pts=14960,
dts=14880, size=23, duration=0, flags=0
[flv @ 0x101007c00] av_read_frame_internal stream=0, pts=15000,
dts=14920, size=24, duration=0, flags=0


I'd expect the small frame sizes to signal a repeated frame.

- David

On Tue, Jan 31, 2012 at 8:53 AM, aviad rozenhek <aviadr1 at gmail.com> wrote:
> On Sun, Jan 29, 2012 at 17:42, Steven Walters <kemuri9 at gmail.com> wrote:
>
>> I would instead suggest going back to using a single instance, but apply
>> the demuxer thread patch so you can tell the demuxer that is decoding your
>> original .mpg file to multithread the decode.
>> This would alleviate the decode bottleneck problem, though it would not
>> alleviate a downscale bottleneck...
>>
>
>
> I followed your suggestion and used an x264 build with threaded demuxer
> from http://komisar.gin.by/
> unfortunately, I only reached about ~30% cpu utilization on my 8 core Xeon
> E5520 machine, so it doesn't solve the bottleneck.
> is fragmented encoding really such a bad idea?
>
> --
> Aviad Rozenhek
>
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> http://mailman.videolan.org/listinfo/x264-devel
>