I found out what the problem was. The command defaults because I wasn't specifying a 2-channel (stereo) 192kHz audio input. Here's an example of a command that did work:
$ arecord -f S24_LE -c 2 -r 192000 -d 20 test.wav
The -c 2 is what fixed my commands.
Recording live video and audio during a call (or during any X11 desktop activity) is not very difficult thanks to ffmpeg and the amount of help articles available (including this site). However, if you aim at higher quality, you will quickly reach the limits of the simple approach of simultaneous media grabbing and compressing. Hence the need for ...
A neat trick you can do with PulseAudio: redirect the audio output of your computer to the microphone input, so that any application that supports recording from a mic will get your audio output instead.
I hope it does the trick. It is primarily utilizing ALSA plugin for Audacity
You don't have to play anything if you want but it should create a virtual ...
First identify your microphone device file; should be something similar to /dev/snd/pcmC0D0c. To help you find the device file, you can start a test recording with arecord or such, then do lsof | grep '/dev/snd'; it will list all programs and their associated device file.
Then you can peek usage of the microphone using fuser /dev/snd/pcmC0D0c. It will ...
Just pass asciinema rec a file name as an argument, in which case it will simply save the recording to the local file and not try to upload it to the server. For example:
$ asciinema rec demo.cast
You can then play the recording locally (on the terminal) with:
$ asciinema play demo.cast
And finally upload it with:
$ asciinema upload demo.cast
See the ...
The field owner_pid in the procfs file status of a PCM device shows which program has opened it:
$ grep owner_pid /proc/asound/card*/pcm*/sub*/status
/proc/asound/card2/pcm0p/sub0/status:owner_pid : 1803
$ ps -p 1803
PID TTY TIME CMD
1803 pts/0 00:00:00 aplay
Interesting question, a long time ago I was thinking about simple recording
of digital audio and video, possible via some virtual audio and video
drivers, but never got there.
I used your configuration file and had exactly same problem as you
described. (I removed OSS compatibility drivers from ALSA to be sure, tested different
kernels - did not seem to ...
Firstly, reading your question I wouldn't do it like this. I would be snooping the network and trying to capture the stream. It's probably in a pretty predictable place that can be scripted out with a simple call to tshark. That's another question though.
Improvement over ALSA
While your method is a valid approach, I wouldn't use ALSA. ALSA is a ...
Did you remember to "modprobe snd-aloop"? I've tried it and it works for me with your asound.conf on youtube, pandora, tunein, vonage, and this java player. Could be something specific to Fios, but I don't have Fios to test with. Can you find another publicly available site that also causes the problem?
Also, try recording to a file, then play it back:
It turns out the sound stack developers have anticipated me and written a workaround specifically for situations like mine - I just wasn't able to find it at first.
Aoss does exactly the desired thing: it preloads libaoss.so and then runs another command line, which will then see a /dev/dsp and be able to ioctl/read/write it. So instead of, e.g.
Open Broadcaster Software (OBS) Studio ties all these requirements into an easy to use frontend.
It's open source, and cross platform:
For Ubuntu 15.04 and later:
sudo add-apt-repository ppa:obsproject/obs-studio
sudo apt-get update && sudo apt-get install obs-studio ffmpeg
For other ...
After spending more than one hour trying to vainly setup the ALSA loopback device on Debian, the most effective and least time-consuming solution was to solder an actual device in 5 minutes.
Seriously, I recompiled the kernel to enable the ALSA loopback, I tweaked the /etc/asound.conf and ~/.asound.rc without results.
Via ALSA emulation
I don't have a Debian 6.0.x box to test on, but I think this way will probably work. Courtesy an example on the Arch wiki.
First, use pacmd list-sources to find the name of your sound card's monitor stream. Grep for .monitor works pretty well:
$ pacmd list-sources | grep '\.monitor'
The flac encoder definitely will not do sample rate / bit depth conversion. However, sox can do this for you on the fly. Try this out:
arecord -d4 -f dat -t wav -r 48000 -c 2 | sox - -b16 -r16k -c1 -t wav - | flac - -o message.flac
Arguments to sox are:
- use stdin
-b16 output bit depth
-r16k output 16kHz sample rate
-c1 output one channel
-t wav ...
The manual page for script gives the answer:
Output timing data to standard error, or to file when given.
This data contains two fields, separated by a space. The
first field indicates how much time elapsed since the previous
output. The second field indicates how many characters were
output this time. This information can ...
Here's what I've found to work for recording PulseAudio output.
You can record multiple processes and hear what's being recorded at the same time.
You'll need Pulse Audio volume control (pavucontrol) and some software such as Audacity to record the audio.
Go to the Input Devices tab on pavucontrol and mute all the input devices, unless ...
You will first need to setup ALSA correctly by loading the snd_aloop module and using its named device in an mdev plugin. You will simultaneously output an application's audio through the loop back device and another device of your choice.
Okay, I found an answer. It was right there in the man page of recordmydesktop. In the man page, it is clearly given that recordmydesktop will stop recording AND save the video, if it receives any of these signals: SIGTERM or SIGINT.
Now, by default kill command sends the SIGTERM signal. Hence, if we know the pid of the running recormydesktop process, we ...
Umm so looking at the pulseaudio documentation.
We have the following environment variables
$PULSE_SERVER: the server string specifying the server to connect to when a client asks for a sound server connection and doesn't explicitly ask for a specific
server. The server string is a list of server addresses separated by ...
So after a lot of back and forth with Caleb we've finally come up with a solution to the problem. The login i was trying to do straight to the inventory management software was fiddly, but to quote as per our back and forward conversations tonight, this solved it. No need for recording keystrokes at all. Just good old noggin usage.
The first connection in ...
The ipc_key is used for communication between the programs that share the same device. This means that you have to use different values for different hardware devices, but that all virtual devices that access the same hardware device (i.e., the same slave usb_audio_1) must use the same ID.
The following is simplest procedure I came up with. It will work on any GNU/Linux handheld, but instructions for an Ubuntu touch device are provided, anyway.
On the handheld device
Ubuntu Touch specific: Increase the size of the system.img of your Ubports phone with some extra gigs.
Ubuntu Touch specific: Make your rootfs writable
sudo mount -o remount,...
There are more than one solutions here:
Use tmux-logging plugin.
Use a .bash_profile to log the output to a script.
If you want to use record-session you can always use tmuxinator to setup the ENV and run the commands.
There are probably more ways to do it, but best way IMHO would be to use the plugin.
You can use script and scriptreplay to capture and replay a CLI session. It should already be in your system as part of util-linux. It does not offer play/pause features, though.
script -t 2> timefile
to start the recording (type 'exit' to stop recording) using the default filename typescript and the timing file timefile
You might be looking for recordmydesktop. You can get a window id using wmctrl or xwininfo and then use that id:
recordmydesktop --windowid <id_of_window>
you can use --pause-shortcut to define a key combination for pause/continue.
Excerpt from the arecord's man page:
Interrupt after # seconds. A value of zero means infinity. The default is zero, so if this option is omitted then the record/play‐
back process will run until it is killed.
This is the command I used to record sound indefinitely with a Kinobo Akiro USB microphone using a sampling ...