softhddevice mit vdpau: Überblick verloren

Hier hat seahawk1986 mal eine sehr schöne Übersicht erstellt:

Ausgabeplugins für yaVDR

Die Übersicht ist zwar speziell für das ansible-book von yaVDR erstellt, aber im Prinzip ist sie allgemeingültig!
Da werden Deine Fragen ziemlich gut beantwortet.

Als nvidia-Treiber kannst Du für die GT1030 den aktuellsten nehmen.

Hi,

Es gibt für nvidia die Version von lnj und die von jojo61 die gepflegt werden.

Bei beiden kann über Parameter gesteuert werden, welche Version es werden soll : Softhddevice oder softhdcuvid oder softhddrm etc.

Ich würde, wenn du X nehmen willst lnjs Version testen. Wenn ohne X (umschalten zu Kodi dann schwer machbar) dann Softhddrm.

Wenn UHD relevant bleibt meine ich nur jojos softhdcuvid. Aber ganz unberechtigt ist die Frage echt nicht 😉

MfG Stefan

For Nvidia softhddevice or softhdcuvid only.

I am using this version, maintained by seahawk

vdr-plugin-softhddevice-cuvid:
Installiert:           1.2.7+git20211229-1-e7cda5e-0yavdr2~focal
Installationskandidat: 1.2.7+git20211229-1-e7cda5e-0yavdr2~focal

It's available at http://ppa.launchpad.net/seahawk1986-hotmail/vdr-2.6.0/ubuntu focal/main amd64 Packages and actually the same as the vdpau version, you just have to change one line in the config file to switch:

#
# softhddevice VDR plugin arguments
#

[softhddevice]

-v cuvid
# -v vdpau

and restart vdr to change between both variants.

Yes, vdpau seems to have more deinterlace options and appears to be sharper with SHD, but struggles a bit with UHD.

@nvertigo

Not quite right.

Supported softhd* git now:

softhddevice

https://github.com/ua0lnj/vdr-plugin-softhddevice.git - vaapi, vdpau, cuvid. OpenGL osd with vdpau and cuvid.

softhdcuvid(softhdvaapi, softhddrm)

https://github.com/jojo61/vdr-plugin-softhdcuvid.git - vaapi (drm), cuvid, OpenGL osd with all. Uses libplacebo for HDR, but requires more powerful CPU.

For GT1030 cuvid is better than vdpau.

With the latest Nvidia driver and cuvid, you will get 10-bit h265 UHD decoding without any other action.

Vdpau can 8 bit h265 UHD, but can't 10 bit.

You can try everything and choose what you like best.

Quote from lnj

For GT1030 cuvid is better than vdpau.

With the latest Nvidia driver and cuvid, you will get 10-bit h265 UHD decoding without any other action.

Do you mean over HDMI-Output or Displayport?

If only Displayport, can you get a recommendation for a DP-HDMI-Adapter?

I mean 10-bit h265 UHD decoding.

No 10 bit output with Nvidia yet.

Was ist denn momentan optimal für einen NUC? Softhddrm läuft, aber der Ton ist schlecht, und bei meinem NUC geht das aktuelle softhdvaapi auch nicht, es verträgt sich nicht mit satip, der VDR läuft nach einiger Zeit Amok. Nur eine alte Installation geht noch, da stehen mittlerweile 79 Änderungen an, aber wenn ich den Update mache, ist die Installation auch verloren.

Habe ich eigentlich noch eine Alternative?

In the latest Intel drivers, was removed support for vaapi subpicture and apparently GLX too, so OSD in softhddevice does not work with latest Intel UHD graphics now.

So it would be useful to take care not to update Intel drivers when updating the system by apt-get dist-upgrade?

It happens with UHD Graphics 730. With UHD Graphics 630 all works like before. Yet.

But you can use softhdvaapi (softhddrm) with Intel.

Are there any other advantages of opengl osd apart from being able to use skindesigner or are there even drawbacks in comparison to the standard softdevicehd (which graphics API does it use instead btw?)?

The question is not entirely correct. You can disable openGL osd and use normal osd in softhddevice plugin.

A lot has changed since the last post in this thread.

Ah ok, I get it now! So is enabling OpenGL OSD recommended only in case of wanting to use skindesigner?

OpenGL osd creates a small load on the video card, if you do not have the first generation Intel or Nvidia older than gt210, you can not disable anything.

But I think your original question was about whether or not to switch from the original softhddevice to a fork?

lnj,

I would like to benefit from your expert knowledge

As Claus mentioned here, we are currently developing a new version of MLD and encountering the same issues as the thread starter.

Our intention is to provide an out-of-the-box running VDR system for end-users. For Intel systems, we are currently using your test-branch with the vaapi switch (if the card JUST supports i965_drv) or vaapi-egl (if the card supports iHD_drv).

Could you please give us some advice on how we can cover mainstream users and provide them with the best options?

If possible for intel pre iHD (i965) / intel iHD / nvidia vdpau / nvidia cuvid

Thx alot