Skip to content

[🐛 Bug]: ffmpeg is being built without audio devices support(pulse, alsa) #2584

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
alexblatov opened this issue Jan 14, 2025 · 5 comments · Fixed by #2586
Closed

[🐛 Bug]: ffmpeg is being built without audio devices support(pulse, alsa) #2584

alexblatov opened this issue Jan 14, 2025 · 5 comments · Fixed by #2586

Comments

@alexblatov
Copy link

alexblatov commented Jan 14, 2025

What happened?

Since these changes d66ac52
We lost the option to use ffmpeg with capturing audio args:
ffmpeg -y -f x11grab -video_size 1920x1080 -i $DISPLAY -f pulse -ac 2 -i default -r 12 -c:v libx264 /home/seluser/chromium/desktop-capture.mp4

The reason is because ffmpeg is being built without
--enable-pulse
flag on ./configure step.

Command used to start Selenium Grid with Docker (or Kubernetes)

ffmpeg -y -f x11grab -video_size 1920x1080 -i $DISPLAY **-f pulse -ac 2 -i default** -r 12 -c:v libx264 /home/seluser/chromium/desktop-capture.mp4

Relevant log output

$ ffmpeg -y -f x11grab -video_size 1920x1080 -i $DISPLAY -f pulse -ac 2 -i default -r 12 -c:v libx264 /home/seluser/chromium/desktop-capture.mp4
ffmpeg version 7.1 Copyright (c) 2000-2024 the FFmpeg developers
  built with gcc 13 (Ubuntu 13.3.0-6ubuntu2~24.04)
  configuration: --prefix=/usr/local --extra-cflags=-I/usr/local/include --extra-ldflags=-L/usr/local/lib --pkg-config-flags=--static --enable-gpl --enable-nonfree --enable-libx264 --enable-libxcb --enable-static
  libavutil      59. 39.100 / 59. 39.100
  libavcodec     61. 19.101 / 61. 19.101
  libavformat    61.  7.100 / 61.  7.100
  libavdevice    61.  3.100 / 61.  3.100
  libavfilter    10.  4.100 / 10.  4.100
  libswscale      8.  3.100 /  8.  3.100
  libswresample   5.  3.100 /  5.  3.100
  libpostproc    58.  3.100 / 58.  3.100
[x11grab @ 0x558149dd9940] Stream #0: not enough frames to estimate rate; consider increasing probesize
Input #0, x11grab, from ':99.0':
  Duration: N/A, start: 1736849663.162687, bitrate: 1988667 kb/s
  Stream #0:0: Video: rawvideo (BGR[0] / 0x524742), bgr0, 1920x1080, 1988667 kb/s, 29.97 fps, 1000k tbr, 1000k tbn
[in#1 @ 0x558149de2840] Unknown input format: 'pulse'
Error opening input file default.
Error opening input files: Invalid argument

Operating System

Windows 10

Docker Selenium version (image tag)

4.27.0-20250101

Selenium Grid chart version (chart version)

No response

Copy link

@alexblatov, thank you for creating this issue. We will troubleshoot it as soon as we can.


Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

@VietND96
Copy link
Member

Ok, I will add this. It will be delivered via Nightly image tag for your evaluation.

@VietND96
Copy link
Member

@alexblatov can you use selenium/video:nightly and confirm before we release official images?

@alexblatov
Copy link
Author

alexblatov commented Jan 23, 2025

tested on our side, works fine now, thank a lot for your support @VietND96 !

Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Feb 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants