Today (for the second time I was using the MT for a mission-critical purpose), it failed.
Firmware: 1.2.0 (I hadn't checked for a newer one, d'oh)
1/4" TRS inputs (Left and Right) with +27dB boost on, M setting, de-linked levels, 16 bit 44.1 KHz
Kingston Elite Pro 50x GF 1GB 1024-S (supported officially by m-audio) ... which was formatted on the MT under 1.2.0 (not sure if it came formatted, but was constantly reformatted in the first days of me fooling around with 1.2.0)
Now, I've always been very antsy about the way this thing records.... That is, you can record over an hour and then when you stop the recording you have to wait (and sweat bullets) while it "writes file." If that part fails, the data is likely lost. Is it just me or does this feel really scary?
Anyway, today I noticed about half an hour into recording, the recording was stopped. It was on track 1/1 00:00:00/00:00:00
I was perplexed, because I had about an hour left. So I hit the record button to stop the file... thinking the numbers were just strange. Then the write file window came up (Writing File...) but it just stayed on screen forever. I tried powering off and a popup said you can't power off while still recording. And since the file wasn't being written successfully, it wouldn't let me power off.
When I got home, it was finally off (I did have auto-off at 15 min, maybe that's it)... when I powered on, it showed there was a file there ... but it was 0 byte. It was never written successfully, so I don't know how the file even got there. I thought if the MT doesn't finalize a file, it's just not there.
Anyway, before I had a chance to peruse these threads, I had already reformatted the CF card, so I don't even get to try the method using chkdsk /f on the MT, then recovery of the WAV file through CEP (what is CEP by the way?)
Now, what could cause my initial problem? What happens when the MT can't finish writing a file? Is there a way to hard-reset the unit? Should you eject the card manually or not?
I hope (hope hope hope) that the bug I got (suddenly the counters read 00:00:00/00:00:00 which I thought was suspicious, and the recording stopped, and it couldn't record any more) is related to the incorrect time remaining counters that were just fixed. But maybe not.
maybe this problem is going to happen again and again. I really lost face today when I had to admit to my client that the whole interview may have been lost.
Anyone else have this issue or know anything about it?