Softhddevice + ffmpeg > 3.2 (vdpau)

lnj · 31. Dezember 2020

Very interesting, I'll look it.

You use boblight plugin?

cooljay032 · 31. Dezember 2020

Zitat von lnj

You use boblight plugin?

No

lnj · 2. Januar 2021

I can't reproduce this.

But try this patch, may be it help you.

Diff

--- 1/vdr-plugin-softhddevice/video.c   2020-12-31 20:35:15.360795708 +1000
+++ 3/vdr-plugin-softhddevice/video.c   2021-01-02 15:41:58.990449250 +1000
@@ -12990,9 +12990,8 @@ static void CuvidDisplayFrame(void)
        }
     }

-    glXWaitVideoSyncSGI (2, (Count + 1) % 2, &Count);   // wait for previous frame to swap
-
     glXMakeCurrent(XlibDisplay, VideoWindow, GlxThreadContext);
+    glXWaitVideoSyncSGI (2, (Count + 1) % 2, &Count);   // wait for previous frame to swap
     glClear(GL_COLOR_BUFFER_BIT);

     // check if surface was displayed for more than 1 frame

Alles anzeigen

cooljay032 · 2. Januar 2021

With your patch it works as usual again, thanks!

lnj · 3. Januar 2021

Added to git.

SurfaceCleanerZ · 3. Januar 2021

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

wmautner · 4. Januar 2021

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.

seahawk1986 · 4. Januar 2021

Zitat von wmautner

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

jsffm · 2. Mai 2021

After this 2 messages

Code

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

restart without further messages

lnj · 3. Mai 2021

Give full messages log, with debug enabled in Makefile.

0709 - cuda context not initialized.

You use cuvid, not vdpau?

jsffm · 3. Mai 2021

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

lnj · 3. Mai 2021

Then the log, which was before, as it is, maybe something will be clear.

jsffm · 3. Mai 2021

Code

May  2 18:44:13 vdr3-2 vdr[2718]: video/cuvid: synced after 6 frames
May  2 18:44:17 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:17 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:17 vdr3-2 vdr[2718]: [29234] playing '/disk2/video/Formel_1_Motorhome/2021-05-02.18.00.113-0.rec/00002.ts'
May  2 18:44:18 vdr3-2 vdr[2718]: video/cuvid: synced after 55 frames
May  2 18:44:18 vdr3-2 vdr[2718]: [2857] VNSI: Requesting clients to reload timers
May  2 18:44:26 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:26 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:28 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:28 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:29 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:29 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:30 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:30 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:31 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:31 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:31 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:31 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:32 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:32 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:32 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:32 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:33 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:33 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:33 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:33 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:34 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:34 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:34 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:34 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:35 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:35 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:35 vdr3-2 vdr[2718]: audio/alsa: using pass-through device 'default'
May  2 18:44:35 vdr3-2 vdr[2718]: audio/alsa: start delay 500ms
May  2 18:44:35 vdr3-2 vdr[2718]: Cuvid Driver API error = 0709
May  2 18:44:35 vdr3-2 vdr[2718]: video/cuvid: render frame error
May  2 18:44:41 vdr3-2 kernel: saa7146: unregister extension 'budget dvb'

Alles anzeigen

I worked with a crop mark, set, move

Softhddevice + ffmpeg > 3.2 (vdpau)

Jetzt mitmachen!

Teilen

Tags