Re: [Audacity-devel] Re: 3 Audacity 1.1.3 Comments.
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Daniel J. <da...@mo...> - 2003-04-10 13:41:14
|
> In other words, I still believe that if we implement aliasing > properly, users never need to know that it's going on. It's > just the bugs and limitations of the current implementation that > are causing problems. > > This isn't meant to be the final word; I haven't decided one > way or another yet. Those are just my current thoughts. I'd > like to hear more opinions. Let's go for data safety every time. If we're overwriting an original fil= e, we=20 should always warn the user. What if we get a crash during overwriting?=20 Surely the whole file is at risk, both new and old versions?=20 Personally, I always export as a different filename, in case I've corrupt= ed=20 the file or made a big editing mistake. Sometimes those musical moments c= an=20 never be recaptured...=20 I'm not sure if visually distinguishing between wav and project files is = a=20 good idea. Once the wav is imported, it is a project file - even if it's = only=20 in the temp directory. You could distinguish between imported file formats by colour - eg wav, m= p3,=20 ogg. Then you'd know at a glance if you were working with compressed audi= o,=20 for instance. Stuff recorded directly in to Audacity would then be .au=20 colour, I guess. =20 Cheers Daniel |