[Arny Krueger]

"Rick Ruskin" wrote in message

On Mon, 14 Jun 2010 16:32:08 -0400, "Arny Krueger"
wrote:

"Rick Ruskin" wrote in message

On Mon, 14 Jun 2010 10:59:08 -0400, "Arny Krueger"
wrote:

"Rick Ruskin" wrote in message


I'm transferring some old 1/2" 16 track material to
wav for a client. I'm saving all files as 24 bit
rather than Audition's default 32 bit floating point
because some programs can't deal with floating
point.. 1 set of files crashes the program when I
attempt to verify they are actually 24 rather than 32
bit. Any ideas as to what's going on and how to
remedy it without having to re-transfer from analog?

I am unfamiliar with what you mean by "verify they are
actually 24 rather than 32 bit".

How are you doing that?




I answered this once before. Audition has a utility in
edit view that will analyze whatever file is being
viewed and give the actual bit rate.

1. In edit view, click on Analyze
2. Choose "Statistics" option from the Analyse menu.
3. The last item on the left ahnd column is "bit
depth."


Try this:

Open the file.
In edit view, click on file, save as
In the file save dialog box, click on Options.
There will be a window titled "format 32 bit data as".
The text in this window will state the actual file
format and allow you to verify that they are actually 24
bit rather than 32 bit.

I did that.

Well, there's your answer. Why continue to struggle?

With the one group of files at issue,
Audition did not behave properly and screwed the files
up.

If you question the integrity of your Audition installation, uninstall it
and reinstall it.

How many times do I have to keep going over the same
ground?

Good question. You're the guy trapped in the loop. You kept doing the same
thing over and over again, expecting a different result. When a fairly
well-debugged program like Audition locks up accessing file data, it usually
means that data files are truely corrupted in unusual ways.

At this point, I don't care anymore because
I've re-transferred the material.

Unless you've diagnosed some problem with your system and corrected it, the
same thing is likely to happen again.

At this point many possibilities seem open. There could be a hardware
problem with your hard drive, and it works up from there.

Semi-relevant anecdote. My primary A/V production computer has 4 hard drives
ranging from 250 GB to 1 TB each. The machine started locking up randomly -
once a week, then once a day, then it would only stay up for a few hours. I
eventually isolated the problem to the 500 GB boot drive. It took a fair
amount of time and effort to recover the disk and transfer the data, but
once the failing drive was replaced with aa new 1 TB drive, all was well.

My point is that the failures that I now see on hard drives are different
from past experience. Instead of data corruption that we saw in the past, I
now see more systems either totally locking up or blocks of data just going
missing.