From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Leo Famulari <leo@famulari.name>
Cc: "help-guix\\\\@gnu.org" <help-guix@gnu.org>
Subject: Re: ffmpeg and alsa/pulseaudio
Date: Fri, 29 May 2020 08:31:51 +0000 [thread overview]
Message-ID: <9g4-oPiGW1KcD2rBiliRz7XQIi7tsTaGGjrDOFdYkajzYe7DqUwLsSIxmtDHmtK5t7MLCVrGU_Ooo-TX9XWrUr0Q_rVqrDdU0Aa6Inf8iZw=@elenq.tech> (raw)
In-Reply-To: <20200529013434.GH5443@jasmine.lan>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, May 29, 2020 3:34 AM, Leo Famulari <leo@famulari.name> wrote:
> On Tue, Apr 07, 2020 at 11:54:35AM +0000, Ekaitz Zarraga wrote:
>
> > Hi,
> > I'm trying to make a screencast with ffmpeg and I'm having issues.
> > I had a screen recording script on the past, based on alsa, but it's not working in guix because it looks like ffmpeg wasn't compiled with alsa. Is that true? Is there something I missing to activate alsa on ffmpeg?
> > This is the command I was running:
> > ffmpeg \
> > -y -f x11grab -draw_mouse 1 -framerate 25 -video_size 1920x1080 -i $DISPLAY \
> > -f alsa -ac 2 -i default \
> > -pix_fmt yuv420p -c:v libx264 -preset veryfast \
> > -c:a libmp3lame -q:v 1 -s 1920x1080 -f matroska \
> > output.mkv
>
> I tried this but it failed with ":0: Invalid argument". That's the
> $DISPLAY variable. Do you know what it should say?
Hi Leo,
Thanks for the answer. I have :1 in DISPLAY and it's not failing because of that.
More on the issue: I had to use a different microphone for this just because of this issue. Looks like when I use a USB microphone and use pulseaudio engine it breaks somehow and records audio with wrong timestamps. An analog microphone works well.
With alsa I found a working configuration but it doesn't work :(
Thanks!
prev parent reply other threads:[~2020-05-29 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 11:54 ffmpeg and alsa/pulseaudio Ekaitz Zarraga
2020-05-29 1:34 ` Leo Famulari
2020-05-29 8:31 ` Ekaitz Zarraga [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='9g4-oPiGW1KcD2rBiliRz7XQIi7tsTaGGjrDOFdYkajzYe7DqUwLsSIxmtDHmtK5t7MLCVrGU_Ooo-TX9XWrUr0Q_rVqrDdU0Aa6Inf8iZw=@elenq.tech' \
--to=ekaitz@elenq.tech \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).