diff options
| author | Klaus Schmidinger <vdr@tvdr.de> | 2011-06-12 14:24:09 +0200 |
|---|---|---|
| committer | Klaus Schmidinger <vdr@tvdr.de> | 2011-06-12 14:24:09 +0200 |
| commit | b0fd7ed93387b2958aa438b0bbbf190874413f29 (patch) | |
| tree | d7050b3d9872739fe4b7a54842cc072aa19d01c2 /HISTORY | |
| parent | 72d342ce02cbeddfccf1c56fc0e614dfbe569608 (diff) | |
| download | vdr-b0fd7ed93387b2958aa438b0bbbf190874413f29.tar.gz vdr-b0fd7ed93387b2958aa438b0bbbf190874413f29.tar.bz2 | |
Fixed overwriting the fps value in a recording's info file
Diffstat (limited to 'HISTORY')
| -rw-r--r-- | HISTORY | 6 |
1 files changed, 5 insertions, 1 deletions
@@ -6607,7 +6607,7 @@ Video Disk Recorder Revision History - Avoiding an unecessary call to Recordings.ResetResume() (thanks to Reinhard Nissl). -2011-06-11: Version 1.7.19 +2011-06-12: Version 1.7.19 - Fixed cString's operator=(const char *String) in case the given string is the same as the existing one (thanks to Dirk Leber). @@ -6640,3 +6640,7 @@ Video Disk Recorder Revision History - The frame detector now only starts collecting PTS values after it has seen the first I-frame, otherwise it might get MaxPtsValues values and stop analyzing even though the incoming data is still garbage (reported by Derek Kelly). +- The info file of a recording is now only overwritten with a new fps value if + that new value is not the default value (thanks to Derek Kelly for reporting a + problem with the fps value being overwritten in case a recording was interrupted + and resumed, and the fps value could not be determined after resuming recording). |