4 replies to this topic

[ambrosa]

I've added in main /etc/tuxbox/terrestrial.xml the ITalian freq. list for DVB-T

Can I suggest to include the new file in main distribution ?

It works fine with many USB DVB-T


Attached here

Attached Files

•  terrestrial.xml.zip   1.77KB   122 downloads

[Gennar1]

Thank you for the effort, but I think there is no need for a dedicated list of channels in Italy. The standard "Europe DVB-T" table is valid for Italy too.

Moreover, there are several errors in your file, and probably it is working only because many USB DTT drivers use only frequency/bandwidth in their set_frontend functions, and all other parameters are ignored.

For example, for all UHF channels you put:
constellation="2"
which means 64QAM modulation. But in my area for example there is a DVB-H frequency which is using QAM16 and a DVB-T channel which is using QPSK (Rete Capri, CH 57).

Another example is:
guard_interval="0"
which means a guard interval equal to 1/32. While some regional channel is still using this configuration, most national channels (as well as big regional networks) are now using SFN networks (at least in the switch-off areas) so they adopt much higher guard intervals such as 1/4.

In the end, I think there is no need to specify advanced modulation parameters, since most drivers are simply ignoring them and those parameters can depend on the regional area and can change from time to time. So again the best solution is the one provided in the current "terrestrial.xml" file.

Edited by Gennar1, 21 November 2011 - 12:19.

[ambrosa]

As usual you have right

But in my location (Milan, Italy) with my setup (CT9100 and Avermedia A835) using OpenPli "Europe DVB-T" I tune 283 channels.
With Italy freqs as I suggested before, I tune 323 channels : 40 more

In next days I will do more deep test to discover which channels are missing with OpenPli DVB-T Europe setup and WHY they are missing......

Edited by ambrosa, 21 November 2011 - 18:59.

[Gennar1]

That's weird, you should be able to get exactly the same channels with both configurations.
Probably there is some bug in the search algorithm for the A835 (maybe some incorrect timing?).
There must be some good reason if the patch to enable A835 support is not officially included in the kernel...

[Dimitrij]

With the level of SNR(Avermedia A835) is no solution there?