Beiträge anzeigen

Diese Sektion erlaubt es ihnen alle Beiträge dieses Mitglieds zu sehen. Beachten sie, dass sie nur solche Beiträge sehen können, zu denen sie auch Zugriffsrechte haben.


Nachrichten - sundtekdsm7user

Seiten: [1]
1
Treiber / Re: Sundtek Synology Treiber Paket FAQ
« am: Juni 14, 2024, 07:03:57 Nachmittag »
Vielen Dank für die Befehle, super Möglichkeit zum Testen!

Leider geht es nach dem Scan noch immer nicht. Sender "Das Erste HD" ist zwar da in der tvh App, aber es kommt kein Bild bzw. "Wiedergabefehler".

Der Scan ergibt folgendes Ergebnis:

./mediaclient -m DVBC -f 330000000 -M Q256 -S 6900000
Using device: /dev/dvb/adapter0/frontend0
Checking for lock:
. [LOCKED]

> ./mediaclient --tsscan /dev/dvb/adapter0/dvr0
media scan tp: 0
** NO GROUP GIVEN **
** NO GROUP GIVEN **
** NO GROUP GIVEN **
** NO GROUP GIVEN **
PMT PID: 0x13ec
  Program Number: 0x283d
  TransportstreamID: 1051
  Encrypted: No
  Service type: 19
  Service running: Yes
  Provider Name: ARD
  Service Name: Das Erste HD
    --> 0x0492 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections)
    --> 0x0498 (ISO/IEC 13818-6 type C)
    --> 0x087b (ISO/IEC 13818-6 type B)
    --> 0x087c (ISO/IEC 13818-6 type B)
    --> 0x13ed (27)
    --> 0x13ee (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x13ef (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x13f0 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x13f1 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x13f3 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
PMT PID: 0x140a
  Program Number: 0x2840
  TransportstreamID: 1051
  Encrypted: No
  Service type: 19
  Service running: Yes
  Provider Name: ARD
  Service Name: SWR RP HD
    --> 0x055a (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections)
    --> 0x087b (ISO/IEC 13818-6 type B)
    --> 0x09ac (ISO/IEC 13818-6 type C)
    --> 0x140b (27)
    --> 0x140c (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x140d (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x140e (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x140f (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x1411 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
PMT PID: 0x157c
  Program Number: 0x6eac
  TransportstreamID: 1051
  Encrypted: No
  Service type: 19
  Service running: Yes
  Provider Name: ARD
  Service Name: WDR HD Köln
    --> 0x087b (ISO/IEC 13818-6 type B)
    --> 0x0942 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections)
    --> 0x0948 (ISO/IEC 13818-6 type C)
    --> 0x157d (27)
    --> 0x157e (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x157f (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x1580 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x1581 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x1583 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
PMT PID: 0x012c
  Program Number: 0x6ee2
  TransportstreamID: 1051
  Encrypted: No
  Service type: 1
  Service running: Yes
  Provider Name: ARD
  Service Name: SR Fernsehen
    --> 0x0515 (ITU-T Rec. H.262 | ISO/IEC 13818-2 Video or ISO/IEC 11172-2 constrained parameter video stream)
    --> 0x0516 (ISO/IEC 11172 Audio)
    --> 0x0517 (ISO/IEC 11172 Audio)
    --> 0x0518 (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets containing private data)
    --> 0x087b (ISO/IEC 13818-6 type B)
    --> 0x0b9a (ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections)
    --> 0x0ba0 (ISO/IEC 13818-6 type C)
Total found: 4 PMTs (incl. unknown 0x0000)
Scan finished after 13 packets (2444 bytes)

Bei der Signalstärke ist BER gleich 0, aber es steht immer "Locked: Yes". Was bedeutet das?

...
SIGNAL: [........................         ] ( 72%) BER:      0 CNR: 35.00 FREQ: 330000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
...

2
Treiber / Re: Sundtek Synology Treiber Paket FAQ
« am: Juni 14, 2024, 05:01:04 Nachmittag »
Es fehlt "Das Erste HD" sowie die anderen Sender auf Frequenz 330 MHz (SWR HD, WDR HD, SR SD), obwohl der Mux mit Frequenz 330 laut tvheadend als Suchergebnis "ok" hat und aktiviert ist.

3
Treiber / Re: Sundtek Synology Treiber Paket FAQ
« am: Juni 14, 2024, 07:49:24 Vormittag »
Nach Komplettlöschung und Neuinstallation von tvheadend findet er den Tuner. Klasse, vielen Dank!

Aber leider gibt es noch Probleme, alle Sender funktioniere noch nicht...

4
Treiber / Re: Sundtek Synology Treiber Paket FAQ
« am: Juni 13, 2024, 08:41:39 Nachmittag »
Danke, aber genau nach der Anleitung bin ich vorgegangen. Ich habe eben nochmal alles wiederholt und nach Anleitung neu installiert. Das Ergebnis ist das gleiche wie in meinem letzten Post geschrieben und in den log-Dateien dargestellt.

Das tvheadend log zeigt den Fehler, dass er "/dev/dvb/adapter0/frontend0" nicht öffnen kann, obwohl der sundtek Stick aber offensichtlich erkannt wird.

Im /var/log/messages gibt es folgende Fehlermeldungen (nicht sicher, ob sie damit etwas zu tun haben):

2024-06-13T19:12:58+02:00 KDiskStation synopkgctl[16338]: io_utils.cpp:58 Failed to read, Resource temporarily unavailable
2024-06-13T19:12:58+02:00 KDiskStation synopkgctl[16338]: /run/synoscgi-fastapi.sock APIRunner.cpp:1872 recv broken
2024-06-13T19:13:05+02:00 KDiskStation synopkgctl[14524]: io_utils.cpp:58 Failed to read, Resource temporarily unavailable
2024-06-13T19:13:05+02:00 KDiskStation synopkgctl[14524]: /run/synoscgi-fastapi.sock APIRunner.cpp:1872 recv broken
2024-06-13T19:13:07+02:00 KDiskStation synopkgctl[12134]: io_utils.cpp:58 Failed to read, Resource temporarily unavailable
2024-06-13T19:13:07+02:00 KDiskStation synopkgctl[12134]: /run/synoscgi-fastapi.sock APIRunner.cpp:1872 recv broken
2024-06-13T19:14:49+02:00 KDiskStation synouser[18316]: synouser.c:1114 ret 0
2024-06-13T19:23:32+02:00 KDiskStation tvheadend[26145]: config: unknown subsystem '""'
2024-06-13T19:23:37+02:00 KDiskStation tvheadend[26145]: linuxdvb: unable to open /dev/dvb/adapter0/frontend0
2024-06-13T19:39:31+02:00 KDiskStation tvheadend[11278]: config: unknown subsystem '""'
2024-06-13T19:39:40+02:00 KDiskStation tvheadend[11278]: linuxdvb: unable to open /dev/dvb/adapter0/frontend0
2024-06-13T20:04:47+02:00 KDiskStation tvheadend[3082]: config: unknown subsystem '""'

ls -l vom device sieht wie folgt aus:

> ls -l /dev/dvb/adapter0/frontend0
crwxrwxrwx 1 root root 212, 0 Jun 13 20:36 /dev/dvb/adapter0/frontend0

Der Treiber scheint auch grundsätzlich zu funktionieren:

>/volume1/@appstore/sundtek/opt/bin/mediaclient -C
Using device: /dev/dvb/adapter0/frontend0
Audio processing: Audio playback is handled by the driver
> /volume1/@appstore/sundtek/opt/bin/mediaclient --blindscan=/dev/dvb/adapter0/frontend0
Succeeded this device supports Hardware Blindscan


5
Treiber / Re: Sundtek Synology Treiber Paket FAQ
« am: Juni 13, 2024, 07:50:44 Nachmittag »
Hallo,
ich versuche bei meiner Synology DS218play mit DSM7 den Sundtek MediaTV Pro III (EU) DVB-C USB Stick mit tvheadend zum Laufen zu bekommen.

Ich habe wie in der Anleitung angegeben nach Installation des Sundtek Driver packages "sudo /var/packages/sundtek/scripts/allowroot.sh" erfolgreich ausgeführt.

Der MediaTV Pro III an der Synology wird auch erkannt laut lsusb:

> lsusb
...
|__usb4          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (Linux 4.4.302+ xhci-hcd xHCI Host Controller xhci-hcd.5.auto) hub
  |__4-1         2659:1210:4001 ef  2.00  480MBit/s 500mA 7IFs (Sundtek MediaTV Pro III (EU) U180829034033)
...

mediaclient -e sieht wie folgt aus:

> ./mediaclient -e
**** List of Media Hardware Devices ****
device 0: [MediaTV Pro III (EU)]  DVB-C, DVB-T, DVB-T2, ANALOG-TV, FM-RADIO, REMOTE-CONTROL, OSS-AUDIO, RDS
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 4-1
  [SERIAL]:
     ID: U180829034033
  [DVB-C,DVB-T,DVB-T2]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [ANALOG-TV]:
     VIDEO0: /dev/video0
     VBI0: /dev/vbi0
  [FM-RADIO]:
     RADIO0: /dev/radio0
     RDS: /dev/rds0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0
  [OSS]:
     OSS0: /dev/dsp0

Trotzdem sehe ich bei tvheadend keinen TV Adapter. Das tvheadend log zeigt den Fehler, dass er "/dev/dvb/adapter0/frontend0" nicht öffnen kann:

Starting tvheadend command tvheadend -f -C -u sc-tvheadend -g synocommunity --http_port 9981 --htsp_port 9982 -c /volume1/@appdata/tvheadend -p /volume1/@appdata/tvheadend/tvheadend.pid -l /volume1/@appdata/tvheadend/tvheadend.log --debug ""
2024-06-13 19:39:31.217 [  ERROR]:config: unknown subsystem '""'
2024-06-13 19:39:31.217 [   INFO]:main: Log started
2024-06-13 19:39:31.295 [   INFO]:http: Starting HTTP server 0.0.0.0:9981
2024-06-13 19:39:31.295 [   INFO]:htsp: Starting HTSP server 0.0.0.0:9982
2024-06-13 19:39:31.406 [   INFO]:config: loaded
2024-06-13 19:39:31.406 [   INFO]:config: scanfile (re)initialization with path <none>
2024-06-13 19:39:31.875 [   INFO]:transcode: 'video' context type registered
2024-06-13 19:39:31.875 [   INFO]:transcode: 'audio' context type registered
2024-06-13 19:39:31.875 [   INFO]:transcode: '&TVHH264Decoder' decoder helper registered
2024-06-13 19:39:31.875 [   INFO]:transcode: '&TVHTHEORADecoder' decoder helper registered
2024-06-13 19:39:31.875 [   INFO]:transcode: '&TVHAACDecoder' decoder helper registered
2024-06-13 19:39:31.875 [   INFO]:transcode: '&TVHVORBISDecoder' decoder helper registered
2024-06-13 19:39:31.875 [   INFO]:transcode: '&TVHOPUSDecoder' decoder helper registered
2024-06-13 19:39:31.875 [   INFO]:transcode: '&TVHMPEG2VIDEOEncoder' encoder helper registered
2024-06-13 19:39:31.875 [   INFO]:transcode: '&TVHH264Encoder' encoder helper registered
2024-06-13 19:39:31.875 [   INFO]:transcode: '&TVHHEVCEncoder' encoder helper registered
2024-06-13 19:39:31.875 [   INFO]:transcode: '&TVHAACEncoder' encoder helper registered
2024-06-13 19:39:32.762 [   INFO]:codec: 'mpeg2video' encoder registered
2024-06-13 19:39:33.106 [   INFO]:codec: 'mp2' encoder registered
2024-06-13 19:39:33.106 [   INFO]:codec: 'aac' encoder registered
2024-06-13 19:39:33.106 [   INFO]:codec: 'vorbis' encoder registered
2024-06-13 19:39:33.106 [   INFO]:codec: 'flac' encoder registered
2024-06-13 19:39:33.176 [   INFO]:codec: 'libx264' encoder registered
2024-06-13 19:39:33.176 [   INFO]:codec: 'libx265' encoder registered
2024-06-13 19:39:33.176 [   INFO]:codec: 'libvpx' encoder registered
2024-06-13 19:39:33.176 [   INFO]:codec: 'libvpx-vp9' encoder registered
2024-06-13 19:39:33.176 [   INFO]:codec: 'libtheora' encoder registered
2024-06-13 19:39:33.176 [   INFO]:codec: 'libvorbis' encoder registered
2024-06-13 19:39:33.176 [   INFO]:codec: 'libfdk_aac' encoder registered
2024-06-13 19:39:33.176 [   INFO]:codec: 'libopus' encoder registered
2024-06-13 19:39:33.490 [   INFO]:codec: 'webtv-aac' codec profile created
2024-06-13 19:39:33.490 [   INFO]:codec: 'webtv-h264' codec profile created
2024-06-13 19:39:33.490 [   INFO]:codec: 'webtv-vp8' codec profile created
2024-06-13 19:39:33.490 [   INFO]:codec: 'webtv-vorbis' codec profile created
2024-06-13 19:39:37.586 [   INFO]:descrambler: adding CAID 2600/FFFF as ConstCW interval 10000ms pc 20 ep default (BISS)
2024-06-13 19:39:37.586 [   INFO]:descrambler: adding CAID 0E00/FFFF as MultiPID interval 1000ms pc 2 ep default (PowerVu)
2024-06-13 19:39:37.967 [   INFO]:iptv: Using 2 input thread(s)
2024-06-13 19:39:39.648 [   INFO]:scanfile: DVB-S - loaded 1 regions with 116 networks
2024-06-13 19:39:39.649 [   INFO]:scanfile: DVB-T - loaded 46 regions with 1134 networks
2024-06-13 19:39:39.649 [   INFO]:scanfile: DVB-C - loaded 20 regions with 82 networks
2024-06-13 19:39:39.649 [   INFO]:scanfile: ATSC-T - loaded 2 regions with 13 networks
2024-06-13 19:39:39.649 [   INFO]:scanfile: ATSC-C - loaded 1 regions with 5 networks
2024-06-13 19:39:39.649 [   INFO]:scanfile: ISDB-T - loaded 2 regions with 1297 networks
2024-06-13 19:39:40.542 [  ERROR]:linuxdvb: unable to open /dev/dvb/adapter0/frontend0
2024-06-13 19:39:40.805 [   INFO]:dvr: Creating new configuration ''
2024-06-13 19:39:42.072 [   INFO]:epggrab: module uk_freesat created
2024-06-13 19:39:42.072 [   INFO]:epggrab: module uk_freesat_eit created
2024-06-13 19:39:42.072 [   INFO]:epggrab: module uk_freeview created
2024-06-13 19:39:42.072 [   INFO]:epggrab: module nz_freeview2 created
2024-06-13 19:39:42.072 [   INFO]:epggrab: module nz_freeview1 created
2024-06-13 19:39:42.072 [   INFO]:epggrab: module viasat_baltic created
2024-06-13 19:39:42.072 [   INFO]:epggrab: module Bulsatcom_39E created
2024-06-13 19:39:42.072 [   INFO]:epggrab: module uk_cable_virgin created
2024-06-13 19:39:42.072 [   INFO]:epggrab: module eit created
2024-06-13 19:39:42.072 [   INFO]:epggrab: module psip created
2024-06-13 19:39:42.081 [   INFO]:epggrab: module opentv-skyuk created
2024-06-13 19:39:42.082 [   INFO]:epggrab: module opentv-skynz created
2024-06-13 19:39:42.082 [   INFO]:epggrab: module opentv-skyit created
2024-06-13 19:39:42.083 [   INFO]:epggrab: module opentv-ausat created
2024-06-13 19:39:42.083 [   INFO]:epggrab: module xmltv created
2024-06-13 19:39:42.834 [   INFO]:spawn: Executing "/volume1/@appstore/tvheadend/bin/tv_grab_url"
2024-06-13 19:39:43.557 [   INFO]:epggrab: module /volume1/@appstore/tvheadend/bin/tv_grab_url created
2024-06-13 19:39:43.560 [   INFO]:spawn: Executing "/volume1/@appstore/tvheadend/bin/tv_grab_file"
2024-06-13 19:39:43.724 [   INFO]:epggrab: module /volume1/@appstore/tvheadend/bin/tv_grab_file created
2024-06-13 19:39:43.726 [   INFO]:spawn: Executing "/volume1/@appstore/tvheadend/bin/tv_grab_zap2epg"
2024-06-13 19:39:44.774 [   INFO]:epggrab: module /volume1/@appstore/tvheadend/bin/tv_grab_zap2epg created
2024-06-13 19:39:44.776 [   INFO]:spawn: Executing "/volume1/@appstore/tvheadend/bin/tv_grab_wg"
2024-06-13 19:39:44.853 [   INFO]:epggrab: module /volume1/@appstore/tvheadend/bin/tv_grab_wg created
2024-06-13 19:39:44.857 [   INFO]:tbl-eit: module eit - scraper disabled by config
2024-06-13 19:39:44.893 [   INFO]:epgdb: gzip format detected, inflating (ratio 138.6% deflated size 79)
2024-06-13 19:39:44.893 [   INFO]:epgdb: parsing 57 bytes
2024-06-13 19:39:44.893 [   INFO]:epgdb: loaded v3
2024-06-13 19:39:44.893 [   INFO]:epgdb:   config     1
2024-06-13 19:39:44.893 [   INFO]:epgdb:   broadcasts 0
2024-06-13 19:39:44.893 [   INFO]:dvr: Purging obsolete autorec entries for current schedule
2024-06-13 19:39:44.894 [ NOTICE]:START: HTS Tvheadend version 4.3~f32c7c5 started, running as PID:11278 UID:276776 GID:207066, CWD:/ CNF:/volume1/@appdata/tvheadend

Das Sundtek Driver Setup sieht wie folgt aus:

Enable Network Server: (aktiviert) [Win Network Driver] |
[Linux Instruction]
Only create /dev/dvb nodes for Docker
 

Install Sundtek Streaming Server

Driver Architecture:
Architecture: arm64

Detected Devices:
MediaTV Pro III (EU)

Applications accessing the device:
**** List of Media Clients ****
/dev/dvb/adapter0/frontend0:
  No client connected
/dev/dvb/adapter0/dvr0:
  No client connected
/dev/dvb/adapter0/demux0:
  No client connected
/dev/video0:
  No client connected
/dev/vbi0:
  No client connected
/dev/radio0:
  No client connected
/dev/rds0:
  No client connected
/dev/mediainput0:
  No client connected
/dev/dsp0:
  No client connected

Scanning Network for devices
IP Devicename Serial
192.168.xx.xx:0 MediaTV Pro III (EU) U180829034033 Connect

Click here to Disable user authentication with tvheadend
Click here to Enable user authentication with tvheadend

Was mache ich falsch?

Seiten: [1]