softhddevice mit OSD (va-api-glx) und 720p - kein Bild

  • I tested a software decoder very little, there was no such error, I will test more.

    Cause i'm blocked here :) Is there anything i can do like debug outputs or other to support you to find the reason for these 'TS packet(s) not accepted in Transfer Mode' errors? Or there any alternatives with OSD in the meantime? xinelibout seems to work but with high cpu load...


    Thanks

    Torsten

    VDR: Silverstone SG05 Lite, ASRock MB H510M-HDV R2.0, I3 10100, 8GB RAM, Ubuntu 22.04, vdr 2.6.4, 120GB SSD, 8TB SSD, Digital Devices Max S8X, Nvidia GT730, IR-WAKEUP USB

  • i've recompiled with debug. Attached the log of the transfer error.


    softhdvaapi doesn't work at all, log is full of these messages:

    Code
    VAAPI-ERROR: video/vaapi: vaSyncSurface failed: operation failed

    For softhddrm it's not clear for me how to use, with or without X11?

  • Zitat

    For softhddrm it's not clear for me how to use, with or without X11?

    ja wird ohne X11 genutzt.

    (VDR) NUC11PAH & GEEKOM MINI-IT11-11. Generation * BM2LTS * DD NET S2 Max * NC * (Sound) Cinebar Lux Set * (Stream) Apple TV 4K (2022) *

    (Light) PHILIPS Hue Play HDMI Sync Box & Gradient Lightstrip * (OLED TV) LG OLED65G29LA

  • Make a log from normal softhddevice work to first buffer overflow please.

    But va-api-glx is not working there. I can only try without OSD (-v va-api -f -D -w no-hw-decoder).


    For softhddrm i have no clue. I startet vdr (without X11) with "softhddrm -f -D -w no-hw-decoder -a hw:0,7 -p hw:0,7" but i get no picture at all. Are there any additional configuration required for drm? i attached the start log for drm.

  • Ye, missunderstanding... here the full log.

    But maybe its the log of "-v va-api-egl -w no-hw-decoder" instead of "-v cpu-egl". Is this a problem? But options are behave identically.

  • xinelibout is also possible without vaapi but only without the skindesigner plugin as vdr crashes with them.

    I've reproduced the problem now.

    skindesigner and other skins use "True Color OSD". For this reason, TrueColor must first be set in xineliboutput "Setup->OSD->Color depth".

    Other entries do not work in this case.

    The log then shows the following:

    No Segfault at all, but no OSD either. Everything else is functional.

    I think this is the real problem in this case: "[input_osd] ARGB overlay not supported by video driver".

    I don't know if there is a configuration parameter to enable ARGB.

    So, that problem cant be fixed in the skins.


    PS: for skin lcars you have to use "Automatic" in "Setup->OSD->Color depth"


    Grüße

    kamel5

    VDR 2.6.6: ASUS Prime X470-PRO, Ryzen 7 5700X, 64GB, 6TB HD, GT1030, Fedora 39 Kernel 6.7 X86_64, Devicebonding 2 x 1 auf 2, TT6400, DVBSky S952 V3

    Git-Repo: gitlab.com/kamel5

  • I have done some short tests and it's also working here. I will have a look next days, to see if there are any problems left.

    Thanks for your work!


    Torsten

    VDR: Silverstone SG05 Lite, ASRock MB H510M-HDV R2.0, I3 10100, 8GB RAM, Ubuntu 22.04, vdr 2.6.4, 120GB SSD, 8TB SSD, Digital Devices Max S8X, Nvidia GT730, IR-WAKEUP USB

  • Very short Test :( i got the same problem like said some posts before with -w no-hw-decoder, but here i tested with HW decoder (va-api-egl). Means randomly the picture hangs about a minute with these log entries:

    Code
    Nov 20 17:40:12 vdr vdr: [7115] ERROR: 1 TS packet(s) not accepted in Transfer Mode
    Nov 20 17:40:17 vdr vdr: [7118] i/o throttle activated, count = 1 (tid=7118)
    Nov 20 17:40:23 vdr vdr: [7118] buffer usage: 100% (tid=7115)
    Nov 20 17:40:24 vdr vdr: [7118] ERROR: driver buffer overflow on device 1

    I will recompile with debug enabled. Any ideas about that problem?

    VDR: Silverstone SG05 Lite, ASRock MB H510M-HDV R2.0, I3 10100, 8GB RAM, Ubuntu 22.04, vdr 2.6.4, 120GB SSD, 8TB SSD, Digital Devices Max S8X, Nvidia GT730, IR-WAKEUP USB

    Einmal editiert, zuletzt von wtor ()

  • I retested with debug enabled. VDR was started at Nov 20 17:48, and it hangs at 21:36 for about a minute. Here the start and the end of the problem in short:


    Code
    Nov 20 21:36:03 vdr vdr: [22173] ERROR: 1 TS packet(s) not accepted in Transfer Mode
    Nov 20 21:36:09 vdr vdr: [22175] i/o throttle activated, count = 1 (tid=22175)
    Nov 20 21:36:17 vdr vdr: [22175] ERROR: driver buffer overflow on device 1
    Nov 20 21:36:54 vdr vdr: [22175] i/o throttle released, count = 0 (tid=22175)

    So, the vdr runs fine without problems for about 4 hours, then the problem occured. This happens in different time ranges (today afternoon it happend about 20 minutes after vdr start). I attached the full log for further analyzing.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!