pipelka / vdr-plugin-xvdr

DISCONTINUED - XVDR Plugin for VDR
GNU General Public License v2.0
43 stars 22 forks source link

Locking of channels while switching still occurs #42

Closed dhardtke closed 12 years ago

dhardtke commented 12 years ago

Commit 5e20cc39d82d8cc9633e9fd2acacf844a8eeebd2 didn't solve the fixed locking of channels for me .. why not? I have the latest version compiled and in use and here is a part of the log from VDR: Jan 20 18:14:37 htpc vdr: [6146] frontend 0/0 lost lock on channel 5, tp 442 Jan 20 18:14:38 htpc vdr: [6146] frontend 0/0 regained lock on channel 5, tp 442 Jan 20 18:14:50 htpc vdr: [6146] frontend 0/0 lost lock on channel 5, tp 442 Jan 20 18:14:51 htpc vdr: [6146] frontend 0/0 regained lock on channel 5, tp 442 Jan 20 18:15:27 htpc vdr: [6146] frontend 0/0 lost lock on channel 5, tp 442 Jan 20 18:15:27 htpc vdr: [6146] frontend 0/0 regained lock on channel 5, tp 442 Jan 20 18:17:01 htpc CRON[6957]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jan 20 18:17:26 htpc vdr: [6616] XVDR-Error: cxSocket::read: read() error at 0/4 Jan 20 18:17:26 htpc vdr: [6932] cLiveStreamer stream processor thread ended (pid=6047, tid=6932) Jan 20 18:17:26 htpc vdr: [6931] XVDR: LiveQueue stopped Jan 20 18:17:26 htpc vdr: [6616] buffer stats: 149272 (14%) used Jan 20 18:17:26 htpc vdr: [6148] XVDR: Client with ID 12 seems to be disconnected, removing from client list Jan 20 18:17:26 htpc vdr: [6936] TS buffer on device 1 thread ended (pid=6047, tid=6936) Jan 20 18:17:26 htpc vdr: [6935] buffer stats: 75764 (3%) used Jan 20 18:17:26 htpc vdr: [6935] receiver on device 1 thread ended (pid=6047, tid=6935) Jan 20 18:17:30 htpc vdr: [6603] XVDR-Error: cxSocket::read: read() error at 0/4 Jan 20 18:17:30 htpc vdr: [6148] XVDR: Client with ID 11 seems to be disconnected, removing from client list Jan 20 18:17:33 htpc lircd-0.9.0[1136]: removed client

Thanks in advance!

pipelka commented 12 years ago

It looks to me like reception problems. I already saw this a couple of times and it was always a broken antenna, misadjusted LNB, ... A friend of mine had a loosly tighened LNB and was hitten by these lost/regained lock errors from time to time.

BTW, this is a VDR error message and not related to XVDR.

dhardtke commented 12 years ago

Thanks for your fast reply. I thought about that at first too, but it's working properly with my integrated receiver in the TV and with another external receiver, so it can't be because of my antenna, etc. ( btw. I'm using DVB-C ;) )

pipelka commented 12 years ago

Then it might be HW related.

pipelka commented 12 years ago

Please try running femon. It will tell you more about your signal quality.

dhardtke commented 12 years ago

Ok, I will try that .. I read phenom will output the results to the OSD .. but how can I see that when I have no OSD provider available? (only dummy)

pipelka commented 12 years ago

Try femon: http://www.vdr-wiki.de/wiki/index.php/Dvb-apps_femon

its a simple console application.

dhardtke commented 12 years ago

Interesting, with the latest version of xbmc & xvdr (both plugins for XBMC and VDR) it doesn't happen anymore... But I have another problem and will open another issue for that!