Closed stahlhelmknacker closed 3 years ago
It's hard thing for me as first - I don't have such hardware and secondly - a free time for develop this feature.... :( Nevertheless I am open for any submission which are tested and are enabling such a feature. I assume oscam also need to handle this MTD properly. No idea if it is doing so currently... I am leaving this open for reference...
I have researched this question. MTD in the form made in vdr will not work with dvbapi plugin and oscam. The functionality of the MTD must be done in the Oscam itself. Vdr changes real pids and sid to unique ones in the case of working with MTD, but oscam only needs real pids and sid. Dvbapi plugin must transfer real pids to oscam, so it is impossible to make support for MTD at the dvbapi plugin level. This issue can be closed, and need made a topic on the oscam forum.
Thank you for your research. Closing.
Hello Manio, Thank you very much for your work! Since VDR version 2.4.0, Multiple Transponder Decryption (MTD) is supported (http://www.tvdr.de/changelog.htm). Would there be a possibility to add this feature to the DVBAPI plugin?
Currently, when i start a second stream the de-scrambling of the stream is not working. If I am switching to a different channel on the same Transponder it works (so Multiple Channel Decryption is working). I am posting the Log Files of the VDR + OSCAM:
Initialization VDR
Decrypt Channel 1 on Device 1
Decrypt Channel 2 on Device 2
OSCAM Log
MTD Info VDR (mtd.h)
Multiple Transponder Decryption (MTD) is the method of sending TS packets
from channels on different transponders to one single CAM for decryption. While decrypting several channels from the same transponder ("Multi Channel Decryption") is straightforward, because the PIDs are unique within one transponder, channels on different transponders might use the same PIDs for different streams.
Here's a summary of how MTD is implemented in VDR:
Identifying the relevant source code
The actual code that implements the MTD handling is located in the files mtd.h and mtd.c. There are also a few places in ci.[hc], device.c and menu.c where things need to be handled differently for MTD. All functions and variables that have to do with MTD have the three letters "mtd" (upper- and/or lowercase) in their name, so that these code lines can be easily identified if necessary.
What a plugin implementing a cCiAdapter/cCamSlot needs to do
If an implementation of cCiAdapter/cCamSlot supports MTD, it needs to fulfill the following requirements:
Thank you very much!