Channel scanner stores DVB transports incorrectly.

[anonymous]

I started with a fresh install, removing the entire database first.

Doing a full scan on (freq=240000000, symbolrate=7146000 inversion=none, fec=none) got lock on that transport and correctly detected the channels on it, storing them to database. The other transports reported by that transport were also stored, but not scanned automatically.

However, the transport itself was stored incorrectly, as seen here: ​http://zi.fi/mythtv.txt

After setting the missing values directly on the database, it started working. I did not adjust frequency back to the nominal value of 240 MHz, but let it stay at 239.97... MHz instead.

[danielk]

This is pulled from the DVB drivers and needs to be fixed there. But we'll allow this to be overridden in the new channel scanner slated for the 0.22 release.