Project is corrupt (unable to work with the blockfiles)

[jademan]

Here you go

Login - Dropbox

Sorry, that won’t work. You will have to use the dropbox share facilites to provide a link. See: How to share a Dropbox file or folder

Scroll down to the section: Share a Dropbox file or folder

[Nvinther]

All right. Can I just put “jademan” in the sharing-with-box? Or do I need an email address?

[Nvinther]

Well, just tried that. I need an email address to share it with you.

[jademan]

Well, just tried that. I need an email address to share it with you.

So the trick is to skip steps 4, 5, & 6, so anyone who has the link can access the file. PM me the link and I’ll keep it close to the vest. Anyway, you can delete the file once I’ve got it. I’ll let you know.

[Nvinther]

https://www.dropbox.com/sh/z9jqboo7ffhiyz5/AAA-e5eknUcbfrET-1UYKkd0a?dl=0

[jademan]

Go it. - Later…

[jademan]

Dropbox - Audacity - Simplify your life

So I was able to recover most of your project
Unfortunately, there was an error on the second clip of the third track: Blue On Blue - Session 3 råspor, so that clip is omitted in the “PartlyRecovered” project I have uploaded.

I have sent you a link to the recovered file via PM.

[Nvinther]

Hey jademan,

It is doing it again. It is now everytime I am supposed to edit my podcast episodes. I run two. I have just installed the latest update of the software just to see if the bug has been fixed - same problem.

I have a corrupted file that you need to help me with, but honestly I cant work like this. It is the last thing you need to deal with when preparing podcasts in your sparetime.

Let me know what to do.

Thanks

Kr, Niels

[jademan]

It is doing it again. It is now everytime I am supposed to edit my podcast episodes. I run two. I have just installed the latest update of the software just to see if the bug has been fixed - same problem.

I assume you are referring to 3.1.2 which was released earlier today.

I have a corrupted file that you need to help me with, but honestly I cant work like this. It is the last thing you need to deal with when preparing podcasts in your sparetime.

So this is the third (or more) time this has happened to your project. Do you have any suspicions as to why this is happening to you among all people? Candidates might include networked drive, using SD card, running low on storage, power issues, computer issues, etc.

Anyway, you know the drill. I’ll try to rope in a developer. We’ll see what there is to see. The ball in in your court.

[Nvinther]

Hi jademan,

Thanks - I am now uploading the file to my Dropbox.

None of the possible issues you mention is a problem. The only thing I can think of is that I am using an external harddrive, but that has plenty of space and I have been using it with Audacity for more than a year with no problems. The problems started after I updated the software around a month ago.

I will try to use my local drive onwards and see if it solves it.

I will hint you when the file is ready.

Thanks.

Kr, Niels

[Nvinther]

Here you go:
https://www.dropbox.com/s/3z1fecoxqkk2g3v/%2311%20Your%20Run_Alex_ntv%20råbånd.aup3?dl=0

[jademan]

Here you go:

1. OK, I have contacted the developers so we will wait to hear what they have to say.

2. I have a few experimental versions of Audacity that I use to help recover damaged projects. In one of them it went through the project recovery phase then successfully rescued an empty project. Don’t be concerned about this. The reason that I bring it up is that the name of the recovered project was changed:

     2,235,826,176 #11 Your Run_Alex_ntv r†b†nd.aup3
           393,216 #11 Your Run_Alex_ntv r?b?nd.aup3

Which brings up the question: Could this be contributing to the Error #11?

3. I am making better progress with a different recovery program and I feel hopeful that we may be able to recover the first track and possibly part of the second one. Later…

[Nvinther]

Thanks a lot for the efforts!

The most important is the first track. That I only have as aud-file. The other track is an imported mp3-file-recording.

For the file name dont worry - those are Danish letters which is why they are not recognized in your system.

[jademan]

1. OK, I have PM’d you the link. The second track is a little short.

2. The developers said they will look into this matter.

[jademan]

For the file name dont worry - those are Danish letters which is why they are not recognized in your system.

Well, actually I am a little worried - they are recognized. But differently - one way when reading the project file, another way when writing the project file.

[crsib]

The only thing I can think of is that I am using an external harddrive

This potentially can be a problem, although unlikely.

I have been using it with Audacity for more than a year with no problems

And this really can be a problem. Sadly, hard drives fail, and audio editing software does perform lots of writes. Audacity is well known for that too. For regular HDD there is always a chance of mechanical damages. Can you please run

chkdsk

on it? (Assuming you are on Windows)

The reason I suspect some hardware issues is I see a fair amount of “random” bytes out of place in your file. These issues were less critical for Audacity before version 3.0, as it had written many “small” files. The new file format, based on SQLite, can be very sensitive to hardware failures.

[Nvinther]

Hi jademan,

Here link to corrupted file.

https://www.dropbox.com/s/4mvk8e08ei9grj6/BOBCAST%20episode%20%238%20Creative%20process%202_The%20Radio%20They%20Fear.aup3?dl=0

Kr, Niels

[jademan]

@Nvinther

Hi jademan,

Thanks for this. THe file worked fine after you worked with it.

I tried to run the command in cmd, but the system wouldnt allow it to run.
…

So, to run chkdsk, I believe you first need to run cmd as administrator. To do this type in “cmd” in the search box, then press Enter while holding the Shfit & Ctrl keys down.

[Nvinther]

Cheers. I have sent the result in a PM. Seems no bad files and no problems detected

[jademan]

Today you wrote:

@Nvinther

…
To continue working with Audacity I installed the first 3. version and that seemed to solve it, until last night when it made the same crash with a fully edited podcast episode. I am adding a lot of music files under the podcast - I dont know if that could be the issue. The other podcast I run is more simple and there I tend not to have any issues.

Anyways, I need your help again recovering the latest file. I will send a Dropbox link when ready.

My computer runs fine with everything else I do, so it seems weird that there should be an issue with that. I am thinking maybe to install a version 2 instead since there were no issues at all with that software edition.

Thanks for your kind help.

Kr, Niels

and

Cheers. I have sent the result in a PM. Seems no bad files and no problems detected

If you recall, earlier you said:

…corrupted file that you need to help me with, but honestly I cant work like this. It is the last thing you need to deal with when preparing podcasts in your sparetime.

Let me know what to do.

So we asked the developers to take a look. If you recall, they asked you to run chkdsk. They (and I) are anxiously awaiting the results. This may or may not provide useful results.

Please do not misunderstand: I (we) cannot get anymore help from the developers until until we (you) complete this phase first.

So, please let us know how you make out with chkdsk. Thank you.

The ball is in your court.