On Wed, 3 Nov 2010 23:05:59 +0100, Halim Sahin <halim.sahin@xxxxxxxxxxx> wrote: > Hi, > On Wed, Nov 03, 2010 at 04:56:13PM +0100, Rene Bartsch wrote: >> The most sensible solution is to just add a UNIX_Timestamp >> of the exact recording start to the info file. > > That would need a well synchronized systemtime to dvb-time of the > transponder were the recording comesfrom. > Aditionally the cuttingmarks will differ for cable/sat users due to some > delays of the > broadcasters etc. Maybe the cut function of VDR can be improved to move cutmarks relatively to the start of a recording. If you get cutlists, the offsets BETWEEN the cutmarks are the SAME, but the offset to the START of the recording can DIFFER. A solution would be to import cutmarks into VDR and move the first mark to the correct position with e.g. the left/right keys. The correction offset can then be applied to all other cut marks automatically. > Finding a well working solutions seems dificult to me . Not really. Sharemarks uses the PTS in the TS-stream to place exact cut marks. The database server is still online, but the 3 year old last version of Sharemarks it not compatible with VDR 1.7. Maybe someone can revive the Sharemarks script and adjust it to new VDR versions. But it still would be great to have the start timestamp (and maybe the option to move all cutmarks with the same offset) to import non-VDR cutlists. > Better use some of noad/markad plugin. Better NOT. NOAD worked relatively well, but markad messes up cutmarks. There are channels with over 50 cutmarks in one recording. I really don't want to remind how much time it has cost to remove so much wrong cutmarks from ONE 90-minute recording. Or VDR just uses cutmarks with NTP-based timestamp and PTS in the marks file ;-) That way the PTS can be used and timestamps if there is no PTS or broken PTS. Best regards, Renne _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
