Project

General

Profile

Actions
Copy link

Bug #1917

closed

Git master fails to find services in some muxes that 3.3 could discover

Added by Koen Kooi over 11 years ago. Updated almost 11 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
DVB
Target version:
-
Start date:
2014-01-07
Due date:
% Done:

0%

Estimated time:
Found in version:
git
Affected Versions:

Description

tvheadend 3.3 had some issues tuning into some channels where I had to do 'killall tvheadend' (and restart) to make the stream work. Since I'm forced to use that closed source crap TBS6618 driver I can't safely say who's at fault, the driver or tvheadend. Anyway, fast forward to this week and the troublesome channels don't even show up anymore when tvheadend scans the muxes! I know that lcn 112 should contain HBO2, but tvheadend says:

Jan 07 08:32:22 soekris tvheadend10610: mpegts: 396000 - starting for 'initscan' (weight 2)
Jan 07 08:32:22 soekris tvheadend10610: mpegts: 396000 - tuning on /dev/dvb/adapter0/frontend0
Jan 07 08:32:22 soekris tvheadend10610: subscription: 'initscan' subscribing to mux, weight: 2, adapter: '/dev/dvb/adapter0/frontend0', network: 'Ziggo', mux: '396000'
Jan 07 08:32:37 soekris tvheadend10610: mpegts: 396000 - initial scan no data, failed

Is there a way to force tvheadend to take a closer look into that mux? And is there a way to see if this is caused by a buggy driver or the dvb rewrite?

Files

Download all files
tvh.log (1.34 MB) tvh.log tvheadend --trace mpegts,linuxdvb,pat -l tvh.log Koen Kooi, 2014-01-07 09:27
tvh.log (20.3 KB) tvh.log Ivan Angelov, 2014-01-15 21:43
syslog discover 28E2.txt (59.7 KB) syslog discover 28E2.txt muxes added that have no services Rob vh, 2014-02-03 13:14
tvh.log (348 KB) tvh.log Viktor Kuzmin, 2014-07-06 23:04
tvh.log (348 KB) tvh.log Viktor Kuzmin, 2014-07-06 23:05
Actions
Copy link

Also available in: Atom PDF