Comment 3 for bug 588034

I don't know if this is related, but there's another mighty ugly elapsed time bug with this version. I'm running the same specs as on this bug report header.

It can't count right.

I'm serious. Bring up the applet to adjust the time/date so that you can see the seconds tick by. Start recording (I did mp3) and note the difference in the elapsed time and date/time clocks. After a few minutes you'll see the program's elapsed time get a second ahead and it keeps going. Record 8 hours worth of stuff and it's waaaaaaay off.

This about drove me insane as I was righting a Python program to read a video captions file (srt) and read the captions using espeak at the correct times, while recording with GMR. I kept staring at the logic, trying to figure out how it could be getting slower and slower...until I realized that GMR was counting too fast!

Oh, for the good old days when the stability of a package was inversely proportional to the version number. Just the reverse now.