Tvheadend

Could you retest with latest? I believe that commit d27c11d2c9fa11898cf8c529f055a3a03d91f740 should fix the bad behaviour.

I run version on QNAP, will need to wait for virtualdj to build it and deploy. Will keep this record updated.

jiri urbanec wrote:

I run version on QNAP, should version 4.3-117~gddf420b work the?

I run version on QNAP, should version 4.3-117~gddf420b work then please?

The commit is v4.3-139-gd27c11d .

Negative, still same behaviour in the version HTS Tvheadend 4.3-196~gad61cad. Even worse {name-not-set} is created after muxes scan and not after service mapping as in previous.

The .wrf format is not a standard and problematic when you are only Linux user. Anyway, the channel names should be copied from the service names. So it depends, if the service is valid at the channel creation time. Please, describe the faulty behaviour more and provide screenshots from the service grid and channel grid.

I see now. The {name-not-set} is because you probably removed the previous network thus all services. TVH copies names from services, so if you remove them, the channels become invalid.

Unfortunately, I cannot reproduce the behaviour with the channel field in the service grid here. Could you try a different browser?

Allright, that is true, after cleaning the services the {name not set} channels disappeared.

In fact I was expecting a "grouping" (in terms of GUI - "merging") the services to one channel because they can be HD, T/T2 or from different services and should appear as one channel (with services priority) - mapped to one name same as is done when mapping the services|merge the same name.

If that is not supported, I would propose the improvement, if this should be supported - this does not work as expected.

Anyway thanksfor clarification.

Regards.

Unfortunately, 'Nova' and 'Nova HD' are two different strings. The current match works only for identical strings.