Audacity Forum

Today, I was recording something normally, but just as I finished, a message from Windows came up saying that the program stopped working and that it must closed. I could do nothing but press OK and I had not yet had a chance to save. I downloaded the file recovery software and used it. It recovered 105 small files and 2 large mono (what does that even mean?) ones. However, when I tried to import them back into Audacity, they sounded all messed up and garbled. Looking at the FAQ, I found software (http://www.mesw.de/audacity/recovery/) that could fix it. Apparently, I had to "Import as Raw Data". I then had to use one of the other programs to determine the sample file and endianness (what are those?) of the mono sound clips. The problem is that whenever I try to open it, the same Windows message of it not working appear and the program closes. Is this my only way to find the specs and return the files to its original sound? I am an inexperienced user and all I want to do is return my recovered sound files back to their original sound quality. When looking up help, all I get is confusing technical gibberish that has absolutely nothing to do with my porblem. They talk about using two files and returning it to something to do with stereo and "left" and "right". Can someone please help me? I am in agony over this and I cannot rest until I have a solution.

Not only that, but every time i finish recording anything, the message saying Windows has stopped working appears and the program closes.

<<<Today, I was recording something normally>>>

What was the something?

Koz

Just recording my own voice for a project. It went on for about twenty minutes. I apologize for the ambiguity.

And it's worked OK up until now, or it's never worked? Which Windows?

Sudden Onset Computer Insanity can be caused by your hard drive filling up. Particularly if the crash recovery itself started crashing or acting oddly, that could mean it didn't have any place to put the finished show. Most computers will go nuts when they start to cramp up from lack of space.

-- Right Click Start > Explore > Right Click Local Drive C: > Properties (Used, Remaining)

Koz

Hi,
I also get same problem.

I create a little batch program to recover the .au files an put it on two large channels.
Here the message from my Buzz account:

Franklin Medina - Buzz - Public - Muted
For audacity users,

A very simple way to join crashed .au files. You need to get unix tail command. You may gather it from: http://tailforwin32.sourceforge.net/

You can get it from (need a gmail address)
https://docs.google.com/leaf?id=0B3X-lg ... JkZDgyOTYz

Well, here the program lines.
----------------------------------------------------------------
@echo off
goto START

Save script as: join_AU.bat
Join audacity .au files from a crashed session
----------------------------------------------
Created by Franklin Medina 2010
-------------------------------
Just Run it with parameter the Folder where the .au files are located.
For example: "C:WINDOWSTempaudacity_tempproject3851"
Use:
join_AU "C:WINDOWSTempaudacity_tempproject3851"

:START
set myRnd=%RANDOM%
set Ch_0="%tmp%Channel_0_%myRnd%.au"
set Ch_1="%tmp%Channel_1_%myRnd%.au"

set myPath=%~1
if "%myPath%"=="" ( echo.&echo Usage: %0 [Path] & goto END )

echo.
echo.
echo Channels are [%Ch_0%]
echo and [%Ch_1%]
echo.

REM Must gather [1048576] bytes
GOTO JOIN_DO
A full .au file is: 1.01 MB -> 1,037 KB -> 1,060,956 bytes
We need to get last xxx bytes to avoid sharp noise
tail --bytes=1024 J:mediaAudacityThevenotren_0_1001.au

:JOIN_DO
set bytes=1048576
set /A ctr = 0
set /A idx = %ctr%
FOR /F "usebackq tokens=*" %%i IN ( `dir /B /S /OD "%myPath%*.au"` ) DO (
set /A ctr += 1
set /A mod = !ctr! %% 2
set /A idx += !mod!
set myCh=%tmp%Channel_!mod!_%myRnd%.au
echo !idx!
if !idx! EQU 1 (
echo Copy file [%%~nxi] to [!myCh!]...
copy "%%i" "!myCh!"
) ELSE (
echo Adding [%bytes%] from file [%%~nxi] to [!myCh!]...
tail --bytes=%bytes% "%%i">>!myCh!
)
)
echo.&echo Done

I wonder about that. A common complaint is that Audacity 1.3 au files aren't in numerical order like they are in Audacity 1.2. Could that be because theyr'e in hex instead of decimal?

Koz