VDR 2.7.9: Cutting clean HD recording generates tons of errors

Rene · February 9, 2026 at 9:16 PM

Hi,

I have a strange problem when cutting clean hdtv recordings with the latest 2 or 3 release versions of vdr. I have recordings without errors (according to VDR Live status of a recording), but when i cut them, i get a ton of errors. One example is a clean 1920x1080 dvb-c recording that after cutting gets 32304 errors and cutting points are getting artifacts. I do not see any errors in the lots either.

This has actually got worse since i switched from SD to HDTV last autumn (finland swithced from sd to hd last year).

Does anyone know why this happens?

jsffm · February 9, 2026 at 9:34 PM

Do you set the cutting points by hand or autom. by markad or similar tool?

Rene · February 9, 2026 at 10:52 PM

I'm doing it by hand. Markad works pertty bad compared to noad that i used before. Markad marks almost none of my recordings I was actually starting to look if i could run markad manually..

kfb77 · February 10, 2026 at 12:15 AM

Quote from Rene

Markad works pertty bad compared to noad that i used before. Markad marks almost none of my recordings

offtopic: If you want, I can take a look at a log (but then a new thread or in the markad thread).

Rene · February 10, 2026 at 7:32 PM

Quote from kfb77

offtopic: If you want, I can take a look at a log (but then a new thread or in the markad thread).

That would be great! I'll check if i can figure out how to enable debugging for markad! A working ad marker is the only thing that i am missing

kfb77 · February 10, 2026 at 7:38 PM

You will find the command for a good log and more information here:

kfb77/vdr-plugin-markad: Continuation of the development from https://projects.vdr-developer.org/git/vdr-plugin-markad.git

Rene · February 10, 2026 at 9:07 PM

ahaaaa! I missed that i could run markad manually too! This makes much more sense now Thanks!

I'll look for the markad thread, and post some logs

SHF · February 12, 2026 at 2:02 AM

In vdr2.7.8 there was change/fix in the errorhandling which may result in a wrong errorcount of older recordings.
The recommendation is to reindex all older recordings with vdr --genindex.
There is a script available too: #11
I'm not sure if it helps here, but it worth a try, I think.

Rene · February 12, 2026 at 8:54 AM

This happened with a fresh recording done with 2.7.8, but it would make sense to reindex all recordings if there has been a change during all these years I'll have a look!

SHF · February 13, 2026 at 12:50 AM

Quote from Rene

This happened with a fresh recording done with 2.7.8

Then it is probably a different problem.

Is the audio also affected or video only?

Quote from Rene

finland swithced from sd to hd last year

Maybe some new type/subtype of codec or unusual encoder setting, vdr doesn't fully support yet?

What does mediainfo and ffprobe tell about the recordings?

SHF · February 15, 2026 at 1:50 AM

There are now similar reports about cutting-bugs.

Post

RE: VDR version 2.7.9 freigegeben

Ich habe jetzt auch eine Ungereimtheit festgestellt:

UHD-Aufnahme (2160p)
Originalaufnahme: 0 Fehler (verm. mit VDR 2.7.7 gemacht)
Geschnitten: 4 Fehler (die man auch sieht, Pixelsalat jeweils im unteren Viertel des Bildes, verm. mit VDR 2.7.8 geschnitten)
Index neu erstellt mit VDR 2.7.9: nur noch 1 Fehler, aber der Ausgabedecoder hat an den drei unmarkierten Stellen immer noch Probleme und hält kurz an, d.h. die Fehler sind definitiv da

FireFly

February 14, 2026 at 4:00 PM

RE: VDR version 2.7.9 freigegeben

Participate now!