I would like to record an output of a program with PulseAudio using command line/bash script. It is important not to record all output, but only the output from one specific program.
I thought I would have to create a new null-sink and than move the program's output to this new sink. Than tell parec to use this specific monitor to record.
The first step would be something like this:
pactl load-module module-null-sink sink_name=steam
But how to move the program's output now to this sink?
And how to record the specific sink with a bash script?
Try something like this:
In a terminal enter
(this is the CLI of the PulseAudio-Server) then use
(where you get the indices of the running inputs) Now find the index of your input. Now referred to as $INDEX
the scriptable part is:
Explanations:
Improving Waschtl answer of this thread so you can BOTH LISTEN AND RECORD the app sound:
First, we look for our default output and put its sink name in
$DEFAULT_OUTPUT
:Then, we create a combined sink that has only one slave: $DEFAULT_OUTPUT. The sound generated by the app (source) will be forwarded to the slave sink (ie. real output), and we'll also record it. It is different than a null sink where the source sound is not forwarded.
sink_properties
is optional and may bug if you use spaces in the description name.Then, we could use
pactl move-sink-input ...
command of Waschtl answer (with record-n-play instead of steam) but GUIpavucontrol
is more simple (and great for checking/troubleshooting):Then, we play some sound in the app we want to record. In
pavucontrol
Playback tab, we select in the app dropdown list: "Record-and-Play".Finally, we're good to record and listen at the same time! (lame mp3 example, run in foreground)
Or we can record in background and stop at any time:
NB:
pulseaudio -k
works great to reset everything to session's defaults.pactl load-module module-combine-sink sink_name=record-n-play slaves=real-output-1,real-output-2
.EDIT: Beware, since Ubuntu 18 (maybe 17 too), the combined sink tends to become the default system output device, instead of the real output device. So when you change the volume using the sound icon in the system tray it impacts your record sound. Workaround: After creating the combined sink, open
pavucontrol
in Output tab. Select "View: Virtual Output Devices" and reset the sound volume of the combined sink to 100%. Then select "View: Hardware Output Devices" and press the green icon "Define as alternative" on the real output device.@Waschtl's answer is fantastic. @ixtmixilix asked about restoring regular audio after the recording is finished. Here's the easiest way I know of:
Install and run the
pavucontrol
GUI. You should see your audio-outputting application and it's volume meter under the Playback tab in there. There will be a button next to it showing that it's playing on Null Output. Click on that and change it to your ordinary audio output, Built-in Audio Analog Stereo in my case.Here's a screenshot of what you're looking for:
You can also use this approach to set up your recording in the future, after you've run the
load-module
command in @Waschtl's answer to create the sink.Improving KrisWebDev's answer further, if you want record-n-play to always be available, first find out the default output:
which will output something like:
Next, create a file
~/.config/pulse/default.pa
:Please replace
alsa_output.pci-0000_00_1b.0.analog-stereo
with whatever output you got from thepacmd
command. Pulse does not read the default config file when a custom config file exists - that's why the first line above includes the default config file. That way pulseaudio still loads the default config first.Run
pulseaudio -k
to kill the current pulseaudio instance so a new one is started with the new configuration.If at any time you want to undo the changes here, just remove the
~/.config/pulse/default.pa
file and runpulseaudio -k
.If you want the record-n-play to be the default sink for all outputs, you can do that by adding yet another line to the end of
~/.config/pulse/default.pa
:For programs that pulseaudio already has stored information on, it remembers whatever output device they used last, so you'll have to manually reconfigure those using one of the methods described in KrisWebDev's answer.
I've created this bash script based on the answers provided by @Waschtl and @KrisWebDev answers.
Available here: https://gist.github.com/ramast/4be3314bc73f28f55e3604497188b007
How to use?
New version
I've created a python script that offer some improvements over the old one. https://gist.github.com/ramast/c47bd5e57586e9c2deb74975e27089f0
How to use?
When you press enter the recording will start immediately. if by the time you hit enter the application was already stopped (i.e you closed mplayer for example) the script will wait until the app appear again and start recording.
The only draw back to that script (vs original one) is that if the list contain two entries with same name, the script won't behave correctly. For example
Edit: This is an improved version of the script by @anarcat
Usage:
To produce ogg recording
./pulse-recorder.py -i -o 'test.ogg'
To produce mp3 recording
./pulse-recorder.py -i --encoder "lame -r -q 3 --lowpass 17 --abr 192 - '%s'" -o 'test.mp3'
If a single program is outputting sound you can use this bash one-liner:
Output seems to be about 10MB per minute, and don't mute the program!
I believe this to be a good solution as I don't download a new script, and I don't have to create a new null sink in pulseaudio. It should give odd results if the program has no audio-output when the one-liner starts, or if multiple programs are outputting audio when the command starts.
parec should stop recording when you are done with the application that's playing audio. Some editing applications might have trouble with a aiff file that's 600 minutes long though, if they try and load it into RAM twice.
This is also a poor solution if the application stops and starts outputting audio.
All these answers are amazing and demonstrate the power of PulseAudio ! Digging-in to try to understand them I found a simpler solution (maybe it's a new feature) : we can directly tap into the default output's monitor.
Works great if you want to capture video as well.
One small improvement to solutions here. First, the problem: you may need to adjust the volume of the playback (monitor) of the application while listening to other audio, but not the recording volume. The module-null-sink works if no output is desired, but what if some is needed or this needs to be controlled on-the-fly?
The problem is that PulseAudio does not allow separate adjustment of a single "slave" or output separately from the sink volume. In other words, you could adjust the application (which will affect everything below in the chain, so that's not good) or the sink the application has been connected to, but the end result in both cases is that playback and recording volume will both be affected - regardless if the recording software connects to the application or the sink.
One solution is: we need to add at least one more sink to the chain.
A solution:
Solution here is obvious: by adding one more sink into chain to allow decreasing volume after the recording step without affecting recording. I.e. a simple diagram for the above setup:
This way we can adjust playback volume at
MON
separately from volume incoming toREC
and other applications (music, voice chat etc.) connected toMASTER_SINK
(=speakers).Alternative solution:
But in case REC volume has been decreased and one wants to increase it at MON, some bitdepth will be lost (if I guess correctly how PulseAudio works). Another (perhaps more elegant solution?) would hence be:
But this requires a third sink. But now both recording and playback volume can be genuinely adjusted separately without affecting each other (the first solution works nicely only if the volume needs to be decreased only). Like so:
Now connect your applications output to
rec-n-monitor
, recording software withrec
and can adjust volume of monitor by adjustingrec_monitor
and recording volume by adjustingrec
.For monitor latency, set
DESIRED_LATENCY
for whatever you want. I use 20 (unit is ms). Of course, it depends on your system what the actual latency will be; also see pactl man page. There are other general tricks for lowering Pulseaudio latency, but that is out of scope for this question...