Reply to thread

Message

<blockquote data-quote="jafa" data-source="post: 282020" data-attributes="member: 27991">Hi,I am QA testing the latest HDHomeRun drivers for use with MediaPortal 1.0.0 RC1.MediaPortal seems to test QAM64 and QAM256 on each channel.1) It does not test 8VSB.Some US cable providers use 8VSB on cable (or a mixture of 8VSB and QAM).The channel numbering is cable based, not using OTA frequencies.2) Many ATSC/QAM tuners including the HDHomeRun support auto-modulation detection.The trick is to query the &quot;IBDA_AutoDemodulate&quot; interface. If this interface exists, call put_AutoDemodulate. If this function returns OK then the tuner supports automatic modulation detection. Pass -1 for the modulation type.Result - the scan is 2-3 times faster as MP does not need to iterate through all the modulation types.NickAdditional... MP is waiting 23 seconds per modultion type.135 channels x 2 modulation types (should be 3) x 23 seconds = 1h 44m!Timeout should be closer to 2.5 seconds.Nick</blockquote>

[QUOTE="jafa, post: 282020, member: 27991"] Hi, I am QA testing the latest HDHomeRun drivers for use with MediaPortal 1.0.0 RC1. MediaPortal seems to test QAM64 and QAM256 on each channel. 1) It does not test 8VSB. Some US cable providers use 8VSB on cable (or a mixture of 8VSB and QAM). The channel numbering is cable based, not using OTA frequencies. 2) Many ATSC/QAM tuners including the HDHomeRun support auto-modulation detection. The trick is to query the "IBDA_AutoDemodulate" interface. If this interface exists, call put_AutoDemodulate. If this function returns OK then the tuner supports automatic modulation detection. Pass -1 for the modulation type. Result - the scan is 2-3 times faster as MP does not need to iterate through all the modulation types. Nick Additional... MP is waiting 23 seconds per modultion type. 135 channels x 2 modulation types (should be 3) x 23 seconds = 1h 44m! Timeout should be closer to 2.5 seconds. Nick [/QUOTE]

Verification