Audacity Forum

Hello.
Thx for the links


But unfortunately there is no AppData or Roaming folder in my User/Gustavs/ folder

I did reinstall it 2 times and the folder wasn't there, but that I did because i can scroll trough my time line only by seconds and that is annoying. But I probably miss clicked something in options to make it like that.
(I did the guide for showing hidden folders, still nothing. ) sorry


If there is another thing I can do or try, let me know.

I went to preferences and copied the location from temporary file directory and posted it in my folder. And it took me to a project file folder, but all i saw there was AU format sound. ( with or w/o the extension hiding)

Gustavs wrote:unfortunately there is no AppData or Roaming folder in my User/Gustavs/ folder

It's probably hidden by Windows.
See here for how to make hidden files and folders visible: http://windows.microsoft.com/en-US/wind ... dden-files

Yes, Steve, that worked. I were able to get to the AutoSave folder going trough all the folders you mentioned( appdata/Roaming and then Audacity) but it was empty

This is awkward, pffffffffffft

Gustavs wrote:I were able to get to the AutoSave folder going trough all the folders you mentioned( appdata/Roaming and then Audacity) but it was empty

Thanks for trying. You only have an autosave file if there are unsaved changes. If Audacity crashes, there will be unsaved changes, so that would be the time to make a copy of the autosave file for us to take a look. You want to leave the original autosave file there for Audacity to recover from.

Are you still getting crashes? If it is only the one project doing it, have you tried Export Multiple to export WAV files for all the tracks, then import the WAV files into a new project and save it as a new name?



Gale

Yes, I made Audacity Crash again, and got an autosave file. But I cant send it to you, since I'm getting this message "The extension autosave is not allowed" when trying to post it here.

Edit:I did make a copy on my desktop and tried to add the file from there .

Edit: Audacity didnt crash on my new project which at this point doesnt have a lot of tracks yet, so I loaded the old one who has plenty, and got the crash. Tho there have been times when it goes trough, thou like 1 out of 30.


Edit: I have not tried what you recomended by exporting multiple tracks, but I did just fine by applying the compresion to all tracks, and after the crash pressing "Recover Project" which got me to the point where the Compression has been applied. Tho it might be so that it skipped some clips, tho I didnt notice.

Gustavs wrote:Yes, I made Audacity Crash again, and got an autosave file. But I cant send it to you, since I'm getting this message "The extension autosave is not allowed" when trying to post it here.

Sorry, I didn't consider that you would have to rename it to .txt extension. But I allowed the "autosave" extension now as it is Audacity-specific. We cannot allow ".cfg" extension for the Audacity settings file for security reasons.

Gustavs wrote:Edit: Audacity didnt crash on my new project which at this point doesnt have a lot of tracks yet, so I loaded the old one who has plenty, and got the crash. Tho there have been times when it goes trough, thou like 1 out of 30.

Edit: I have not tried what you recomended by exporting multiple tracks, but I did just fine by applying the compresion to all tracks, and after the crash pressing "Recover Project" which got me to the point where the Compression has been applied. Tho it might be so that it skipped some clips, tho I didnt notice.

The only real point in doing export multiple is if there is some structural/corruption problem with a particular project.

How many tracks do you have in the project that crashes? If you have that number of tracks in other projects, does that crash?

As I said before, you may do better by mixing tracks as soon as you can, or storing some tracks in a separate project window and copying and pasting them between projects when you need to.

Also make sure you do not have "Audio cache" enabled in the Directories Preferences because it uses memory for most editing.


Gale

I had around 70 tracks + I'd say.

When I will start to get crashes on the new project il check the count.

When I was assembling my latest soundtrack using 1.3.9 I hit a crash trying to add the 30th track. I upgraded to 1.3.14 and completed the project successfully (49 tracks). I then did a "Help...Run Benchmark..." using default values and the report indicated I could handle 79 tracks on my configuration. It could be that the 70 tracks is close to the limit for Gustavs' machine?

Peter

Gustavs wrote:I had around 70 tracks + I'd say.

When I will start to get crashes on the new project il check the count.

Thanks for the autosave file. It looks fine structurally, assuming the empty tracks you had halfway down the project were intended.

@Peter. The Benchmark test is only a very rough and ready indication and doesn't take much account of the length of the tracks. Gustav's tracks are mostly only about 10 seconds long, but he would probably crash with fewer tracks if they were longer.

Some improvements to handle more tracks were made a few Beta versions ago, but there are still practical limits which will vary from machine to machine.



Gale