Debian Etch Gnome

Hi all,

I found K3b a burning program which is working
Ok after installing a decent cdrecord file.
Under K3b there is an option to transform a
Flac file into a wav file, that seems to work
fine too, getting a nice triumph sound at the end.
OK now I like to know where this new created
.wav file is gone to.
I never was very successful using commands like
"find" or "locate", the gnome search tool doesn't
me much either.
How do I find this wav file on my computer?
Are there any other tools for fast copying
or ripping a track of an audio CD, lossless that is.

What I do want is burning a CD with both MP3 converted
to wav and Flac converted to wav for double blind tests.

BTW under my former OS BeOS I could simply browse
an audio CD and copy any track to my computer
in a flash, is this somehow possible under
Linux too?

Edmund

[ Post a follow-up to this message ]

Horton heard a Who named Edmund saying:
> Debian Etch Gnome
>
> Hi all,
>
> I found K3b a burning program which is working
> Ok after installing a decent cdrecord file.
> Under K3b there is an option to transform a
> Flac file into a wav file, that seems to work
> fine too, getting a nice triumph sound at the end.
> OK now I like to know where this new created
> .wav file is gone to.
> I never was very successful using commands like
> "find" or "locate", the gnome search tool doesn't
> me much either.
> How do I find this wav file on my computer?

Do in a terminal find -name '*.wav' -print

> Are there any other tools for fast copying
> or ripping a track of an audio CD, lossless that is.
<snip>

ogg is as good or better than wav and has a *much* smaller file size than wa
v. I
like soundconverter. My MP3 player requires MP3 so I convert ogg to
MP3 with soundconverter.

--
sk8r-365
The only way to make Windows "secure":
1) go to http://goodbye-microsoft.com
2) replace existing operating system.

[ Post a follow-up to this message ]

Edmund wrote:

> Great I found it.
> Don't know what happened but locate does
> the job too!? Maybe I need a new pair of
> glasses.

Or just read the documentation of the programs
you use.

From the locate(1) manpage:

NAME
locate - list files in databases that match a pattern

SYNOPSIS
locate [-d path |--database=path] [-e | -E | --[non-]existing]
[-i | --ignore-case] [-0 | --null] [-c | --count]
[-w | --wholename] |-b |  --basename]  [-l  N  | --limit=N]
[-S | --statistics] [-r | --regex ] [-P | -H | --nofollow]
[-L | --follow] [--version] [-A | --all] [-p | --print] [
;--help]
pattern...

DESCRIPTION
This manual page documents the GNU version of locate. For each
given pattern, locate searches one or more databases of file
names and displays the file names that contain the pattern.


To speed up the searches "locate" doesn't read the disk contents
but pre-composed databases containing the names of all files and
directories. Changes on the file system will not be seen by "locate"
until the next update of the databases. See also the updatedb(1)
manpage.
On debian etch "updatedb" will be started once a day from:
/etc/cron.daily/find.

Regards,

Kees.

--
Kees Theunissen.

[ Post a follow-up to this message ]

Kees Theunissen wrote:

> Edmund wrote:
> 
>
> Or just read the documentation of the programs
> you use.
>

> Kees.

I get it, thanks :-)

Edmund
>

[ Post a follow-up to this message ]