Backend Setup - DVB-S Channel Scan. Frequency in KHz should be Hz

Bug #452492 reported by Simon Harrison
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mythbuntu
Expired
Low
Unassigned

Bug Description

Mythbuntu 9.10 i386

Backend Setup. DVB-S Capture card, channel scan (Manual, Tuned)

When entering the the required parameters for the above scan, there is no default frequency (Strange, in itself, but I'll leave that for another day), the field is blank, so you have no clues.
The helper text at the bottom of the screen says 'Enter Frequency in Kilohertz', but this is incorrect, it should be Hertz.

eg, Astra 28.2, transponder 50. Frequency is 10.847 GHz, that's 10847 KHz, or 10847000 Hz.

If I enter 10847, I get nothing. What it actually needs it 10847000, and I get a full scan. The giveaway, in the end, was that if I put a decimal point (eg 10817.50, for transponder 48) I get an 'Error parsing parameters' error when selecting 'Next' to commence the scan.

So my suggestion would be to correct the text to specify Hertz, as a minimum, but maybe add an example with a GHz to Hz conversion for the non-scientific among us.

Regarding the no default frequency issue, I imagine it's because nobody has compiled a frequency table, such as there is for DVB-T. I would be happy to attempt to compile a UK table, and maybe help with an international one. Would that be useful?

summary: - Backen setup - DVB-S Channel Scan. Frequency in KHz should be Hz
+ Backend Setup - DVB-S Channel Scan. Frequency in KHz should be Hz
Revision history for this message
Thomas Mashos (tgm4883) wrote :

Thank you for helping to improve Mythbuntu by opening this ticket. I am marking this ticket as confirmed because it appears to have enough information to help the developers understand the problem. It is possible I am wrong and another more experienced triager or developer may adjust the status of the ticket to "incomplete" and request additional information.

Changed in mythbuntu:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Thomas Mashos (tgm4883) wrote :

Marking incomplete as this release isn't supported anymore. Can anyone confirm that this issue is still present on a supported Mythbuntu/MythTV release?

Changed in mythbuntu:
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Mythbuntu because there has been no activity for 60 days.]

Changed in mythbuntu:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.