1.3.3 recording signal drops to -1.0 - was OK in 1.3.2

[quack]

Hi people
long time user, first time poster (as they say on the radio)

Wonder if anybody can help me with a problem I've found using 1.3.3 and 1.3.4

I'm making long length recordings at low bit-rate, using 8000Hz sampling, 16-bit mono.

I've found that, after a couple of hours, the signal level drops from its usual "hovering around 0" position to -1 (i.e. the bottom of the chart) and stays there. The exact time it takes is variable... sometimes 1 hour, sometimes 13 hours, but once it's there it never comes back.

This worked fine in 1.3.2 - and continues to do so if I reinstall 1.3.2, but 1.3.3 and 1.3.4 both exhibit this problem.

I'm using the mic input of the built-in sound on an Asus P4P800-deluxe motherboard which has an AD1985 AC97 codec. I guess it might be something to do with my hardware but the fact that I can reinstall Audacity 1.3.2 and things work fine makes me suspect Audacity.

Anybody else seen anything like this?

Thanks

Jon

[quack]

Here's a capture of what my audacity looks like right now to illustrate the problem.

I started the recording with a freshly running copy of Audacity 1.3.4 and a new project. Running on a fully patched version of Windows XP-SP2

You'll notice that the input level meter is still responding but the track panel shows the signal level down at -1.0 and that's what's been recorded (so there's a loud click at the cut-off point and then silence),

I don't have massive amounts of free disk space on this drive, but the 2GB free translates to several days of recording at this sample rate and the project is currently only taking up 450MB

Jon

audacity.jpg (45.02 KiB) Viewed 501 times