Reply to thread

Message

<blockquote data-quote="Django.edwards" data-source="post: 735826" data-attributes="member: 98942">[USER=82144]mm1352000[/USER]So I did some tests with your libraries this morning. See my logs.What I observed is that with the version 0.1a not all channels are decrypted. With 0.1b all channels which are on the same transponder works fine. With the astoncrypt module, everything works fine, when I put my original module in, there is a difference on his behavior. The module decrypt 2 channels at the same time, but I observed that, each time when I switch a channel, both channels changes from &quot;scrambled no&quot; to &quot;scrambled yes&quot; and then back to &quot;scrambled no&quot;. So timeshifting is not a problem. The first user who is watching a channel has a little glitch at the moment when I switch between channels. Thats the same for the recording, theres this glitch also. With the astoncrypt this does not happen.Hope this can help you.</blockquote>

[QUOTE="Django.edwards, post: 735826, member: 98942"] [USER=82144]mm1352000[/USER] So I did some tests with your libraries this morning. See my logs. What I observed is that with the version 0.1a not all channels are decrypted. With 0.1b all channels which are on the same transponder works fine. With the astoncrypt module, everything works fine, when I put my original module in, there is a difference on his behavior. The module decrypt 2 channels at the same time, but I observed that, each time when I switch a channel, both channels changes from "scrambled no" to "scrambled yes" and then back to "scrambled no". So timeshifting is not a problem. The first user who is watching a channel has a little glitch at the moment when I switch between channels. Thats the same for the recording, theres this glitch also. With the astoncrypt this does not happen. Hope this can help you. [/QUOTE]

Verification