VDR developer version 1.7.32 is now available atftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.32.tar.bz2A 'diff' against the previous version is available atftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.31-1.7.32.diffMD5 checksums:068ba78fd427694dcc480fe3b2d07148 vdr-1.7.32.tar.bz2222f1e9b4d4edaa6fe57286409614cc7 vdr-1.7.31-1.7.32.diffWARNING:========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 Recordings menuif 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 cRemoveDeletedRecordingsThread::Action(),to suspend removing deleted recordings in case this is necessary to make room fornew, ongoing recordings (suggested by Udo Richter).- The cThread constructor now has an additional boolean parameter that can be set totrue to have this thread run at a lower priority. Plugin authors that use lowpriority threads may want to use this instead of the calls to SetPriority(19) andSetIOPriority(7). The priority of a thread ("low" or "high") is now logged when thethread starts.- Changed DTV_DVBT2_PLP_ID to DTV_STREAM_ID in dvbdevice.c to adapt to an incompatiblechange 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 PeterMünster).- Added including the Make.global and Make.config files to the dvbdhffdevice'slibhdffcmd/Makefile.- Added options to build a 32-bit version of VDR on a 64-bit machine toMake.config.template.- Fixed handling VPS timers in case the running status of an event goes to '1' (notrunning) and later goes to '4' (running).- If a frame position in the 'marks' file of a recording doesn't point to an I-frame,it will now be shifted towards the next I-frame, either up or down, whichever iscloser (suggested by Udo Richter).- Fixed a possible memory leak in SI::StructureLoop::getNextAsPointer() (reported bySundararaj Reel).- Fixed handling timers in case an event is modified and "phased out" while the timeris recording.- Improved frame detection by parsing just far enough into the MPEG-4 NAL units to getthe necessary information about frames and slices.- The initial syncing of the frame detector is now done immediately after the firstcomplete GOP has been seen. This makes recordings and especially pausing live videostart 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 sortingof the list of marks the returned pointer might have pointed to a totally differentmark. 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 cutting 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 (this was actually generated at the beginning of the last GOP, so that a subsequent edit would have cut off the last GOP)+ no longer generating any editing marks if the edited recording results on just one single sequence+ ignoring pairs of editing marks that are placed at exactly the same position of 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 theysimply 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 topof each other, the '4' key moves the first one of them to the left, while the '6'key moves the last one of them to the right. The '7' and '9' key handle multiplemarks at the same place as if it were one single mark.- Modified editing marks are now written to disk whenever the replay progress displaygets hidden (thanks to Christoph Haubrich).Have fun!Klaus
0 Members and 1 Guest are viewing this topic.