This section is now closed
Forum rules
Audacity 1.2.x is now obsolete. Please use the
current Audacity 2.1.x version.
Mac 0S X 10.3 and earlier are no longer supported but you can download legacy versions of Audacity for those systems
HERE.
-
waxcylinder
- Forum Staff
- Posts: 14585
- Joined: Tue Jul 31, 2007 11:03 am
- Operating System: Windows 10
Post
by waxcylinder » Mon Jun 01, 2009 8:54 am
kozikowski wrote:
The problem comes when you actually start editing a Project. Should you, say, import a sound clip into your show, that clip, in its current location becomes part of the Project. You can Save Project all day long, but if you move that one clip, the show collapses.
Unless that is you take the trouble to reset your Audacity preferences so that on importing audio files the audio is
copied into the the project rather than just referenced an pointed at. The copy option is not the default and therefore you are required to set it - the Copy option is marked as "safer" whereas the pointer option is marked as "faster" -which is why many folks leave the setting as it is - they want it fast, who doesn't?
But this faster option is really targetted at power-users who really know waht they are doing with Audacity.
As Koz alludes to many newbie (and some not-so-newbie) Audacity users get burnt by moving or deleting the referenced sound clip .
WC
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * FAQ * * * * * Tutorials * * * * * Audacity Manual * * * * *
-
taueva
- Posts: 11
- Joined: Sat May 30, 2009 1:06 am
- Operating System: Please select
Post
by taueva » Mon Jun 01, 2009 9:30 pm
So does this mean that if I make the change in Prefs to copy that I won't have the crash problem described by Koz?
-
kozikowski
- Forum Staff
- Posts: 68941
- Joined: Thu Aug 02, 2007 5:57 pm
- Operating System: macOS 10.13 High Sierra
Post
by kozikowski » Mon Jun 01, 2009 10:04 pm
The crash problem can be caused by anything, any instability. Remember Audacity runs on multiple platforms and they're all constantly evolving. The code can't be unconditionally stable everywhere all the time. So given that sooner or later Audacity is going to go face-first into the mud, it's good to have that last WAV file to go back to. There should be no reason to ever need to go back and capture the work again. The capture master WAV files take care of that.
The people who get killed are the ones who capture a once-in-a-lifetime live performance, Save the Project, edit it, and try to export to MP3. No Exports anywhere in the pipeline. When that Audacity fails, the whole show dies. "But I saved my AUP sound file regularly," they complain, completely misunderstanding how Audacity works.
Koz