Project

General

Profile

Bug #1380

Two identical adapters seen with identical name drive to adapter already in use in xbmc

Added by Szymon Życińśki about 12 years ago. Updated about 12 years ago.

Status:
Invalid
Priority:
High
Assignee:
Category:
General
Target version:
-
Start date:
2012-11-02
Due date:
% Done:

0%

Estimated time:
Found in version:
3.2
Affected Versions:

Description

I have two identical tuners in ubuntu pid&vid 048d:9006 (ite9135) tvheadend 3.2 shows both in configuration as "ite 9135(9006) generic_1". Both devices configured to use the same multiplexes. If i recors with one and want to switch channel the second one is in use by other subscription. When i used af9015 and only one ite9135 there were no problems. Maybe it is becouse both are seen with exactly the same name?

In log:
Nov 02 22:00:40 dvr: "Dance Chart" on "ESKA TV" starting at 2012-11-02 20:58:00, scheduled for recording by "xbmc"
Nov 02 22:00:40 dvr: "Dance Chart" on "ESKA TV" recorder starting
Nov 02 22:00:40 subscription: No transponder available for subscription "DVR: Dance Chart" to channel "ESKA TV"
Nov 02 22:00:40 dvr: Recording unable to start: "Dance Chart": Adapter in use by other subscription

The second adapter even that is seen as /dev/dvb/adapter1 (while currently recording is on /dev/dvb/adapter0) is inactive at all.

History

#1

Updated by Szymon Życińśki about 12 years ago

This is really weird. Few restarts and error was still active but .... i removed one of the tuners while TVHeadEnd was recording on another. Then plug it back and .... i have three same named tuners on the list but ... two of them (with links to /dev/dvb/adapter*) WORKS!

Hope the tuner manager will be available in 3.4. The tuner nameing mechanism is weird.

#2

Updated by Szymon Życińśki about 12 years ago

Plug in third adapter af9015 and now issue returned.

My /dev/dvb/ looks like:
.:
razem 0
drwxr-xr-x 5 root root 100 lis 2 22:39 .
drwxr-xr-x 16 root root 4300 lis 2 22:39 ..
drwxr-xr-x 2 root root 120 lis 2 22:39 adapter0
drwxr-xr-x 2 root root 120 lis 2 22:39 adapter1
drwxr-xr-x 2 root root 120 lis 2 22:39 adapter2

./adapter0:
razem 0
drwxr-xr-x 2 root root 120 lis 2 22:39 .
drwxr-xr-x 5 root root 100 lis 2 22:39 ..
crw-rw----+ 1 root video 212, 0 lis 2 22:39 demux0
crw-rw----+ 1 root video 212, 1 lis 2 22:39 dvr0
crw-rw----+ 1 root video 212, 3 lis 2 22:39 frontend0
crw-rw----+ 1 root video 212, 2 lis 2 22:39 net0

./adapter1:
razem 0
drwxr-xr-x 2 root root 120 lis 2 22:39 .
drwxr-xr-x 5 root root 100 lis 2 22:39 ..
crw-rw----+ 1 root video 212, 4 lis 2 22:39 demux0
crw-rw----+ 1 root video 212, 5 lis 2 22:39 dvr0
crw-rw----+ 1 root video 212, 7 lis 2 22:39 frontend0
crw-rw----+ 1 root video 212, 6 lis 2 22:39 net0

./adapter2:
razem 0
drwxr-xr-x 2 root root 120 lis 2 22:39 .
drwxr-xr-x 5 root root 100 lis 2 22:39 ..
crw-rw----+ 1 root video 212, 8 lis 2 22:39 demux0
crw-rw----+ 1 root video 212, 9 lis 2 22:39 dvr0
crw-rw----+ 1 root video 212, 11 lis 2 22:39 frontend0
crw-rw----+ 1 root video 212, 10 lis 2 22:39 net0

All adapters joined to the same antena via http://images.dipol.com.pl/pict/r60104+.jpg and all got 100% SNR, copied the same muxes to all of them. Services found but it seems that multituner setup was broken in this release. While i record if i try to watch program from different mux i see in log:

Nov 02 23:10:22 htsp: 192.168.1.191: Welcomed client software: XBMC Media Center
Nov 02 23:10:22 htsp: 192.168.1.191 [ XBMC Media Center ]: Identified as user xbmc
Nov 02 23:10:22 htsp: 192.168.1.191 [ xbmc | XBMC Media Center ]: Privileges raised
Nov 02 23:10:22 subscription: No transponder available for subscription "192.168.1.191 [ xbmc | XBMC Media Center ]" to channel "Polsat"

#3

Updated by Szymon Życińśki about 12 years ago

You can delete. No channels were not mapped. I was sure that on the same mux channel mapping was copied with mux.

#4

Updated by Adam Sutton about 12 years ago

  • Status changed from New to Invalid
  • Affected Versions deleted (3.2)

Closed as user reported this was human error in the config. Hopefully the updates in 3.4 (when I get around to them) will make this sort of thing easier to manage!

Adam

Also available in: Atom PDF