VDR developer version 1.7.32 is now available at
A 'diff' against the previous version is available at
This is a *developer* version. Even though *I* use it in my productive
environment. I strongly recommend that you only use it under controlled
conditions and for testing and debugging.
The main focus of this version is on an improved frame detection code,
and improvements to the cutting process. When cutting a recording, VDR
now removes any "dangling" TS packets from the beginning of an editing
sequence and pulls in any "pending" TS packets at the end of a sequence.
It also fixes all timestamps and continuity counters.
However, while the results look much better now in, for instance, Kaffeine,
the TT S2-6400 still shows some video artifacts at the editing points, and
the Mac video player sometimes totally chokes on edited material.
I did spend a lot of time trying to find out what could still be wrong here,
but couldn't come up with any new ideas. So I think it's now time to invite
others to test this new cutting code, read the source code and try to find
out what's still going wrong here. Maybe (hopefully ;-) it's just some stupid
little error... ;-)
The changes since version 1.7.31:
- Pressing the Play key during normal live viewing mode now opens the
if there is no "last viewed" recording (thanks to Alexander Wenzel).
The same behavior has been implemented for the Blue key in the main menu.
- cIoThrottle::Engaged() is now also checked in
to suspend removing deleted recordings in case this is necessary to make room
new, ongoing recordings (suggested by Udo Richter).
- The cThread constructor now has an additional boolean parameter that can be
true to have this thread run at a lower priority. Plugin authors that use low
priority threads may want to use this instead of the calls to SetPriority(19)
SetIOPriority(7). The priority of a thread ("low" or "high") is now logged
- Changed DTV_DVBT2_PLP_ID to DTV_STREAM_ID in dvbdevice.c to adapt to an
change in DVB API 5.8 (reported by Derek Kelly).
Removed the meanwhile obsolete definition of FE_CAN_TURBO_FEC.
- Fixed some compiler warnings under gcc version 4.7.1.
- Fixed setting the video format in the dvbhdffdevice (thanks to Torsten Lang).
- Fixed 'make install' to not overwrite existing configuration files (thanks to
- Added including the Make.global and Make.config files to the dvbdhffdevice's
- Added options to build a 32-bit version of VDR on a 64-bit machine to
- Fixed handling VPS timers in case the running status of an event goes to '1'
running) and later goes to '4' (running).
- If a frame position in the 'marks' file of a recording doesn't point to an
it will now be shifted towards the next I-frame, either up or down, whichever
closer (suggested by Udo Richter).
- Fixed a possible memory leak in SI::StructureLoop::getNextAsPointer()
- Fixed handling timers in case an event is modified and "phased out" while the
- Improved frame detection by parsing just far enough into the MPEG-4 NAL units
the necessary information about frames and slices.
- The initial syncing of the frame detector is now done immediately after the
complete GOP has been seen. This makes recordings and especially pausing live
start up to twice as fast as before.
- Updated the Romanian OSD texts (thanks to Lucian Muresan).
- Fixed handling the very last entry in a recording index.
- The return type of cMarks::Add() has been changed to void, since due to the
of the list of marks the returned pointer might have pointed to a totally
mark. Besides, the return value was never actually used.
- Improved editing TS recordings by
+ stripping dangling TS packets from the beginning of a sequence
+ including pending TS packets at the end of a sequence
+ fixing all timestamps and continuity counters
+ generating editing marks for the edited version in such a way that each
point is marked by an "end" and "begin" mark with the same offset
+ no longer generating an editing mark at the "end" of the edited recording
was actually generated at the beginning of the last GOP, so that a
edit would have cut off the last GOP)
+ no longer generating any editing marks if the edited recording results on
one single sequence
+ ignoring pairs of editing marks that are placed at exactly the same
a recording when actually cutting the recording
+ not doing anything if the editing marks in place would result in the edited
version being the same as the original recording
- Editing marks can now be placed directly on top of each other, in which case
simply mark a position, but have no effect on the actual cutting process.
- When positioned at an offset where two (or more) editing marks are placed on
of each other, the '4' key moves the first one of them to the left, while the
key moves the last one of them to the right. The '7' and '9' key handle
marks at the same place as if it were one single mark.
- Modified editing marks are now written to disk whenever the replay progress
gets hidden (thanks to Christoph Haubrich).
vdr mailing list