From: novaTopFlex via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "bryan@lunduke.com" <bryan@lunduke.com>,
"ffmpeg-user@ffmpeg.org" <ffmpeg-user@ffmpeg.org>,
"ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Cc: novaTopFlex <andrewkaymars@proton.me>
Subject: [FFmpeg-devel] X Window Capture using FFmpeg
Date: Mon, 30 Jun 2025 14:56:45 +0000
Message-ID: <mailman.4805.1751295415.1384.ffmpeg-devel@ffmpeg.org> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 2493 bytes --]
From: novaTopFlex <andrewkaymars@proton.me>
To: "bryan@lunduke.com" <bryan@lunduke.com>, "ffmpeg-user@ffmpeg.org" <ffmpeg-user@ffmpeg.org>, "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: X Window Capture using FFmpeg
Date: Mon, 30 Jun 2025 14:56:45 +0000
Message-ID: <7kUVe_Rv_14MK1xZpdmukfXUeis0W1DSmKDYJ3iI8-xWkbejMQULq62Pf5uF_TPG7L4ee5AdSAeqpK6tkLUcviTj7vSlyrI0UUkUX59fLHk=@proton.me>
I have just reported an incident where I had attempted to utilize ffmpeg with the specific purpose of X window capture. As of now, X window capture is not currently supported using FFmpeg. So far, the latest command that I had attempted for an X window capture was the following:
ffmpeg -f x11grab -framerate 60 -video_size 644x537 -show_region 1 -i :0.0+137,292 out2.mp4
Unfortunately, however, my goal was not to record this portion of the screen specifically. Instead, my goal was to utilize the window identifier, 0x0614eb7.
Andrew Kay (novaTopFlex)
Sent with [Proton Mail](https://proton.me/mail/home) secure email.
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
reply other threads:[~2025-06-30 14:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.4805.1751295415.1384.ffmpeg-devel@ffmpeg.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=andrewkaymars@proton.me \
--cc=bryan@lunduke.com \
--cc=ffmpeg-user@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git