INTERACT FORUM
Windows => Television => Topic started by: ABA on March 01, 2018, 01:05:33 am
-
Hello,
I have setup TV channels succesfully on MC22. All of my provider's transponders are QAM256 with one exception of QAM64. For some reason MC22 fails to find the channels on that particular transponder. DVBLogic TVSource and HDHomeRun Viewer both find all channels including the ones on the QAM64 transponder.
It may be worth noting that the transponder in question is the one my provider uses for DVB-C NIT scan.
Setup:
Windows 10
HDHomeRun HDHR3-EU (software setup to JRiver)
TV provider: Glenten, Odense, Denmark
-
For DVB-C setup, I find these files that are for Denmark:
Denmark.Parknet Copenhagen
Denmark.Stofa Aarhus
Denmark.Stofa Hjallerup
Denmark.Yousee Aarhus
Denmark.Yousee Copenhagen
Denmark.Yousee Global
Denmark.YouSee Nordjylland
Denmark.Yousee.Odense.Kragsbjerg
Which one did you select for channel scanning?
-
I made my own based on the one I made for DVBLink TVSource (which as mentioned works fine for all transponders).
<?xml version="1.0" encoding="utf-8"?>
<DVBCTransponders version="1.0">
<Transponder Frequency="122000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="130000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="138000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="146000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="154000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="162000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="170000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="178000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="378000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="386000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="394000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="402000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="410000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="418000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="434000" Modulation="64QAM" SymbolRate="6875" />
<Transponder Frequency="442000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="450000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="458000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="466000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="474000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="482000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="490000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="562000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="570000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="578000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="650000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="658000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="666000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="674000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="682000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="690000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="770000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="778000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="786000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="842000" Modulation="256QAM" SymbolRate="6875" />
<Transponder Frequency="850000" Modulation="256QAM" SymbolRate="6875" />
</DVBCTransponders>
-
OK then. This is the only thing that I can think of that may cause missing channels. Are you sure the table is complete?
-
Yes, I am pretty sure it is complete. In any case, MC22 does not find the channels on the 434000 transponder that is included in the list while other software packages do. I have a log file that I can forward, if you tell me where to forward it to.
-
Email it to yaobing at jriver dot com
-
The log file shows that frequency 43400 could not lock. We set the frequency, modulation type, and symbol rate, but could not get the tuner to lock. Its lock status is 0, and signal quality is 0 too.
During the scanning of the other frequency, we actually did scan NIT, which gave a number of transponders, including the one for frequency 43400. But we just could not tune to it.
Is this channel protected?
-
Not sure what protected means, but since my TV, DVBLink and the HDHomeRun software finds the channels on the 434000 frequency without problems, I guess not... Also, the missing channels are part of the base package with the provider.
Regarding NIT: Now that you mention, I remember from the past that the NIT can be found on other frequencies too, but the provider lists the 434000 frequency as the one to use.
Just did a rescan with success on DVBLink - screendumps sent to your email. Also, did a rescan in MC22 with the full frequency list and the problem remains.
It seems to be a bug with MC22 not being abto to tune that frequency...?
-
By "protected" I meant premium channels, those that are encrypted. We are not able to support such channels.
If the channel is supposed to be free to air, I don't know why it would not tune. We tune all channels the same way, using Microsoft provided methods.
-
I've had issues with tuning to channels using a different modulation as well. I would recommend to try moving it to another spot in the XML file and see if that helps at all (that changes the order in which MC tries to tune them).
I re-build the XML file from scratch for my area and the changed order seemed to have solved it back then for me.
-
Problem solved. HDHomeRun modulation configuration had somehow been setup to 3x QAM256/6875 rather than QAM64/6875, QAM128/6875 and 256/QAM256.
-
That's good to know.