Beiträge von corvy

Both Sony and Phillips have won many price versus picture tests in Norway. Samsung is not a cheaper option. But they (all mentioned) do good quality TVs for sure. Panasonic as-well deserves a mention. And LG.

If you only want the great picture at high price go for B&O or Loewe. Wonderful!

Thank you HelmutB. Maybe I had some kind of freak error, my CAM stalling or I dunno. Who knows! I will keep investigating!

Yes, I kind of agree. My preferred smart TV these days is an OSMC box with Kodi. Great little thing. Soon it will have Netflix as-well. In the meantime I have this box together with a Chromecast. Then I have 4K support all the way and great speed and stability combined with the best TV picture. Kodi on the Smart TV is not as snappy and well performing as on the OSMC. Best thing is that I can control it with the TV remote over the HDMI cable. My wife doesnt even know its a separate box!

Ok thanks. No I do not find anything in the CAM menu regarding any counters but there is a lot of "stuff" in there around subscriptions and stuff. Guess I will just have to wait and see again. There is nothing I can do in the logs? Enable some kind of debugging or similar?

Is there any way to manually check if subscription updates actually are receiving (pre next expiration).

kls are you using the patch from HelmutB ?

Thanks both of you!

Hello HelmutB do you think camtweaks could be interferring the subscription updates?

Ok thanks kls

I think TV2 HD would be one to send this as it seems to be one that is reccommended from the Cable provider but how could I find out what transponder is suitable? Futhermore, when I put the CAM in the TV it was on TV2 HD for just 10-12 minutes and it decoded. I tried the same channel/transponder on VDR and it is one that is watched quite a bit so if this is actually transmitting updates we should have gotten it a long time ago....

Buy a TV with Android and run Kodi, that is what I do and it works perfect. For 4k you might need something more powerful. Sony and Philips are better choises than Samsung.

Hello!

I have a 2.4.0 installation with patches for ddci2 (vdr-2.4.0-06-fix-channel-switch.diff and vdr-2-4-0-camtweaks-1.patch) and it has been working perfect until a few days ago. Then I get "no access" error to all channels. When I see the CAM menu I find that my subscriptions are expired and no new updates over the DVB-C network. Just as a workaround I tried to move the CAM and CI access card to my TV and after about 15 minutes the decoding works again. Moved the CAM and CI back to VDR and now everything is perfect again.

So my question is why does it not update the subscription over the network? How I can debug it? The card reader is from DD (DD DuoFlex CI).

Perfect, I will do so! Thanks haraldov

Hello, I have been working with a new config of VDR with 2.4.0 version and ddci2. Kernel 4.19.2. It has been working fine for a while but last 2 days I have had two freezes. Anyone seen errors like this?

Nov 23 13:30:31 timeshift vdr: [6953] device 1 TS buffer thread ended (pid=29666, tid=6953)
Nov 23 13:30:31 timeshift vdr: [6952] buffer stats: 188 (0%) used
Nov 23 13:30:31 timeshift vdr: [6952] device 1 receiver thread ended (pid=29666, tid=6952)
Nov 23 13:30:31 timeshift vdr: [29690] VNSIStatus thread ended (pid=29666, tid=29690)
Nov 23 13:30:31 timeshift vdr: [29692] VNSI: cxSocket::read(fd=15): eof, connection closed
Nov 23 13:30:31 timeshift vdr: [29692] VNSI Client 0->10.0.0.101:57404 thread ended (pid=29666, tid=29692)
Nov 23 13:30:31 timeshift vdr: [29693] VNSI: cxSocket::read(fd=16): eof, connection closed
Nov 23 13:30:31 timeshift vdr: [29693] VNSI Client 1->10.0.0.114:58886 thread ended (pid=29666, tid=29693)
Nov 23 13:30:31 timeshift vdr: [29691] VNSITimers thread ended (pid=29666, tid=29691)
Nov 23 13:30:31 timeshift vdr: [29666] VNSI: VNSI Server stopped
Nov 23 13:30:31 timeshift vdr: [29666] stopping plugin: ddci2
Nov 23 13:30:31 timeshift vdr: [29682] DDCI Send (/dev/dvb/adapter4/sec0) thread ended (pid=29666, tid=29682)
Nov 23 13:30:31 timeshift vdr: [29688] DDCI Recv Deliver (/dev/dvb/adapter4/sec0) thread ended (pid=29666, tid=29688)
Nov 23 13:30:31 timeshift vdr: [29683] DDCI Recv (/dev/dvb/adapter4/sec0) thread ended (pid=29666, tid=29683)
Nov 23 13:30:31 timeshift vdr: [29681] DDCI adapter /dev/dvb/adapter4/ca0 thread ended (pid=29666, tid=29681)
Nov 23 13:30:31 timeshift vdr: [29686] DDCI Send (/dev/dvb/adapter5/sec0) thread ended (pid=29666, tid=29686)
Nov 23 13:30:32 timeshift vdr: [29689] DDCI Recv Deliver (/dev/dvb/adapter5/sec0) thread ended (pid=29666, tid=29689)
Nov 23 13:30:32 timeshift vdr: [29687] DDCI Recv (/dev/dvb/adapter5/sec0) thread ended (pid=29666, tid=29687)
Nov 23 13:30:32 timeshift vdr: [29684] DDCI adapter /dev/dvb/adapter5/ca0 thread ended (pid=29666, tid=29684)
Nov 23 13:30:32 timeshift vdr: [29666] DDCI-Inf: plugin stopped
Nov 23 13:30:32 timeshift vdr: [29666] saved setup to /var/lib/vdr/setup.conf
Nov 23 13:30:32 timeshift vdr: [29671] device 1 section handler thread ended (pid=29666, tid=29671)
Nov 23 13:30:32 timeshift vdr: [29670] frontend 0/0 tuner thread ended (pid=29666, tid=29670)
Nov 23 13:30:32 timeshift vdr: [29674] device 2 section handler thread ended (pid=29666, tid=29674)
Nov 23 13:30:32 timeshift vdr: [29673] frontend 1/0 tuner thread ended (pid=29666, tid=29673)
Nov 23 13:30:32 timeshift vdr: [29677] device 3 section handler thread ended (pid=29666, tid=29677)
Nov 23 13:30:32 timeshift vdr: [29676] frontend 2/0 tuner thread ended (pid=29666, tid=29676)
Nov 23 13:30:32 timeshift vdr: [29680] device 4 section handler thread ended (pid=29666, tid=29680)
Nov 23 13:30:32 timeshift vdr: [29679] frontend 3/0 tuner thread ended (pid=29666, tid=29679)
Nov 23 13:30:32 timeshift vdr: [29666] deleting plugin: vnsiserver
Nov 23 13:30:32 timeshift vdr: [29666] deleting plugin: ddci2
Nov 23 13:30:32 timeshift vdr: [29666] CAM 1/1: deleting MTD CAM slot
Nov 23 13:30:32 timeshift vdr: [29666] buffer stats: 0 (0%) used
Nov 23 13:30:32 timeshift vdr: [29666] CAM 1/2: deleting MTD CAM slot
Nov 23 13:30:32 timeshift vdr: [29666] buffer stats: 32524 (3%) used
Nov 23 13:30:32 timeshift vdr: [29666] CAM 1/3: deleting MTD CAM slot
Nov 23 13:30:32 timeshift vdr: [29666] buffer stats: 10152 (0%) used
Nov 23 13:30:32 timeshift vdr: [29666] emergency exit!
Nov 23 13:30:32 timeshift vdr: [29666] exiting, exit code 1

Das ist gut! Danke!

Seems my files are all OK

timeshift@timeshift:/srv/vdr/video/vdr-recordings$ find -iname *.ts -exec vdr-checkts {} \;
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0
Errors: 0

Ok grand, thanks for the tips! I will apply the patch and do some more testing. The recordings were also on a NTFS volume, moved that away and over to Btrfs so hopefully that will solve some issues. Chekts is a good tips, thanks!

Was there a good reason to be a new kernel? Was there some patches or updates applied there? I do not quite understand the statements around that.

Hello! I have also the Digital Devices cards with the DuoFlex CI card reader. I have been running fine now for a few days with the patch for enabling dual-channel descramble and MTD with VDR 2.4.0 but my German is not so good and Google translate is not perfect either. Right now I am on Linux Kernel 4.19.2 since I kind-of gathered that I needed a new driver based on what I read in this thread.

Sometimes I get some stuttering, especially if I watch on two clients at one time, or I do recording at the same time as watch another channel. Some very few times the stream freeze. To try and fix this I upgraded to kernel 4.19.2 and I wonder do I need the patch referenced above?

https://www.vdr-portal.de/inde…0-fix-shared-capids-diff/

From before I run the vdr-2-4-0-camtweaks-1.patch and the vdr-2.4.0-06-fix-channel-switch.diff and also the latest EPG fix patch from Klaus.

Would this aditional patch be needed or is the new driver from updated kernel enough? If someone could explain what is the conclusion from the last ~40 posts in this thread I would be very grateful!

haraldov I understand. Replacing VNSI. Could be an interesting way of doing it Thanks for the tip!

kls Thanks for your help! EPG is working great now!

haraldov vdr is my only choice due to MTD support only working on VDR. I love the fact that dvblink/tvmosaic creates images in kodi for recordings, and GUI candy in EPG would be nice; but for now this looks like a very stable solution. Much faster than any VDR solution I have used to date AND I do not have to manually struggle to get all the EPG matched from XMLTV....

Thanks to all for helping!

Yes sir!! It works!

haraldov when you use honeybee do you get images in the GUI of Kodi as-well (or do you only use OSD directly from VDR?)?

Thanks seahawk1986 ! I managed to exit with pressing OK and then it worked. Will see if this gives me any EPG information!

I cannot get it to save my settings for some reason. I finally managed to add the channel (right arrow to "selected" was the step I did not understand!) then I get the option to map the channel to EPG source. So I go to EPG SOURCE CHANNEL MAPPINGS, click on "none", select the EPG channel and then it looks like this.

At this point in the log it says "saved setup to /var/lib/vdr/setup.conf".

What does F4 / Copy mean here? If I click it it just prompts to "copy to all mapped channels?" but I dont know how to accept... (tried F2 since the color was green but....)

If I backspace out of the menu and back in the mapping is gone. What am I doing wrong?