Tvheadend

Too bad you do not want to simplify user life! The tuning takes only 7 minutes and is always exact.

BTW, I do not receive you chnage by mail.

The real problem is that you do not use a file format that other tools can generate (e.g vdr channels.conf) and by relying on things that are most of the time obsolete you force the end user to run w_scan anyway and feed you file with its own result.

The idea behind Tvheadend is that there is no need for a "file format", just like any regular STB that you can buy off the shelves.

By including a set of predefined DVB networks the idea was that it would make it easier for people to add DVB networks. If a network was not in that list people could still manually add one (or more) frequencies from their network manually (just like on a standard STB)

The included list is actually compiled directly into the Tvheadend binary it self. As you an other used have found out, this list is not always up to date and actually changing the list would require a new Tvheadend binary. Ticket #72 was created to remove this compiled list and use a file format. This has not been implemented yet. Some discussion has been taken place about what format would be ideal, but nothing has been formalized yet.

So it is not that we do not want to simplify user life, but including a brute force scanning tool like w_scan (or similair option) is not they way forward.

I find your STB analogy (or even HDTV internal DVB-T decoder) quite amusing: they just do brute forcescan and nobody is against that. So It think for DVB-T, this IS the way to go. This is what kaffeine, vdr, mplayer rely upon.

I do not care if you do a script that parse the output of w_scan (any form of generated channel.conf you prefer) or even if you use w_scan -x just to find the transponder. I do mind having always obsolete data and having to use w_sacn to find the transponder anyway.