ProSieben HD with caids0=0x098c but what about the others that are needed for testing??
Use only the caid which your smartcard supports as parameter to modprobe vtunerc
ProSieben HD with caids0=0x098c but what about the others that are needed for testing??
Use only the caid which your smartcard supports as parameter to modprobe vtunerc
Use only the caid which your smartcard supports as parameter to modprobe vtunerc
modprobe vtunerc caids0=0x186a ? for ProSieben HD
modprobe vtunerc caids0=0x186a ? for ProSieben HD
If that is the caid your smartcard handles: yes. Maybe you can find in the net lists of caids and smartcards ....
If that is the caid your smartcard handles: yes. Maybe you can find in the net lists of caids and smartcards ....
I'm just not sure if Joe_D has already integrated all the possibilities into vtuner-ng code / git?
The vTuner CAID is independent of the real CAID. This can only cause problems if the selected vTuner CAID is "removed" due to an update. If I use CAID 0x98C, I can "switch" to 160 channels. With CAID 0x186a, it's 53. Whether these can be decoded is still determined by the "physical CAM." To avoid timeouts, there is the option to specify individual SIDs, which allows for pre-filtering.
With 0x98C is switch to ORF1
Aug 31 09:09:41 vdr vdr: [3309] switching to channel 1120 S19.2E-1-1007-4911 (ORF1 HD)
Aug 31 09:09:41 vdr vdr: [3309] CAM 1: assigned to device 1
Aug 31 09:09:42 vdr vdr: [3308] device 1 TS buffer thread ended (pid=3300, tid=3308)
Aug 31 09:09:42 vdr vdr: [3307] buffer stats: 1780924 (10%) used
Aug 31 09:09:42 vdr vdr: [3307] device 1 receiver thread ended (pid=3300, tid=3307)
Aug 31 09:09:42 vdr vdr: [3417] device 1 receiver thread started (pid=3300, tid=3417, prio=high)
Aug 31 09:09:42 vdr vdr: [3418] device 1 TS buffer thread started (pid=3300, tid=3418, prio=high)
Aug 31 09:09:42 vdr vdr: [3309] SVDRP vdr < 127.0.0.1:36182 connection closed
Aug 31 09:09:42 vdr vdr: [3309] SVDRP vdr < 127.0.0.1:36182 server destroyed
Aug 31 09:09:44 vdr vdr: [3300] retuning due to modification of channel 1120 (ORF1 HD)
Aug 31 09:09:44 vdr vdr: [3300] switching to channel 1120 S19.2E-1-1007-4911 (ORF1 HD)
Aug 31 09:09:44 vdr vdr: [3300] CAM 1: unassigned from device 1
Aug 31 09:09:44 vdr vdr: [3300] CAM 1: assigned to device 1
Aug 31 09:09:44 vdr vdr: [3418] device 1 TS buffer thread ended (pid=3300, tid=3418)
Aug 31 09:09:44 vdr vdr: [3417] buffer stats: 160364 (0%) used
Aug 31 09:09:44 vdr vdr: [3417] device 1 receiver thread ended (pid=3300, tid=3417)
Aug 31 09:09:44 vdr vdr: [3419] device 1 receiver thread started (pid=3300, tid=3419, prio=high)
Aug 31 09:09:44 vdr vdr: [3420] device 1 TS buffer thread started (pid=3300, tid=3420, prio=high)
Display More
And i switch to Prosieben HD:
Aug 31 09:12:09 vdr vdr: [3309] switching to channel 1127 S19.2E-1-1017-61301 (ProSieben HD)
Aug 31 09:12:09 vdr vdr: [3309] CAM 1: assigned to device 1
Aug 31 09:12:09 vdr vdr: [3464] device 1 TS buffer thread ended (pid=3300, tid=3464)
Aug 31 09:12:09 vdr vdr: [3463] buffer stats: 0 (0%) used
Aug 31 09:12:09 vdr vdr: [3463] device 1 receiver thread ended (pid=3300, tid=3463)
Aug 31 09:12:09 vdr vdr: [3466] device 1 receiver thread started (pid=3300, tid=3466, prio=high)
Aug 31 09:12:09 vdr vdr: [3309] SVDRP freetz < 127.0.0.1:35448 connection closed
Aug 31 09:12:09 vdr vdr: [3309] SVDRP freetz < 127.0.0.1:35448 server destroyed
Aug 31 09:12:09 vdr vdr: [3467] device 1 TS buffer thread started (pid=3300, tid=3467, prio=high)
Aug 31 09:12:11 vdr vdr: [3300] retuning due to modification of channel 1127 (ProSieben HD)
Aug 31 09:12:11 vdr vdr: [3300] switching to channel 1127 S19.2E-1-1017-61301 (ProSieben HD)
Aug 31 09:12:11 vdr vdr: [3300] CAM 1: unassigned from device 1
Aug 31 09:12:11 vdr vdr: [3300] CAM 1: assigned to device 1
Aug 31 09:12:11 vdr vdr: [3467] device 1 TS buffer thread ended (pid=3300, tid=3467)
Aug 31 09:12:11 vdr vdr: [3466] buffer stats: 100204 (0%) used
Aug 31 09:12:11 vdr vdr: [3466] device 1 receiver thread ended (pid=3300, tid=3466)
Aug 31 09:12:11 vdr vdr: [3468] device 1 receiver thread started (pid=3300, tid=3468, prio=high)
Aug 31 09:12:11 vdr vdr: [3469] device 1 TS buffer thread started (pid=3300, tid=3469, prio=high)
Display More
I cannot switch to a channel with "unsupported" caids:
Aug 31 09:14:08 vdr vdr: [3309] switching to channel 1101 S19.2E-1-1043-12522 (Eurosport 1 HD Austria)
Aug 31 09:14:08 vdr vdr: [3309] CAM 1: unassigned from device 1
Aug 31 09:14:08 vdr vdr: [3309] SVDRP vdr < 127.0.0.1:52418 connection closed
Aug 31 09:14:08 vdr vdr: [3309] SVDRP vdr < 127.0.0.1:52418 server destroyed
Aug 31 09:14:08 vdr vdr: [3489] device 1 TS buffer thread ended (pid=3300, tid=3489)
Aug 31 09:14:08 vdr vdr: [3488] buffer stats: 174276 (1%) used
Aug 31 09:14:08 vdr vdr: [3488] device 1 receiver thread ended (pid=3300, tid=3488)
Aug 31 09:14:08 vdr vdr: [3300] info: Kanal nicht verfügbar!
I'm just not sure if Joe_D has already integrated all the possibilities into vtuner-ng code / git?
I included all code to be able to switch to decoded channels. And that works pretty good! I don't have any decryption hardware, so i can't do any further codings...
What i'm not able to test and what the_man should do is to extend the satip program in a way that the transmitted pmt-pid gets send out in a proper way.
I included all code to be able to switch to decoded channels. And that works pretty good! I don't have any decryption hardware, so i can't do any further codings...
What i'm not able to test and what the_man should do is to extend the satip program in a way that the transmitted pmt-pid gets send out in a proper way.
Hi,
I just had time to test it. Please, confirm i'm doing it right.
Or maybe missed/misunderstanded something.
I have cloned the git repo vtuner-ng, switched to the `develop` branch.
cd kernel
make clean && make && make install
modprobe vtunerc caids0=0x1843
[ 722.684755] virtual DVB adapter driver, version 2.0, (c) 2021 Honza Petrous, SmartImp.cz
[ 722.691898] dvbdev: DVB: registering new adapter (vTuner proxy)
[ 722.694140] (NULL device *): DVB: registering adapter 0 frontend 0 (vTuner proxyFE DVB-Multi)...
[ 722.696650] vtunerc0: found caids 1843 for CAM slot0
[ 722.700902] vtunerc0: registered /dev/vtunerc0
[ 722.701274] dvb_ca_en50221: dvb_ca adapter 0: DVB CAM detected and initialised successfully
ls /dev/dvb/adapter0/
ca0 demux0 dvr0 frontend0
Start the VDR:
vdr -v /var/lib/vdr -c /etc/vdr --device 0 -L /usr/lib/vdr/plugins -P"streamdev-server" -l 4
In logs i see:
Sep 2 13:18:48 ddvt vdr: [4498] CAM 1: module ready
Sep 2 13:18:48 ddvt vdr: [4498] CAM 1: vtuner-ng, 01, 0001, 0815
Sep 2 13:18:49 ddvt vdr: [4498] CAM 1: system ids: 1843
Sep 2 13:18:49 ddvt vdr: [4498] CAM 1: replies to QUERY - multi channel decryption (MCD) possible
Sep 2 13:18:58 ddvt vdr: [4495] loading /var/cache/vdr/cam.data
Sep 2 13:18:58 ddvt vdr: [4495] CAM 1: ready, master (vtuner-ng)
Sep 2 13:18:58 ddvt vdr: [4495] switching to channel 1 S19.2E-1-1017-61301 (ProSieben HD
Now i go to satip section:
cd ../satip
make clean && make && make install
And run it:
/usr/local/bin/satip -s 192.168.0.22 -D DVBS2 -d /dev/vtunerc0 -f 1 -l 3
Open the VLC with the playlist:
http://192.168.0.52:3000/channels.m3u
Got a list of channels, and can Play the FTA channels.
When I switched to the Encrypted one, I expected to get the PTM in
satip_vtuner.c -> Line 249
...
DEBUG(MSG_NET,"got PMT: %i\n", msg->body.pidlist[i] & 0x1FFF);
But there is nothing.
At the same time, in msg->body.pidlist[i] i see all pids:
Sep 02 13:42:05 [6495 satip_vtuner.c:255] debug: MSG_SET_PIDLIST:
Sep 02 13:42:05 [6495 satip_vtuner.c:258] debug: 18
Sep 02 13:42:05 [6495 satip_vtuner.c:258] debug: 20
Sep 02 13:42:05 [6495 satip_vtuner.c:258] debug: 0
Sep 02 13:42:05 [6495 satip_vtuner.c:258] debug: 17
Sep 02 13:42:05 [6495 satip_vtuner.c:258] debug: 16
Sep 02 13:42:05 [6495 satip_vtuner.c:258] debug: 511
Sep 02 13:42:05 [6495 satip_vtuner.c:258] debug: 515
Sep 02 13:42:05 [6495 satip_vtuner.c:258] debug: 97 --> this one is real PMT for this channel.
Sep 02 13:42:05 [6495 satip_vtuner.c:258] debug: 33
Sep 02 13:42:05 [6495 satip_vtuner.c:258] debug: 19
---------------------------------------------------------
Thanks.
the_man Sorry, i introduced a bug ...
the_man Sorry, i introduced a bug ..
No problem. That's absolutely fine for development.
No problem. That's absolutely fine for development.
Ok, you can try again ![]()
Ok, you can try again
Good, now I have gotten the PMT.
I will write feedback when i implement that into the rtp uri.
Thanks!
Hier ist noch ein Dokument, was die Interaktion mit dem CI erklärt:
https://download.digital-devices.eu/download/dokum…onet_ci_en.html
Demnach muss schon beim Start des Streams das x_pmt (und bei Bedarf x_ci) gesetzt werden weil das CI später nicht mehr "attached" werden kann. Das erklärt auch den Error 455 ....
Demnach muss schon beim Start des Streams das x_pmt (und bei Bedarf x_ci) gesetzt werden weil das CI später nicht mehr "attached" werden kann. Das erklärt auch den Error 455 ....
Das ist für das satip Programm kein Problem, das kann ja dann einfach nochmals den Stream öffnen mit dem x_pmt
Beim satip-Plugin sieht das etwas anders aus, da muss einiges umgebaut werden und einige wollen alle Streams dauerhaft beziehen um die Tuner zu reservieren, was dann nicht mehr geht.
Nach Rücksprache mit DD werde ich die Box am Freitag retournieren. Bis dahin stehen wir
z.V.
Ich könnte meine OctopusNet für weitere Tests zur Verfügung stellen. Hilft das was?
Hi all,
So, looks like it works.
But not very stable.
Say if I switch encrypted channels fast, sometimes I do not receive the PMT PID
or receive the PMT PID from the previous channel.
If I stay on the channel for a while and then switch, mostly it gets the PMT, and descrambling works.
If I switch from FTA to an Encrypted channel, it also most cases works well.
To summarize:
- First step is done.
- need to improve the PMT receiving
- need to add Cleaning of PMT if channel is FTA
Some presentations are here:
https://drive.google.com/file/d/10m1y6s…iew?usp=sharing
PS. It is all about the SPTS.
Hier ist noch ein Dokument, was die Interaktion mit dem CI erklärt:
Hab' ich mir nun auch mal angeschaut. Also dämlicher kann man das ganze wohl nicht gestalten ![]()
Anstatt einfach ein CI dynamisch zu belegen bei addpids=1920,1921,0,107,1925&x_pmt=107 muss schon "vorher" das CI auf dem Stream "festgenagelt" werden mit x_pmt=0 ![]()
Da frage ich mich dann wenn über diesen Stream etwas unverschlüsseltes aufgenommen wird, ist das CI dann dauerblockiert? Oder hilft hier die Device-Auswahl im vdr das zu verhindern?
Lustigerweise wurde vergessen eine Möglichkeit zu schaffen das CI von einem Stream wieder zu "entnageln", z.B. mit x_ci=0 oder x_pmt=-1 - so wie es aussieht muss das CI mit einem Teardown gekickt werden. Bislang erstellt das satip-Programm einen Stream der erst abgebaut wird wenn der VDR ihn nicht mehr verwendet. Bei Live-Fernsehen also nie. Die rasanten Umschaltzeiten haben mich darin bestätigt.
Und auch so Vorgaben wie "use the following sequence exactly as specified" mit der obligatorischen Vorgabe die pmt-Pid als letztes zu entfernen ... wer kommt denn auf sowas?? ![]()
Ich könnte meine OctopusNet für weitere Tests zur Verfügung stellen. Hilft das was?
Denke schon, musst dann aber auch vtuner aufsetzen...
Joe_D Can i commit the new branch to the /vtuer-ng/ repo?
Or it is better to create a fork?
So, looks like it works
Would be helpful for me to see logs of the satip program ..
Or it is better to create a fork?
It's better to create a fork ..
Here it is -> `xpmt` branch :
https://github.com/paliydmn/vtuner-ng/tree/xpmt
As for log.
I'll try to make it today.
Don’t have an account yet? Register yourself now and be a part of our community!