home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
Improvement Suggestions
Improving the support for KNC One + CAM
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 767392" data-attributes="member: 82144"><p>Hi Django</p><p></p><p>Thanks for starting the thread. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p>Just some brief comments for a start...</p><p></p><p></p><p>That is certainly a significant difference in the number of channels found. I did a quick analysis:</p><p></p><p></p><p></p><p>So card 1 is more reliable than card 2 on DiSEqC port 0, but it also has *massive* problems with tuning on DiSEqC port 1. It fails to find channels on a single horizontal transponder on port 1.</p><p></p><p>I also notice that both tuners *always* failed to tune transponders with modulation NBC QPSK - that is probably either an MP bug, driver bug, or hardware limitation. Very easy to find out. Please attempt to manually scan:</p><p></p><p>Frequency = 11432000</p><p>Symbol Rate = 27500</p><p>Polarisation = Vertical</p><p>Inner FEC Rate = 2/3</p><p>DiSEqC = Simple A</p><p>Pilot = Off</p><p>Roll Off = 0.35</p><p></p><p>Use different modulation values, especially QPSK and NBC QPSK (DVB-S2). If you can find a modulation that allows the tuner to lock on that transponder then please let me know and I will update the code. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>In truth, any failure to tune is very bad, and unfortunately I don't have an explanation for most of the failures. I wonder:</p><p></p><p>Are you using the latest drivers?</p><p>Is there any difference in performance when the CI modules are not connected?</p><p>Is there any difference in performance if you take one card out temporarily?</p><p>Have you tried swapping the satellite cables to the two cards? (Note you should turn the computer and any STBs off before unplugging or replugging cables.)</p><p>Is there any difference in performance of card 1 if it is connected directly to the LNB?</p><p></p><p></p><p>The likelihood of an MP code bug is relatively small here. You tried switching the smartcards and CAMs, but did you also try switching CI modules? Maybe one of the CI modules (or even the cable to the module) is not reliable. Alternatively, it is possible that the drivers don't work very well when more than one of the same card is installed in a single PC.</p><p></p><p></p><p>Now that could definitely be a bug. I will try to find some time to look at the logs.</p><p></p><p></p><p>This was a mistake on our part. We forgot to check the external DLL dependencies when we released 1.2.0b. We will be including the VC++2008 redistributable again with 1.2.0rc and for the forseeable future because some of the external DLLs are tied to VC++2008 and we are waiting for replacements from the DLL providers. Note that I received an updated KNC DLL just yesterday. The interface is slightly different to the old one (which is several years old now) so we will have to make code changes before that DLL should be included. I think it will be included with 1.3.x...</p><p></p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 767392, member: 82144"] Hi Django Thanks for starting the thread. :thx: Just some brief comments for a start... That is certainly a significant difference in the number of channels found. I did a quick analysis: So card 1 is more reliable than card 2 on DiSEqC port 0, but it also has *massive* problems with tuning on DiSEqC port 1. It fails to find channels on a single horizontal transponder on port 1. I also notice that both tuners *always* failed to tune transponders with modulation NBC QPSK - that is probably either an MP bug, driver bug, or hardware limitation. Very easy to find out. Please attempt to manually scan: Frequency = 11432000 Symbol Rate = 27500 Polarisation = Vertical Inner FEC Rate = 2/3 DiSEqC = Simple A Pilot = Off Roll Off = 0.35 Use different modulation values, especially QPSK and NBC QPSK (DVB-S2). If you can find a modulation that allows the tuner to lock on that transponder then please let me know and I will update the code. :) In truth, any failure to tune is very bad, and unfortunately I don't have an explanation for most of the failures. I wonder: Are you using the latest drivers? Is there any difference in performance when the CI modules are not connected? Is there any difference in performance if you take one card out temporarily? Have you tried swapping the satellite cables to the two cards? (Note you should turn the computer and any STBs off before unplugging or replugging cables.) Is there any difference in performance of card 1 if it is connected directly to the LNB? The likelihood of an MP code bug is relatively small here. You tried switching the smartcards and CAMs, but did you also try switching CI modules? Maybe one of the CI modules (or even the cable to the module) is not reliable. Alternatively, it is possible that the drivers don't work very well when more than one of the same card is installed in a single PC. Now that could definitely be a bug. I will try to find some time to look at the logs. This was a mistake on our part. We forgot to check the external DLL dependencies when we released 1.2.0b. We will be including the VC++2008 redistributable again with 1.2.0rc and for the forseeable future because some of the external DLLs are tied to VC++2008 and we are waiting for replacements from the DLL providers. Note that I received an updated KNC DLL just yesterday. The interface is slightly different to the old one (which is several years old now) so we will have to make code changes before that DLL should be included. I think it will be included with 1.3.x... mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
Improving the support for KNC One + CAM
Contact us
RSS
Top
Bottom
