We use Audiologger set up to record from three stations in our group. Installed late in 2013, before I got here.
Trying to get to the root of a problem where we get error windows on a regular basis - usually “integer overflow” and sometimes “invalid floating point operation.” At least once a day we’ve cleared as many as a dozen of those accumulated windows … software is still functioning, although if too many errors pile up, it’ll crash the application.
Up until last week, we had it set to record full WAVs, purging all files older than 14 days. Thinking that the machine’s resources might be taxed, I changed the settings so it now records all three stations in 256-bit MP3. Oddly, we went almost a full day without an error, then I caught just one (1). The result of my change was fewer of these popups, however I notice they seem to be again happening more frequently.
At the surface, nothing looks out of sorts. Any help will be most appreciated!
Russell Wells
Louisville Public Media
Louisville, Ky.
Yes - however, the machine is not linked to the ‘outside world’ … unless there’s a way to save a bug report locally that I missed, the best I can do is offer screen shots of the various “detail” tabs.
Thanks. Looks like this happens when the silence duration (time since the signal was above the Silence Threshold value) grows too large. Workaround is to disable silence detection by setting the threshold to 0dB. I’ll let you know when I have a permanent fix available.
Haven’t yet installed the link you gave, but after tweaking the silence-detection to 0 for the two which were set at -30 (one was already at 0), I haven’t had an error window in 24 hours.
I’ll put the new one in later today, and give it a test over the long weekend.
