GNOME Bugzilla – Bug 696371
Allow recording sound when using the integrated recorder
Last modified: 2013-03-22 10:05:03 UTC
I wanted to report a bug in GNOME. I needed to create a video screencast including sound, in order for the developers to better understand the issue. Because I know gnome-shell recorder can't record sound, I used gtk-recordmydesktop. Unfortunately it's somewhat broken and the end of my video was muted. Then I googled a bit and found out the gnome-shell recorder can be modified to record sound: http://askubuntu.com/questions/112473/audio-not-working-for-gnome-screencast-ctrl-alt-shift-r I tried both the pipelines and none of them work. When I set it and hit Ctrl+Alt+Shift+R, nothing happens, the recorder doesn't start. I would like to demonstrate that you need to provide an easy way for people to report their issues, if you want to know their issues. Of course, all of the problems above are solvable, but it's one obstacle after another, and only a handful of people will make it all the way. So, I would like to propose: 1. Record sound by default. If you search the Internet, people are asking for it. If someone doesn't want his sound to be recorded, he can simply mute the microphone. Every general user knows how to mute the microphone. Almost no one knows how to modify gstreamer pipelines. -or- 2. Have a dconf option to enable sound recording. Don't require people to input whole gstreamer pipelines, which can go wrong on so many places. No, just a checkbox. If someone is able to find out about Ctrl+Alt+Shift+R, he's probably also able to open up a dconf-editor, find the key and tick the checkbox. Or execute a simple terminal command to flip the boolean option on or off. Both options would be a great improvement on current situation. Thanks. Software version: https://fedoraproject.org/wiki/Test_Day:2013-03-21_Gnome_3.8 - the included x86_64 live image gnome-shell-3.7.92-2.fc19.x86_64
After a bit more googling, I assume the gstreamer pipelines didn't work, because Fedora contains newer gstreamer (1.0 vs 0.10) which has changed syntax and commands a bit. This is yet another example why you shouldn't require users to input whole pipelines if they want to change one simple thing - turn on audio.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 665548 ***