Recording Timer Rolls over at 24 Hours

[MeadeRobert]

WARNING: Filling out the template below is NOT optional. Issues not filling out this template will be closed without review.

FIRST: Before reporting any bug, make sure that the bug you are reporting has not been reported before. Also, try to use the nightly version if possible in case I've already fixed the bug.

Hardware

• CPU: Intel i9 12900k
• RAM: 128 GB
• GPU: NVIDIA RTX 3090
• SDR: Remote - sdrpp server for Airspy HF+running on an x86 ubuntu server machine

Software

• Operating System: Windows 11 x64
• SDR++: v1.1.0 (Built at 01:55:44, Oct 29 2023) Bug Description The recording timer overflows at 24 hours and starts ticking from 0 again even if a new file is not opened. The timer could count higher rather than overflowing or this function should be documented.

Steps To Reproduce

1. Record 24 hours or greater of baseband
2. ...
3. ...

Only If SDR++ fails to lauch or the SDR fails to start: Run SDR++ from a command line window with special parameters:

• On Windows, open a terminal and cd to SDR++'s directory and run .\sdrpp.exe -c (if running SDR++ version 1.0.4 or older, use -s instead, though you should probably update SDR++ instead...)
• On Linux: Open a terminal and run sdrpp -c
• On MacOS: Open a terminal and run /path/to/the/SDR++.app/Contents/MacOS/sdrpp -c Then, post the entire logs from start to after the issue. DOT NOT truncate to where you think the error is...

Screenshots

Additional info

[AlexandreRouma]

Well yeah, that's just how time works, the number of days just isn't shown because recording for that long is silly and almost certainly results in a file larger than what WAV supports in the first place.