Project

General

Profile

Bug #4562

bouquet import - using enigma2 (.tv) formatted files

Added by Toni Meyer about 7 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Service Mapping
Target version:
-
Start date:
2017-08-29
Due date:
% Done:

0%

Estimated time:
Found in version:
Tvheadend 4.3-308~g063765e
Affected Versions:

Description

I use Tvheadend 4.3-308~g063765e
I want to import my own bouquet using enigma2 (.tv) formatted files.

Whith DVB-S bouquets works fine.
For exaple "userbouquet.ard_zdf.tv" :

#NAME öffentlich - rechtlich
#SERVICE 1:64:1:0:0:0:0:0:0:0:
#DESCRIPTION ARD-ZDF SAT
#SERVICE 1:0:1:6dca:44d:1:c00000:0:0:0:
#SERVICE 1:0:1:6d66:437:1:c00000:0:0:0:
#SERVICE 1:0:1:6dcb:44d:1:c00000:0:0:0:
#SERVICE 1:0:1:11fc:3fd:1:c00000:0:0:0:
#SERVICE 1:0:1:7032:41b:1:c00000:0:0:0:
#SERVICE 1:0:1:6f47:445:1:c00000:0:0:0:
#SERVICE 1:0:1:7031:41b:1:c00000:0:0:0:
#SERVICE 1:0:1:6d6b:437:1:c00000:0:0:0:
#SERVICE 1:0:1:6d6e:437:1:c00000:0:0:0:
#SERVICE 1:0:1:6d67:437:1:c00000:0:0:0:
#SERVICE 1:0:1:6d68:437:1:c00000:0:0:0:
#SERVICE 1:0:1:7034:41b:1:c00000:0:0:0:
#SERVICE 1:0:1:7035:41b:1:c00000:0:0:0:
#SERVICE 1:0:1:6e40:431:1:c00000:0:0:0:
#SERVICE 1:0:1:6e46:431:1:c00000:0:0:0:
#SERVICE 1:0:1:6dd1:44d:1:c00000:0:0:0:
#SERVICE 1:0:1:6f76:457:1:c00000:0:0:0:
#SERVICE 1:0:1:6e2d:431:1:c00000:0:0:0:
#SERVICE 1:0:1:6f46:445:1:c00000:0:0:0:
#SERVICE 1:0:1:6dcc:44d:1:c00000:0:0:0:

->parsed Enigma2 bouquet ARD-ZDF (20 services)

Whith DVB-C bouquets wont work.
For exaple "userbouquet.ard_zdf.tv" :

#NAME öffentlich - rechtlich
#SERVICE 1:64:1:0:0:0:0:0:0:0:
#DESCRIPTION ARD-ZDF Cable
#SERVICE 1:0:1:6dca:44d:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6d66:437:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6dcb:44d:1:ffff0000:0:0:0:
#SERVICE 1:0:1:7034:41b:1:ffff0000:0:0:0:
#SERVICE 1:0:1:7035:41b:1:ffff0000:0:0:0:
#SERVICE 1:0:1:7031:41b:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6f47:445:1:ffff0000:0:0:0:
#SERVICE 1:0:1:7032:41b:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6D6E:437:1:FFFF0000:0:0:0:
#SERVICE 1:0:1:6d6e:437:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6d67:437:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6d68:437:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6dcc:44d:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6e44:431:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6e40:431:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6e2d:431:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6f46:445:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6dd1:44d:1:ffff0000:0:0:0:
#SERVICE 1:0:1:6dcf:44d:1:ffff0000:0:0:0:

->parsed Enigma2 bouquet HD ARD-ZDF (0 services)

The "tv-files" are created with Dreamset and the channels works correct at Dreabox.

Sorry for my english :-(
Can anyone Help me please?

Files

test1.patch (988 Bytes) test1.patch Jaroslav Kysela, 2017-08-31 16:06

History

#1

Updated by Jaroslav Kysela about 7 years ago

I don't see why there's issue for DVB-C. The matching code is in mpegts_service_find_e2() in src/input/mpegts/mpegts_service.c . Could you check if TSID/ONID/SID numbers are correctly detected by tvh ?

#2

Updated by Toni Meyer about 7 years ago

I tested now all with one channel (1:0:1:6DCA:44D:1:FFFF0000:0:0:0:)

TSID/ONID/SID/NS

- Transport stream ID (TSID)
- Original Network ID (ONID)
- Service ID (SID)
- Namespace (NS)

#SERVICE 1:0:    DVB_TYPE    :SID    :TSID    :ONID    :NS        :0:0:0:
#SERVICE 1:0:    1        :6dca    :44d    :1    :ffff0000    :0:0:0: - >Cable

In Webinterface @Services = Service ID (SID) is 280106 DEZ = 6DCA HEX ...should be OK

In Webinterface @Muxes = Transport stream ID (TSID) is 1101 DEZ = 44D HEX ...should be OK

In Webinterface @Muxes = Original Network ID (ONID) is 1 ...should be OK

Where can i see the correct Namespace (NS)?

If i map the channel ( 1:0:1:6DCA:44D:1:FFFF0000:0:0:0: ) manually, i can stream correctly and the corret picon will be shown

picon://1_0_1_6DCA_44D_1_FFFF0000_0_0_0.png

#3

Updated by Jaroslav Kysela about 7 years ago

Please, try attached test1.patch (apply the patch using 'cat test1.patch | patch -p1' in the source tree). Report back the lines from tvh's log.

Also available in: Atom PDF