Softhddevice + ffmpeg > 3.2 (vdpau)

  • I can't reproduce this.

    But try this patch, may be it help you.

  • With your patch it works as usual again, thanks!

    Asus H170 PRO GAMING, Intel Core i7-6700T, 16GB RAM, GeForce GTX 1050 2GB, Samsung SSD 860 EVO 1TB SSD + 3TB WD Red, Mystique SaTiX-S2 Dual, Archlinux -> VDR4Arch


    "Freunde sind Menschen, die dich mögen obwohl sie dich kennen"

  • Hi lnj,

    Do you have any solution for the green OSD problem with Ubuntu Focal on Nvidia Kepler cards (GT730/630 and 720) with thevonly working driver 450?

    Linux Anfänger bittet um Unterstützung bei der V5

    I have no idea. It happens not only with Skindesigner but also with anthra in text2skin and others.

    Regards and thank you for supporting and your development of your Softhddevice fork!!

    Stefan

    Test-VDR1: HP rp5700 Fertigsystem, Core2Duo E6400, 2GB RAM, FF-SD C-2300, nvidia Slim-GT218 x1 | easyVDR 2.0 64Bit
    VDR3: in Rente

    VDR4: MSI G31M2 v2, Digitainer2-Geh., t6963c 6" gLCD, E5200, 2GB, 3TB WD Red, GT730, 2x TT S2-3200; easyVDR 3.5 64bit
    VDR5: Gigabyte
    GA-G31M-S2L, Intel E2140, Zotac GT730 passiv, Digitainer2-Geh., t6963c 6 " gLCD, 2 TB WD Red, 2x TT S2-3200 (an 1 Kabel) easyVDR 3.5 64bit
    VDR6:
    Intel E5200, GT630 passiv, F1 750 GB, t6963c gLCD, 2x TT S2-3200 | easyVDR 3.5 64bit
    VDR-User #1068
    www.easy-vdr.de

  • I use a gt720 as well, with yavdr-ansible, and never had a "green OSD" or green teletext. Just now I even have updated to the latest nvidia-460.97-beta from the .run-file, and it installs flawlessly, even with the nvidia-uvm module and dkms (when uvm did not compile using the -450 version).

    What is the major difference between easyvdr5 and yavdr there, regarding this nvidia-card?

    Btw,. using softhddevice, inj-branch.

    --
    vdr User #2022 - hdvdr2: Lenovo SFF M83, Intel(R) Core(TM) i5-4670S, 14 GB Ram, zram-swap/tmp, ubuntu-focal, softhddevice-vdpau
    ddbridge-6.x mit 2xDVB-S2 und (Flex) 2xDVB-C/T Tunern, nvidia-GF1050Ti SFF (nvidia-dkms-495), System SSD btrfs,

    snapper, 8TB HDD XFS/cow /srv/vdr, yavdr-ansible-2.5.6-seahawk, vdr-epg-daemon mit Frodo-plugins, Kernel 5.15.6-xfsscrub

    vdradmin-am, live+webstreaming, vdrmanager (Smartphones als FB), ffmpeg-4.3.1-libfdk_aac, vdr-plugin-hbbtv.

  • What is the major difference between easyvdr5 and yavdr there, regarding this nvidia-card?

    My current theory is that easyvdr5's openbox configuration rules cause unwanted size changes for the softhddevice window(s): Linux Anfänger bittet um Unterstützung bei der V5

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • After this 2 messages

    Code
    1. May 2 18:44:35 vdr3-2 vdr[2718]: Cuvid Driver API error = 0709
    2. May 2 18:44:35 vdr3-2 vdr[2718]: video/cuvid: render frame error

    restart without further messages :(


    vdr-User-# 755 to_h264 chk_r vdr-transcode github

  • I use cuvid, I can´t turn back time to enable debug.


    vdr-User-# 755 to_h264 chk_r vdr-transcode github

  • I worked with a crop mark, set, move


    vdr-User-# 755 to_h264 chk_r vdr-transcode github