Thanks a lot for chiming in, Richard :-)
On 11 May 2019 at 11:28, Richard Scobie wrote:
Frantisek Rysanek wrote:
50i). Maybe the VLC can somehow cope with that (perform rate conversion on the fly) but the vaapidevice plugin cannot. Maybe I should attach a TV as a second display and set the PC's HDMI frame refresh rate to 50 Hz.
I have not yet started down the vaapi path yet, (soon), but I believe you will need to set your display for 50Hz. See post #2 in this thread:
https://www.vdr-portal.de/forum/index.php?thread/132471-xserver-f%C3%BCr-vaa...
Will check that. Oh cool, that thread is stuffed with useful information. Und ich werde Deutsch mal wieder etwas üben. Anscheinend KLS selber hat mit demselben problem gekämpft :-) Meiner Weg wurde bereits beschritten.
Another issue is: how do I control the OSD on the vaapidevice output, if I only have a PC keyboard and mouse?
Keyboard control needs to be specified at compile time - on by default, see Make.config.template in the source package.
I have never used the keyboard, but I have assumed that when started for the first time, you are prompted for which keys you want mapped to which vdr function, when using a remote. Maybe this is not the case with the keyboard? See the "Remote Control Keys" entry in the command "man 5 vdr".
Thanks for the pointer. Yes, VDR, when started with vaapidevice, does ask me to press some keys on my remote to "detect the protocol". Except that I probably don't have a compatible remote for the mygica, or maybe the mygica "input device" in xinput does not count as a "LIRC remote", or I don't have lircd running, or its config is empty, or some such. Will need to check that. I can work on that later. The startup autodetector doesn't seem to respond to keyboard inputs. And I do have the source directory for VDR on my hdd, so I'm gonna check the compile-time config as well.
Frank