Softhddevice + ffmpeg > 3.2 (vdpau)

lnj · December 31, 2020 at 12:04 AM

Very interesting, I'll look it.

You use boblight plugin?

cooljay032 · December 31, 2020 at 12:47 PM

Quote from lnj

You use boblight plugin?

No

lnj · January 2, 2021 at 7:01 AM

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

Display More

cooljay032 · January 2, 2021 at 8:36 PM

With your patch it works as usual again, thanks!

lnj · January 3, 2021 at 3:25 AM

Added to git.

SurfaceCleanerZ · January 3, 2021 at 1:53 PM

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 · January 4, 2021 at 11:15 AM

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 · January 4, 2021 at 12:00 PM

Quote from 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 · May 2, 2021 at 6:56 PM

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 · May 3, 2021 at 4:59 PM

Give full messages log, with debug enabled in Makefile.

0709 - cuda context not initialized.

You use cuvid, not vdpau?

jsffm · May 3, 2021 at 5:03 PM

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

lnj · May 3, 2021 at 5:07 PM

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

jsffm · May 3, 2021 at 5:58 PM

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'

Display More

I worked with a crop mark, set, move

Softhddevice + ffmpeg > 3.2 (vdpau)

Participate now!

Tags

Users Viewing This Thread