[Audacity-devel] HowTo: ExportAsWav be default for "CleanSpeech"?

[Lynn A. <l_d...@ad...>]

<alert comment="newbie to aup projects">

I would appreciate some mentoring on "disengaging" the .aup project
logic from "CleanSpeech". I'm getting ready to attempt to "hack" it
out by trial-and-error on variables such as mDirty, but that seems
like a flawed and unproductive approach.

For a starter, I'd like "CleanSpeech" to be able to detect if the wav
has been modified, and only ask about "Save As" if that was so. Simply
loading and listening to a sermon would not trigger the mDirty flag to
ask about "Save As .aup" at exit. The default would be "Export As Wav"
or "Export as Mp3".

My impression is that the typical Audacity end-user is an advanced
techie/musician who is pain-stakingly mixing together a bunch of
tracks into a stereo demo cd. Audacity seems designed to save a bunch
of pieces into a "knitted .aup project" so it can be loaded quickly as
a unit. The amateur audio engineer might spend hours getting
everything just right over multiple sessions.

Is it kind of like saving a video game in the middle, and being able
to later start it up where you left off?

In contrast, the typically "CleanSpeech / SermonEditor" end-user might
be a church volunteer with average computer literacy and donated
computer, microphone(s), and casette deck. They have two years worth
of sermons to get ready to "broadcast" via their own website, or to
upload to a sermon "repository" such as SermonOnline.

They want to quickly load a sermon, trim the beginning and end as
appropriate, "prep/clean" it in one step (or "batched" with something
like CleanChain), and write it out as a mono .wav file using a low
sample rate to reduce the file size. The last step in an associated
"CleanChain" app would be conversion to a low sample rate .mp3 file.

They DON'T want to have to start each of four-to-six steps in
"attended" mode, with each step taking two to 10 minutes or longer.
(Noise reduction could easily take an hour on an older computer ...
ouch ... these are bbbiiiiggg files)

The current altenatives are $300 - $700 commercial apps ...
complicated and full featured ... tend to have a significant learning
curve.

</alert>