MeTV assumes 10.6GHz LNB, need ability to specify
Bug #1767538 reported by
Austin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Me TV |
New
|
Undecided
|
Unassigned | ||
Bug Description
Using MeTV in New Zealand, with a satellite tuner card. The LNB local oscillator frequency is 11.3GHz, but MeTV seems to be assuming it is 10.6GHz. Tried to use initial scan file for Optus D1, but MeTV says "can't process a line in the file". The only way I can make it work is to generate a channels.conf file elsewhere, the manually edit the file, subtracting 0.7GHz from every frequency entry. This is a pain, and also displays the incorrect frequencies in MeTV.
Revision history for this message
| Russel Winder (russel) wrote | #1 |
To post a comment you must log in.
I am not sure which version of Me TV your are using on what platform. I am not sure anyone is going to be maintaining the 1.3.x, 1.4.x, or 2.0.x codebases. My suspicion is that the Linux DVB API has changed and the Me TV codebase has not.
I started a rewrite of Me TV in C++ using GTK+-3 and GStreamer, but this has turned into a written from scratch Rust program that is labelled Me TV v3.0.0. It is working fine but not formally released: no EPG yet.
To use it you need to have Rust and Cargo installed along with dvbv5-scan, GTK+-3 >= 3.10.0, and GStreamer >= 1.12.0 Then clone the GitHub repository and run "cargo run". There are two known users, myself and a person in eastern Australia.
https:/