Re: [vdr] Getting started with Pi TV HAT and gpio-ir

[Richard F]

Hi all,

I regret that I did not buy the Pi TV HAT earlier. The USB stick is 
simply garbage compared to it.


The Astrometa USB stick switches channels very slowly and the tuner 
very frequently produces errors in the bit stream, when using a good 
outdoor aerial that other devices have no trouble with. By design, its 
infrared receiver will lose messages when a button is being held down, 
because a 128-byte buffer of the microcontroller would overflow, and 
there is no way to use it as a ring buffer (I tried). A kernel 
maintainer came up with some experimental patches that significantly 
improved the situation, but every few of seconds some key-repeat 
events were still being lost.


Thanks for that info. Does anyone on this list maintain or know who 
maintains https://www.linuxtv.org ? As you say at lot of it is now quite 
dated.


A couple of my own observations - I have the same issue with the 
Astrometa receiver, not so good, but my Hauppage USB ones (290 & 292) 
seem to randomly die, and are harder to get these days - at least at a 
reasonable price, given the reliability.  I had to fiddle udev to make 
the Astrometa work with VDR - even latest - and as you say glitches 
onscreen every few mins, though I was suspecting an EMC/interference 
problem with my setup, it could just be poor hardware or driver bugs also.


A lot of cheap remotes, incl the Hauppage MVP ones I repurposed, have 
the problem that the rubber mat bleeds an oily substance after a few 
years even if kept perfectly clean, as you say open them up with a paint 
scraper or credit card and clean the PCB & back of the rubber mat with 
isopropyl alcohol or similar, and they're good for another couple of years.


Richard
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Getting started with Pi TV HAT and gpio-ir

[Marko Mäkelä]

Hi all,

Much of this message would probably belong to some wiki page, along with 
some photographs that I made. Before starting to write this, I checked 
https://vdr-projects.github.io and did not find any hardware projects.  
The hardware section of the VDR wiki at https://www.linuxtv.org does not 
seem to have been updated for years; it does not mention Raspberry Pi at 
all, despite it being a viable alternative for more than 10 years.


I was an active VDR user from 2004 or 2005, when I built a PC based 
setup, using a "budget" DVB-T card (Hauppauge Nova-T PCI). That system 
was never upgraded to DVB-T2; instead, we got a flat screen TV with a 
built-in tuner. Gradually, as our children got older, recordings were 
made and watched less often.


We mostly stopped using VDR about 10 years ago. Since then, I have made 
some attempts to "come back", initially, using a Raspberry Pi 2 B and an 
Astrometa USB DVB-T/T2 stick.


This month, I purchased a TV HAT case and the DVB-T/T2 uHAT for my 
Raspberry Pi 2 B. As far as I understand, the plexiglass TV HAT case 
should fit the Raspberry Pi 2, 3, and 4. The LED holes next to the 
MicroSD card slot are on the wrong side for the Pi 2, but everything 
fits perfectly.


I regret that I did not buy the Pi TV HAT earlier. The USB stick is 
simply garbage compared to it.


The Astrometa USB stick switches channels very slowly and the tuner very 
frequently produces errors in the bit stream, when using a good outdoor 
aerial that other devices have no trouble with. By design, its infrared 
receiver will lose messages when a button is being held down, because a 
128-byte buffer of the microcontroller would overflow, and there is no 
way to use it as a ring buffer (I tried). A kernel maintainer came up 
with some experimental patches that significantly improved the 
situation, but every few of seconds some key-repeat events were still 
being lost.


Out of that effort, a tiny patch from me was included in the Linux 
kernel, to have the kernel's LIRC interface set the "repeat" flag for 
all IR protocols: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b464763cc3489af406437a7650de8575a0973235


The Pi TV HAT is missing an infrared receiver out of the box. I soldered 
an IR receiver module to some thin wires, isolating the legs with heat 
shrink tube. The other ends of the thin wires I soldered to some pads 
next to the connector: 3.3V at pin 1, ground at pin 6 (or 9), and the 
signal output to GPIO 18 (pin 12). GPIO 17 at pin 11 would have worked 
as well. I made the IR receiver module stick out from a vent hole on the 
top, because my initial attempt of keeping the module inside the 
transparent lid of the case did not work that well.


The module can pick up IR signal some 8 meters away.

The software configuration was easy:

(1) Add the following line to /boot/config.txt:

dtoverlay=gpio-ir,gpio_pin=18

(2) Execute "sudo apt install ir-keytable"

(3) Edit /etc/rc_maps.cfg to load a suitable table for your remote 
control unit. To reuse the old remote control unit that I had, I wrote 
an entry

* * hauppauge.toml

(4) Reboot for the config.txt change to take effect.

For me, the remote control unit appeared in /dev/input/event0 as well as 
/dev/lirc0 and some buttons (such as the number keys) would directly 
work in the /dev/tty1 textual login prompt.


For starting up VDR, I used a command like this:

vdr -v /var/lib/vdr/video --no-kbd -Prpihddevice -P'remote -i /dev/input/event0'

Yes, the Pi TV HAT was detected automatically; I did not have to do 
anything special. I had previously used the same VDR configuration with 
an Astrometa USB stick.


This is with a copy of https://github.com/reufer/rpihddevice with some 
critical patches applied. (The issues and a pull request that I opened 
in January 2022 are still unattended.)


The experience with the Pi TV HAT is simply great. The Sony tuner in the 
Pi TV HAT produces an error-free bit stream and switches transponders 
very quickly. The kernel GPIO IR driver is rock solid. I think that the 
user experience is at least as good as with my old PC setup.


Some buttons on my remote control unit were unreliable. Using an expired 
debit card, I was able to pry open the grey Hauppauge remote control 
unit, starting next to the IR LED. I guess I should upload pictures of 
the internals somewhere, to help others open theirs.


Next, I plan to attach some external storage for recordings. A USB 3.0 
NVMe drive would allow faster backups (when detached from the Raspberry 
Pi 2) and an upgrade to a Pi 3 or 4.


On the software side, I am thinking to apply my kernel patch and to 
write a "kernel LIRC plugin" for VDR that would allow me to use 
/dev/lirc0 for the input. I would prefer to use the lower-level 
interface where each IR message corresponds to an event. I do not like 
the key-repeat timer logic of the kernel's input event driver. And I 
never liked the user-space lircd.


With best 

Re: [vdr] https://www.vdr-portal.de/

[it's me]

Unfortunately a very long maintenance period. Login is possible, but nothing 
else.
What to do without "our" VDR portal?! :o(

Markus

Von: vdr  im Auftrag von Narcis Garcia 

Gesendet: Montag, 12. September 2022 19:10
An: VDR - SPM 
Betreff: Re: [vdr] https://www.vdr-portal.de/

HTTPS certificate expired.



Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 12/9/22 a les 16:59, Manuel Reimer ha escrit:
> On 12.09.22 16:49, Jürgen Schneider wrote:
>> Hi,
>>
>> does anybody know what´s up with https://www.vdr-portal.de ?
>>
>> Jürgen
>>
>>
> It has been down in the past for maintenance and was up again shortly
> after. So probably we should just wait a little longer.
>
> Manuel
>
>
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] https://www.vdr-portal.de/

[Frank Neumann]

Well, known fact, vdr-portal.de has been in maintenance mode before certificate 
did expire.

I assume its again "unfriendly fire", too many crazy people out there, but 
haven't got any feedback till date ... unfortunately.

Cheers
fnu

-Ursprüngliche Nachricht-
Von: vdr  Im Auftrag von Narcis Garcia
Gesendet: Montag, 12. September 2022 19:11
An: VDR - SPM 
Betreff: Re: [vdr] https://www.vdr-portal.de/

HTTPS certificate expired.



Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't masked 
enough at this mail public archive. Public archive administrator should fix 
this against automated addresses collectors.
El 12/9/22 a les 16:59, Manuel Reimer ha escrit:
> On 12.09.22 16:49, Jürgen Schneider wrote:
>> Hi,
>>
>> does anybody know what´s up with 
>> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.vdr-portal.de%2Fdata=05%7C01%7C%7Cedcf6b6c55144947ac9a08da94e1d2a4%7C84df9e7fe9f640afb435%7C1%7C0%7C637985994870346879%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=6dBMzX9nj24O595I74xErRAT8EC9mav7k6HKBGL7y8Q%3Dreserved=0
>>  ?
>>
>> Jürgen
>>
>>
> It has been down in the past for maintenance and was up again shortly 
> after. So probably we should just wait a little longer.
> 
> Manuel
> 
> 
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> linuxtv.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fvdrdata=05%7C01%7C%7
> Cedcf6b6c55144947ac9a08da94e1d2a4%7C84df9e7fe9f640afb435%7
> C1%7C0%7C637985994870346879%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD
> AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Cs
> data=sc8kvdEXcfmoggGYgCEXM1ImmCfEBVwGBcqBop3PAlY%3Dreserved=0

___
vdr mailing list
vdr@linuxtv.org
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linuxtv.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fvdrdata=05%7C01%7C%7Cedcf6b6c55144947ac9a08da94e1d2a4%7C84df9e7fe9f640afb435%7C1%7C0%7C637985994870346879%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=sc8kvdEXcfmoggGYgCEXM1ImmCfEBVwGBcqBop3PAlY%3Dreserved=0

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] https://www.vdr-portal.de/

[Narcis Garcia]

HTTPS certificate expired.



Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't 
masked enough at this mail public archive. Public archive administrator 
should fix this against automated addresses collectors.

El 12/9/22 a les 16:59, Manuel Reimer ha escrit:

On 12.09.22 16:49, Jürgen Schneider wrote:

Hi,

does anybody know what´s up with https://www.vdr-portal.de ?

Jürgen



It has been down in the past for maintenance and was up again shortly
after. So probably we should just wait a little longer.

Manuel


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] https://www.vdr-portal.de/

[Manuel Reimer]

On 12.09.22 16:49, Jürgen Schneider wrote:

Hi,

does anybody know what´s up with https://www.vdr-portal.de ?

Jürgen



It has been down in the past for maintenance and was up again shortly
after. So probably we should just wait a little longer.

Manuel


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] https://www.vdr-portal.de/

[Jürgen Schneider]

Hi,

does anybody know what´s up with https://www.vdr-portal.de ?

Jürgen


--
Diese E-Mail wurde von Avast-Antivirussoftware auf Viren geprüft.
www.avast.com

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Richard F]

Brilliant - thanks. I have some updates to do, but summer dictates some 
other priorities right now   I've accepted the invite, and will make 
edits and updates in a while


Thanks again

Richard

On 31/07/2022 10:22, Manuel Reimer wrote:

Just a small follow up. I've also fixed the links in your Readme.txt and
as your syntax actually is valid markdown, I renamed it to "README.md"
to show how the project landing page can look like if the markdown is
actually parsed as such.

Feel free to drop my commits if you don't like it.

Manuel

On 31.07.22 11:04, Manuel Reimer wrote:

Hi Richard,

Sorry for the late response. I finally found the time to port over your
wiki pages.

I've sent you an invite that you just have to accept. This should give
you full permissions on the repository.

Unfortunately I was late for downloading the files, shared by Tobi. So I
tried to find a simple way to port the wiki pages without this.

If someone else wants to port wiki pages:
Forget about pandoc. It tries to migrate everything but the kitchen sink
including class names used by redmine internally. It sucks to edit all
that out.

The surprisingly easy way to port wiki page content:

- Copy the whole wiki page content on the readonly mirror hosted by Tobi
- Open https://stackedit.io/
- Click "START WRITING" there
- Now delete the whole example markdown on the left side
- Paste the copied wiki content
- StackEdit converts the pasted content to surprisingly nice markdown
- Now do minor fixes like adding code blocks, fix links, ...
- Copy the resulting markdown over to whatever hosting platform you like

Manuel


On 10.07.22 22:20, Richard F wrote:

Yes, please make me owner of the repo + import the wiki pages, as I
actually have some updates to do.

My login on github is "keynet". Let me know if you need any more info -
Thanks

On 10/07/2022 12:48, Manuel Reimer wrote:

On 07.07.22 17:02, Richard F wrote:
RIP as you say, but many thanks for keeping it going r/o. I'm 
actually
still maintaining vdr-convert for my own use + using it quite a 
lot. I

plan to recover the wiki pages which represented quite a lot of work.
Has code been copied to github ?  Who's owning / maintaining it 
there ?


If you like, I could try to import the Wiki pages, Tobi has 
exported, to

https://github.com/vdr-projects/vdr-convert

I think all repos should be mirrored into context of
https://github.com/vdr-projects where they now more or less stay
unchanged as long as no one provides pull requests, patches, or "wants
his project back".

If you like to maintain your project here:
https://github.com/vdr-projects/vdr-convert then I could make you the
owner of this repo. But it would also be totally OK if you prefer to
host somewhere else. In this case I would replace the repository
description with information about where the project is maintained and
mark the whole repo as "archived" so no none thinks that this is the
official home of the project.

Manuel




___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr



___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr



___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Manuel Reimer]

Just a small follow up. I've also fixed the links in your Readme.txt and
as your syntax actually is valid markdown, I renamed it to "README.md"
to show how the project landing page can look like if the markdown is
actually parsed as such.

Feel free to drop my commits if you don't like it.

Manuel

On 31.07.22 11:04, Manuel Reimer wrote:

Hi Richard,

Sorry for the late response. I finally found the time to port over your
wiki pages.

I've sent you an invite that you just have to accept. This should give
you full permissions on the repository.

Unfortunately I was late for downloading the files, shared by Tobi. So I
tried to find a simple way to port the wiki pages without this.

If someone else wants to port wiki pages:
Forget about pandoc. It tries to migrate everything but the kitchen sink
including class names used by redmine internally. It sucks to edit all
that out.

The surprisingly easy way to port wiki page content:

- Copy the whole wiki page content on the readonly mirror hosted by Tobi
- Open https://stackedit.io/
- Click "START WRITING" there
- Now delete the whole example markdown on the left side
- Paste the copied wiki content
- StackEdit converts the pasted content to surprisingly nice markdown
- Now do minor fixes like adding code blocks, fix links, ...
- Copy the resulting markdown over to whatever hosting platform you like

Manuel


On 10.07.22 22:20, Richard F wrote:

Yes, please make me owner of the repo + import the wiki pages, as I
actually have some updates to do.

My login on github is "keynet". Let me know if you need any more info -
Thanks

On 10/07/2022 12:48, Manuel Reimer wrote:

On 07.07.22 17:02, Richard F wrote:

RIP as you say, but many thanks for keeping it going r/o. I'm actually
still maintaining vdr-convert for my own use + using it quite a lot. I
plan to recover the wiki pages which represented quite a lot of work.
Has code been copied to github ?  Who's owning / maintaining it there ?


If you like, I could try to import the Wiki pages, Tobi has exported, to
https://github.com/vdr-projects/vdr-convert

I think all repos should be mirrored into context of
https://github.com/vdr-projects where they now more or less stay
unchanged as long as no one provides pull requests, patches, or "wants
his project back".

If you like to maintain your project here:
https://github.com/vdr-projects/vdr-convert then I could make you the
owner of this repo. But it would also be totally OK if you prefer to
host somewhere else. In this case I would replace the repository
description with information about where the project is maintained and
mark the whole repo as "archived" so no none thinks that this is the
official home of the project.

Manuel




___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr



___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr



___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Manuel Reimer]

Hi Richard,

Sorry for the late response. I finally found the time to port over your
wiki pages.

I've sent you an invite that you just have to accept. This should give
you full permissions on the repository.

Unfortunately I was late for downloading the files, shared by Tobi. So I
tried to find a simple way to port the wiki pages without this.

If someone else wants to port wiki pages:
Forget about pandoc. It tries to migrate everything but the kitchen sink
including class names used by redmine internally. It sucks to edit all
that out.

The surprisingly easy way to port wiki page content:

- Copy the whole wiki page content on the readonly mirror hosted by Tobi
- Open https://stackedit.io/
- Click "START WRITING" there
- Now delete the whole example markdown on the left side
- Paste the copied wiki content
- StackEdit converts the pasted content to surprisingly nice markdown
- Now do minor fixes like adding code blocks, fix links, ...
- Copy the resulting markdown over to whatever hosting platform you like

Manuel


On 10.07.22 22:20, Richard F wrote:

Yes, please make me owner of the repo + import the wiki pages, as I
actually have some updates to do.

My login on github is "keynet". Let me know if you need any more info -
Thanks

On 10/07/2022 12:48, Manuel Reimer wrote:

On 07.07.22 17:02, Richard F wrote:

RIP as you say, but many thanks for keeping it going r/o. I'm actually
still maintaining vdr-convert for my own use + using it quite a lot. I
plan to recover the wiki pages which represented quite a lot of work.
Has code been copied to github ?  Who's owning / maintaining it there ?


If you like, I could try to import the Wiki pages, Tobi has exported, to
https://github.com/vdr-projects/vdr-convert

I think all repos should be mirrored into context of
https://github.com/vdr-projects where they now more or less stay
unchanged as long as no one provides pull requests, patches, or "wants
his project back".

If you like to maintain your project here:
https://github.com/vdr-projects/vdr-convert then I could make you the
owner of this repo. But it would also be totally OK if you prefer to
host somewhere else. In this case I would replace the repository
description with information about where the project is maintained and
mark the whole repo as "archived" so no none thinks that this is the
official home of the project.

Manuel




___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr



___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] How to use /dev/lirc0 in VDR?

[Marko Mäkelä]

Wed, Jul 20, 2022 at 12:34:19PM +0300, Marko Mäkelä wrote:

Mon, Jul 18, 2022 at 09:36:55AM +0300, Marko Mäkelä wrote:
TL;DR: How could I connect VDR to the kernel-provided /dev/lirc0 
device?  Is there a dummy lircd implementation that would simply 
open /dev/lirc0 in LIRC_MODE_SCANCODE and relay its contents over a 
socket?


I wrote a simple converter (attached) that is compatible with vdr 
--lirc=/dev/shm/lirc. Alas, as far as I can tell, the socket interface 
does not currently allow any "repeat" flag to be passed explicitly.  
Instead, lirc.c will detect long keypresses by itself based on some 
time stamps or timeouts, and then pass the parameter to 
cRemote::Put().


I took a further step along this path and wrote an experimental patch 
that makes --lirc=/dev/lirc0 work (while completely breaking 
compatibility with lircd). The attached patch is only a proof of 
concept; a final version of this would have to be tied to a dedicated 
command line option.


I did not clean up the timer logic yet. The lirc_scancode events already 
contain monotonic timestamps; those could be used in order to reduce the 
number of system calls.


This patch assumes that the /dev/lirc0 interface is setting the 
LIRC_SCANCODE_FLAG_REPEAT for subsequent messages sent for a long key 
press, as in 
https://patchwork.linuxtv.org/project/linux-media/list/?series=8338
(and before that, only for some RCUs that send special "repeat" 
messages). The flag could be simulated in userspace by keeping track of 
the timestamps.


The Linux kernel documentation gave me the impression that the 
/dev/input/event interface is the modern way to handle any input.


I wonder if a /dev/input/event interface could be implemented natively 
in the VDR core. It would remove the need for both lircd and 
vdr-plugin-remote in many typical installations.


It seems that in any case, I'd better write a converter from 
/dev/lirc0 to /dev/uinput, to have the key events generated in my way, 
slightly differently from the kernel's built-in /dev/input/event 
driver.


I experimented with a program that would convert /dev/lirc0 to 
/dev/uinput, but it quickly got too complex for my taste, starting from 
the fact that all potential keycodes have to be declared upfront. While 
searching for information, I learned that lircd could already generate 
input events: https://www.lirc.org/html/lircd-uinput.html


The /dev/input/event driver in the kernel rc-core has (in my opinion) a 
design problem that the key-repeat events are triggered by an 
independent timer and not directly by the reception of IR messages from 
the RCU. When multiple clock sources are involved, timers will easily 
get out of sync, and in this case cause input lag: For example, a 
perceivable time (such as 0.1s) after a button was already released, the 
independent timer might fire one more key-repeat event.


VDR's existing LIRC interface avoids such input lag by always triggering 
Put() calls by the reception of IR messages. It merely "filters out" 
some IR messages by enforcing RcRepeatDelay and RcRepeatDelta.


Best regards,

Marko
diff --git a/lirc.c b/lirc.c
index 9cc287a6..d7797009 100644
--- a/lirc.c
+++ b/lirc.c
@@ -10,19 +10,13 @@
  */
 
 #include "lirc.h"
-#include 
-#include 
-
-#define RECONNECTDELAY 3000 // ms
+#include 
 
 cLircRemote::cLircRemote(const char *DeviceName)
 :cRemote("LIRC")
 ,cThread("LIRC remote control")
 {
-  addr.sun_family = AF_UNIX;
-  strn0cpy(addr.sun_path, DeviceName, sizeof(addr.sun_path));
-  if (!Connect())
- f = -1;
+  Connect(DeviceName);
   Start();
 }
 
@@ -35,18 +29,17 @@ cLircRemote::~cLircRemote()
  close(fh);
 }
 
-bool cLircRemote::Connect(void)
+inline void cLircRemote::Connect(const char *DeviceName)
 {
-  if ((f = socket(AF_UNIX, SOCK_STREAM, 0)) >= 0) {
- if (connect(f, (struct sockaddr *), sizeof(addr)) >= 0)
-return true;
- LOG_ERROR_STR(addr.sun_path);
+  unsigned mode = LIRC_MODE_SCANCODE;
+  f = open(DeviceName, O_RDONLY, 0);
+  if (f < 0)
+ LOG_ERROR_STR(DeviceName);
+  else if (ioctl(f, LIRC_SET_REC_MODE, )) {
+ LOG_ERROR_STR(DeviceName);
  close(f);
  f = -1;
  }
-  else
- LOG_ERROR_STR(addr.sun_path);
-  return false;
 }
 
 bool cLircRemote::Ready(void)
@@ -56,50 +49,30 @@ bool cLircRemote::Ready(void)
 
 void cLircRemote::Action(void)
 {
+  if (f < 0)
+ return;
   cTimeMs FirstTime;
   cTimeMs LastTime;
   cTimeMs ThisTime;
-  char buf[LIRC_BUFFER_SIZE];
-  char LastKeyName[LIRC_KEY_BUF] = "";
+  uint32_t LastKeyCode = 0;
   bool pressed = false;
   bool repeat = false;
   int timeout = -1;
 
   while (Running()) {
-
-bool ready = f >= 0 && cFile::FileReady(f, timeout);
-int ret = ready ? safe_read(f, buf, sizeof(buf)) : -1;
-
-if (f < 0 || ready && ret <= 0) {
-   esyslog("ERROR: lircd connection broken, trying to reconnect every %.1f seconds", float(RECONNECTDELAY) / 1000);
-   if (f >= 0)
-  close(f);
-   f = 

Re: [vdr] How to use /dev/lirc0 in VDR?

[Marko Mäkelä]

Mon, Jul 18, 2022 at 09:36:55AM +0300, Marko Mäkelä wrote:
TL;DR: How could I connect VDR to the kernel-provided /dev/lirc0 
device?  Is there a dummy lircd implementation that would simply open 
/dev/lirc0 in LIRC_MODE_SCANCODE and relay its contents over a socket?


I wrote a simple converter (attached) that is compatible with vdr 
--lirc=/dev/shm/lirc. Alas, as far as I can tell, the socket interface 
does not currently allow any "repeat" flag to be passed explicitly.  
Instead, lirc.c will detect long keypresses by itself based on some time 
stamps or timeouts, and then pass the parameter to cRemote::Put().


The Linux kernel documentation gave me the impression that the 
/dev/input/event interface is the modern way to handle any input.


I wonder if a /dev/input/event interface could be implemented natively 
in the VDR core. It would remove the need for both lircd and 
vdr-plugin-remote in many typical installations.


It seems that in any case, I'd better write a converter from /dev/lirc0 
to /dev/uinput, to have the key events generated in my way, slightly 
differently from the kernel's built-in /dev/input/event driver.


Marko
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

static struct lirc_scancode sc[64];

int main(void)
{
  unsigned mode = LIRC_MODE_SCANCODE;
  int fd, s;
  struct sockaddr_un name;

  memset(, 0, sizeof name);
  name.sun_family = AF_UNIX;
  strncpy(name.sun_path, "/dev/shm/lirc", sizeof name.sun_path - 1);

  s = socket(AF_UNIX, SOCK_STREAM, 0);

  if (s == -1) {
perror("socket");
return 1;
  }

  if (bind(s, (const struct sockaddr*) , sizeof name) == -1) {
perror("bind");
return 1;
  }

  fd = open("/dev/lirc0", O_RDONLY | O_NONBLOCK);

  if (fd == -1) {
perror("open");
return 1;
  }
  if (ioctl(fd, LIRC_SET_REC_MODE, )) {
perror("ioctl");
return 1;
  }

  if (listen(s, 1) == -1) {
perror("listen");
return 2;
  }

  for (;;) {
int sock = accept(s, NULL, NULL);
if (sock == -1) {
  perror("accept");
  return 2;
}
for (;;) {
  ssize_t rd;
  struct pollfd polls[2] = {
{ .fd = fd, .events = POLLIN },
{ .fd = sock, .events = POLLERR },
  };
  if (poll(polls, 2, -1) < 0) {
if (errno == EINTR)
  continue;
perror("poll");
return 2;
  }
  rd = read(fd, sc, sizeof sc);
  if (rd > 0) {
ssize_t i, n = rd / sizeof *sc;
char buf[14];
for (i = 0; i < n; i++) {
  int l = sprintf(buf, "0 0 %08x\n", sc[i].keycode);
  if (-1 == write(sock, buf, 13)) {
perror("write");
goto end;
  }
}
  } else if (errno == EAGAIN) {
continue;
  } else {
perror("read");
return 2;
  }
}
end:
close(sock);
  }
}
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] How to use /dev/lirc0 in VDR?

[Marko Mäkelä]

Hi all,

TL;DR: How could I connect VDR to the kernel-provided /dev/lirc0 device?  
Is there a dummy lircd implementation that would simply open /dev/lirc0 
in LIRC_MODE_SCANCODE and relay its contents over a socket?


As far as I understand, LIRC was first implemented as a user-space 
daemon that would decode a bitstream (via various bit-banging 
interfaces) into scancodes that would then be relayed over a socket to 
the final application.


At some point (before I started to use VDR in 2005 or 2006), support for 
remote control units was expanded in the Linux kernel, and also a 
translation into input events was implemented.  In VDR, the input event 
interface can be used via the "remote" plugin (vdr -Premote). I think 
that this is what I always used with VDR, first using the cx88 driver 
(Hauppauge Nova-T PCI 90002) and now trying to use a USB stick 
(rtl82xxu, Astrometa DVB-T2) on a Raspberry Pi.


The input event interface is mapping the stream of IR messages to 
"key-down", "key-up" and "key-repeat" events, which adds some 
inaccuracy. For the rtl82xxu, the repeat logic is broken: key-repeat or 
key-down events for long key presses are only being sent intermittently.  
The fix in 
https://patchwork.linuxtv.org/project/linux-media/list/?series=7322 
improves it a lot. The USB interface for delivering IR events in a 
128-byte buffer is prone to race conditions, and that cannot be fixed 
without changing the device firmware.


There is also a kernel-based interface (such as /dev/lirc0) that can 
provide scan codes to end applications. Both the input event interface 
and this one would be polled by "ir-keytable -t".


I would like to use the /dev/lirc0 interface with VDR, so that VDR has a 
chance to react to each and every IR message that is sent by the remote 
control unit. I think that this would minimize the disturbance caused by 
the broken USB protocol of the rtl82xxu. It is OK if one LIRC scancode 
of a long keypress (say, browsing a list of recordings) would be lost; 
another one would be sent in 113ms by the RC5 protocol. With the input 
event driver, a lost IR message would result in a bogus key-up event, a 
bogus key-down event, and a long delay before key-repeat events are 
generated again.


My initial attempt at using /dev/lirc0 did not work:

vdr -v /var/lib/vdr/video --no-kbd --lirc=/dev/lirc0 -Prpihddevice

That is, pressing any buttons on the remote control unit did not have 
any effect, and VDR did not start in the "learning mode" either, even 
after I renamed the remote.conf that it is opening at startup. It 
appeared that a read() on "/dev/lirc0" would block indefinitely, but I 
did not check that.


I noticed that VDR's lirc.c is explicitly opening a Unix domain socket 
to the LIRC device, while "ir-keytable -t" would invoke open(2) followed 
by ioctl(lircfd, LIRC_SET_REC_MODE, ):

https://git.linuxtv.org/v4l-utils.git/tree/utils/keytable/keytable.c

My goal would be to use the Hauppauge remote control with the Astrometa 
DVB-T2 stick and for it to be as responsive as it was back in 2006 with 
my patched cx88 driver. My implementation back then directly mapped IR 
messages to input events:


(1) produced a key-down event for the first IR message
(2) discard the first repeated IR message (to have an initial delay)
(3) produced key-repeat events for subsequent IR messages (every 113ms)
(4) if any key-up events were produced, that would be after a timeout 
that would be reset in (1),(2),(3).


I think that it should be possible to implement this behaviour in a 
dummy lircd that translates /dev/lirc0 into a socket. Before I implement 
that from the scratch, I would like to know if something similar already 
exists.


Related to this, I submitted a fix to the kernel to set the "repeat" 
flag in the LIRC scan codes when appropriate: 
https://patchwork.linuxtv.org/project/linux-media/list/?series=8338
Without this fix, it should still be possible to detect repeat key 
events (long key presses) by comparing successive scancodes. For 
protocols that do not include a toggle flag (like RC5 does), it might be 
possible to compare timestamps to distinguish long button presses from 
multiple short presses.


Best regards,

Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] EPG table 0

[Richard F]

On 16.07.22 14:07, Richard F wrote:
>/I've just updated to VDR V2.61 after a long time on V2.2, using 
the same config and the epgtableid0 (2.4.0) plug-in. />//>/The issue 
I'm seeing is that when VDR is restarted, it doesn't seem to be 
reading/respecting the epg.data file. />/... /

Is this the only EPG handler you have installed, or are there others?
If so, make sure this one is installed FIRST.

Klaus
Actually after more testing it seems the table 0 EPG entries are 
always being overwritten after EPG scans, not just at startup.
The only EPG handler I have is XMLTV using SVDRP: once a day a script 
clears the existing EPG then inserts new entries in table 0
The correct table 0 entries can be seen in VDR for a while, then get 
overwritten after automatic scans.
I do need both types, as some channels / programmes don't have 
current data in XMLTV, only DVB.


My command line is:
/usr/bin/vdr -c /etc/vdr -E /mnt/lvm0/TV/epg.data -l 2 --no-kbd -P 
streamdev-server -P epgsearch -v 1 -l /var/log/epgsearch.log -m 
/usr/local/bin/sendEmail.pl -P epgtableid0 -P vnsiserver -P 
vdrmanager -P dummydevice -r /usr/local/bin/vdr-auto -u vdr --vfat -v 
/mnt/lvm0/TV


There are quotes missing:

/usr/bin/vdr -c /etc/vdr -E /mnt/lvm0/TV/epg.data -l 2 --no-kbd -P 
streamdev-server -P "epgsearch -v 1 -l /var/log/epgsearch.log -m 
/usr/local/bin/sendEmail.pl" -P epgtableid0 -P vnsiserver -P 
vdrmanager -P dummydevice -r /usr/local/bin/vdr-auto -u vdr --vfat -v 
/mnt/lvm0/TV


Klaus

I should have explained - earlier I quoted the command line reported by 
the kernel.  It's actually created by runvdr.extreme.


So the plugins are recognised, the same way they were in 2.20 - here's 
an excerpt of the startup


Jul 17 14:39:00 ha-server vdr[8699]: [8699] frontend 0/0 provides DVB-T with 
QPSK,QAM16,QAM64 ("Conexant CX22702 DVB-T")
Jul 17 14:39:00 ha-server vdr[8699]: [8699] frontend 1/0 provides DVB-T,DVB-T2,DVB-C with 
QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("Silicon Labs Si2168")
Jul 17 14:39:00 ha-server vdr[8699]: [8699] found 2 DVB devices
Jul 17 14:39:00 ha-server vdr[8699]: [8699] initializing plugin: 
streamdev-server (0.6.3): VDR Streaming Server
Jul 17 14:39:00 ha-server vdr[8699]: [8699] initializing plugin: epgsearch 
(2.4.1): search the EPG for repeats and more
Jul 17 14:39:00 ha-server vdr[8699]: [8699] initializing plugin: epgtableid0 
(2.4.0): EPG handler for events with table id 0x00
Jul 17 14:39:00 ha-server vdr[8699]: [8699] initializing plugin: vnsiserver 
(1.8.0): VDR-Network-Streaming-Interface (VNSI) Server
Jul 17 14:39:00 ha-server vdr[8699]: [8699] initializing plugin: vdrmanager 
(0.15): VDR-Manager plugin
Jul 17 14:39:00 ha-server vdr[8699]: [8699] initializing plugin: dummydevice 
(2.0.0): Output device that does nothing

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] EPG table 0

[Klaus Schmidinger]

On 17.07.22 13:23, Richard F wrote:

On 16.07.22 14:07, Richard F wrote:
>/I've just updated to VDR V2.61 after a long time on V2.2, using the same config and 
the epgtableid0 (2.4.0) plug-in. />//>/The issue I'm seeing is that when VDR is 
restarted, it doesn't seem to be reading/respecting the epg.data file. />/... /
Is this the only EPG handler you have installed, or are there others?
If so, make sure this one is installed FIRST.

Klaus

Actually after more testing it seems the table 0 EPG entries are always being 
overwritten after EPG scans, not just at startup.
The only EPG handler I have is XMLTV using SVDRP: once a day a script clears 
the existing EPG then inserts new entries in table 0
The correct table 0 entries can be seen in VDR for a while, then get 
overwritten after automatic scans.
I do need both types, as some channels / programmes don't have current data in 
XMLTV, only DVB.

My command line is:
/usr/bin/vdr -c /etc/vdr -E /mnt/lvm0/TV/epg.data -l 2 --no-kbd -P 
streamdev-server -P epgsearch -v 1 -l /var/log/epgsearch.log -m 
/usr/local/bin/sendEmail.pl -P epgtableid0 -P vnsiserver -P vdrmanager -P 
dummydevice -r /usr/local/bin/vdr-auto -u vdr --vfat -v /mnt/lvm0/TV


There are quotes missing:

/usr/bin/vdr -c /etc/vdr -E /mnt/lvm0/TV/epg.data -l 2 --no-kbd -P streamdev-server -P 
"epgsearch -v 1 -l /var/log/epgsearch.log -m /usr/local/bin/sendEmail.pl" -P 
epgtableid0 -P vnsiserver -P vdrmanager -P dummydevice -r /usr/local/bin/vdr-auto -u vdr 
--vfat -v /mnt/lvm0/TV

Klaus

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] EPG table 0

[Richard F]

On 16.07.22 14:07, Richard F wrote:
>/I've just updated to VDR V2.61 after a long time on V2.2, using the 
same config and the epgtableid0 (2.4.0) plug-in. />//>/The issue I'm seeing is that when VDR is restarted, it doesn't seem 
to be reading/respecting the epg.data file. />/... /

Is this the only EPG handler you have installed, or are there others?
If so, make sure this one is installed FIRST.

Klaus

Actually after more testing it seems the table 0 EPG entries are always being 
overwritten after EPG scans, not just at startup.
The only EPG handler I have is XMLTV using SVDRP: once a day a script clears 
the existing EPG then inserts new entries in table 0
The correct table 0 entries can be seen in VDR for a while, then get 
overwritten after automatic scans.
I do need both types, as some channels / programmes don't have current data in 
XMLTV, only DVB.

My command line is:
/usr/bin/vdr -c /etc/vdr -E /mnt/lvm0/TV/epg.data -l 2 --no-kbd -P 
streamdev-server -P epgsearch -v 1 -l /var/log/epgsearch.log -m 
/usr/local/bin/sendEmail.pl -P epgtableid0 -P vnsiserver -P vdrmanager -P 
dummydevice -r /usr/local/bin/vdr-auto -u vdr --vfat -v /mnt/lvm0/TV
(same as V2.20)

Thx/Richard

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] EPG table 0

[Klaus Schmidinger]

On 16.07.22 14:07, Richard F wrote:

I've just updated to VDR V2.61 after a long time on V2.2, using the same config 
and the epgtableid0 (2.4.0) plug-in.

The issue I'm seeing is that when VDR is restarted, it doesn't seem to be 
reading/respecting the epg.data file.
...


Is this the only EPG handler you have installed, or are there others?
If so, make sure this one is installed FIRST.

Klaus


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] EPG table 0

[Richard F]

I've just updated to VDR V2.61 after a long time on V2.2, using the same 
config and the epgtableid0 (2.4.0) plug-in.


The issue I'm seeing is that when VDR is restarted, it doesn't seem to 
be reading/respecting the epg.data file.


It's starting an EPG scan and seems to be overwriting table 0 entries 
from the OTA EPG. So for example this (via xmltv import)


E 42885 1657987200 3600 0 FF
T The Great British Bake Off
S Biscuits and Traybakes
D The remaining eight bakers offer Mary and Paul their twists on 
everything from bakewells to banoffees and brownies, as they face the 
biscuit and traybake challenges.|Director: Scott Tankard|Producers: 
Samantha Beddoes, Anna Beattie|Presenters: Mel Giedroyc, Sue 
Perkins|Category: Reality, Cooking|Episode: 3.4.|Episode: 
EP013163930033|Stereo: stereo|Subtitles: teletext|Repeat: No

G A5

is becoming something like this from the OTA EPG  (not same ID I know, 
just an example)


E 18475 1657987200 3600 50 13
T The Great British Bake-Off
D Almost halfway through, the remaining eight bakers are faced with 
biscuits- and the Signature Challenge requires them to produce their 
favourite traybake. S4/Ep5

G A0
X 2 03 eng
X 1 03 und
X 3 10 eng

Is there something else I need to import into table 0, or some other issue ?

Thanks

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Richard F]

Yes, please make me owner of the repo + import the wiki pages, as I 
actually have some updates to do.


My login on github is "keynet". Let me know if you need any more info - 
Thanks


On 10/07/2022 12:48, Manuel Reimer wrote:

On 07.07.22 17:02, Richard F wrote:

RIP as you say, but many thanks for keeping it going r/o. I'm actually
still maintaining vdr-convert for my own use + using it quite a lot. I
plan to recover the wiki pages which represented quite a lot of work.
Has code been copied to github ?  Who's owning / maintaining it there ?


If you like, I could try to import the Wiki pages, Tobi has exported, to
https://github.com/vdr-projects/vdr-convert

I think all repos should be mirrored into context of
https://github.com/vdr-projects where they now more or less stay
unchanged as long as no one provides pull requests, patches, or "wants
his project back".

If you like to maintain your project here:
https://github.com/vdr-projects/vdr-convert then I could make you the
owner of this repo. But it would also be totally OK if you prefer to
host somewhere else. In this case I would replace the repository
description with information about where the project is maintained and
mark the whole repo as "archived" so no none thinks that this is the
official home of the project.

Manuel




___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Manuel Reimer]

On 07.07.22 17:02, Richard F wrote:

RIP as you say, but many thanks for keeping it going r/o. I'm actually
still maintaining vdr-convert for my own use + using it quite a lot. I
plan to recover the wiki pages which represented quite a lot of work.
Has code been copied to github ?  Who's owning / maintaining it there ?


If you like, I could try to import the Wiki pages, Tobi has exported, to
https://github.com/vdr-projects/vdr-convert

I think all repos should be mirrored into context of
https://github.com/vdr-projects where they now more or less stay
unchanged as long as no one provides pull requests, patches, or "wants
his project back".

If you like to maintain your project here:
https://github.com/vdr-projects/vdr-convert then I could make you the
owner of this repo. But it would also be totally OK if you prefer to
host somewhere else. In this case I would replace the repository
description with information about where the project is maintained and
mark the whole repo as "archived" so no none thinks that this is the
official home of the project.

Manuel

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Tobi]

If this helps: Heres the vdr-convert wiki exported via the redmine to
gitlab migrator, including the full edit history as a git repo:

https://psitransfer.home.e-tobi.net/35312b371c42

Tobias

On 07.07.22 17:02, Richard F wrote:
> RIP as you say, but many thanks for keeping it going r/o. I'm actually
> still maintaining vdr-convert for my own use + using it quite a lot. I
> plan to recover the wiki pages which represented quite a lot of work.  Has
> code been copied to github ?  Who's owning / maintaining it there ?
> 
> Thanks
> 
> On 7/07/2022 0:59, Tobi wrote:
>> Hello!
>>
>> The projects.vdr-developer.org server has been shut down tonight. RIP!
>>
>> I will provide a readonly-mirror of the Redmine projects, tickets and
>> downloads as well as all the git repositories on:
>>
>> https://vdr-projects.e-tobi.net
>> https://vdr-projects.e-tobi.net/git
>>
>> This is still work in progress, but I will have everything up and running
>> by the end of the week.
>>
>> BR,
>> Tobias
>>
>>
>>
> 
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Martin Dummer]

Am 07.07.22 um 17:02 schrieb Richard F:

Has code been copied to github ?  Who's owning / maintaining it there ?


Please use this

https://vdr-projects.github.io/

as a first info page. Although this list has not been updated,
vdr-convert has been mirrored to https://github.com/vdr-projects/vdr-convert

If you want to add more code etc.. place a pull request, or "want your
repo back", tell us on

https://www.vdr-portal.de/forum/index.php?thread/135173-migration-von-projects-vdr-developer-org-auf-alternative-plattformen/

what your plans are.


Bye

Martin


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Richard F]

RIP as you say, but many thanks for keeping it going r/o. I'm actually 
still maintaining vdr-convert for my own use + using it quite a lot. I 
plan to recover the wiki pages which represented quite a lot of work.  
Has code been copied to github ?  Who's owning / maintaining it there ?


Thanks

On 7/07/2022 0:59, Tobi wrote:

Hello!

The projects.vdr-developer.org server has been shut down tonight. RIP!

I will provide a readonly-mirror of the Redmine projects, tickets and
downloads as well as all the git repositories on:

https://vdr-projects.e-tobi.net
https://vdr-projects.e-tobi.net/git

This is still work in progress, but I will have everything up and running
by the end of the week.

BR,
Tobias





___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Tobi]

Hello!

The projects.vdr-developer.org server has been shut down tonight. RIP!

I will provide a readonly-mirror of the Redmine projects, tickets and
downloads as well as all the git repositories on:

https://vdr-projects.e-tobi.net
https://vdr-projects.e-tobi.net/git

This is still work in progress, but I will have everything up and running
by the end of the week.

BR,
Tobias


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Recording an event on BBC4 HD this Sunday

[Reinhard Nißl]

Hi,

is anyone willing to record this event:
https://www.bbc.co.uk/programmes/m0018s20

Bye.
-- 
Reinhard Nißl___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Manuel Reimer]

On 24.05.22 21:33, Tobi wrote:

Over the last years, the projects.vdr-developer.org site was hosted on a
server sponsored by Xeatre.tv. This server will now go offline on June, 7'th.


At least for now it still seems to run...


I haven't made a final decision on how to proceed, but I'm leaning towards
taking the site offline. In this case I will archive the git repositories
on gitlab or github and possibly keep a read-only instance of Redmine on
my private vServer for a while.


I have not checked in detail but I think most of Redmine is already
archived by archive.org.

If you have a definitive date where the server will shut down, then I
could make sure that all repos are archived over to
https://github.com/vdr-projects where many projects are already mirrored
to (many probably outdated as at some point the automated mirror service
was disabled).

Manuel

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Manuel Reimer]

On 25.05.22 20:11, Richard F wrote:

I find it regularly useful, and refer to the pages from some of the
plugins I use. So sad to see these things that look thousands of hours
to create and debug now falling by the wayside.  And once you get used
to it, the Redmine markdown is actually quite a good workmanlike
solution for documenting stuff, a lot better than GitHub typical pages
anyway.  Pity to lose that. A big vote for keeping it from me !


Out of curiosity I had a look at how Redmine syntax looks like and for
me this looked a lot like "not Markdown". I did some search and the
syntax seems to be actually called "Textile":
https://www.redmine.org/boards/2/topics/41244

And there even exists a way to convert this to actual Markdown
automatically:
https://github.blog/2016-03-01-upgrading-your-textile-posts-to-markdown/

I did a try with the pandoc "try it out" page and this seems to work
just fine: https://pandoc.org/try/

GitHub Wikis (and GitHub pages, too) use actual Markdown and there is a
nice online editor to have direct feedback on how the result will look
like (you can still write plain Markdown text but get a rendering
immediately):

https://stackedit.io/app#


Manuel

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Richard F]

I find it regularly useful, and refer to the pages from some of the 
plugins I use. So sad to see these things that look thousands of hours 
to create and debug now falling by the wayside.  And once you get used 
to it, the Redmine markdown is actually quite a good workmanlike 
solution for documenting stuff, a lot better than GitHub typical pages 
anyway.  Pity to lose that. A big vote for keeping it from me !


I was contemplating a new release of my transcoder 
(https://projects.vdr-developer.org/projects/vdr-convert/wiki), but 
perhaps that will need to wait. Quite a few additional features ready.


cheers

Richard


On 24/05/2022 20:33, Tobi wrote:

Hi!

Over the last years, the projects.vdr-developer.org site was hosted on a
server sponsored by Xeatre.tv. This server will now go offline on June, 7'th.

Currently there are about 10 projects with activity in the last 12 months.

I haven't made a final decision on how to proceed, but I'm leaning towards
taking the site offline. In this case I will archive the git repositories
on gitlab or github and possibly keep a read-only instance of Redmine on
my private vServer for a while.

Let me know, what you think. If there are many comments in favor of
keeping the site online, I'm sure I can find a solution.

BR,

Tobias




___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Manuel Reimer]

In the end each individual developer has to decide where he wants to
continue his development.

Years ago a small group of VDR users already created a possible
alternative here:

https://vdr-projects.github.io/
https://github.com/vdr-projects

This GitHub organization has a similar goal as
projects.vdr-developer.org had. Somewhat "organize" VDR related
development and (if the developer wants that) hosting repositories in
context of this GitHub organization to make it possible to hand over the
whole project to a new maintainer if the current maintainer, for
whatever reason, no longer continues to maintain his project for a
considerable amount of time or actively abandons it.

If one of the developers, who is still active on
projects.vdr-developer.org, wants to continue his work in context of the
vdr-projects GitHub organization, then I could migrate his project over.
Best starting point for this would be to create an Issue here:

https://github.com/vdr-projects/vdr-projects.github.io/issues

Then I would also directly have the GitHub user name to give full
permissions on the newly created project.

Manuel


On 24.05.22 21:33, Tobi wrote:

Hi!

Over the last years, the projects.vdr-developer.org site was hosted on a
server sponsored by Xeatre.tv. This server will now go offline on June, 7'th.

Currently there are about 10 projects with activity in the last 12 months.

I haven't made a final decision on how to proceed, but I'm leaning towards
taking the site offline. In this case I will archive the git repositories
on gitlab or github and possibly keep a read-only instance of Redmine on
my private vServer for a while.

Let me know, what you think. If there are many comments in favor of
keeping the site online, I'm sure I can find a solution.

BR,

Tobias

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr



___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] projects.vdr-developer.org might come to an end

[Tobi]

Hi!

Over the last years, the projects.vdr-developer.org site was hosted on a
server sponsored by Xeatre.tv. This server will now go offline on June, 7'th.

Currently there are about 10 projects with activity in the last 12 months.

I haven't made a final decision on how to proceed, but I'm leaning towards
taking the site offline. In this case I will archive the git repositories
on gitlab or github and possibly keep a read-only instance of Redmine on
my private vServer for a while.

Let me know, what you think. If there are many comments in favor of
keeping the site online, I'm sure I can find a solution.

BR,

Tobias

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Termination of ftp.tvdr.de

[Klaus Schmidinger]

On 02.03.22 11:34, Narcis Garcia wrote:

What is the total weight of published data there?
(I'm thinking in deploying a mirror of this HTTP site)


The total amount of data on ftp.tvdr.de is 221 MB.

Klaus


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Termination of ftp.tvdr.de

[Narcis Garcia]

What is the total weight of published data there?
(I'm thinking in deploying a mirror of this HTTP site)


Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't 
masked enough at this mail public archive. Public archive administrator 
should fix this against automated addresses collectors.

El 2/3/22 a les 11:30, Klaus Schmidinger ha escrit:
Since all versions of VDR are now available at git.tvdr.de, new versions 
will be
distributed exclusively through the GIT, and FTP in general is 
considered "legacy"
and frowned upon (Firefox, for instance, doesn't even support it any 
more), I intend
to shut down ftp.tvdr.de. If you still need something from there, please 
download it now.
If you are mirroring this server you may want to stop doing so, to 
prevent your local

copy from disappearing when files vanish from the server.

Klaus


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Termination of ftp.tvdr.de

[Klaus Schmidinger]

Since all versions of VDR are now available at git.tvdr.de, new versions will be
distributed exclusively through the GIT, and FTP in general is considered 
"legacy"
and frowned upon (Firefox, for instance, doesn't even support it any more), I 
intend
to shut down ftp.tvdr.de. If you still need something from there, please 
download it now.
If you are mirroring this server you may want to stop doing so, to prevent your 
local
copy from disappearing when files vanish from the server.

Klaus


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] [ANNOUNCE] VDR version 2.6.1 released

[Klaus Schmidinger]

VDR version 2.6.1 is now available at the official VDR GIT archive

  git://git.tvdr.de

You can also get the latest stable version with

  git clone --branch stable/2.6 git://git.tvdr.de/vdr.git

or as a tar archive with

  http://git.tvdr.de/?p=vdr.git;a=snapshot;h=refs/tags/2.6.1;sf=tbz2

This version fixes a few bugs that came up after the release of version 2.6.0.

The changes since version 2.6.0:

- Replaced strncpy() with memcpy() in strreplace() to avoid a compiler warning
  (reported by Marco Mäkelä).
- Fixed starting replay after jumping to an editing mark.
- Updated the Italian OSD texts (thanks to Diego Pierotto).
- Added some missing "AUTO" values to vdr.5 (thanks to Winfried Köhler).
- Fixed handling zero bytes in cH264Parser (thanks to Christoph Haubrich).
- Fixed handling error conditions in the index file (reported by Markus 
Ehrnsperger).
- Fixed a possible deadlock in cDevice::DetachAllReceivers() (thanks to Helmut 
Binder).
- Clarified some potentially mistakable code in cSectionHandler::SetStatus() 
(pointed
  out by Onur Sentürk).
- Official release.

Homepage: http://www.tvdr.de
Facebook: https://www.facebook.com/VideoDiskRecorder

Have fun!

Klaus

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] vdr with softhddevice

[Josce]

Thank you Klaus for the new 2.6 version!

What is currently the best ( most updated? ) plugin to use with vdpau or  cuvid.

Trying to install vdr on an unused vivobook with NVIDIA Corporation GP108M 
[GeForce MX150]

Josce



___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Tobi]

Many thanks to Klaus for version 2.6.0!

For the state of the Debian packages see:

https://qa.debian.org/developer.php?email=pkg-vdr-dvb-devel%40lists.alioth.debian.org

Besides this I have in my private repository:

deb https://packages.e-tobi.net/vdr-experimental bullseye base
vdr-multipatch addons
deb-src https://packages.e-tobi.net/vdr-experimental bullseye base
vdr-multipatch addons


vdr-addon-acpiwakeup0.0.13
vdr-dev 2.6.0-1~etobi1
vdr-plugin-dummydevice  2.0.0-6
vdr-plugin-dvbhddevice  2.2.0-15
vdr-plugin-dvbsddevice  2.2.0-15
vdr-plugin-dvd  0.3.6~b03+git20211216-2
vdr-plugin-epg2vdr  1.2.5-1
vdr-plugin-epgsearch2.4.1-2
vdr-plugin-epgsync  1.0.1-8
vdr-plugin-examples 2.6.0-1~etobi1
vdr-plugin-femon2.4.0-5
vdr-plugin-fritzbox 1.5.4-2
vdr-plugin-graphlcd 1.0.6-2
vdr-plugin-imonlcd  1.0.3-1
vdr-plugin-iptv 2.4.0-3
vdr-plugin-live 3.1.3-2
vdr-plugin-menuorg  0.5.2-3
vdr-plugin-mp3  0.10.4-2
vdr-plugin-mplayer  0.10.4-2
vdr-plugin-noepg0.0.5-3
vdr-plugin-osdserver0.1.3-22
vdr-plugin-osdteletext  2.3.1-1
vdr-plugin-pvrinput 2015-11-07-4
vdr-plugin-remote   0.7.0-6
vdr-plugin-satip2.4.1-2
vdr-plugin-skindesigner-dbg 1.2.17-1
vdr-plugin-skindesigner 1.2.17-1
vdr-plugin-skinelchi0.3.0-4
vdr-plugin-skinenigmang 0.1.2+git20190720-4
vdr-plugin-skinflatplus 0.6.1-3
vdr-plugin-skinsoppalusikka 2.4.0-2
vdr-plugin-softhddevice 1.2.7-2
vdr-plugin-streamdev-client 0.6.1+git20180514-5
vdr-plugin-streamdev-server 0.6.1+git20180514-5
vdr-plugin-svdrposd 1.0.0-11
vdr-plugin-svdrpservice 1.0.0-10
vdr-plugin-vdrmanager   0.12+git20211220-2
vdr-plugin-vnsiserver   1:1.8.0+git20211205-2
vdr-plugin-wirbelscan   2021.12.11-3
vdr-plugin-xineliboutput2.2.0+git20211212-2
vdr 2.6.0-1~etobi1

BR,

Tobias

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Attempting to use rpihddevice on Debian

[Marko Mäkelä]

Mon, Jan 03, 2022 at 09:47:11AM +0200, Marko Mäkelä wrote:

Sat, Jan 01, 2022 at 06:41:19PM +0200, Marko Mäkelä wrote:

sudo make -C vdr install
LD_LIBRARY_PATH=/opt/vc/lib:/opt/vc/lib/plugins vdr -Prpihddevice

It failed due to an unresolved symbol:

vdr: /opt/vc/lib/libEGL.so: undefined symbol: glPointSizePointerOES


With the preinstalled raspberrypi-userland of Raspberry OS Legacy, that 
problem does not exist. I submitted a fix:


https://github.com/reufer/rpihddevice/pull/3

I wasted quite a bit of time because the README file of that repository 
points to git://projects.vdr-developer.org/vdr-plugin-rpihddevice.git 
which has not been updated since 1.0.4. Other compilation issues that I 
faced had been fixed in the 1.0.5 release.


For Debian Bookworm, I compiled and installed the userland library like 
this:


sudo apt install build-essential cmake
git clone https://github.com/raspberrypi/userland.git/
(cd userland; ./buildme)

With this in place, I was able to compile and install vdr and the two 
plugins that I intend to use.


git clone http://git.tvdr.de/vdr.git

(cd vdr/PLUGINS/src; git clone https://github.com/reufer/rpihddevice.git)

curl http://www.escape-edv.de/endriss/vdr/vdr-remote-0.7.0.tgz --output -|
tar xzf - -C vdr/PLUGINS/src
ln -s remote-0.7.0 vdr/PLUGINS/src/remote

make -C vdr -j$(nproc)
sudo make -C vdr install

Currently, VDR refuses to start up like this:
* failed to open vchiq instance

I did not have that problem on Raspberry OS Legacy last week. I believe 
that I will have to adjust some boot parameters to allow more memory to 
be allocated to the VideoCore GPU. The booting setup appears to be a bit 
different between Debian and Raspberry OS.


I understand that for users in Germany, rpihddevice may be of limited 
use due to the lack of H.265 support:

https://github.com/raspberrypi/firmware/issues/1168/
Luckily, Finland uses H.264 for DVB-T2.

It would be great if raspberrypi-userland and rpihddevice could be 
packaged in Debian.


Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Configuring the remote control unit for the Astrometa USB stick

[Marko Mäkelä]

Sun, Dec 03, 2017 at 09:16:31PM +0200, Marko Mäkelä wrote:

On Sat, Dec 02, 2017 at 09:57:37PM +0200, Marko Mäkelä wrote:
Now I will only have to figure out how to get the remote control to 
work.


The Astrometa driver in the Linux kernel exposes a /dev/input/event 
device that did not react to any of my remote control units, including 
the one that was bundled with the USB stick.


I figured out that the package ir-keytable needs to be installed.

After I added the line
* * hauppauge.toml
as the first non-comment line of /etc/rc_maps.cfg
I was able to use my Hauppauge RCU with the USB DVB stick. It is also 
recognized by vdr-plugin-remote (vdr -Premote).


This is nice, because "sudo apt install inputlirc lirc" would consume 
more than 85 megabytes due to some Python and X11 dependencies.


One problem remains. If I hold a button down, "ir-keytable -t" will keep 
reporting key_down and key_up events. I also feel that it is discarding 
at least every second RC5 packet (occasionally discarding more), no 
matter which --period or --delay settings I try. I had a crude patch for 
the cx88 kernel driver years ago to fix the key-repeat (for example, so 
that holding the volume button will adjust the volume as quickly as 
possible). Now it could be time to port the patch to the new 
infrastructure and submit it.


Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Attempting to use rpihddevice on Debian

[Marko Mäkelä]

Sat, Jan 01, 2022 at 06:41:19PM +0200, Marko Mäkelä wrote:

sudo make -C vdr install
LD_LIBRARY_PATH=/opt/vc/lib:/opt/vc/lib/plugins vdr -Prpihddevice

It failed due to an unresolved symbol:

vdr: /opt/vc/lib/libEGL.so: undefined symbol: glPointSizePointerOES

A similar problem (with no solution yet) has been reported in
https://github.com/malcolmstill/cl-egl/issues/1

I might next try a recent Raspberry OS.


I tried two versions of it. The most recent one indeed is not only 
missing the OMX interface, but there also is no source package available 
for its version of raspberry-userland.


Raspberry OS Legacy (based on Debian 10 and a 5.10 kernel) worked almost 
out of the box, and it had /opt/vc and the development tools 
preinstalled.


https://www.raspberrypi.com/software/operating-systems/#raspberry-pi-os-legacy

In the rpihddevice/Makefile I additionally had to replace -lGLESv2 -lEGL 
with -lbrcmGLESv2 -lbrcmEGL. In fact, if -lGLESv2 -lEGL of the wrong 
kind were available, you could end up with no picture or OSD. This was 
actually reported on vdr-portal.de already in 2017. :-o


Maybe using the Broadcom libraries would also have fixed the above issue 
when using Debian and self-built rasberry-userland; I am yet to try 
that.


I have submitted the patches to the author of rpihddevice, hoping to see 
them in the repository soon.


Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Marko Mäkelä]

Sat, Jan 01, 2022 at 06:44:52PM +0100, Narcis Garcia wrote:

As Far As I Know w-scan2 is needed to tune DVB-T2

https://github.com/stefantalpalaru/w_scan2/


Another DVB-T2 compatible solution (which also supports DVB-T) is 
t2scan.


This is how I built and invoked it on my Raspberry Pi 2 (using Debian, 
or 2 different most recent versions of Raspberry OS):


git clone https://github.com/mighty-p/t2scan
cd t2scan
./configure
make -j$(nproc)
./t2scan -E -d|tee channels.conf

Before this, I had to copy the firmware blob for the Astrometa DVB-T2 
adapter to /lib/firmware/dvb-demod-mn88473-01.fw and plug in the USB 
adapter. For some reason, that firmware is missing from Debian.


Without the firmware, the scan would fail with "no signal" on every 
channel.


The t2scan program is apparently using LANG or LC_CTYPE to guess the 
current country, which only works if the locale files have been built.  
The default (Germany) may be overridden with the -Y flag.


Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Narcis Garcia]

As Far As I Know w-scan2 is needed to tune DVB-T2

https://github.com/stefantalpalaru/w_scan2/

What I don't know is how to do to manage TV tunning from Kodi interface.



Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't 
masked enough at this mail public archive. Public archive administrator 
should fix this against automated addresses collectors.

El 7/12/21 a les 9:40, Narcis Garcia ha escrit:

vdr-plugin-dvbhddevice
vdr-plugin-dvbsddevice
vdr-plugin-femon
vdr-plugin-live
vdr-plugin-osdserver
vdr-plugin-streamdev-client
vdr-plugin-streamdev-server
vdr-plugin-vnsiserver
w-scan2


Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't 
masked enough at this mail public archive. Public archive administrator 
should fix this against automated addresses collectors.

El 7/12/21 a les 9:05, Reiner Buehl ha escrit:

Hello Tobi,

I use the following plugins on my Debian based VDR systems:

  vdr-plugin-epgsearch
  vdr-plugin-extrecmenu
  vdr-plugin-graphlcd
  vdr-plugin-markad-ng
  vdr-plugin-menuorg
  vdr-plugin-skinflatplus
  vdr-plugin-xineliboutput
  vdr-plugin-streamdev-*

Thanks for maintaining the packages!

Best regards,
Reiner

Am 2021-12-06 22:45, schrieb Tobi:

Hi!

To my shame, I have rather neglected the maintenance of the VDR and VDR
plugin packages for Debian and e-tobi.net over the last 2 years.
I am in the process of catching up. However, I would like to get rid of
some plugins where nothing is happening upstream anymore.
Which plugins do you consider indispensable and would like to see them
continue in the official Debian and/or e-tobi.net Debian repositories?

BR,

Tobias

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr




___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Attempting to use rpihddevice on Debian

[Marko Mäkelä]

Thu, Dec 30, 2021 at 07:55:40PM +0200, Marko Mäkelä wrote:

https://github.com/raspberrypi/userland


I was able to build and install this in /opt/vc (which is where 
rpihddevice looks for it) after installing sudo and cmake:


git clone https://github.com/raspberrypi/userland
(cd userland;./buildme)

rm vdr/PLUGINS/src/rpihddevice/.dependencies
make -j$(nproc) -C vdr

The compilation would spit out some deprecation warnings, as well as 
errors for missing FF_INPUT_BUFFER_PADDING_SIZE in audio.c. After I 
replaced those with AV_INPUT_BUFFER_PADDING_SIZE, the build succeeded.  
This was with libavcodec-dev and libavcodec58 (7:4.4.1-2+b1).


Finally, I installed and attempted to start up vdr:

sudo make -C vdr install
LD_LIBRARY_PATH=/opt/vc/lib:/opt/vc/lib/plugins vdr -Prpihddevice

It failed due to an unresolved symbol:

vdr: /opt/vc/lib/libEGL.so: undefined symbol: glPointSizePointerOES

A similar problem (with no solution yet) has been reported in
https://github.com/malcolmstill/cl-egl/issues/1

I might next try a recent Raspberry OS. My goal is not only to upgrade 
and configure VDR for my own casual use, but also to document the 
process and to make it as easy as possible for others.


Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] [SOLVED] Looking for DVB-C channels conf for Kabel DE München

[Harald Milz]

OK, disregard all after good morning. I found that you can download the full
up-to-date channels list in various formats from
https://helpdesk.vodafonekabelforum.de, including channels.conf. 



On Sat, Jan 01, 2022 at 11:28:26AM +0100, Harald Milz wrote:
> Hi all, 
> 
> happy new year everyone! 
> 
> I would like to add my DVB-C channels to my existing setup but can't seem to
> find a working channels.conf for Kabel Deutschland München anywhere. There are
> only older versions around but I know that they changed their channel
> assignments considerably in the last few years. 
> 
> Any help is appreciated!
> 
> 
> -- 
> This night methinks is but the daylight sick.
>   -- William Shakespeare, "The Merchant of Venice"

-- 
Q:  Why do WASPs play golf ?
A:  So they can dress like pimps.

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Looking for DVB-C channels conf for Kabel DE München

[Harald Milz]

Hi all, 

happy new year everyone! 

I would like to add my DVB-C channels to my existing setup but can't seem to
find a working channels.conf for Kabel Deutschland München anywhere. There are
only older versions around but I know that they changed their channel
assignments considerably in the last few years. 

Any help is appreciated!


-- 
This night methinks is but the daylight sick.
-- William Shakespeare, "The Merchant of Venice"

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Marko Mäkelä]

Wed, Dec 29, 2021 at 04:56:54PM +0200, René wrote:
Klaus just released 2.6.0. Any chance if we could get that version too? 
:-)


For me, git://projects.vdr-developer.org/vdr-plugin-rpihddevice.git 
would be a must-have feature.


Today I made an attempt of installing Debian Sid from the scratch on a 
new SD card, starting with https://wiki.debian.org/RaspberryPiImages and 
documenting the steps.


The non-obvious first steps (to enable system clock updates and make the 
system visible in the .local network) were as follows:


apt install systemd-timesyncd avahi-daemon
timedatectl set-ntp on

Tobias wrote:

Still on the TODO list are:

∙ vdr-plugin-rpihddevice

[snip]

For rpihddevice I'm not sure what to do - OMX and MMAL have been
deprecated in Raspbian/bullseye, so it doesn't even build out of the box.
And it doesn't look like a V4L2 version is being worked on.


Today, I was almost able to compile VDR 2.6.0 on Debian Sid with 
rpihddevice. First, the dependencies:


apt install build-essential git
apt install pkg-config gettext
apt install libfreetype6-dev libfontconfig1-dev libjpeg62-turbo-dev
apt install libcap-dev libncurses5-dev
apt install libavcodec-dev libavformat-dev

Then, as a normal user, execute the following:

git clone http://git.tvdr.de/vdr.git
git clone git://projects.vdr-developer.org/vdr-plugin-rpihddevice.git
ln -s ../../../vdr-plugin-rpihddevice vdr/PLUGINS/src/rpihddevice
make -C vdr -j$(nproc)

The build failed due to a missing header:

ilclient.c:50:10: fatal error: interface/vcos/vcos.h: No such file or directory

There are very few Raspberry specific packages in Debian. libbcm2835-dev 
is covering something else.


As far as I can tell, the file is provided by the Raspberry OS or Ubuntu 
package libraspberrypi-dev in /opt/vc/include or /usr/include, 
respectively. That package appears to be missing from Debian, even the 
non-free section.


Tobias, would it be possible to add these packages to Debian Sid?

https://github.com/raspberrypi/userland

I am not familiar with this, but I see that something in interface/vcos 
was changed only 2 months ago. Most of the files are years old, but so 
is my Raspberry Pi 2. I did not notice any deprecation message, but I 
suppose that you were referring to some other interface being 
deprecated.


The Ubuntu package could serve as a starting point:

https://packages.ubuntu.com/source/impish/raspberrypi-userland

My aim is to document the process of creating a minimal VDR installation 
on a Raspberry Pi. It would be great if all code were available out of 
the box.


For me, the "killer feature" would be custom configuration for making 
VDR automatically start up when the USB DVB adapter is plugged in. An 
unplugged adapter cannot waste electricity or let a lighting bolt kill 
the server.


Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Andreas Kreuzinger]

Hi,

* Tobi  [2021-12-06 22:45]:

> To my shame, I have rather neglected the maintenance of the VDR and VDR
> plugin packages for Debian and e-tobi.net over the last 2 years.
> I am in the process of catching up. However, I would like to get rid of
> some plugins where nothing is happening upstream anymore.
> Which plugins do you consider indispensable and would like to see them
> continue in the official Debian and/or e-tobi.net Debian repositories?

I am using these (and it would be nice to have them or an equivalent):
vdr
vdradmin-am
vdr-markad
vdr-plugin-epgsearch
vdr-plugin-femon
vdr-plugin-remote
vdr-plugin-streamdev-server
vdr-plugin-svdrposd
vdr-plugin-vnsiserver
vdr-plugin-xineliboutput

Thank you for your work.  :)

mfg @ndy
-- 


signature.asc
Description: PGP signature
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] [ANNOUNCE] VDR version 2.6.0 released

[Klaus Schmidinger]

VDR version 2.6.0 is now available at the official VDR GIT archive

  git://git.tvdr.de

You can get the latest stable version with

  git clone --branch stable/2.6 git://git.tvdr.de/vdr.git

If you want to download the source as a tar archive, use

  http://git.tvdr.de/?p=vdr.git;a=snapshot;h=refs/tags/2.6.0;sf=tbz2

A summary of all the major changes since the last stable version can be found at

  http://www.tvdr.de/changelog.htm

There is also a new version with important fixes in the stable/2.4 branch, for
those who don't want to or can't switch to version 2.6 at this time:

  http://git.tvdr.de/?p=vdr.git;a=snapshot;h=refs/tags/2.4.8;sf=tbz2

When updating from an earlier version of VDR please make sure you read the 
INSTALL
and MANUAL files that come with the VDR source _before_ doing so!
Please make sure you have backup copies of all your configuration files,
and verify carefully that your timers will be set to the correct channels
after switching to this new version.

Thanks to the many people who have contributed in the making, testing and
debugging of this new version of VDR, and also to all users who just
enjoy VDR!

Please also visit the VDR homepage at

 http://www.tvdr.de

and VDR's facebook page at

 https://www.facebook.com/VideoDiskRecorder

Have fun!

Klaus

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] PetShopBoys on BBC

[Reinhard Nißl]

Hello Karl-Heinz,

I just had a glance at onlinetvrecorder.com and will give it a try.

Thanks.

Bye.
--
Reinhard Nißl

Am 26.12.2021 um 10:09 schrieb Karl-Heinz Volk:

The Big New Years Years Eve Party with Kylie and Pet Shop Boys
 have ich gerade auf
onlinetvrecorder.com  programmiert (UK BBC
One).

Viele Grüße
   Karl-Heinz

Am Sa., 25. Dez. 2021 um 22:40 Uhr schrieb Reinhard Nißl mailto:rni...@gmx.de>>:

Hi,

is anyone willing to record a couple of radio- and TV-broadcasts on
BBC the next days?

See

http://view.e.wmg.com/?qs=5783d1cfd364e6f6d8d27a784af750a84bce302b7d9a37ba4535c8900ffc38e05d63fb3234aab2db20328a264177cf22c655045331c803fee59e9d9ce7334c4b157c7bfb770b2c6e9d2682e5fb411dfc


 for
schedules.

Thanks in advance.

Bye.
--
Reinhard Nißl
___
vdr mailing list
vdr@linuxtv.org 
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr




--
Karl-Heinz Volk
Pastorenweg 78 B
28237 Bremen

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] PetShopBoys on BBC

[Narcis Garcia]

Are these spam letters?


Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't 
masked enough at this mail public archive. Public archive administrator 
should fix this against automated addresses collectors.

El 26/12/21 a les 10:09, Karl-Heinz Volk ha escrit:
The Big New Years Years Eve Party with Kylie and Pet Shop Boys 
<*nlinetvrecorder.com/v2/search/title/The Big New Years 
Years Eve Party with Kylie and Pet Shop Boys> have ich gerade auf 
onlinetvrecorder.com <*nlinetvrecorder.com> programmiert (UK BBC 
One).


Viele Grüße
   Karl-Heinz

Am Sa., 25. Dez. 2021 um 22:40 Uhr schrieb Reinhard Nißl <*mx.de 
<*mx.de>>:


Hi,

is anyone willing to record a couple of radio- and TV-broadcasts on
BBC the next days?

See

*iew.e.wmg.com/?qs=5783d1cfd364e6f6d8d27a784af750a84bce302b7d9a37ba4535c8900ffc38e05d63fb3234aab2db20328a264177cf22c655045331c803fee59e9d9ce7334c4b157c7bfb770b2c6e9d2682e5fb411dfc

<*iew.e.wmg.com/?qs=5783d1cfd364e6f6d8d27a784af750a84bce302b7d9a37ba4535c8900ffc38e05d63fb3234aab2db20328a264177cf22c655045331c803fee59e9d9ce7334c4b157c7bfb770b2c6e9d2682e5fb411dfc>
 for
schedules.

Thanks in advance.

Bye.
-- 
Reinhard Nißl

___
vdr mailing list
vdr@linuxtv.org 
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr




--
Karl-Heinz Volk
Pastorenweg 78 B
28237 Bremen

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr



___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] PetShopBoys on BBC

[Karl-Heinz Volk]

The Big New Years Years Eve Party with Kylie and Pet Shop Boys
 have ich gerade auf
onlinetvrecorder.com programmiert (UK BBC One).

Viele Grüße
  Karl-Heinz

Am Sa., 25. Dez. 2021 um 22:40 Uhr schrieb Reinhard Nißl :

> Hi,
>
> is anyone willing to record a couple of radio- and TV-broadcasts on BBC
> the next days?
>
> See
> http://view.e.wmg.com/?qs=5783d1cfd364e6f6d8d27a784af750a84bce302b7d9a37ba4535c8900ffc38e05d63fb3234aab2db20328a264177cf22c655045331c803fee59e9d9ce7334c4b157c7bfb770b2c6e9d2682e5fb411dfc
> 
>  for
> schedules.
>
> Thanks in advance.
>
> Bye.
> --
> Reinhard Nißl
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>


-- 
Karl-Heinz Volk
Pastorenweg 78 B
28237 Bremen
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] PetShopBoys on BBC

[Reinhard Nißl]

Hi,

is anyone willing to record a couple of radio- and TV-broadcasts on BBC the 
next days?

See 
http://view.e.wmg.com/?qs=5783d1cfd364e6f6d8d27a784af750a84bce302b7d9a37ba4535c8900ffc38e05d63fb3234aab2db20328a264177cf22c655045331c803fee59e9d9ce7334c4b157c7bfb770b2c6e9d2682e5fb411dfc
  for schedules.

Thanks in advance.

Bye.
-- 
Reinhard Nißl___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net (Tobi)

[Richard F]

Heroic work - thanks, and Merry Xmas

Richard

On 22/12/2021 12:00, vdr-requ...@linuxtv.org wrote:


Today's Topics:

1. Re: VDR packages in Debian and e-tobi.net (Tobi)

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Tobi]

So far, I've updated the following packages in debian/sid, which soon will
migrate to debian/testing:

∙ vdr 2.4.7
∙ vdr-plugin-dvd 0.3.6~b03+git20211216
∙ vdr-plugin-dvbhddevice 2.2.0
∙ vdr-plugin-dvbsddevice 2.2.0
∙ vdr-plugin-epgsearch 2.4.1
∙ vdr-plugin-epgsync 1.0.1
∙ vdr-plugin-femon 2.4.0
∙ vdr-plugin-live 3.1.3
∙ vdr-plugin-osdserver 0.1.3
∙ vdr-plugin-osdteletext 2.3.0
∙ vdr-plugin-remote 0.7.0
∙ vdr-plugin-satip 2.4.1
∙ vdr-plugin-skinenigmang 0.1.2+git20190720
∙ vdr-plugin-streamdev 0.6.1+git20180514
∙ vdr-plugin-svdrposd 1.0.0
∙ vdr-plugin-svdrpservice 1.0.0
∙ vdr-plugin-vnsiserver 1:1.8.0+git20211205-1
∙ vdr-plugin-xineliboutput 2.2.0+git20211212-1

For vnsiserver I use the original version from FernetMenta, not the fork
from mdre77, which seems to be more up to date. But as the original
version works fine for me, I will stay with it, until someone can convince
me to switch to the fork.

Additionally to these packages, the following plugins are also available
in my private repository:

deb https://packages.e-tobi.net/vdr-experimental bullseye base
vdr-multipatch addons

∙ vdr-plugin-dummydevice 2.0.0
∙ vdr-plugin-epg2vdr 1.1.118
∙ vdr-plugin-femon 2.4.0
∙ vdr-plugin-fritzbox 1.5.4
∙ vdr-plugin-graphlcd 1.0.6
∙ vdr-plugin-iptv 2.4.0
∙ vdr-plugin-menuorg 0.5.2
∙ vdr-plugin-noepg 0.0.5
∙ vdr-plugin-pvrinput 2015-11-07
∙ vdr-plugin-skinelchi 0.3.0
∙ vdr-plugin-skinflatplus 0.6.1
∙ vdr-plugin-skinsoppalusikka 2.4.0
∙ vdr-plugin-softhddevice 1.2.6
∙ vdr-plugin-vdrmanager 0.12+git20211220
∙ vdr-plugin-wirbelscan 2021.12.11

Still on the TODO list are:

∙ vdr-plugin-rpihddevice
∙ vdr-plugin-markad or markad-ng
∙ vdr-plugin-extrecmenu or extrecmenung
∙ vdr-plugin-yaepghd
∙ vdr-plugin-vaapidevice
∙ vdr-plugin-undelete
∙ vdr-plugin-tvguide
∙ vdr-plugin-trayopenng
∙ vdr-plugin-suspendoutput
∙ vdr-plugin-osdpip
∙ vdr-plugin-noepg
∙ vdr-plugin-loadepg
∙ vdr-plugin-cdplayer
∙ vdr-plugin-skindesigner
∙ vdr-plugin-imonlcd

For rpihddevice I'm not sure what to do - OMX and MMAL have been
deprecated in Raspbian/bullseye, so it doesn't even build out of the box.
And it doesn't look like a V4L2 version is being worked on.

For undelete I'm thinking about applying this patch instead:

https://www.vdr-portal.de/forum/index.php?thread/132378-vdr-2-4-x-und-undelete/

Maybe Klaus can consider this for 2.5.x/2.6.x.

I can't test all these plugins. The only plugins I really use, are
vnsiserver, epgsearch and rarely xineliboutput and femon.

BR,
Tobias

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Udo Richter]

On 13.12.21 00:28, Tobi wrote:

I hope to have at least have the top 20 plugin packages updated by the end
of the year.


If you need help with any of my old plugins or patches, let me know.

Cheers,

Udo


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Tobi]

Thanks for your suggesstions!

I hope to have at least have the top 20 plugin packages updated by the end
of the year.

Packages will be updated in debian/unstable first.

BR,

Tobias

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Matthias Maisenbacher]

> I am in the process of catching up.
That sounds great.

> Which plugins do you consider indispensable and would like to see them
> continue in the official Debian and/or e-tobi.net Debian repositories?
I'd really like to see undelete again
(Or any other plugin with that functionality)

Thank you for your work.

  Matthias

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Torgeir Veimo]

Having VDR running natively on android would be nice, but there's no
v4l there. Did you try robotv with the livechannels app? It works
fairly well, but it's not the native VDR OSD, and there's dropout from
time to time.

On Thu, 9 Dec 2021 at 18:17, Karl-Heinz Volk  wrote:
>
> Nice to hear that you are planning a new repository:
>
> vdr-plugin-streamdev-client
> vdr-plugin-streamdev-server
> vdr-plugin-softhddevice
> vdr-plugin-rpihddevice
> vdr-plugin-vaapidevice
>
> And is it really so far away, to have a vdr for Android-TV? I own a Sony 
> 43X8309C. 6 Years old and only usable with a Firetv-Stick...
>
> Viele Grüße
>   Karl-Heinz
>
>
>
> Am Mi., 8. Dez. 2021 um 16:41 Uhr schrieb Piotr Długosz :
>>
>> Thank you Tobias for your work!
>>
>> I'm using VDR with:
>>
>> vdr-plugin-epgsearch
>> vdr-plugin-femon
>> vdr-plugin-live
>> vdr-plugin-skinelchi
>> vdr-plugin-streamdev-client
>> vdr-plugin-streamdev-server
>> vdr-plugin-svdrposd
>> vdr-plugin-tvguide
>> vdr-plugin-vdrmanager
>> vdr-plugin-xineliboutput
>>
>> However, I would happily change the skin plugin because skinelchi is in
>> use for >10 years already ;-) Only I have to find nicer skin working
>> well on obsolete Full HD TV...
>>
>> Best regards,
>> Piotr
>>
>> W dniu pon, 06.12.2021 o godzinie 22∶45 +0100, użytkownik Tobi napisał:
>> > Hi!
>> >
>> > To my shame, I have rather neglected the maintenance of the VDR and
>> > VDR
>> > plugin packages for Debian and e-tobi.net over the last 2 years.
>> > I am in the process of catching up. However, I would like to get rid
>> > of
>> > some plugins where nothing is happening upstream anymore.
>> > Which plugins do you consider indispensable and would like to see
>> > them
>> > continue in the official Debian and/or e-tobi.net Debian
>> > repositories?
>> >
>> > BR,
>> >
>> > Tobias
>> >
>> > ___
>> > vdr mailing list
>> > vdr@linuxtv.org
>> > https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>>
>>
>> ___
>> vdr mailing list
>> vdr@linuxtv.org
>> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>
>
>
> --
> Karl-Heinz Volk
> Pastorenweg 78 B
> 28237 Bremen
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr



-- 
-Tor

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Karl-Heinz Volk]

Nice to hear that you are planning a new repository:

vdr-plugin-streamdev-client
vdr-plugin-streamdev-server
vdr-plugin-softhddevice
vdr-plugin-rpihddevice
vdr-plugin-vaapidevice

And is it really so far away, to have a vdr for Android-TV? I own a Sony
43X8309C. 6 Years old and only usable with a Firetv-Stick...

Viele Grüße
  Karl-Heinz



Am Mi., 8. Dez. 2021 um 16:41 Uhr schrieb Piotr Długosz :

> Thank you Tobias for your work!
>
> I'm using VDR with:
>
> vdr-plugin-epgsearch
> vdr-plugin-femon
> vdr-plugin-live
> vdr-plugin-skinelchi
> vdr-plugin-streamdev-client
> vdr-plugin-streamdev-server
> vdr-plugin-svdrposd
> vdr-plugin-tvguide
> vdr-plugin-vdrmanager
> vdr-plugin-xineliboutput
>
> However, I would happily change the skin plugin because skinelchi is in
> use for >10 years already ;-) Only I have to find nicer skin working
> well on obsolete Full HD TV...
>
> Best regards,
> Piotr
>
> W dniu pon, 06.12.2021 o godzinie 22∶45 +0100, użytkownik Tobi napisał:
> > Hi!
> >
> > To my shame, I have rather neglected the maintenance of the VDR and
> > VDR
> > plugin packages for Debian and e-tobi.net over the last 2 years.
> > I am in the process of catching up. However, I would like to get rid
> > of
> > some plugins where nothing is happening upstream anymore.
> > Which plugins do you consider indispensable and would like to see
> > them
> > continue in the official Debian and/or e-tobi.net Debian
> > repositories?
> >
> > BR,
> >
> > Tobias
> >
> > ___
> > vdr mailing list
> > vdr@linuxtv.org
> > https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>
>
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>


-- 
Karl-Heinz Volk
Pastorenweg 78 B
28237 Bremen
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Piotr Długosz]

Thank you Tobias for your work!

I'm using VDR with:

vdr-plugin-epgsearch   
vdr-plugin-femon   
vdr-plugin-live
vdr-plugin-skinelchi   
vdr-plugin-streamdev-client
vdr-plugin-streamdev-server
vdr-plugin-svdrposd
vdr-plugin-tvguide 
vdr-plugin-vdrmanager  
vdr-plugin-xineliboutput   

However, I would happily change the skin plugin because skinelchi is in
use for >10 years already ;-) Only I have to find nicer skin working
well on obsolete Full HD TV...

Best regards,
Piotr

W dniu pon, 06.12.2021 o godzinie 22∶45 +0100, użytkownik Tobi napisał:
> Hi!
> 
> To my shame, I have rather neglected the maintenance of the VDR and
> VDR
> plugin packages for Debian and e-tobi.net over the last 2 years.
> I am in the process of catching up. However, I would like to get rid
> of
> some plugins where nothing is happening upstream anymore.
> Which plugins do you consider indispensable and would like to see
> them
> continue in the official Debian and/or e-tobi.net Debian
> repositories?
> 
> BR,
> 
> Tobias
> 
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Patrick Cernko]

Hi Tobi,

I'm using

vdr
vdr-plugin-epgsearch
vdr-plugin-extrecmenung (from https://gitlab.com/kamel5/extrecmenung)
vdr-plugin-femon
vdr-plugin-live
vdr-plugin-osdteletext
vdr-plugin-streamdev-server
vdr-plugin-xineliboutput (from deb-multimedia.org)
vdradmin-am

on my vdr running as headless server and xineliboutput-sxfe (from 
deb-multimedia.org) on my Viewer-Client.


Best,
--
Patrick Cernko | mailto:err...@errror.org | http://www.errror.org



smime.p7s
Description: S/MIME Cryptographic Signature
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Narcis Garcia]

vdr-plugin-dvbhddevice
vdr-plugin-dvbsddevice
vdr-plugin-femon
vdr-plugin-live
vdr-plugin-osdserver
vdr-plugin-streamdev-client
vdr-plugin-streamdev-server
vdr-plugin-vnsiserver
w-scan2


Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't 
masked enough at this mail public archive. Public archive administrator 
should fix this against automated addresses collectors.

El 7/12/21 a les 9:05, Reiner Buehl ha escrit:

Hello Tobi,

I use the following plugins on my Debian based VDR systems:

  vdr-plugin-epgsearch
  vdr-plugin-extrecmenu
  vdr-plugin-graphlcd
  vdr-plugin-markad-ng
  vdr-plugin-menuorg
  vdr-plugin-skinflatplus
  vdr-plugin-xineliboutput
  vdr-plugin-streamdev-*

Thanks for maintaining the packages!

Best regards,
Reiner

Am 2021-12-06 22:45, schrieb Tobi:

Hi!

To my shame, I have rather neglected the maintenance of the VDR and VDR
plugin packages for Debian and e-tobi.net over the last 2 years.
I am in the process of catching up. However, I would like to get rid of
some plugins where nothing is happening upstream anymore.
Which plugins do you consider indispensable and would like to see them
continue in the official Debian and/or e-tobi.net Debian repositories?

BR,

Tobias

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr




___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR packages in Debian and e-tobi.net

[Reiner Buehl]

Hello Tobi,

I use the following plugins on my Debian based VDR systems:

 vdr-plugin-epgsearch
 vdr-plugin-extrecmenu
 vdr-plugin-graphlcd
 vdr-plugin-markad-ng
 vdr-plugin-menuorg
 vdr-plugin-skinflatplus
 vdr-plugin-xineliboutput
 vdr-plugin-streamdev-*

Thanks for maintaining the packages!

Best regards,
Reiner

Am 2021-12-06 22:45, schrieb Tobi:

Hi!

To my shame, I have rather neglected the maintenance of the VDR and VDR
plugin packages for Debian and e-tobi.net over the last 2 years.
I am in the process of catching up. However, I would like to get rid of
some plugins where nothing is happening upstream anymore.
Which plugins do you consider indispensable and would like to see them
continue in the official Debian and/or e-tobi.net Debian repositories?

BR,

Tobias

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


--
--
Reiner Bühl  Internet:
Karlstrasse 3rei...@buehl.net
70771 Leinfelden-Echterdingen
Germany
--


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] VDR packages in Debian and e-tobi.net

[Tobi]

Hi!

To my shame, I have rather neglected the maintenance of the VDR and VDR
plugin packages for Debian and e-tobi.net over the last 2 years.
I am in the process of catching up. However, I would like to get rid of
some plugins where nothing is happening upstream anymore.
Which plugins do you consider indispensable and would like to see them
continue in the official Debian and/or e-tobi.net Debian repositories?

BR,

Tobias

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Making VDR run under Systemd

[Marko Mäkelä]

Thu, Oct 21, 2021 at 02:06:37AM +0300, glenvt18 wrote:
I'm not sure VDR is "idle" while a recording is paused. What is the log 
output?


I can only see a clue "trying device number 2 instead":

Oct 20 21:37:56 raspberrypi vdr: [3878] DVB API version is 0x050B (VDR was 
built with 0x050A)
Oct 20 21:37:56 raspberrypi vdr: [3878] frontend 0/0 provides DVB-T with QPSK,QAM16,QAM64 
("Realtek RTL2832 (DVB-T)")
Oct 20 21:37:57 raspberrypi kernel: [257117.778208] mn88473 3-0018: downloading 
firmware from file 'dvb-demod-mn88473-01.fw'
Oct 20 21:37:57 raspberrypi vdr: [3878] frontend 0/1 provides DVB-T,DVB-T2,DVB-C with 
QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("Panasonic MN88473")
Oct 20 21:37:58 raspberrypi vdr: [3878] found 1 DVB device
Oct 20 21:37:58 raspberrypi vdr: [3878] initializing plugin: rpihddevice 
(1.0.4): HD output device for Raspberry Pi
Oct 20 21:37:58 raspberrypi vdr: [3878] rpihddevice: HwInit() done, display 
size is 1920x1080
Oct 20 21:37:58 raspberrypi vdr: [3878] setting primary device to 1
Oct 20 21:37:58 raspberrypi vdr: [3878] device 1 has no MPEG decoder
Oct 20 21:37:58 raspberrypi vdr: [3878] trying device number 2 instead
Oct 20 21:37:58 raspberrypi vdr: [3878] setting primary device to 2
Oct 20 21:37:58 raspberrypi vdr: [3878] setting current skin to "lcars"
Oct 20 21:37:58 raspberrypi vdr: [3878] loading 
/var/lib/vdr/themes/lcars-default.theme
Oct 20 21:37:58 raspberrypi vdr: [3878] starting plugin: rpihddevice
Oct 20 21:37:58 raspberrypi lircd-0.9.4c[3811]: Notice: accepted new client on 
/var/run/lirc/lircd
Oct 20 21:37:58 raspberrypi vdr: [3878] switching to channel 1 T-8438-8193-1501 
(Yle TV1 HD (T))
Oct 20 21:37:58 raspberrypi lircd-0.9.4c[3811]: Info: [lirc] protocol is enabled
Oct 20 21:37:58 raspberrypi vdr: [3911] SVDRP raspberrypi opening port 6419/tcp
Oct 20 21:37:58 raspberrypi vdr: [3911] SVDRP raspberrypi listening on port 
6419/tcp
Oct 20 21:37:58 raspberrypi vdr: [3907] rpihddevice: loading 
/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf ...
Oct 20 21:37:58 raspberrypi vdr: [3907] rpihddevice: loading 
/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf ...
Oct 20 21:38:01 raspberrypi vdr: [3878] retuning due to modification of channel 
1 (Yle TV1 HD (T))
Oct 20 21:38:01 raspberrypi vdr: [3878] switching to channel 1 T-8438-8193-1501 
(Yle TV1 HD (T))
Oct 20 21:40:00 raspberrypi vdr: [3911] SVDRP raspberrypi < 127.0.0.1:52142 
client connection accepted
Oct 20 21:40:08 raspberrypi vdr: [3878] replay 
/var/lib/video/XXX/2019-01-05.19.07.19-0.rec
Oct 20 21:40:08 raspberrypi vdr: [3878] loading 
/var/lib/video/XXX/2019-01-05.19.07.19-0.rec/marks
Oct 20 21:40:08 raspberrypi vdr: [3947] resuming replay at index 807 
(0:00:32.07)
Oct 20 21:40:13 raspberrypi vdr: [3911] SVDRP raspberrypi < 127.0.0.1:52142 
connection closed
Oct 20 21:41:55 raspberrypi vdr: [3878] stopping plugin: rpihddevice
Oct 20 21:41:55 raspberrypi lircd-0.9.4c[3811]: Info: removed client
Oct 20 21:41:55 raspberrypi vdr: [3878] saved setup to /var/lib/vdr/setup.conf

If I remember, there is a softhddevice's command/option called 
"suspend" or "detach", or whatever, which stops live TV. That

causes idle state too.


I remember (co-)developing such a feature for softdevice (without the 
"hd" part). Apart from saving power, another motivation was to reduce 
the probability of crashes, because reception errors of the DVB-T stream 
used to cause that back then.


Maybe I could check if something similar could be done in rpihddevice.

Still, in my opinion, when a recording is being watched and nothing is 
being simultaneously recorded or streamed, there should normally be no 
reason to keep any tuners powered.



BTW. Do you use both DVB-T and DVB-T2?


Yes, some transponders are DVB-T and some are DVB-T2, and I think that 
all free-to-view DVB-T2 channels are also available via DVB-T. I do not 
know when that transition period will end here. Wikipedia says that it 
was supposed to complete by April 2020 already. The first DVB-T2 
transponders were introduced in 2011.



And I've never tried the patch with VDR > 2.4.6.


The patch applied without glitches, only some line number differences.  
In VDR 2.5, the EPG works for me. In 2.4, I think I never got it to 
cover the DVB-T2 transponders.


Best regards,

Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Making VDR run under Systemd

[glenvt18]

I'm not sure VDR is "idle" while a recording is paused. What is the log
output?

I myself don't use a standalone VDR (using softhddevice etc.). I use it
only as a streaming server. When you start VDR as a server, it enters
idle mode after a configured timeout. It might be different for a
standalone VDR. If I remember, there is a softhddevice's command/option
called "suspend" or "detach", or whatever, which stops live TV. That
causes idle state too.

BTW. Do you use both DVB-T and DVB-T2?

And I've never tried the patch with VDR > 2.4.6.

On Wed, Oct 20, 2021 at 10:04:26PM +0300, Marko Mäkelä wrote:
> Mon, Oct 18, 2021 at 11:44:32PM +0300, glenvt18 wrote:
> > What is the output of
> > 
> >lsof | grep frontend
> > 
> > when VDR is in the "idle" state?
> 
> I produced some output from /proc/$(pgrep vdr)/fd which I think might be
> more helpful. The last-but-one "ls" output was "too soon" after I started
> and paused the recording, so VDR was still in normal mode.
> 
> In case you wonder, the connection between lircd and vdr did not work last
> time I tried, and probably also not this time. That is why I used telnet to
> the SVDRP port.
> 
> The last "ls" command was when VDR was expected to be idle (after 1-minute
> timeout, instead of the 15-minute timeout of your patch). I ran the command
> once more after a while, and the output remained identical.
> 
> Note that this USB DVB-T stick has two frontends for the same aerial
> connector. I think that one is for DVB-T and another for DVB-T2. You can see
> that "frontend1" was replaced with "frontend0" in the not-quite-idle mode.
> 
> I am happy to try a revised patch, and I can also use GDB ("thread apply all
> backtrace" and such) if that is needed.
> 
> This was the latest commit 0d50ec57f50375c8fda92d117e348dd8fd5a77a9
> ("Version 2.5.6") from http://git.tvdr.de/vdr.git with only your patch on
> top (and the 15-minute timeout changed to 1 minute).
> 
> Best regards,
> 
>   Marko
> 
> pi@raspberrypi:~ $ sudo service lircd start
> pi@raspberrypi:~ $ pgrep lircd
> 3811
> pi@raspberrypi:~ $ sudo ls -l /proc/3811/fd
> yhteensä 0
> lr-x-- 1 root root 64 loka  20 21:37 0 -> /dev/null
> lrwx-- 1 root root 64 loka  20 21:37 1 -> socket:[47310]
> lrwx-- 1 root root 64 loka  20 21:37 2 -> socket:[47310]
> lrwx-- 1 root root 64 loka  20 21:37 3 -> socket:[49360]
> lrwx-- 1 root root 64 loka  20 21:37 4 -> socket:[47311]
> lrwx-- 1 root root 64 loka  20 21:37 5 -> /run/lirc/lircd.pid
> lr-x-- 1 root root 64 loka  20 21:37 6 -> 
> /sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.5/rc/rc0/protocols
> lr-x-- 1 root root 64 loka  20 21:37 7 -> 
> /sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.5/rc/rc0/protocols
> pi@raspberrypi:~ $ sudo service vdr start
> pi@raspberrypi:~ $ sudo lsof /dev/dvb/adapter0/*
> COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
> vdr 3878  vdr7u   CHR  212,3  0t0 42703 
> /dev/dvb/adapter0/frontend0
> pi@raspberrypi:~ $ sudo ls -l /proc/3878/fd
> yhteensä 0
> lr-x-- 1 root root 64 loka  20 21:37 0 -> /dev/null
> lrwx-- 1 root root 64 loka  20 21:37 1 -> socket:[48975]
> lrwx-- 1 root root 64 loka  20 21:37 10 -> socket:[49006]
> lrwx-- 1 root root 64 loka  20 21:37 11 -> /dev/dvb/adapter0/demux0
> lrwx-- 1 root root 64 loka  20 21:37 12 -> /dev/dvb/adapter0/demux0
> lrwx-- 1 root root 64 loka  20 21:37 13 -> /dev/dvb/adapter0/demux0
> lrwx-- 1 root root 64 loka  20 21:37 14 -> /dev/dvb/adapter0/demux0
> lrwx-- 1 root root 64 loka  20 21:37 15 -> /dev/dvb/adapter0/demux0
> lrwx-- 1 root root 64 loka  20 21:37 16 -> /dev/dvb/adapter0/demux0
> lrwx-- 1 root root 64 loka  20 21:37 17 -> /dev/dvb/adapter0/demux0
> lrwx-- 1 root root 64 loka  20 21:37 18 -> /dev/dvb/adapter0/demux0
> lrwx-- 1 root root 64 loka  20 21:37 2 -> socket:[48975]
> lrwx-- 1 root root 64 loka  20 21:37 3 -> socket:[48980]
> lrwx-- 1 root root 64 loka  20 21:37 4 -> /dev/dvb/adapter0/frontend1
> lrwx-- 1 root root 64 loka  20 21:37 5 -> /dev/vchiq
> lrwx-- 1 root root 64 loka  20 21:37 6 -> socket:[49005]
> lrwx-- 1 root root 64 loka  20 21:37 7 -> /dev/dvb/adapter0/demux0
> lrwx-- 1 root root 64 loka  20 21:37 8 -> /dev/dvb/adapter0/demux0
> lr-x-- 1 root root 64 loka  20 21:37 9 -> /dev/dvb/adapter0/dvr0
> pi@raspberrypi:~ $ telnet localhost 6419
> Trying ::1...
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> 220 raspberrypi SVDRP VideoDiskRecorder 2.5.6; Wed Oct 20 21:40:00 2021; UTF-8
> hitk menu
> 250 Key "menu" accepted
> hitk 4
> 250 Key "4" accepted
> hitk red
> 250 Key "red" accepted
> hitk pause
> 250 Key "pause" accepted
> quit
> 221 raspberrypi closing connection
> Connection closed by foreign host.
> pi@raspberrypi:~ $ date
> ke 20.10.2021 21.40.45 +0300
> pi@raspberrypi:~ $ sudo ls -l /proc/3878/fd
> yhteensä 0
> lr-x-- 1 root root 64 loka  20 21:37 0 -> /dev/null
> lrwx-- 1 root root 

Re: [vdr] Making VDR run under Systemd

[Marko Mäkelä]

Mon, Oct 18, 2021 at 11:44:32PM +0300, glenvt18 wrote:

What is the output of

   lsof | grep frontend

when VDR is in the "idle" state?


I produced some output from /proc/$(pgrep vdr)/fd which I think might be 
more helpful. The last-but-one "ls" output was "too soon" after I 
started and paused the recording, so VDR was still in normal mode.


In case you wonder, the connection between lircd and vdr did not work 
last time I tried, and probably also not this time. That is why I used 
telnet to the SVDRP port.


The last "ls" command was when VDR was expected to be idle (after 
1-minute timeout, instead of the 15-minute timeout of your patch). I ran 
the command once more after a while, and the output remained identical.


Note that this USB DVB-T stick has two frontends for the same aerial 
connector. I think that one is for DVB-T and another for DVB-T2. You can 
see that "frontend1" was replaced with "frontend0" in the not-quite-idle 
mode.


I am happy to try a revised patch, and I can also use GDB ("thread apply 
all backtrace" and such) if that is needed.


This was the latest commit 0d50ec57f50375c8fda92d117e348dd8fd5a77a9 
("Version 2.5.6") from http://git.tvdr.de/vdr.git with only your patch 
on top (and the 15-minute timeout changed to 1 minute).


Best regards,

Marko

pi@raspberrypi:~ $ sudo service lircd start
pi@raspberrypi:~ $ pgrep lircd
3811
pi@raspberrypi:~ $ sudo ls -l /proc/3811/fd
yhteensä 0
lr-x-- 1 root root 64 loka  20 21:37 0 -> /dev/null
lrwx-- 1 root root 64 loka  20 21:37 1 -> socket:[47310]
lrwx-- 1 root root 64 loka  20 21:37 2 -> socket:[47310]
lrwx-- 1 root root 64 loka  20 21:37 3 -> socket:[49360]
lrwx-- 1 root root 64 loka  20 21:37 4 -> socket:[47311]
lrwx-- 1 root root 64 loka  20 21:37 5 -> /run/lirc/lircd.pid
lr-x-- 1 root root 64 loka  20 21:37 6 -> 
/sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.5/rc/rc0/protocols
lr-x-- 1 root root 64 loka  20 21:37 7 -> 
/sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.5/rc/rc0/protocols
pi@raspberrypi:~ $ sudo service vdr start
pi@raspberrypi:~ $ sudo lsof /dev/dvb/adapter0/*
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
vdr 3878  vdr7u   CHR  212,3  0t0 42703 /dev/dvb/adapter0/frontend0
pi@raspberrypi:~ $ sudo ls -l /proc/3878/fd
yhteensä 0
lr-x-- 1 root root 64 loka  20 21:37 0 -> /dev/null
lrwx-- 1 root root 64 loka  20 21:37 1 -> socket:[48975]
lrwx-- 1 root root 64 loka  20 21:37 10 -> socket:[49006]
lrwx-- 1 root root 64 loka  20 21:37 11 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 12 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 13 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 14 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 15 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 16 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 17 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 18 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 2 -> socket:[48975]
lrwx-- 1 root root 64 loka  20 21:37 3 -> socket:[48980]
lrwx-- 1 root root 64 loka  20 21:37 4 -> /dev/dvb/adapter0/frontend1
lrwx-- 1 root root 64 loka  20 21:37 5 -> /dev/vchiq
lrwx-- 1 root root 64 loka  20 21:37 6 -> socket:[49005]
lrwx-- 1 root root 64 loka  20 21:37 7 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 8 -> /dev/dvb/adapter0/demux0
lr-x-- 1 root root 64 loka  20 21:37 9 -> /dev/dvb/adapter0/dvr0
pi@raspberrypi:~ $ telnet localhost 6419
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 raspberrypi SVDRP VideoDiskRecorder 2.5.6; Wed Oct 20 21:40:00 2021; UTF-8
hitk menu
250 Key "menu" accepted
hitk 4
250 Key "4" accepted
hitk red
250 Key "red" accepted
hitk pause
250 Key "pause" accepted
quit
221 raspberrypi closing connection
Connection closed by foreign host.
pi@raspberrypi:~ $ date
ke 20.10.2021 21.40.45 +0300
pi@raspberrypi:~ $ sudo ls -l /proc/3878/fd
yhteensä 0
lr-x-- 1 root root 64 loka  20 21:37 0 -> /dev/null
lrwx-- 1 root root 64 loka  20 21:37 1 -> socket:[48975]
lrwx-- 1 root root 64 loka  20 21:37 10 -> socket:[49006]
lrwx-- 1 root root 64 loka  20 21:37 13 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 14 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 15 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 16 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 17 -> /dev/dvb/adapter0/demux0
lrwx-- 1 root root 64 loka  20 21:37 2 -> socket:[48975]
lrwx-- 1 root root 64 loka  20 21:37 3 -> socket:[48980]
lrwx-- 1 root root 64 loka  20 21:37 4 -> /dev/dvb/adapter0/frontend1
lrwx-- 1 root root 64 loka  20 21:37 5 -> /dev/vchiq
lrwx-- 1 root root 64 loka  20 21:37 6 -> socket:[49005]
lr-x-- 1 root 

Re: [vdr] Making VDR run under Systemd

[glenvt18]

What is the output of

lsof | grep frontend

when VDR is in the "idle" state?

On Sun, Oct 17, 2021 at 10:52:11PM +0300, Marko Mäkelä wrote:
> Tue, Oct 12, 2021 at 07:21:10PM +0300, glenvt18 wrote:
> > Here you can find an updated version of the patch:
> > https://github.com/glenvt18/vdr/commits/vdr-2.4.6
> 
> Thank you. I just conducted some tests with my uncalibrated Agilent power
> supply. The USB cable of such low quality that the Raspberry Pi complained
> several times about undervoltage.
> 
> I measured the following current draw at 5 volts, in ascending order:
> 
> 81 mA: Raspberry Pi 2B shut down
> 200 mA: Raspberry Pi 2B powered up, no Ethernet plugged in
> 240 mA: Ethernet cable plugged in (HDMI cable makes no difference)
> 320 mA: Ethernet + USB DVB stick plugged in
> 440 mA: compiling VDR with "make -j4" (all CPU cores busy)
> 550 mA: VDR playing back a recording
> 530 mA: recording paused in VDR
> 510 mA: EPG scan running
> 600 mA: VDR displaying live DVB-T2
> 
> https://github.com/glenvt18/vdr/commit/b368f67d00d0b466ae36028efb9336e81f77dba8
> applied cleanly on the latest VDR source. I changed the PowerdownTimeoutM
> from 15 to 1 minute to speed up my testing.
> 
> The patch only had a minimal impact. After 1 or 2 minutes of the playback of
> a recording being paused, the power consumption dropped from 530 mA to 500
> mA.
> 
> I noticed that VDR is consuming about 5% of the CPU power according to
> "top". Could it not be made more event-based? It might be interesting to
> check with "powertop" how many wakeups per second there are, and with "perf
> record" and "perf replay" (or simply "perf top") where the CPU cycles are
> being spent when the playback of a recording is paused.
> 
> The bulk of the the power consumption ought to be caused by the USB DVB
> stick not being in fully idle state. After all, utilizing all 4 CPU cores
> during the "make -j4" minutes showed a pretty stable power consumption of
> 440 mA for several minutes, which is much less than when the VDR process was
> running.
> 
> Here is a summary of the power consumption measured at 5 volts.
> 
> 1.2 W (240 mA)  mostly idle Raspberry Pi 2B (Ethernet plugged in)
> 1.6 W (320 mA)  USB DVB stick plugged in, VDR not running
> 2.5 W (500 mA)  lowest power consumption achieved with VDR
> 3.0 W (600 mA)  VDR displaying live TV
> 
> My conclusion is that I will configure udev so that VDR will automatically
> start up or shut down when the USB stick is plugged in or removed. In that
> way, the power consumption of the system will only be more than doubled when
> VDR is actually in use.
> 
> I am planning to install the most recent Raspberry Pi and to document the
> minimal changes on top of that.
> 
> Best regards,
> 
>   Marko
> 
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

-- 
glenvt18

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Making VDR run under Systemd

[Marko Mäkelä]

Tue, Oct 12, 2021 at 07:21:10PM +0300, glenvt18 wrote:

Here you can find an updated version of the patch:
https://github.com/glenvt18/vdr/commits/vdr-2.4.6


Thank you. I just conducted some tests with my uncalibrated Agilent 
power supply. The USB cable of such low quality that the Raspberry Pi 
complained several times about undervoltage.


I measured the following current draw at 5 volts, in ascending order:

81 mA: Raspberry Pi 2B shut down
200 mA: Raspberry Pi 2B powered up, no Ethernet plugged in
240 mA: Ethernet cable plugged in (HDMI cable makes no difference)
320 mA: Ethernet + USB DVB stick plugged in
440 mA: compiling VDR with "make -j4" (all CPU cores busy)
550 mA: VDR playing back a recording
530 mA: recording paused in VDR
510 mA: EPG scan running
600 mA: VDR displaying live DVB-T2

https://github.com/glenvt18/vdr/commit/b368f67d00d0b466ae36028efb9336e81f77dba8
applied cleanly on the latest VDR source. I changed the PowerdownTimeoutM
from 15 to 1 minute to speed up my testing.

The patch only had a minimal impact. After 1 or 2 minutes of the 
playback of a recording being paused, the power consumption dropped from 
530 mA to 500 mA.


I noticed that VDR is consuming about 5% of the CPU power according to 
"top". Could it not be made more event-based? It might be interesting to 
check with "powertop" how many wakeups per second there are, and with 
"perf record" and "perf replay" (or simply "perf top") where the CPU 
cycles are being spent when the playback of a recording is paused.


The bulk of the the power consumption ought to be caused by the USB DVB 
stick not being in fully idle state. After all, utilizing all 4 CPU 
cores during the "make -j4" minutes showed a pretty stable power 
consumption of 440 mA for several minutes, which is much less than when 
the VDR process was running.


Here is a summary of the power consumption measured at 5 volts.

1.2 W (240 mA)  mostly idle Raspberry Pi 2B (Ethernet plugged in)
1.6 W (320 mA)  USB DVB stick plugged in, VDR not running
2.5 W (500 mA)  lowest power consumption achieved with VDR
3.0 W (600 mA)  VDR displaying live TV

My conclusion is that I will configure udev so that VDR will 
automatically start up or shut down when the USB stick is plugged in or 
removed. In that way, the power consumption of the system will only be 
more than doubled when VDR is actually in use.


I am planning to install the most recent Raspberry Pi and to document 
the minimal changes on top of that.


Best regards,

Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Making VDR run under Systemd

[Marko Mäkelä]

Mon, Oct 11, 2021 at 04:02:43PM +0100, Richard F wrote:

Powersaving for DVB receivers - try the attached patch from glenvt18


Thank you. I will test it later once I have hooked up the Raspberry Pi 
to my laboratory power supply so that I can observe the total power 
consumption.


While "uhubctl -a off" would cause an optimal mouse to power off its 
LED, it will not completely cut the power. I tested this by plugging in 
a mobile phone to the USB port. It indicated that charging is available.


One impact of "uhubctl -a off" is that any plug/unplug events for the 
affected ports will be disabled, and "lsusb" will reflect the state as 
it was before the invocation.


I just confirmed with a laboratory power supply that my USB DVB-T/T2/C 
stick is consuming 61 mA at 5 volts. If I remember correctly, USB 
devices are allowed to drain up to 100 mA without any negotiation, so it 
should not be out-of-spec. Those additional 0.35 watts should be a 
significant portion of the total power consumption. I did not measure 
yet, but I hope it to be in the range of 2 to 3 watts.


For my use case, I think that I will only configure udev events for 
inserting or removing the stick. No shutdown command would be configured 
in VDR. I would abruptly shut down VDR and lircd by unplugging the 
adapter. They would observe the abrupt loss of DVB hardware, followed by 
a terminating signal sent by systemd or udevd.


Best regards,

Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Making VDR run under Systemd

[glenvt18]

Hi.

Here you can find an updated version of the patch:
https://github.com/glenvt18/vdr/commits/vdr-2.4.6

On Mon, Oct 11, 2021 at 04:02:43PM +0100, Richard F wrote:
> Mon, Sep 13, 2021 at 08:51:05PM +0200, Martin Wache wrote:
> > So, back to the plan with the Raspberry Pi 2B. One problem that I wanted
> > to solve is the power consumption of the DVB-T dongle when it is not in
> > use. I found https://github.com/mvp/uhubctl which can switch off power
> > on individual USB ports. I wrote a VDR shutdown script that does the
> > following:
> > 
> > sudo service lircd stop
> > uhubctl -p ... -a off
> > sudo service vdr stop
> > 
> > I did not refine the uhubctl invocation yet. The physical port could
> > vary.
> > 
> > An easy way to start up VDR could be a udev rule that would start up the
> > lircd and vdr services when the USB DVB stick is plugged in. Obviously,
> > if we power off the port during VDR shutdown, the adapter would have to
> > be plugged into a different port.
> > 
> > A simpler option for the occasional use of VDR might be to simply write
> > udev rules that will start up lircd and vdr when the DVB adapter is
> > plugged in, and shut down the services when the adapter is removed. 
> > That would be too risky if recording timers are being used.
> > 
> > I am not yet sure whether powering off the USB port makes any
> > difference, because the plastic case of the DVB stick feels slightly
> > warm to the touch even when the port is supposedly powered off. It might
> > be that some internal heat produced by the Rasberry is being dissipated
> > via the USB port. The metal frame of the USB jacks feels a bit warm too.
> > 
> > I think that I must measure the input power of the Raspberry Pi as well
> > as the voltage on the USB port when it is supposedly powered off.
> > 
> > Marko
> 
> Powersaving for DVB receivers - try the attached patch from glenvt18
> 
> 
> This has worked for me for a few years without noticeable problems on both
> USB and PCI cards.  I'm still on V2.20 by the way.  There's a little bit of
> log chatter as it powers up/down receivers when VDR scans the EPG etc, but
> you can filter that   I reckoned it saved around 3W at the mains for a
> 2-receiver server setup when I tested it back in 2016 - which adds up over
> time.
> 
> usbhubctl is a bit of a sledgehammer !
> 
> HTH
> 
> Richard
> 

> From 656cce97750882fd945d9ba76c47cb93a74c3059 Mon Sep 17 00:00:00 2001
> From: glenvt18 
> Date: Tue, 24 May 2016 00:39:01 +0300
> Subject: [PATCH] Device power saving feature
> 
> ---
>  config.c|  9 ++
>  config.h|  3 ++
>  device.c| 96 
> +++--
>  device.h| 29 +++
>  dvbdevice.c | 39 +
>  dvbdevice.h |  7 +
>  eitscan.c   |  7 -
>  menu.c  |  9 +-
>  vdr.c   |  6 
>  9 files changed, 201 insertions(+), 4 deletions(-)
> 
> diff --git a/config.c b/config.c
> index 9c6b71e..e196353 100644
> --- a/config.c
> +++ b/config.c
> @@ -395,6 +395,9 @@ cSetup::cSetup(void)
>PositionerSpeed = 15;
>PositionerSwing = 650;
>PositionerLastLon = 0;
> +  PowerdownEnabled = 0;
> +  PowerdownTimeoutM = 15;
> +  PowerdownWakeupH = 4;
>SetSystemTime = 0;
>TimeSource = 0;
>TimeTransponder = 0;
> @@ -617,6 +620,9 @@ bool cSetup::Parse(const char *Name, const char *Value)
>else if (!strcasecmp(Name, "PositionerSpeed")) PositionerSpeed= 
> atoi(Value);
>else if (!strcasecmp(Name, "PositionerSwing")) PositionerSwing= 
> atoi(Value);
>else if (!strcasecmp(Name, "PositionerLastLon"))   PositionerLastLon  = 
> atoi(Value);
> +  else if (!strcasecmp(Name, "PowerdownEnabled"))PowerdownEnabled   = 
> atoi(Value);
> +  else if (!strcasecmp(Name, "PowerdownTimeoutM"))   PowerdownTimeoutM  = 
> atoi(Value);
> +  else if (!strcasecmp(Name, "PowerdownWakeupH"))PowerdownWakeupH   = 
> atoi(Value);
>else if (!strcasecmp(Name, "SetSystemTime"))   SetSystemTime  = 
> atoi(Value);
>else if (!strcasecmp(Name, "TimeSource"))  TimeSource = 
> cSource::FromString(Value);
>else if (!strcasecmp(Name, "TimeTransponder")) TimeTransponder= 
> atoi(Value);
> @@ -743,6 +749,9 @@ bool cSetup::Save(void)
>Store("PositionerSpeed",PositionerSpeed);
>Store("PositionerSwing",PositionerSwing);
>Store("PositionerLastLon",  PositionerLastLon);
> +  Store("PowerdownEnabled",   PowerdownEnabled);
> +  Store("PowerdownTimeoutM",  PowerdownTimeoutM);
> +  Store("PowerdownWakeupH",   PowerdownWakeupH);
>Store("SetSystemTime",  SetSystemTime);
>Store("TimeSource", cSource::ToString(TimeSource));
>Store("TimeTransponder",TimeTransponder);
> diff --git a/config.h b/config.h
> index d1bae04..dbe84bb 100644
> --- a/config.h
> +++ b/config.h
> @@ -273,6 +273,9 @@ public:
>int PositionerSpeed;
>int PositionerSwing;
>int PositionerLastLon;
> +  int 

Re: [vdr] Making VDR run under Systemd

[Richard F]

Mon, Sep 13, 2021 at 08:51:05PM +0200, Martin Wache wrote:
So, back to the plan with the Raspberry Pi 2B. One problem that I 
wanted to solve is the power consumption of the DVB-T dongle when it 
is not in use. I found https://github.com/mvp/uhubctl which can switch 
off power on individual USB ports. I wrote a VDR shutdown script that 
does the following:


sudo service lircd stop
uhubctl -p ... -a off
sudo service vdr stop

I did not refine the uhubctl invocation yet. The physical port could 
vary.


An easy way to start up VDR could be a udev rule that would start up 
the lircd and vdr services when the USB DVB stick is plugged in. 
Obviously, if we power off the port during VDR shutdown, the adapter 
would have to be plugged into a different port.


A simpler option for the occasional use of VDR might be to simply 
write udev rules that will start up lircd and vdr when the DVB adapter 
is plugged in, and shut down the services when the adapter is 
removed.  That would be too risky if recording timers are being used.


I am not yet sure whether powering off the USB port makes any 
difference, because the plastic case of the DVB stick feels slightly 
warm to the touch even when the port is supposedly powered off. It 
might be that some internal heat produced by the Rasberry is being 
dissipated via the USB port. The metal frame of the USB jacks feels a 
bit warm too.


I think that I must measure the input power of the Raspberry Pi as 
well as the voltage on the USB port when it is supposedly powered off.


Marko


Powersaving for DVB receivers - try the attached patch from glenvt18 



This has worked for me for a few years without noticeable problems on 
both USB and PCI cards.  I'm still on V2.20 by the way.  There's a 
little bit of log chatter as it powers up/down receivers when VDR scans 
the EPG etc, but you can filter that   I reckoned it saved around 3W at 
the mains for a 2-receiver server setup when I tested it back in 2016 - 
which adds up over time.


usbhubctl is a bit of a sledgehammer !

HTH

Richard

>From 656cce97750882fd945d9ba76c47cb93a74c3059 Mon Sep 17 00:00:00 2001
From: glenvt18 
Date: Tue, 24 May 2016 00:39:01 +0300
Subject: [PATCH] Device power saving feature

---
 config.c|  9 ++
 config.h|  3 ++
 device.c| 96 +++--
 device.h| 29 +++
 dvbdevice.c | 39 +
 dvbdevice.h |  7 +
 eitscan.c   |  7 -
 menu.c  |  9 +-
 vdr.c   |  6 
 9 files changed, 201 insertions(+), 4 deletions(-)

diff --git a/config.c b/config.c
index 9c6b71e..e196353 100644
--- a/config.c
+++ b/config.c
@@ -395,6 +395,9 @@ cSetup::cSetup(void)
   PositionerSpeed = 15;
   PositionerSwing = 650;
   PositionerLastLon = 0;
+  PowerdownEnabled = 0;
+  PowerdownTimeoutM = 15;
+  PowerdownWakeupH = 4;
   SetSystemTime = 0;
   TimeSource = 0;
   TimeTransponder = 0;
@@ -617,6 +620,9 @@ bool cSetup::Parse(const char *Name, const char *Value)
   else if (!strcasecmp(Name, "PositionerSpeed")) PositionerSpeed= 
atoi(Value);
   else if (!strcasecmp(Name, "PositionerSwing")) PositionerSwing= 
atoi(Value);
   else if (!strcasecmp(Name, "PositionerLastLon"))   PositionerLastLon  = 
atoi(Value);
+  else if (!strcasecmp(Name, "PowerdownEnabled"))PowerdownEnabled   = 
atoi(Value);
+  else if (!strcasecmp(Name, "PowerdownTimeoutM"))   PowerdownTimeoutM  = 
atoi(Value);
+  else if (!strcasecmp(Name, "PowerdownWakeupH"))PowerdownWakeupH   = 
atoi(Value);
   else if (!strcasecmp(Name, "SetSystemTime"))   SetSystemTime  = 
atoi(Value);
   else if (!strcasecmp(Name, "TimeSource"))  TimeSource = 
cSource::FromString(Value);
   else if (!strcasecmp(Name, "TimeTransponder")) TimeTransponder= 
atoi(Value);
@@ -743,6 +749,9 @@ bool cSetup::Save(void)
   Store("PositionerSpeed",PositionerSpeed);
   Store("PositionerSwing",PositionerSwing);
   Store("PositionerLastLon",  PositionerLastLon);
+  Store("PowerdownEnabled",   PowerdownEnabled);
+  Store("PowerdownTimeoutM",  PowerdownTimeoutM);
+  Store("PowerdownWakeupH",   PowerdownWakeupH);
   Store("SetSystemTime",  SetSystemTime);
   Store("TimeSource", cSource::ToString(TimeSource));
   Store("TimeTransponder",TimeTransponder);
diff --git a/config.h b/config.h
index d1bae04..dbe84bb 100644
--- a/config.h
+++ b/config.h
@@ -273,6 +273,9 @@ public:
   int PositionerSpeed;
   int PositionerSwing;
   int PositionerLastLon;
+  int PowerdownEnabled;
+  int PowerdownTimeoutM;
+  int PowerdownWakeupH;
   int SetSystemTime;
   int TimeSource;
   int TimeTransponder;
diff --git a/device.c b/device.c
index 4db7cc2..1c29677 100644
--- a/device.c
+++ b/device.c
@@ -104,6 +104,9 @@ cDevice::cDevice(void)
   dvbSubtitleConverter = NULL;
   autoSelectPreferredSubtitleLanguage = true;
 
+  idleTimerExpires = time(NULL) + Setup.PowerdownTimeoutM * 60;
+  wakeupTimerExpires = 0;
+
   for 

Re: [vdr] Making VDR run under Systemd

[Marko Mäkelä]

Hi all, hi Martin!

Mon, Sep 13, 2021 at 08:51:05PM +0200, Martin Wache wrote:

Yes good times! :-)


I think that softdevice (without HD in the name) was quite an 
achievement for the hardware that was available about 20 years ago.


Today, I made a little progress on this. First, I was thinking to set up 
an unused IBM Thinkpad X60 for VDR. In the end, I found out that 
softhddevice depends on a number of X11 libraries.


I also found some forum posts that suggested that it is not expected to 
work with Wayland. If I understood correctly, Wayland helps reduce the 
CPU overhead, as long as there is some GPU support for compositing RGBA 
buffers, and it could simplify the rendering path.


In the end, I decided that one 32-bit CPU core (2 with hyperthreading) 
and a 1024×768 screen panel would likely not be a good match for HDTV.


So, back to the plan with the Raspberry Pi 2B. One problem that I wanted 
to solve is the power consumption of the DVB-T dongle when it is not in 
use. I found https://github.com/mvp/uhubctl which can switch off power 
on individual USB ports. I wrote a VDR shutdown script that does the 
following:


sudo service lircd stop
uhubctl -p ... -a off
sudo service vdr stop

I did not refine the uhubctl invocation yet. The physical port could 
vary.


An easy way to start up VDR could be a udev rule that would start up the 
lircd and vdr services when the USB DVB stick is plugged in. Obviously, 
if we power off the port during VDR shutdown, the adapter would have to 
be plugged into a different port.


A simpler option for the occasional use of VDR might be to simply write 
udev rules that will start up lircd and vdr when the DVB adapter is 
plugged in, and shut down the services when the adapter is removed.  
That would be too risky if recording timers are being used.


I am not yet sure whether powering off the USB port makes any 
difference, because the plastic case of the DVB stick feels slightly 
warm to the touch even when the port is supposedly powered off. It might 
be that some internal heat produced by the Rasberry is being dissipated 
via the USB port. The metal frame of the USB jacks feels a bit warm too.


I think that I must measure the input power of the Raspberry Pi as well 
as the voltage on the USB port when it is supposedly powered off.


Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Making VDR run under Systemd

[Martin Wache]

Hi all, hi Marko!

Am 12.09.21 um 11:46 schrieb Marko Mäkelä:

I was an active VDR user from about 2004 to 2010


Yes good times! :-)

Actually I still use the VDR excatly for the same reasons: to record
shows for my kids.


If my Raspberry Pi were not an "always-on server" that runs some other
services as well, I might want to reimplement the "wake-on-RCU" hardware
that is generating a wake-on-LAN signal via the Nova-T PCI card,
possibly by extending
https://spellfoundry.com/product/sleepy-pi-2-usb-c/ or a similar product
that would implement a wake-on-timer for the Raspberry Pi. Then, the
system would power up nicely either by RCU or by a recording timer.
Integrating the wake-on-timer logic with Systemd could be another
challenge. I might try this on PC hardware, which already supports
wake-on-timer out of the box. A quick search turned up a promising
starting point:
https://www.freedesktop.org/software/systemd/man/systemd.timer.html

The motivation of this exercise is to have a stand-alone VDR front/back
end installation that plays nicely with Systemd, without reinventing any
logic around scheduling, startup, and shutdown.


I currently don't use systemd, but I have a similar use case for my
server. I agree that a solution with systemd would be nicer, but a few
years back, I didn't get systemd to work with vdr the way I liked.

So I've created a python script which starts vdr, and if vdr stops it
captures the next time vdr requests to be run. Then it kills vdr,
unloads the dvb drivers (which also switches of the LNBs) and opens all
the network ports vdr is using.

A second script runs every 5 minutes or so and checks if vdr is running,
a user is logged in, or some other services have been recently used.
If not it suspends the server and sets the wake-up time to vdr requested
time. So the server wakes up ahead of a recording.

The python script checks if the start time requested by vdr is close,
and starts vdr a few minutes before the requested time.

If I need the server or vdr I just send a wol packet. When I access the
vdr and the python script is running instead of the vdr, the python
script closes all network ports, loads the dvb drivers and starts the vdr.
This even worked very nicely with kodi, but I stopped using kodi, I
don't like the user interface. Now I use vdr-xineliboutput. I have to
start vdr-xineliboutput several times until the vdr is started, but I
don't mind :-).

Using this setup I can use the server for many more services, and don't
waste power when I don't need the vdr.

This was partly inspired by systemd, but I think it is still not
possible to implement this with systemd.

I can share the scripts if you like to modify them for your needs.


Regards,

Martin

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Making VDR run under Systemd

[Marko Mäkelä]

Mon, Sep 13, 2021 at 10:57:23AM +0200, g.bruno wrote:

Hallo,

the problem for the shutdown bottom "no -s option" (not parameter) is 
in /etc/vdr/config.d/00-vdr.conf

where the line 21 concerning shutdown is commented out:

#--shutdown=/usr/lib/vdr/vdr-shutdown.wrapper


Thank you, but it is not that simple in case VDR is not the main use of 
the system.  What I would want to achieve is some kind of a "wake lock" 
(borrowing Android terminology): the system would shut down 
automatically after some timeout, unless a service prevents it from 
shutting down. VDR would be only one such service. There could other 
reasons that prevent a shutdown, say, a user being logged in, or a file 
server running or being actively used.


I would want VDR to release most resources (and stop consuming 5% of CPU 
time and a larger chunk of the 1GiB RAM) when I press the Power button 
on the RCU. If I press the button again, VDR should wake up. Maybe this 
can be achieved with a "shutdown" program that would not actually shut 
anything down, but wait for another Power button press to possibly start 
up VDR.


Another feature that I might want is that when I plug in the DVB-T2 
stick into the computer, VDR will start up. That is, the main purpose of 
the computer could be something else, and the computer would switch to 
"appliance mode" only when needed. Likewise, the USB stick would only 
consume power and expose the system to lighting (via the antenna mast) 
when needed (when someone wants to watch or record something with VDR).  
That I believe is achievable with udev rules. Maybe the whole should 
then be driven via udevd and not systemd.


When time permits, I will try to experiment more.

Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Making VDR run under Systemd

[g.bruno]

Hallo,

the problem for the shutdown bottom "no -s option" (not parameter) is in 
/etc/vdr/config.d/00-vdr.conf

where the line 21 concerning shutdown is commented out:

#--shutdown=/usr/lib/vdr/vdr-shutdown.wrapper

I uncommented it and it worked for me with the power-off-buttom on the 
remote control. Perhaps this will help you.


VDR 2.4.2 on linux mate 20.4

Regards

gbruno

Am 12.09.21 um 11:46 schrieb Marko Mäkelä:

Hi all,

I was an active VDR user from about 2004 to 2010 when my children were 
younger and there was a need to record TV programs for them. The old 
setup was more or less abandoned when I got a smart TV and the family 
started to use video streaming services.


Some years ago, I got a Raspberry Pi 2 B and an Astrometa DVB-T2 USB 
stick that also includes an infrared receiver. Because its bundled 
remote control unit (RCU) has much fewer buttons than the one that I got 
with the Hauppauge Nova-T PCI 90002 years ago, I configured lircd to 
translate the RC5 codes from the old RCU. For output, I am using 
rpihddevice.


Yesterday, I upgraded to VDR 2.5.6 and rpihddevice 1.0.4 from 
git://projects.vdr-developer.org/vdr-plugin-rpihddevice.git while 
keeping the rest of the Raspbian 9.13 mostly intact.


I installed the self-built software simply by replacing the original 
/usr/bin/vdr that was part of the distribution's vdr 2.2.0 package, and 
copying the plugin to /usr/lib/vdr/plugins/. It might not be the 
cleanest solution, but it worked for me.


I had some trouble with Systemd, which I resolved by creating a 
configuration file:


# cat > /etc/systemd/system/vdr.service << EOF
[Service]
Restart=on-failure
RestartSec=1s
ExecStart=/usr/bin/vdr
TimeoutStartSec=infinity
EOF
# systemctl daemon-reload
# service lightdm stop
# service vdr start

I did not double-check it, but I understood that this could entirely 
bypass the /etc/init.d/vdr script, which would invoke the runvdr script 
(which normally runs vdr in a loop). If I choose Restart from the VDR 
menu, systemd will restart it nicely.


I did not configure the Power button yet. Currently, VDR complains that 
no -s parameter is given when I press the Power button on the RCU. 
Ideally, I think that VDR should suspend the live video output and 
somehow inform Systemd that the entire system may be suspended, as far 
as VDR is concerned. (Of course, only if there are no recordings or 
remote connections active to VDR.) Then, if nothing else prevents the 
system from being shut down or suspended, Systemd would do it based on 
its configuration.


Years ago, I developed some patches and configuration at 
https://iki.fi/msmakela/software/vdr/ to achieve something like this on 
my old system, and I would now like to revive this somehow. Ideally, the 
Power button would shut down the DVB receiver and display some 
indication on the OSD or the video frame buffer that the output has been 
suspended.


If my Raspberry Pi were not an "always-on server" that runs some other 
services as well, I might want to reimplement the "wake-on-RCU" hardware 
that is generating a wake-on-LAN signal via the Nova-T PCI card, 
possibly by extending 
https://spellfoundry.com/product/sleepy-pi-2-usb-c/ or a similar product 
that would implement a wake-on-timer for the Raspberry Pi. Then, the 
system would power up nicely either by RCU or by a recording timer.
Integrating the wake-on-timer logic with Systemd could be another 
challenge. I might try this on PC hardware, which already supports 
wake-on-timer out of the box. A quick search turned up a promising 
starting point:

https://www.freedesktop.org/software/systemd/man/systemd.timer.html

The motivation of this exercise is to have a stand-alone VDR front/back 
end installation that plays nicely with Systemd, without reinventing any 
logic around scheduling, startup, and shutdown.


Maybe one day, once some more progress has been made with Wayland and 
when using a Raspberry Pi model with more GPU memory, one could press 
the Power button on the RCU and have the live TV pop up either 
fullscreen or in a window, on top of the graphical desktop (which would 
be available for generic use).


Best regards,

 Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Making VDR run under Systemd

[Marko Mäkelä]

Hi all,

I was an active VDR user from about 2004 to 2010 when my children were 
younger and there was a need to record TV programs for them. The old 
setup was more or less abandoned when I got a smart TV and the family 
started to use video streaming services.


Some years ago, I got a Raspberry Pi 2 B and an Astrometa DVB-T2 USB 
stick that also includes an infrared receiver. Because its bundled 
remote control unit (RCU) has much fewer buttons than the one that I got 
with the Hauppauge Nova-T PCI 90002 years ago, I configured lircd to 
translate the RC5 codes from the old RCU. For output, I am using 
rpihddevice.


Yesterday, I upgraded to VDR 2.5.6 and rpihddevice 1.0.4 from 
git://projects.vdr-developer.org/vdr-plugin-rpihddevice.git while 
keeping the rest of the Raspbian 9.13 mostly intact.


I installed the self-built software simply by replacing the original 
/usr/bin/vdr that was part of the distribution's vdr 2.2.0 package, and 
copying the plugin to /usr/lib/vdr/plugins/. It might not be the 
cleanest solution, but it worked for me.


I had some trouble with Systemd, which I resolved by creating a 
configuration file:


# cat > /etc/systemd/system/vdr.service << EOF
[Service]
Restart=on-failure
RestartSec=1s
ExecStart=/usr/bin/vdr
TimeoutStartSec=infinity
EOF
# systemctl daemon-reload
# service lightdm stop
# service vdr start

I did not double-check it, but I understood that this could entirely 
bypass the /etc/init.d/vdr script, which would invoke the runvdr script 
(which normally runs vdr in a loop). If I choose Restart from the VDR 
menu, systemd will restart it nicely.


I did not configure the Power button yet. Currently, VDR complains that 
no -s parameter is given when I press the Power button on the RCU.  
Ideally, I think that VDR should suspend the live video output and 
somehow inform Systemd that the entire system may be suspended, as far 
as VDR is concerned. (Of course, only if there are no recordings or 
remote connections active to VDR.) Then, if nothing else prevents the 
system from being shut down or suspended, Systemd would do it based on 
its configuration.


Years ago, I developed some patches and configuration at 
https://iki.fi/msmakela/software/vdr/ to achieve something like this on 
my old system, and I would now like to revive this somehow. Ideally, the 
Power button would shut down the DVB receiver and display some 
indication on the OSD or the video frame buffer that the output has been 
suspended.


If my Raspberry Pi were not an "always-on server" that runs some other 
services as well, I might want to reimplement the "wake-on-RCU" hardware 
that is generating a wake-on-LAN signal via the Nova-T PCI card, 
possibly by extending 
https://spellfoundry.com/product/sleepy-pi-2-usb-c/ or a similar product 
that would implement a wake-on-timer for the Raspberry Pi. Then, the 
system would power up nicely either by RCU or by a recording timer.  

Integrating the wake-on-timer logic with Systemd could be another 
challenge. I might try this on PC hardware, which already supports 
wake-on-timer out of the box. A quick search turned up a promising 
starting point:

https://www.freedesktop.org/software/systemd/man/systemd.timer.html

The motivation of this exercise is to have a stand-alone VDR front/back 
end installation that plays nicely with Systemd, without reinventing any 
logic around scheduling, startup, and shutdown.


Maybe one day, once some more progress has been made with Wayland and 
when using a Raspberry Pi model with more GPU memory, one could press 
the Power button on the RCU and have the live TV pop up either 
fullscreen or in a window, on top of the graphical desktop (which would 
be available for generic use).


Best regards,

Marko

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

__
I'm using this dedicated address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 29/11/20 a les 14:11, Helmut Binder ha escrit:
>> $ ls -la /dev/dvb/adapter0/
>> total 0
>> drwxr-xr-x  2 root root  140 de nov.  28 15:57 .
>> drwxr-xr-x  3 root root   60 de nov.  28 15:57 ..
>> crw-rw+ 1 root video 212,  4 de nov.  28 15:57 demux0
>> crw-rw+ 1 root video 212,  5 de nov.  28 15:57 dvr0
>> crw-rw+ 1 root video 212,  3 de nov.  28 15:57 frontend0
>> crw-rw+ 1 root video 212, 19 de nov.  28 15:57 frontend1
>> crw-rw+ 1 root video 212,  7 de nov.  28 15:57 net0
>>
> This is a multi-frontend device. You need VDR-2.4.1 or newer - or at least 
> this patch from here:
> https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi-frontend-devices/=1308966#post1308966

I've just tried same device with Ubuntu 20.10 (it has VDR 2.4.1 on
repositories)
This is not fixed in this version.
I had to do the frontend0 <-> frontend1 workaround to have it working
(channels scan must be done without frontends swap). And no EPG.
Same results as with Raspbian 10


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] [ANNOUNCE] VDR version 2.4.6 released

[Klaus Schmidinger]

VDR version 2.4.6 is now available at

  ftp://ftp.tvdr.de/vdr/vdr-2.4.6.tar.bz2

A 'diff' against the previous version is available at

  ftp://ftp.tvdr.de/vdr/Developer/vdr-2.4.4-2.4.6.diff

MD5 checksums:

aa91614159ae2db45655d35918e2c24e  vdr-2.4.6.tar.bz2
b75cc737a5ea5fc059c2264b7ed21fa9  vdr-2.4.4-2.4.6.diff

You can also get the latest stable version at the official VDR GIT archive with

  git clone --branch stable/2.4 git://git.tvdr.de/vdr.git

This version fixes a few bugs that came up after the release of version 2.4.4.


The changes since version 2.4.4:

- Updated the Italian OSD texts (thanks to Diego Pierotto).
- Fixed handling newline characters in ci.c's CopyString() (reported by 
Winfried Köhler).
- Fixed checking the return value of the Open() call in cFileName::SetOffset() 
(reported
  by Winfried Köhler).
- Fixed a possible invalid lock sequence in cMenuTimers::OnOff().
- Fixed several typos (reported by Jens Schleusener).
- Implemented anti-aliasing for cPixmap::DrawSlope() and cPixmap::DrawEllipse() 
(thanks
  to Christoph Haubrich).
  The version numbers (both VDRVERSNUM and APIVERSNUM) have been bumped to 
2.4.5 to
  indicate this change.
- Fixed alignment of semi-circles in case of odd sizes.
- Increased the size of the TS buffer to 16MB, to have more reserve when 
recording
  several HD programmes.
- Added checking the symbol rate to cDvbTuner::IsTunedTo(), which apparently 
got lost
  in version 1.7.13 (thanks to Helmut Binder).
- Now checking for an empty command in cDvbTuner::GetSignalStats() to avoid a 
possible
  error message (thanks to Helmut Binder).
- Now initializing the status variable in cDvbTuner::GetFrontendStatus() and
  cDvbTuner::GetSignalStats() to avoid problems with drivers that don't do this
  (thanks to Helmut Binder).
- Fixed multiple recording entries in case a recording is started during the 
initial
  reading of the video directory (reported by Claus Muus).
- Fixed an unnecessary double call to Display() in 
cMenuRecording::RefreshRecording()
  (reported by Christoph Haubrich).
- Fixed a crash in case an error occurs when setting a remote timer.
- Fixed allocating memory for cImage (reported by Christoph Haubrich).
- Fixed parsing the '-l' command line option (reported by Harald Milz).
- Fixed possible compilation errors with libjpeg (thanks to Bernd Kuhls).
- Fixed "read incomplete section" errors (thanks to Helmut Binder).
- Fixed generating the HashId in cEIT::cEIT() (thanks to Helmut Binder).
- Added initialization of cDvbFrontend::frontendInfo (thanks to Winfried 
Köhler).
- Fixed a bug in handling shared PMTs, where after the first pass not all SIDs 
of a
  PMT pid were checked any more (thanks to Helmut Binder).
- Fixed PMT handling in case locking the Channels list times out (reported by 
Helmut
  Binder).
- Avoiding a lengthy lock on the Channels list when starting a recording 
(thanks to
  Helmut Binder).
- Fixed error handling when loading a plugin (reported by Markus Ehrnsperger).
- Improved handling missing VDRPluginDestroyer() (thanks to Winfried Köhler).
- Fixed initializing tmpbuf in ExtendedEventDescriptors::getText() (thanks to 
Helmut
  Binder).
- Fixed a compiler warning (thanks to Winfried Köhler).
- Fixed convertCharacterTable() in case iconv_open() fails (thanks to Helmut 
Binder).
- Official release.

Have fun!

Klaus

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

El 29/11/20 a les 22:13, Helmut Binder ha escrit:
> 
> Can you receive any DVB-T2 Channels ? These would use frontend 0/1 with the 
> CXD2837ER demodulator and you could compare the tuning.
> If not, rename frontend1 to frontend0, similar as in Timo's proposal:
> 
> - stop vdr
>  > mv /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/Xfrontend0"
>  > mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0"
> - start vdr
> 
> Helmut
> 

Tried this workaround several times, and last one resulted but in this
order:

1. Tuned channels with devices/frontends "as is"
2. moved frontend1 to frontend0

I'm pending to do more testing and be sure this is the point for my case.

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

A simplified alternative to w_scan2:

https://github.com/mighty-p/t2scan/


Narcis Garcia

El 1/12/20 a les 8:50, Narcis Garcia ha escrit:
> The project sources repository (sadly in a proprietary platform):
> 
> https://github.com/stefantalpalaru/w_scan2
> 
> 
> 
> Narcis Garcia
> 
> El 30/11/20 a les 19:47, Richard F ha escrit:
>> Thanks by the way for the heads-up on w_scan2 - the fork of w_scan I
>> didn't know about.  As an external tool, that now tunes DVB-T2 HD 
>> channels for me at last - the only thing outside VDR itself that works
>> so far :-)
>>
>> Richard
>>
>> On 29/11/2020 2:16 pm, Timo Helkiö wrote:
>>> Timo Helkiö kirjoitti 29.11.2020 klo 16.09:
 Helmut Binder kirjoitti 29.11.2020 klo 15.11:
> On Sat, 28 Nov 2020 17:44:32 +0100
> Narcis Garcia  wrote:
>> _
>> I'm using this dedicated address because personal addresses aren't
>> masked enough at this mail public archive. Public archive
>> administrator
>> should fix this against automated addresses collectors.
>> El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
>>> On 28.11.20 17:30, Narcis Garcia wrote:
 Hello,

 I've installed vdr from Raspbian packages, to use it with Kodi.
 I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
 channels are found.

 But I try to watch some channel and I get no data.
>>>
>>>
>>
>> ___
>> vdr mailing list
>> vdr@linuxtv.org
>> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>>
> 
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
> 

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Richard F]

I cloned it and built it from that source on OpenSuSe 15.2, no problem
(well quite a few warnings...!)

On 1/12/2020 7:50 am, Narcis Garcia wrote:
> The project sources repository (sadly in a proprietary platform):
>
> https://github.com/stefantalpalaru/w_scan2
>
>
> Narcis Garcia
>
> El 30/11/20 a les 19:47, Richard F ha escrit:
>> Thanks by the way for the heads-up on w_scan2 - the fork of w_scan I
>> didn't know about.  As an external tool, that now tunes DVB-T2 HD 
>> channels for me at last - the only thing outside VDR itself that works
>> so far :-)
>>
>> Richard
>>
>>

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

The project sources repository (sadly in a proprietary platform):

https://github.com/stefantalpalaru/w_scan2



Narcis Garcia

El 30/11/20 a les 19:47, Richard F ha escrit:
> Thanks by the way for the heads-up on w_scan2 - the fork of w_scan I
> didn't know about.  As an external tool, that now tunes DVB-T2 HD 
> channels for me at last - the only thing outside VDR itself that works
> so far :-)
> 
> Richard
> 
> On 29/11/2020 2:16 pm, Timo Helkiö wrote:
>> Timo Helkiö kirjoitti 29.11.2020 klo 16.09:
>>> Helmut Binder kirjoitti 29.11.2020 klo 15.11:
 On Sat, 28 Nov 2020 17:44:32 +0100
 Narcis Garcia  wrote:
> _
> I'm using this dedicated address because personal addresses aren't
> masked enough at this mail public archive. Public archive
> administrator
> should fix this against automated addresses collectors.
> El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
>> On 28.11.20 17:30, Narcis Garcia wrote:
>>> Hello,
>>>
>>> I've installed vdr from Raspbian packages, to use it with Kodi.
>>> I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
>>> channels are found.
>>>
>>> But I try to watch some channel and I get no data.
>>
>>
> 
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
> 

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Richard F]

Thanks by the way for the heads-up on w_scan2 - the fork of w_scan I
didn't know about.  As an external tool, that now tunes DVB-T2 HD 
channels for me at last - the only thing outside VDR itself that works
so far :-)

Richard

On 29/11/2020 2:16 pm, Timo Helkiö wrote:
> Timo Helkiö kirjoitti 29.11.2020 klo 16.09:
>> Helmut Binder kirjoitti 29.11.2020 klo 15.11:
>>> On Sat, 28 Nov 2020 17:44:32 +0100
>>> Narcis Garcia  wrote:
 _
 I'm using this dedicated address because personal addresses aren't
 masked enough at this mail public archive. Public archive
 administrator
 should fix this against automated addresses collectors.
 El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
> On 28.11.20 17:30, Narcis Garcia wrote:
>> Hello,
>>
>> I've installed vdr from Raspbian packages, to use it with Kodi.
>> I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
>> channels are found.
>>
>> But I try to watch some channel and I get no data.
>
>

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

El 29/11/20 a les 22:13, Helmut Binder ha escrit:
> On Sun, 29 Nov 2020 17:53:27 +0100
> Narcis Garcia  wrote:
> 
>> El 29/11/20 a les 15:09, Timo Helkiö ha escrit:
>>> Helmut Binder kirjoitti 29.11.2020 klo 15.11:
 On Sat, 28 Nov 2020 17:44:32 +0100
 Narcis Garcia  wrote:

> _
> I'm using this dedicated address because personal addresses aren't
> masked enough at this mail public archive. Public archive administrator
> should fix this against automated addresses collectors.
> El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
>> On 28.11.20 17:30, Narcis Garcia wrote:
>>> Hello,
>>>
>>> I've installed vdr from Raspbian packages, to use it with Kodi.
>>> I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
>>> channels are found.
>>>
>>> But I try to watch some channel and I get no data.
>>
>> Does the user id under which you run VDR have access to the
>> DVB devices?
>>
>> Klaus
>>
>
> $ ls -la /dev/dvb/adapter0/
> total 0
> drwxr-xr-x  2 root root  140 de nov.  28 15:57 .
> drwxr-xr-x  3 root root   60 de nov.  28 15:57 ..
> crw-rw+ 1 root video 212,  4 de nov.  28 15:57 demux0
> crw-rw+ 1 root video 212,  5 de nov.  28 15:57 dvr0
> crw-rw+ 1 root video 212,  3 de nov.  28 15:57 frontend0
> crw-rw+ 1 root video 212, 19 de nov.  28 15:57 frontend1
> crw-rw+ 1 root video 212,  7 de nov.  28 15:57 net0
>

 This is a multi-frontend device. You need VDR-2.4.1 or newer - or at
 least this patch from here:
 https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi-frontend-devices/=1308966#post1308966


 Helmut
>>
>> I've done this like a backport from next Raspbian version:
>>
>> $ sudo apt -t bullseye install vdr
>>
>> /[installing new] gcc-10-base libcbor0 libcrypt-dev libcrypt1 libffi7
>> libfido2-1 libgcc-s1 libnsl-dev libnsl2 libnss-nis libnss-nisplus
>> libreadline8 libtirpc-dev runit-helper/
>>
>> /[upgrading] libc-bin libc-dev-bin libc-l10n libc6 libc6-dbg libc6-dev
>> libpython3.7 libpython3.7-dev libpython3.7-minimal libpython3.7-stdlib
>> libselinux1 libstdc++6 libtirpc-common libtirpc3 locales manpages
>> manpages-dev openssh-client openssh-server openssh-sftp-server python3.7
>> python3.7-dev python3.7-minimal python3.7-venv vdr vdr-plugin-femon
>> vdr-plugin-live vdr-plugin-osdserver vdr-plugin-vnsiserver/
>>
>> (...) Bai:43 http://ftp.cica.es/mirrors/Linux/raspbian/raspbian
>> bullseye/main armhf vdr armhf 2.4.1-4.1 [1043 kB] S'està preparant per a
>> desempaquetar …/vdr_2.4.1-4.1_armhf.deb… S'està desempaquetant vdr
>> (2.4.1-4.1) sobre (2.4.0-1+b1)… (...)
>>
>> $ sudo systemctl stop vdr
>>
>> $ sudo systemctl start vdr
>>
>> $ sudo journalctl -xef -u vdr
>>
>> de nov. 29 17:41:31 raspberrypi systemd[1]: Starting Video Disk Recorder...
>> -- Subject: A start job for unit vdr.service has begun execution
>> -- Defined-By: systemd
>> -- Support: https://www.debian.org/support
>> -- 
>> -- A start job for unit vdr.service has begun execution.
>> -- 
>> -- The job identifier is 867922.
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] VDR version 2.4.1
>> started
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] switched to user 'vdr'
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] codeset is 'UTF-8' -
>> known
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] found 28 locales in
>> /usr/share/locale
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin:
>> /usr/lib/vdr/plugins/libvdr-femon.so.2.4.1
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin:
>> /usr/lib/vdr/plugins/libvdr-live.so.2.4.1
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] [live] INFO:
>> validating server ip '0.0.0.0'
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin:
>> /usr/lib/vdr/plugins/libvdr-osdserver.so.2.4.1
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: INFO: validating live server
>> ip '0.0.0.0'
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin:
>> /usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.4.1
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
>> /var/lib/vdr/setup.conf
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
>> /var/lib/vdr/sources.conf
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
>> /var/lib/vdr/diseqc.conf
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
>> /var/lib/vdr/scr.conf
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
>> /var/lib/vdr/channels.conf
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
>> /var/lib/vdr/timers.conf
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
>> /var/lib/vdr/commands.conf
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
>> /var/lib/vdr/reccmds.conf
>> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
>> 

Re: [vdr] vdr not working in Raspbian 10

[Helmut Binder]

On Sun, 29 Nov 2020 17:53:27 +0100
Narcis Garcia  wrote:

> El 29/11/20 a les 15:09, Timo Helkiö ha escrit:
> > Helmut Binder kirjoitti 29.11.2020 klo 15.11:
> >> On Sat, 28 Nov 2020 17:44:32 +0100
> >> Narcis Garcia  wrote:
> >>
> >>> _
> >>> I'm using this dedicated address because personal addresses aren't
> >>> masked enough at this mail public archive. Public archive administrator
> >>> should fix this against automated addresses collectors.
> >>> El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
>  On 28.11.20 17:30, Narcis Garcia wrote:
> > Hello,
> >
> > I've installed vdr from Raspbian packages, to use it with Kodi.
> > I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
> > channels are found.
> >
> > But I try to watch some channel and I get no data.
> 
>  Does the user id under which you run VDR have access to the
>  DVB devices?
> 
>  Klaus
> 
> >>>
> >>> $ ls -la /dev/dvb/adapter0/
> >>> total 0
> >>> drwxr-xr-x  2 root root  140 de nov.  28 15:57 .
> >>> drwxr-xr-x  3 root root   60 de nov.  28 15:57 ..
> >>> crw-rw+ 1 root video 212,  4 de nov.  28 15:57 demux0
> >>> crw-rw+ 1 root video 212,  5 de nov.  28 15:57 dvr0
> >>> crw-rw+ 1 root video 212,  3 de nov.  28 15:57 frontend0
> >>> crw-rw+ 1 root video 212, 19 de nov.  28 15:57 frontend1
> >>> crw-rw+ 1 root video 212,  7 de nov.  28 15:57 net0
> >>>
> >>
> >> This is a multi-frontend device. You need VDR-2.4.1 or newer - or at
> >> least this patch from here:
> >> https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi-frontend-devices/=1308966#post1308966
> >>
> >>
> >> Helmut
> 
> I've done this like a backport from next Raspbian version:
> 
> $ sudo apt -t bullseye install vdr
> 
> /[installing new] gcc-10-base libcbor0 libcrypt-dev libcrypt1 libffi7
> libfido2-1 libgcc-s1 libnsl-dev libnsl2 libnss-nis libnss-nisplus
> libreadline8 libtirpc-dev runit-helper/
> 
> /[upgrading] libc-bin libc-dev-bin libc-l10n libc6 libc6-dbg libc6-dev
> libpython3.7 libpython3.7-dev libpython3.7-minimal libpython3.7-stdlib
> libselinux1 libstdc++6 libtirpc-common libtirpc3 locales manpages
> manpages-dev openssh-client openssh-server openssh-sftp-server python3.7
> python3.7-dev python3.7-minimal python3.7-venv vdr vdr-plugin-femon
> vdr-plugin-live vdr-plugin-osdserver vdr-plugin-vnsiserver/
> 
> (...) Bai:43 http://ftp.cica.es/mirrors/Linux/raspbian/raspbian
> bullseye/main armhf vdr armhf 2.4.1-4.1 [1043 kB] S'està preparant per a
> desempaquetar …/vdr_2.4.1-4.1_armhf.deb… S'està desempaquetant vdr
> (2.4.1-4.1) sobre (2.4.0-1+b1)… (...)
> 
> $ sudo systemctl stop vdr
> 
> $ sudo systemctl start vdr
> 
> $ sudo journalctl -xef -u vdr
> 
> de nov. 29 17:41:31 raspberrypi systemd[1]: Starting Video Disk Recorder...
> -- Subject: A start job for unit vdr.service has begun execution
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> -- 
> -- A start job for unit vdr.service has begun execution.
> -- 
> -- The job identifier is 867922.
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] VDR version 2.4.1
> started
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] switched to user 'vdr'
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] codeset is 'UTF-8' -
> known
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] found 28 locales in
> /usr/share/locale
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin:
> /usr/lib/vdr/plugins/libvdr-femon.so.2.4.1
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin:
> /usr/lib/vdr/plugins/libvdr-live.so.2.4.1
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] [live] INFO:
> validating server ip '0.0.0.0'
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin:
> /usr/lib/vdr/plugins/libvdr-osdserver.so.2.4.1
> de nov. 29 17:41:31 raspberrypi vdr[26842]: INFO: validating live server
> ip '0.0.0.0'
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin:
> /usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.4.1
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
> /var/lib/vdr/setup.conf
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
> /var/lib/vdr/sources.conf
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
> /var/lib/vdr/diseqc.conf
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
> /var/lib/vdr/scr.conf
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
> /var/lib/vdr/channels.conf
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
> /var/lib/vdr/timers.conf
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
> /var/lib/vdr/commands.conf
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
> /var/lib/vdr/reccmds.conf
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
> /var/lib/vdr/svdrphosts.conf
> de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
> /var/lib/vdr/keymacros.conf
> de nov. 

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

El 29/11/20 a les 15:09, Timo Helkiö ha escrit:
> Helmut Binder kirjoitti 29.11.2020 klo 15.11:
>> On Sat, 28 Nov 2020 17:44:32 +0100
>> Narcis Garcia  wrote:
>>
>>> _
>>> I'm using this dedicated address because personal addresses aren't
>>> masked enough at this mail public archive. Public archive administrator
>>> should fix this against automated addresses collectors.
>>> El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
 On 28.11.20 17:30, Narcis Garcia wrote:
> Hello,
>
> I've installed vdr from Raspbian packages, to use it with Kodi.
> I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
> channels are found.
>
> But I try to watch some channel and I get no data.

 Does the user id under which you run VDR have access to the
 DVB devices?

 Klaus

>>>
>>> $ ls -la /dev/dvb/adapter0/
>>> total 0
>>> drwxr-xr-x  2 root root  140 de nov.  28 15:57 .
>>> drwxr-xr-x  3 root root   60 de nov.  28 15:57 ..
>>> crw-rw+ 1 root video 212,  4 de nov.  28 15:57 demux0
>>> crw-rw+ 1 root video 212,  5 de nov.  28 15:57 dvr0
>>> crw-rw+ 1 root video 212,  3 de nov.  28 15:57 frontend0
>>> crw-rw+ 1 root video 212, 19 de nov.  28 15:57 frontend1
>>> crw-rw+ 1 root video 212,  7 de nov.  28 15:57 net0
>>>
>>
>> This is a multi-frontend device. You need VDR-2.4.1 or newer - or at
>> least this patch from here:
>> https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi-frontend-devices/=1308966#post1308966
>>
>>
>> Helmut

I've done this like a backport from next Raspbian version:

$ sudo apt -t bullseye install vdr

/[installing new] gcc-10-base libcbor0 libcrypt-dev libcrypt1 libffi7
libfido2-1 libgcc-s1 libnsl-dev libnsl2 libnss-nis libnss-nisplus
libreadline8 libtirpc-dev runit-helper/

/[upgrading] libc-bin libc-dev-bin libc-l10n libc6 libc6-dbg libc6-dev
libpython3.7 libpython3.7-dev libpython3.7-minimal libpython3.7-stdlib
libselinux1 libstdc++6 libtirpc-common libtirpc3 locales manpages
manpages-dev openssh-client openssh-server openssh-sftp-server python3.7
python3.7-dev python3.7-minimal python3.7-venv vdr vdr-plugin-femon
vdr-plugin-live vdr-plugin-osdserver vdr-plugin-vnsiserver/

(...) Bai:43 http://ftp.cica.es/mirrors/Linux/raspbian/raspbian
bullseye/main armhf vdr armhf 2.4.1-4.1 [1043 kB] S'està preparant per a
desempaquetar …/vdr_2.4.1-4.1_armhf.deb… S'està desempaquetant vdr
(2.4.1-4.1) sobre (2.4.0-1+b1)… (...)

$ sudo systemctl stop vdr

$ sudo systemctl start vdr

$ sudo journalctl -xef -u vdr

de nov. 29 17:41:31 raspberrypi systemd[1]: Starting Video Disk Recorder...
-- Subject: A start job for unit vdr.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit vdr.service has begun execution.
-- 
-- The job identifier is 867922.
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] VDR version 2.4.1
started
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] switched to user 'vdr'
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] codeset is 'UTF-8' -
known
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] found 28 locales in
/usr/share/locale
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin:
/usr/lib/vdr/plugins/libvdr-femon.so.2.4.1
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin:
/usr/lib/vdr/plugins/libvdr-live.so.2.4.1
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] [live] INFO:
validating server ip '0.0.0.0'
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin:
/usr/lib/vdr/plugins/libvdr-osdserver.so.2.4.1
de nov. 29 17:41:31 raspberrypi vdr[26842]: INFO: validating live server
ip '0.0.0.0'
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading plugin:
/usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.4.1
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
/var/lib/vdr/setup.conf
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
/var/lib/vdr/sources.conf
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
/var/lib/vdr/diseqc.conf
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
/var/lib/vdr/scr.conf
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
/var/lib/vdr/channels.conf
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
/var/lib/vdr/timers.conf
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
/var/lib/vdr/commands.conf
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
/var/lib/vdr/reccmds.conf
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
/var/lib/vdr/svdrphosts.conf
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] loading
/var/lib/vdr/keymacros.conf
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26843] video directory
scanner thread started (pid=26842, tid=26843, prio=low)
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26842] registered source
parameters for 'A - ATSC'
de nov. 29 17:41:31 raspberrypi vdr[26842]: [26844] epg data reader
thread 

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

El 29/11/20 a les 15:09, Timo Helkiö ha escrit:
> Helmut Binder kirjoitti 29.11.2020 klo 15.11:
>> On Sat, 28 Nov 2020 17:44:32 +0100
>> Narcis Garcia  wrote:
>>
>>> _
>>> I'm using this dedicated address because personal addresses aren't
>>> masked enough at this mail public archive. Public archive administrator
>>> should fix this against automated addresses collectors.
>>> El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
 On 28.11.20 17:30, Narcis Garcia wrote:
> Hello,
>
> I've installed vdr from Raspbian packages, to use it with Kodi.
> I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
> channels are found.
>
> But I try to watch some channel and I get no data.

 Does the user id under which you run VDR have access to the
 DVB devices?

 Klaus

>>>
>>> $ ls -la /dev/dvb/adapter0/
>>> total 0
>>> drwxr-xr-x  2 root root  140 de nov.  28 15:57 .
>>> drwxr-xr-x  3 root root   60 de nov.  28 15:57 ..
>>> crw-rw+ 1 root video 212,  4 de nov.  28 15:57 demux0
>>> crw-rw+ 1 root video 212,  5 de nov.  28 15:57 dvr0
>>> crw-rw+ 1 root video 212,  3 de nov.  28 15:57 frontend0
>>> crw-rw+ 1 root video 212, 19 de nov.  28 15:57 frontend1
>>> crw-rw+ 1 root video 212,  7 de nov.  28 15:57 net0
>>>
>>
>> This is a multi-frontend device. You need VDR-2.4.1 or newer - or at
>> least this patch from here:
>> https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi-frontend-devices/=1308966#post1308966
>>
>>
>> Helmut
>>
>>> $ ps -A -o user,group,cmd | grep -ie vdr
>>> vdradmi+ vdradmi+ vdradmind
>>> pi   pi   grep --color=auto -ie vdr
>>> vdr  vdr  /usr/bin/vdr
>>>
>>> $ groups vdr
>>> vdr : vdr video
>>>
>>> I'm trying now with vdr-plugin-live : Same unsuccess result.
>>>
>>> ___
>>> vdr mailing list
>>> vdr@linuxtv.org
>>> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>>
>> ___
>> vdr mailing list
>> vdr@linuxtv.org
>> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>>
> 
> 
> You need to select correct frontend like this:
> 
> #!/bin/bash
> 
> var=$(dvb-fe-tool -a0 -f1 | grep 'Device' | awk '{print $3}')
> 
> echo 'A0 Second frontend is ' $var
> 
> if [ $var == 'MN88473' ]; then
> 
> echo 'A0 frontend is ' $var
> 
> mv /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/frontend2
> mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0
> mv /dev/dvb/adapter0/frontend2 /dev/dvb/adapter0/frontend1
> 
> fi
> 
> var=$(dvb-fe-tool -a0 -f0 | grep 'Device' | awk '{print $3}')
> 
> if [ $var == 'MN88473' ]; then
> 
> dvb-fe-tool -a0 -f0 -d DVBT2
> 
> dvb-fe-tool -a0 -f0 -g |grep DELIVERY
> 
> fi
> 
> 
> Second frontend with this adapter can handle DVBC/ANNEX_A too.
> 
> Vdr should know both frontends and use correct one and setup delivery
> system either by setup parameter or trying which one is working and
> prefer DVBT2. With satelite channnels it knows when to use S2. W_scan
> can handle this too.
> 
> Other version of this device can have CXD2837ER as second frontend name.
> 
> Timo
> 

Not matching cases:
Once I've installed dvb-tools to have dvb-fe-tool program:
$ sudo systemctl stop vdr
$ dvb-fe-tool -a0 -f1 | grep 'Device' | awk '{print $3}'
CXD2837ER
$ dvb-fe-tool -a0 -f0 | grep 'Device' | awk '{print $3}'
RTL2832
$ sudo systemctl start vdr

This is the assembled device:
https://osmc.tv/store/product/tv-dongle/

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

El 29/11/20 a les 14:16, André Weidemann ha escrit:
>
>
> On 29.11.2020 11:33, Narcis Garcia wrote:
>> de nov. 29 11:29:53 raspberrypi vdr[11391]: [11391] ERROR
>> (dvbdevice.c,1650): /dev/dvb/adapter0/frontend1: El dispositiu o recurs
>> es troba ocupat
>
> Looks like the dvb-adapter is already in use.
> You can try to figure which process is holding on to it by running:
>
> sudo lsof |grep /dev/dvb/adap|awk '{print $2}'|uniq|xargs ps -fp
>
> André

$ sudo lsof |grep /dev/dvb/adap|awk '{print $2}'|uniq|xargs ps -fp
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
  Output information may be incomplete.
UID    PID  PPID  C STIME TTY  TIME CMD
vdr  11391 1  0 11:29 ?    00:01:10 /usr/bin/vdr

*Narcís*


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

El 29/11/20 a les 11:44, Klaus Schmidinger ha escrit:
> On 29.11.20 11:33, Narcis Garcia wrote:
>> ...
>> de nov. 29 11:29:53 raspberrypi vdr[11391]: [11391] ERROR
>> (dvbdevice.c,1650): /dev/dvb/adapter0/frontend1: El dispositiu o
>> recurs es troba ocupat
> 
> If this error message was given in English I might be able to interpret it.
> 
> Klaus
> 

"Device or resource is busy"


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

El 29/11/20 a les 9:42, Narcis Garcia ha escrit:
> El 28/11/20 a les 23:01, Klaus Schmidinger ha escrit:
>> On 28.11.20 17:55, Narcis Garcia wrote:
>>> ...
>>> de nov. 28 17:33:12 raspberrypi vdr[30508]: [30514] frontend 0/0 lost
>>> lock on channel 23 (Telecinco), tp 586
>>> de nov. 28 17:33:13 raspberrypi vdr[30508]: [30514] frontend 0/0
>>> regained lock on channel 23 (Telecinco), tp 586
>> Maybe a bad cable/connector?
>>
>> Klaus
>>
> Should not, because Kaffeine app lets watch TV (with VDR stopped).
> Narcís.

I've used "VDR Live" to restart service while tracking log with
"journalctl -xef -u vdr"

*LOG:*

de nov. 29 11:29:47 raspberrypi systemd[1]: Starting Video Disk Recorder...
-- Subject: A start job for unit vdr.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit vdr.service has begun execution.
-- 
-- The job identifier is 222785.
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] VDR version 2.4.0
started
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] switched to user 'vdr'
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] codeset is 'UTF-8' -
known
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] found 28 locales in
/usr/share/locale
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading plugin:
/usr/lib/vdr/plugins/libvdr-femon.so.2.4.0
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading plugin:
/usr/lib/vdr/plugins/libvdr-live.so.2.4.0
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] [live] INFO:
validating server ip '0.0.0.0'
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading plugin:
/usr/lib/vdr/plugins/libvdr-osdserver.so.2.4.0
de nov. 29 11:29:47 raspberrypi vdr[11391]: INFO: validating live server
ip '0.0.0.0'
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading plugin:
/usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.4.0
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading
/var/lib/vdr/setup.conf
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading
/var/lib/vdr/sources.conf
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading
/var/lib/vdr/diseqc.conf
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading
/var/lib/vdr/scr.conf
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading
/var/lib/vdr/channels.conf
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading
/var/lib/vdr/timers.conf
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading
/var/lib/vdr/commands.conf
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading
/var/lib/vdr/reccmds.conf
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading
/var/lib/vdr/svdrphosts.conf
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] loading
/var/lib/vdr/keymacros.conf
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11392] video directory
scanner thread started (pid=11391, tid=11392, prio=low)
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] registered source
parameters for 'A - ATSC'
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] registered source
parameters for 'C - DVB-C'
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11393] epg data reader
thread started (pid=11391, tid=11393, prio=high)
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] registered source
parameters for 'S - DVB-S'
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11393] reading EPG data
from /var/cache/vdr/epg.data
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] registered source
parameters for 'T - DVB-T'
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11392] video directory
scanner thread ended (pid=11391, tid=11392)
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11393] epg data reader
thread ended (pid=11391, tid=11393)
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] probing
/dev/dvb/adapter0/frontend0
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] creating cDvbDevice
de nov. 29 11:29:47 raspberrypi vdr[11391]: [11391] new device number 1
de nov. 29 11:29:48 raspberrypi vdr[11391]: [11391] DVB API version is
0x050B (VDR was built with 0x050B)
de nov. 29 11:29:48 raspberrypi vdr[11391]: [11391] frontend 0/0
provides DVB-T with QPSK,QAM16,QAM64 ("Realtek RTL2832 (DVB-T)")
de nov. 29 11:29:48 raspberrypi vdr[11391]: [11397] frontend 0/0 tuner
thread started (pid=11391, tid=11397, prio=high)
de nov. 29 11:29:48 raspberrypi vdr[11391]: [11397] cTimeMs: using
monotonic clock (resolution is 1 ns)
de nov. 29 11:29:48 raspberrypi vdr[11391]: [11391] cTimeMs: using
monotonic clock (resolution is 1 ns)
de nov. 29 11:29:48 raspberrypi vdr[11391]: [11398] device 1 section
handler thread started (pid=11391, tid=11398, prio=low)
de nov. 29 11:29:53 raspberrypi vdr[11391]: [11391] ERROR
(dvbdevice.c,1650): /dev/dvb/adapter0/frontend1: El dispositiu o recurs
es troba ocupat
de nov. 29 11:29:53 raspberrypi vdr[11391]: [11391] found 1 DVB device
de nov. 29 11:29:53 raspberrypi vdr[11391]: [11391] initializing plugin:
femon (2.4.0): DVB Signal Information Monitor (OSD)
de nov. 29 11:29:53 raspberrypi vdr[11391]: [11391] 

Re: [vdr] vdr not working in Raspbian 10

[Timo Helkiö]

Timo Helkiö kirjoitti 29.11.2020 klo 16.09:

Helmut Binder kirjoitti 29.11.2020 klo 15.11:

On Sat, 28 Nov 2020 17:44:32 +0100
Narcis Garcia  wrote:


_
I'm using this dedicated address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:

On 28.11.20 17:30, Narcis Garcia wrote:

Hello,

I've installed vdr from Raspbian packages, to use it with Kodi.
I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
channels are found.

But I try to watch some channel and I get no data.


Does the user id under which you run VDR have access to the
DVB devices?

Klaus



$ ls -la /dev/dvb/adapter0/
total 0
drwxr-xr-x  2 root root  140 de nov.  28 15:57 .
drwxr-xr-x  3 root root   60 de nov.  28 15:57 ..
crw-rw+ 1 root video 212,  4 de nov.  28 15:57 demux0
crw-rw+ 1 root video 212,  5 de nov.  28 15:57 dvr0
crw-rw+ 1 root video 212,  3 de nov.  28 15:57 frontend0
crw-rw+ 1 root video 212, 19 de nov.  28 15:57 frontend1
crw-rw+ 1 root video 212,  7 de nov.  28 15:57 net0



This is a multi-frontend device. You need VDR-2.4.1 or newer - or at 
least this patch from here:
https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi-frontend-devices/=1308966#post1308966 



Helmut


$ ps -A -o user,group,cmd | grep -ie vdr
vdradmi+ vdradmi+ vdradmind
pi   pi   grep --color=auto -ie vdr
vdr  vdr  /usr/bin/vdr

$ groups vdr
vdr : vdr video

I'm trying now with vdr-plugin-live : Same unsuccess result.

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr




You need to select correct frontend like this:

#!/bin/bash

var=$(dvb-fe-tool -a0 -f1 | grep 'Device' | awk '{print $3}')

echo 'A0 Second frontend is ' $var

if [ $var == 'MN88473' ]; then

echo 'A0 frontend is ' $var

mv /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/frontend2
mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0
mv /dev/dvb/adapter0/frontend2 /dev/dvb/adapter0/frontend1

fi

var=$(dvb-fe-tool -a0 -f0 | grep 'Device' | awk '{print $3}')

if [ $var == 'MN88473' ]; then

dvb-fe-tool -a0 -f0 -d DVBT2

dvb-fe-tool -a0 -f0 -g |grep DELIVERY

fi


Second frontend with this adapter can handle DVBC/ANNEX_A too.

Vdr should know both frontends and use correct one and setup delivery 
system either by setup parameter or trying which one is working and 
prefer DVBT2. With satelite channnels it knows when to use S2. W_scan 
can handle this too.


Other version of this device can have CXD2837ER as second frontend name.

Timo

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


More info:

http://blog.palosaari.fi/2014/09/naked-hardware-18-astrometa-amdvb-t2-v2.html

Timo

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Timo Helkiö]

Helmut Binder kirjoitti 29.11.2020 klo 15.11:

On Sat, 28 Nov 2020 17:44:32 +0100
Narcis Garcia  wrote:


_
I'm using this dedicated address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:

On 28.11.20 17:30, Narcis Garcia wrote:

Hello,

I've installed vdr from Raspbian packages, to use it with Kodi.
I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
channels are found.

But I try to watch some channel and I get no data.


Does the user id under which you run VDR have access to the
DVB devices?

Klaus



$ ls -la /dev/dvb/adapter0/
total 0
drwxr-xr-x  2 root root  140 de nov.  28 15:57 .
drwxr-xr-x  3 root root   60 de nov.  28 15:57 ..
crw-rw+ 1 root video 212,  4 de nov.  28 15:57 demux0
crw-rw+ 1 root video 212,  5 de nov.  28 15:57 dvr0
crw-rw+ 1 root video 212,  3 de nov.  28 15:57 frontend0
crw-rw+ 1 root video 212, 19 de nov.  28 15:57 frontend1
crw-rw+ 1 root video 212,  7 de nov.  28 15:57 net0



This is a multi-frontend device. You need VDR-2.4.1 or newer - or at least this 
patch from here:
https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi-frontend-devices/=1308966#post1308966

Helmut


$ ps -A -o user,group,cmd | grep -ie vdr
vdradmi+ vdradmi+ vdradmind
pi   pi   grep --color=auto -ie vdr
vdr  vdr  /usr/bin/vdr

$ groups vdr
vdr : vdr video

I'm trying now with vdr-plugin-live : Same unsuccess result.

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr




You need to select correct frontend like this:

#!/bin/bash

var=$(dvb-fe-tool -a0 -f1 | grep 'Device' | awk '{print $3}')

echo 'A0 Second frontend is ' $var

if [ $var == 'MN88473' ]; then

echo 'A0 frontend is ' $var

mv /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/frontend2
mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0
mv /dev/dvb/adapter0/frontend2 /dev/dvb/adapter0/frontend1

fi

var=$(dvb-fe-tool -a0 -f0 | grep 'Device' | awk '{print $3}')

if [ $var == 'MN88473' ]; then

dvb-fe-tool -a0 -f0 -d DVBT2

dvb-fe-tool -a0 -f0 -g |grep DELIVERY

fi


Second frontend with this adapter can handle DVBC/ANNEX_A too.

Vdr should know both frontends and use correct one and setup delivery 
system either by setup parameter or trying which one is working and 
prefer DVBT2. With satelite channnels it knows when to use S2. W_scan 
can handle this too.


Other version of this device can have CXD2837ER as second frontend name.

Timo

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Helmut Binder]

On Sat, 28 Nov 2020 17:44:32 +0100
Narcis Garcia  wrote:

> _
> I'm using this dedicated address because personal addresses aren't
> masked enough at this mail public archive. Public archive administrator
> should fix this against automated addresses collectors.
> El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
> > On 28.11.20 17:30, Narcis Garcia wrote:
> >> Hello,
> >>
> >> I've installed vdr from Raspbian packages, to use it with Kodi.
> >> I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
> >> channels are found.
> >>
> >> But I try to watch some channel and I get no data.
> > 
> > Does the user id under which you run VDR have access to the
> > DVB devices?
> > 
> > Klaus
> > 
> 
> $ ls -la /dev/dvb/adapter0/
> total 0
> drwxr-xr-x  2 root root  140 de nov.  28 15:57 .
> drwxr-xr-x  3 root root   60 de nov.  28 15:57 ..
> crw-rw+ 1 root video 212,  4 de nov.  28 15:57 demux0
> crw-rw+ 1 root video 212,  5 de nov.  28 15:57 dvr0
> crw-rw+ 1 root video 212,  3 de nov.  28 15:57 frontend0
> crw-rw+ 1 root video 212, 19 de nov.  28 15:57 frontend1
> crw-rw+ 1 root video 212,  7 de nov.  28 15:57 net0
> 

This is a multi-frontend device. You need VDR-2.4.1 or newer - or at least this 
patch from here:
https://www.vdr-portal.de/forum/index.php?thread/132190-patch-f%C3%BCr-multi-frontend-devices/=1308966#post1308966

Helmut

> $ ps -A -o user,group,cmd | grep -ie vdr
> vdradmi+ vdradmi+ vdradmind
> pi   pi   grep --color=auto -ie vdr
> vdr  vdr  /usr/bin/vdr
> 
> $ groups vdr
> vdr : vdr video
> 
> I'm trying now with vdr-plugin-live : Same unsuccess result.
> 
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

El 28/11/20 a les 23:01, Klaus Schmidinger ha escrit:
> On 28.11.20 17:55, Narcis Garcia wrote:
>> ...
>> de nov. 28 17:33:12 raspberrypi vdr[30508]: [30514] frontend 0/0 lost
>> lock on channel 23 (Telecinco), tp 586
>> de nov. 28 17:33:13 raspberrypi vdr[30508]: [30514] frontend 0/0
>> regained lock on channel 23 (Telecinco), tp 586
> 
> Maybe a bad cable/connector?
> 
> Klaus
> 

Should not, because Kaffeine app lets watch TV (with VDR stopped).
Narcís.

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Klaus Schmidinger]

On 29.11.20 11:33, Narcis Garcia wrote:

...
de nov. 29 11:29:53 raspberrypi vdr[11391]: [11391] ERROR (dvbdevice.c,1650): 
/dev/dvb/adapter0/frontend1: El dispositiu o recurs es troba ocupat


If this error message was given in English I might be able to interpret it.

Klaus

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Klaus Schmidinger]

On 28.11.20 17:55, Narcis Garcia wrote:

...
de nov. 28 17:33:12 raspberrypi vdr[30508]: [30514] frontend 0/0 lost
lock on channel 23 (Telecinco), tp 586
de nov. 28 17:33:13 raspberrypi vdr[30508]: [30514] frontend 0/0
regained lock on channel 23 (Telecinco), tp 586


Maybe a bad cable/connector?

Klaus


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

El 28/11/20 a les 17:44, Narcis Garcia ha escrit:
> _
> I'm using this dedicated address because personal addresses aren't
> masked enough at this mail public archive. Public archive administrator
> should fix this against automated addresses collectors.
> El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
>> On 28.11.20 17:30, Narcis Garcia wrote:
>>> Hello,
>>>
>>> I've installed vdr from Raspbian packages, to use it with Kodi.
>>> I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
>>> channels are found.
>>>
>>> But I try to watch some channel and I get no data.
>> Does the user id under which you run VDR have access to the
>> DVB devices?
>>
>> Klaus
>>
> $ ls -la /dev/dvb/adapter0/
> total 0
> drwxr-xr-x  2 root root  140 de nov.  28 15:57 .
> drwxr-xr-x  3 root root   60 de nov.  28 15:57 ..
> crw-rw+ 1 root video 212,  4 de nov.  28 15:57 demux0
> crw-rw+ 1 root video 212,  5 de nov.  28 15:57 dvr0
> crw-rw+ 1 root video 212,  3 de nov.  28 15:57 frontend0
> crw-rw+ 1 root video 212, 19 de nov.  28 15:57 frontend1
> crw-rw+ 1 root video 212,  7 de nov.  28 15:57 net0
>
> $ ps -A -o user,group,cmd | grep -ie vdr
> vdradmi+ vdradmi+ vdradmind
> pi   pi   grep --color=auto -ie vdr
> vdr  vdr  /usr/bin/vdr
>
> $ groups vdr
> vdr : vdr video
>
> I'm trying now with vdr-plugin-live : Same unsuccess result.
>
WHEN I JUST START SERVICE:

$ sudo systemctl status vdr
● vdr.service - Video Disk Recorder
   Loaded: loaded (/lib/systemd/system/vdr.service; enabled; vendor
preset: enabled)
   Active: active (running) since Sat 2020-11-28 17:31:10 CET; 13s ago
  Process: 30488 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh
commands (code=exited, status=0/SUCCESS)
  Process: 30498 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh
reccmds (code=exited, status=0/SUCCESS)
 Main PID: 30508 (vdr)
   Status: "Ready"
    Tasks: 9 (limit: 3748)
   CGroup: /system.slice/vdr.service
   └─30508 /usr/bin/vdr

de nov. 28 17:31:10 raspberrypi vdr[30508]: [30508] ERROR: no OSD
provider available - using dummy OSD!
de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] loading
/var/cache/vdr/cam.data
de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] switching to channel
1 T-0-17-155 (mega)
de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] setting watchdog
timer to 60 seconds
de nov. 28 17:31:20 raspberrypi vdr[30508]: [32663] SVDRP server handler
thread started (pid=30508, tid=32663, prio=low)
de nov. 28 17:31:20 raspberrypi vdr[30508]: [32663] SVDRP raspberrypi
opening port 6419/tcp
de nov. 28 17:31:20 raspberrypi vdr[30508]: [32663] SVDRP raspberrypi
listening on port 6419/tcp
de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] OSD size changed to
720x480 @ 1
de nov. 28 17:31:20 raspberrypi vdr[30508]: [30508] ERROR: no OSD
provider available - using dummy OSD!
de nov. 28 17:31:21 raspberrypi vdr[30508]: [30508] max. latency time 1
seconds

AFTER A MINUTE OF RUNNING SERVICE (I was trying to switch TV channel
from a client):

$ sudo systemctl status vdr
● vdr.service - Video Disk Recorder
   Loaded: loaded (/lib/systemd/system/vdr.service; enabled; vendor
preset: enabled)
   Active: active (running) since Sat 2020-11-28 17:31:10 CET; 2min 21s ago
  Process: 30488 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh
commands (code=exited, status=0/SUCCESS)
  Process: 30498 ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh
reccmds (code=exited, status=0/SUCCESS)
 Main PID: 30508 (vdr)
   Status: "Ready"
    Tasks: 9 (limit: 3748)
   CGroup: /system.slice/vdr.service
   └─30508 /usr/bin/vdr

de nov. 28 17:33:12 raspberrypi vdr[30508]: [30514] frontend 0/0 lost
lock on channel 23 (Telecinco), tp 586
de nov. 28 17:33:13 raspberrypi vdr[30508]: [30514] frontend 0/0
regained lock on channel 23 (Telecinco), tp 586
de nov. 28 17:33:16 raspberrypi vdr[30508]: [30514] frontend 0/0 lost
lock on channel 23 (Telecinco), tp 586
de nov. 28 17:33:18 raspberrypi vdr[30508]: [30514] frontend 0/0
regained lock on channel 23 (Telecinco), tp 586
de nov. 28 17:33:21 raspberrypi vdr[30508]: [30514] frontend 0/0 lost
lock on channel 23 (Telecinco), tp 586
de nov. 28 17:33:21 raspberrypi vdr[30508]: [30514] frontend 0/0
regained lock on channel 23 (Telecinco), tp 586
de nov. 28 17:33:24 raspberrypi vdr[30508]: [30514] frontend 0/0 lost
lock on channel 23 (Telecinco), tp 586
de nov. 28 17:33:25 raspberrypi vdr[30508]: [30514] frontend 0/0
regained lock on channel 23 (Telecinco), tp 586
de nov. 28 17:33:28 raspberrypi vdr[30508]: [30514] frontend 0/0 lost
lock on channel 23 (Telecinco), tp 586
de nov. 28 17:33:28 raspberrypi vdr[30508]: [30514] frontend 0/0
regained lock on channel 23 (Telecinco), tp 586



___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Narcis Garcia]

_
I'm using this dedicated address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 28/11/20 a les 17:33, Klaus Schmidinger ha escrit:
> On 28.11.20 17:30, Narcis Garcia wrote:
>> Hello,
>>
>> I've installed vdr from Raspbian packages, to use it with Kodi.
>> I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
>> channels are found.
>>
>> But I try to watch some channel and I get no data.
> 
> Does the user id under which you run VDR have access to the
> DVB devices?
> 
> Klaus
> 

$ ls -la /dev/dvb/adapter0/
total 0
drwxr-xr-x  2 root root  140 de nov.  28 15:57 .
drwxr-xr-x  3 root root   60 de nov.  28 15:57 ..
crw-rw+ 1 root video 212,  4 de nov.  28 15:57 demux0
crw-rw+ 1 root video 212,  5 de nov.  28 15:57 dvr0
crw-rw+ 1 root video 212,  3 de nov.  28 15:57 frontend0
crw-rw+ 1 root video 212, 19 de nov.  28 15:57 frontend1
crw-rw+ 1 root video 212,  7 de nov.  28 15:57 net0

$ ps -A -o user,group,cmd | grep -ie vdr
vdradmi+ vdradmi+ vdradmind
pi   pi   grep --color=auto -ie vdr
vdr  vdr  /usr/bin/vdr

$ groups vdr
vdr : vdr video

I'm trying now with vdr-plugin-live : Same unsuccess result.

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] vdr not working in Raspbian 10

[Narcis Garcia]

Hello,

I've installed vdr from Raspbian packages, to use it with Kodi.
I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
channels are found.

But I try to watch some channel and I get no data.
Tried with two clients Kodi software with its VDR plugin (screen
interface) and with vdradmin-am (web interface).

What can I check to find the problem?

Notes:
- TV dongle works; if I stop vdr service and use GUI applicacion
Kaffeine, I can watch all TV channels.
- I see VDR service attending TCP ports 34890 (VNSI), 6419 and 2010

Thank you.

-- 

Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr not working in Raspbian 10

[Klaus Schmidinger]

On 28.11.20 17:30, Narcis Garcia wrote:

Hello,

I've installed vdr from Raspbian packages, to use it with Kodi.
I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV
channels are found.

But I try to watch some channel and I get no data.


Does the user id under which you run VDR have access to the
DVB devices?

Klaus


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr