[solved] MP TV Server cannot find any channels anymore, DVB viewer works (1 Viewer)

[Terra]

Hi there,

My cable provider (DVB-C) has updated some channels and therefore I have to re-scan all the available channels.
The problem I am facing is that MP TV Server cannot find a single channel anymore when searching.

I then installed DVB Viewer and it can find all channels and play them without issues.

Does anybody have an idea what the issue with MP TV Server is and how I can fix it?
I have not changed anything and I use the same TV-Card as before.
I used the same parameters as DVB Viewer shows me, MPTVS cannot find anything.

 

[Owlsroost]

I know very little about DVB-C tuning, but...

Looking at the TVService.log, the log entries where the tuning has been successful have much larger 'SymbolRate' values (1000x larger) e.g.:

[2019-02-22 22:38:55,972] [Log    ] [46       ] [INFO ] - Controller:   channel #1 DVBC:tv:ZDFvision ZDF HD Freq:602000 ONID:1 TSID:1011 SID:11110 PMT:0x17D4 FTA:True LCN:6 SymbolRate:6900000 Modulation:Mod256Qam

...compared to (for the scans):

[2019-02-22 22:38:06,338] [Log    ] [107      ] [INFO ] - dvbc: Scan:DVBC:tv:  Freq:602000 ONID:-1 TSID:-1 SID:-1 PMT:0xFFFFFFFF FTA:False LCN:10000 SymbolRate:6900 Modulation:Mod64Qam

Note the difference - SymbolRate = 6900000 (success) versus 6900 (failed)

Are the SymbolRate values in your MP TVS tuning parameters correct?

 

[Terra]

Note the difference - SymbolRate = 6900000 (success) versus 6900 (failed)

Are the SymbolRate values in your MP TVS tuning parameters correct?

That was the solution.
My Tuning Parameters are correct as far as I understand it, also when I check the other Tuning Parameter Files the Symbolrate is always 4 digits.
Nevertheless I now modified the XML file and added three zeros at the end of the Symbolrate and now it is working.

BEFORE:

<DVBCTuning>
<Frequency>474000</Frequency>
<ModulationType>Mod64Qam</ModulationType>
<SymbolRate>6900</SymbolRate>
</DVBCTuning>

AFTER:

<DVBCTuning>
<Frequency>474000</Frequency>
<ModulationType>Mod64Qam</ModulationType>
<SymbolRate>6900000</SymbolRate>
</DVBCTuning>

 

[Owlsroost]

Interesting....I'll try and work out where those files are parsed in TV server (I agree the SymbolRate values are 4 digits in the installed DVB-C tuning parameter files).

Which version of TV Server are you using?

Which version of windows are you using?

Which tuning parameters .xml file are you editing?

 

[Terra]

Which version of TV Server are you using?

I use 1.21 with an USB "Hauppauge WinTV-soloHD DVBT/C Tuner"

Which version of windows are you using?

I use Windows Server 2008 R2 with DVB hotfix installed.

Which tuning parameters .xml file are you editing?

I use my own as my local provider is not part of the standard MP files.
Here is the file I am using now and where it works:

<?xml version="1.0" encoding="utf-8"?>
<ArrayOfDVBCTuning xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<DVBCTuning><Frequency>474000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>578000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>634000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>642000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>594000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>602000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>610000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>482000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>490000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>498000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>658000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>618000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>626000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>506000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>650000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>514000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>522000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>530000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>538000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>666000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>546000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>554000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>562000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
<DVBCTuning><Frequency>570000</Frequency><ModulationType>Mod64Qam</ModulationType><SymbolRate>6900000</SymbolRate></DVBCTuning>
</ArrayOfDVBCTuning>

 

[Owlsroost]

Interesting....I'll try and work out where those files are parsed in TV server (I agree the SymbolRate values are 4 digits in the installed DVB-C tuning parameter files).

I've had a good look around the code, and as far as I can see the SymbolRate value is always used and stored in the database 'as is' for DVB-C (it's never multiplied by 1000 anywhere), so all I can suggest is that particular tuner driver expects the SymbolRate value as 'bits per second', but most tuner drivers expect it as 'kilobits per second'.

The Windows documentation for the BDA tuner interface doesn't specify the units for that value (as far as I can find), unfortunately.

 

[Yucca]

FYI...
I´m using Mediaportal 2.2.3 and it had this same issue with DVB-C channels until I found this threat.
I also have made my own channel map xml for my operator (LPOnet). I´ll attach it and my local DVB-T map, so that developers can share them at later distributions.
I also notice that it´s not even possible to add those needed zeros in symbolrate option at manual search.
And for those who do not know where these files are located (MP2), DVB-C are at C:\ProgramData\Team MediaPortal\MP2-Server\SlimTVCore\v3.0\TuningParameters\dvbc and DVB-T at C:\ProgramData\Team MediaPortal\MP2-Server\SlimTVCore\v3.0\TuningParameters\dvbt and if I remember correctly they are slightly different path/location at MP1 but, in the same named folder.

 

[Jasmeet_181]

Thanks for the files Yucca, in Finland.Myrskylä.xml, the first multiplex is missing the closing </DVBTTuning> after line 6.

 

[Yucca]

I noticed that ... I fixed it, so if somebody downloads it from here it won´t confuse people...
I deleted the old file and uploaded new file instead.

 

[2102Michael]

I had the same issue here in Austria with Kabelsignal and the Hauppauge WinTV-dual HD DCBC card.

I modified the xml DVBC Channel file and attach it here.