7 replies to this topic

[oxygene76]

Hello to all,

I explain you in a few words the situation.
I have a Vu+ DUO² with 2 hybrid tuners DVB-C/T, both configured in DVB-T mode.
The tuner A is linked to a small indoor active antenna.
The tuner B is linked to the internal distribution of the building (the DVB-T standard was chosen as the internal distribution of the building because modern TVs are equipped with a DVB-T tuner).
When I make a manual scan on the tuner A and the tuner B, all the channels are found well on both tuners.

With the parameter "Preferred tuner" on "Auto": when I display the channels of the tuner A, I have no problem.
On the other hand, as soon as I want to display the channels of the tuner B, I obtain the message "tune failed" (it stays on the tuner A).

But with the parameter "Preferred tuner" set to "Tuner B", I get the message "tune failed" with the tuner A and it is then OK for the channels of the tuner B (which is correct).

Would it be possible to leave the preferred tuner on "Auto" and to have an automatic switch of tuner?
Would you know Where and how to indicate in the file "lamedb" which tuner to use for each service?

Best regards,

oxygene76

 

[Pr2]

Hi,

 

Unfortunately lamedb doesn't have any notion of tuner; so I don't think it can be fixed this way in the lamedb. The only way is perhaps to change the namespace and create two different one (one per tuner), but even with this since both tuner are DVB-T I don't see later on how to assign those fake namespaces to the right tuner. I guess this would required some change in code to support specific namespace by DVB-T tuner.

 

Pr2

[oxygene76]

Hi,

Pr2 thank you for your reply (I continue testing with the files "terrestrial.xml" and "lamedb").

Developers do not have a idea?

 

oxygene76

[Pr2]

Hi,

 

I think that the way to solve this particular case is to add an option in the DVB-T tuner that will allow to create a dummy namespace.

If I am right  namespace EEEE0000 is for all DVB-T tuner and FFFF0000 is for all DVB-C tuner.

 

Can we imagine to include an additional parameter one the DVB-T tuner (or DVB-C) were we can define a kind of namespace "subset".

 

Exemple:

 

Tuner A: DVB-T with subset define to 1 when scanning will create a namespace EEEE0001 for the found channels.

Tuner B: DVB-T with subset define to 2 when scanning will create a namespace EEEE0002 for the found channels

 

So channels will be associated with one and only one tuner.

 

For people with 2*DVB-T on the same reception antenna, they leave the subset to 0 so the namespace will remains the normal one. Same should apply to DVB-C.

 

The only problem will be with EPG and picons since those particular setup will create very specific entries for the services reference. 

 

Pr2

[pieterg]

Yes, that could be a possible solution.
Add a 'network id' setting in the frontend settings, and check that setting in the tuner selection.
Only drawback is that this would alter the serviceref.
People use the serviceref for picons, and if the DVB-C network id (which already exists, but is not added to the namespace field at the moment) were to be included in the serviceref, standard picon sets would no longer work.

[Pr2]

Indeed that's also what I point out picons and EPG will be very sensitive to this implementation and end-user will have to live with it: he will need to assign its own picons and create its own epg-import.xml file.

Or we should consider that picons and EPG for DVB-T and DVB-C don't care about the subset (or network id), but this can lead to other problems and make the code even more complex.

 

Be careful that I mention that this should also be created for DVB-C but the end-user here report the problem with DVB-T.

 

Do you see any other way to assign a channel to a specific tuner (DVB-T or DVB-C)?

[pieterg]

If we are going to use the same aproach for DVB-C (and I think we have to), we should probably introduce an additional network id, and not use the existing network id (maybe come up with a better name, to avoid the confusion).
So people who have only a single DVB-C provider, can keep using their existing nonzero network id, without introducing these issues.

[oxygene76]

Hi,

Thank you Pr2 and pieterg for your answers.