[Audacity-devel] Recovery only sees first of imported tracks

[Gale Andrews]

Hi All

Already marked as essential. If you import more than one audio file (either
with Project > Import > Audio or dragging in multiple files at one go), then
crash Audacity, only the uppermost file that you had on the screen is in the
recovered Project. This does not affect multiple recorded tracks which are
recovered properly.

Win XP SP2


Gale


Outbound message virus free.
Tested on: 9/23/2007 7:32:48 AM

[James Crook]

Please demote to a priority-aim-to.

- The original imported audio is not lost.
- The recovery feature is new, so this is not a regression relative to
1.2.6.
- The failure to import 1.1.x project files, which is not marked as an
essential, is more important than this is, so this has to have same or
lower priority.

--James.

Post by Gale Andrews
Hi All
Already marked as essential. If you import more than one audio file (either
with Project > Import > Audio or dragging in multiple files at one go), then
crash Audacity, only the uppermost file that you had on the screen is in the
recovered Project. This does not affect multiple recorded tracks which are
recovered properly.
Win XP SP2
Gale

[Gale Andrews]

|

[Markus Meyer]

Post by Gale Andrews
If you import more than one audio file (either
with Project > Import > Audio or dragging in multiple files at one go), then
crash Audacity, only the uppermost file that you had on the screen is in the
recovered Project. This does not affect multiple recorded tracks which are
recovered properly.

Are you sure it's not a problem with the time interval? If you import an
audio track, wait 5 minutes, import the next, wait 5 minutes, import the
next etc. then crash Audacity, does it still only recover the first track?


Markus

[Gale Andrews]

|

[m***@mesw.de]

Gale,

Absolutely - I suppose I should have said, but I already waited
after the end of the autosave interval (which I have set to 1
minute) before crashing Audacity.

If the imports take place within the first minute, you can wait forever and it won't create another auto-save point until you do another editing step. Thus, you really need to import the first track, THEN wait some time, then import the second track etc. to test it.

I know this looks counter-intuitive to some and it is not the way many auto-save algorithms work (I also wouldn't have a problem with someone changing this). OTOH, if importing the tracks only takes, say, below 1 minute and it doesn't auto-save, I say, the user only lost 1 minute of work.

Markus

[Gale Andrews]

|

[Gale Andrews]

|

[sl contrib]

Hi Gale,

I guess you're aware of this already, but I've noticed that autosave
recovery seems to depend on whether your are importing into a project
that has been saved already. (Under OS X.)

Scenario 1: Create a new project, save the blank project, import two
tracks, check they are present in the autosave file, crash audacity,
restart. Recovery works fine.

Scenario 2: Create a new project, but don't save it, import two
tracks, check they are present in the autosave file, crash audacity,
restart. Recovery complains about missing files, that nevertheless
exist in temp disk location. No tracks recover.

So somehow there is a problem with recovering audio files from the
temporary files location. There is no problem in scenario 1, where the
blank project is first saved.

Does this match what you are seeing?
Bjoern

[Gale Andrews]

|

[sl contrib]

OK - so the issue is to do with naming unsaved project files. That's
good to know.

I am not sure where this happens in the code - does somebody else know?

The missing </project> tag is noted in the source code - it was
something to do with appending logging data.

Best,
Bjoern

|

[Richard Ash]

Post by sl contrib
The missing </project> tag is noted in the source code - it was
something to do with appending logging data.

Essentially it is because if one was added, it would have to be removed
again before any more could be added to the project, which is a load of
hassle. Therefore it's left open (incomplete) because we always know how
to close it and make a valid project.

Richard