[FFmpeg-devel] Exact screen size not working: Re: [PATCH] Fix segfault with x11grab when switching windows.

davidpbrown openforum at davidpbrown.co.uk
Wed May 6 11:44:07 CEST 2015


@ffmpeg-devel at ffmpeg.org

tldr; Using exact screen size doesn't work but less one pixel does.


I'm new to ffmpeg but I see a recent message below and wonder there
is an error now.

The ffmpeg I built from source only yesterday.


On a 1366x768 screen this below, sees the error suggested:
ffmpeg  -f x11grab -r 30 -s 1366x768 -i :0.0 -vcodec libx264 -preset
ultrafast -crf 0 -y output.mkv

[x11grab @ 0xa578ae0] Capture area 1366x768 at position 0.0 outside the
screen size 1366x768
:0.0: Invalid argument


This with one pixel size down, works fine:
ffmpeg  -f x11grab -r 30 -s 1365x767 -i :0.0 -vcodec libx264 -preset
ultrafast -crf 0 -y output.mkv

Regards
davidpbrown


==================
Re: [FFmpeg-devel] [PATCH] Fix segfault with x11grab when switching windows.

Matthew Smiglarski Fri, 01 May 2015 00:55:15 -0700

On Fri, May 1, 2015 at 12:29 AM, Michael Niedermayer <michae... at gmx.at>
wrote:
> On Thu, Apr 30, 2015 at 09:27:25PM +0100, Matthew Smiglarski wrote:
>> The segfault occurred when running ffmpeg with x11grab and specifying a
>> resolution size greater than the screen, alongside an offset:
>>
>> ./ffmpeg  -f x11grab -r 30 -s 1920x1147 -i :0.0+0,53 output.mkv


> is this still needed after dc83733f2bf2f26433bbf23d42fe92a2c7691df1 and
> f5c5aa968c3c96ff3968bd5b060e5a0f2f278732

No, no longer needed. Good fix.

The segfault is now avoided and the following message is seen:

[x11grab @ 0x28c7200] Capture area 1920x1147 at position 0.53 outside
the screen size 1366x768
:0.0+0,53: Invalid argument

(return code 1)


Thanks,
Matt
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel at ffmpeg.org




More information about the ffmpeg-devel mailing list