Hi all,
On Thu, Apr 30, 2020 at 05:46:44PM +0200, Harald Milz wrote:
Möglicherweise habe ich verpasst, weil ich sehr lange nicht danach geschaut habe, dass sich an den diesbezüglichen Configs von vdr-2.2.0 nach -2.4.0 was geändert hat.
[Background: since my upgrade from 2.2.0 to yavdr-2.4.0, VDR has been confused about channel to device allocation. I have 2 dual LNBs pointing to Astra 19.2E and Hotbird 13E, respectively, attached to a 4-port Digital Devices V 6.5 card. I also upgraded dddvb-0.9.32 to 0.9.38 from git. With the old installation, all worked fine. Sorry for writing in German in my first post.]
In order to bind the 13E channels to device 3, I modified the CAIDs for the affected channels to 3 now. Device 4 should be able to receive these channels as well, but I rarely need 2 of them at the same time, and VDR seems to ignore 2 channels written as x,y in the CAID field anyway.
This seems to work for now, although I do not consider this a permanent fix. I will keep looking if VDR again attempts to use device 3 or 4 for Astra channels.
I also suspected a broken disecq.conf although I had not changed it during the upgrade, and replaced it by an empty file, but this confused VDR even more.
Also, last night I was watching ZDF (with Kodi), when a recording on ARD started, which killed the ZDF live stream and crashed VDR. :-/ That should not happen with 2 available receivers. Turned out, VDR had attempted to use device 3 for the ARD recording, resulting in a VDSB error. m(
Very strange. It feels like a bug, but this would affect everyone with 2.4.0 using 2 sats and 4 receivers, or the yavdr-2.4.0 build would be buggy, which I cannot imagine (why would they patch something here?).
I think it's more plausible that there is something foul in the state of configs, something subtle and not obvious (to me). Any further idea where to look is appreciated!
THX!