I am using software called Gnome Sound Recorder to record some audio. However, it gives me no options to do anything with the recordings aside from deleting it. I have looked high and low for the file, even using the whereis
command and poking around in the corresponding directories, but have found nothing. Any help would be greatly appreciated–I recorded a half hour long recording and don't want to lose it!
Can’t find file recorded using Gnome Sound Recorder
audiognome
Best Answer
n8te commented that the files are in the subdirectory
Recordings
of your home directory. My answer covers how to find the files if the application doesn't give you a clue.While an application has the file open, you can use
lsof
to locate it. Note that this only works while the file is open at the operating system level, which may not always be the case while the application displays the file. For example a text or image editor typically opens the file to read or save it, but closes it immediately after each load or save operation. But I would expect a sound recorder to write progressively to the output file, and for that it would keep the file open as long as it's recording.To find what files an application has open, first install
lsof
. It's available as a package on most distributions. Open a terminal; all my instructions use the command line. You'll need to determine the process ID of the application. You can run the commandps xf
(that's on Linux; other Unix variants have different options for theps
command; as a last resort you can useps -e
to list everything). Trypgrep sound
ps x | grep -i sound
to locate all the running programs whose name contains “sound”. Alternatively, runxprop | grep _NET_WM_PID
and click on the program window. Once you've determined the process ID, for example 1234, runAnother approach is to look for recently modified files. You can use the
find
command for that. For example, to look for files modified in the last 5 minutes:~
means your home directory. A saved file would normally be in your home directory because that's the only location where an application is guaranteed to be able to write, except for temporary files that can be wiped out as soon as the application exits.-type f
restricts to regular files (we don't need to see directories here) and-mmin 5
means “less than 5 minutes ago”. There's also-mtime
which counts in days instead of minutes. If you're looking for a file that's been moved rather than created or modified, use-cmin
instead of-mmin
; the ctime is the time at which anything was last done on the file except for reading it (but including changing permissions, moving, etc.). You can also look for files by name, e.g.looks for files whose name contains
blendervid
(and you can add something like `-mmin -5 further restrict matches to recent files).If you know part of the name of a file and the file was created a while ago, you can use the
locate
command.locate
is a lot faster thanfind
because it uses a pre-built index. But it can only find files that existed when the index was built. Most distributions arrange for the index to be rebuilt every night, or soon after boot (via anacron) if the system isn't always on.