Re: [tlug] Editing Sound Files: Command Line v GUI Programs

["Walter Hansen" <gandalf@example.com>]

my bad. I just figgured he'd read the man page. I used to use something
that was a frontend for sox via GUI, but I really don't remember the name.
Oh,,, also try record and play from the command line. If you've got a mic
hooked up you can record conversations covertly or play ghost noises on
halloween and stuff. Man them for run info.

And yes, sox is a bit clumbersome for editing sound. It has two great
features, 1) it's probably already there, 2) it can do just about
anything. I tend to use it for simple tweaks and conversions and then
bring out something more GUI for stuff that's going to be a lot of work.

> On 17/01/06, Jim <jep200404@example.com> wrote:
>
>> Thanks for example. I _love_ examples.
>
> As do we all.
>
>> How do you know exactly where to snip the excerpt? Unless there's
>> something I'm missing, the command line approach requires
>> cumbersome trial and error to figure out exactly what to extract.
>
> You are correct.
>
>> Audacity allows to me to see the waveform, so that I can make a
>> much better initial guess where to cut, and also allows me to very
>> quickly preview me selection. I'm a big command line bigot, but
>> there some things are just better done with GUIs.
>
> Agreed. I would also choose Audacity for this application, but since
> someone brought up sox without providing an example of *how* to do it,
> I provided one.
>
> Education, you see. ;)
>
> Cheers,
> Josh
>
>