Opened 4 years ago

Closed 8 months ago

#12965 closed Bug Report - General (Unverified)

can't go to channel 4.1 bu numpad when channel 41.1 exists.

Reported by: marcjw53@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: 0.28.0
Severity: medium Keywords:
Cc: Ticket locked: no


In my area a channel scan results in acquiring both channels 4.1 and a bunch of 41s (41.1, .2, .3, etc). If I leave the channel 41 series active, I cannot select channel 4.1 by numpad. When I type 41<Enter>, nothing happens. I discovered that since I have the 41 series active, Myth is always waiting for another integer when I type 41. Indeed, if I type 411 (or 412, or 412, etc) it will change to that 41.1 channel. But there appears to be no way to change to 4.1 - it's always expecting another integer and when it doesn't get one the number display eventually just goes away.

I've deleted the 41 series of channels from the channel editor for now as a work around. With the 41 series gone, I can now type 41 and Myth will change to channel 4.1 (4_1). But when the 41 series of channels exists, I can't do that.

I would like to be able to type 41<Enter> (or GO on my remote) and have Myth change the channel to 4.1 even when the channel 41 series exists.

Change History (5)

comment:1 Changed 4 years ago by stevegoodey@…

What happens if you enter 041?

comment:2 Changed 4 years ago by marcjw53@…

Now that I've already deleted the channel 41 series, it doesn't matter to me if padding a channel number with a leading zero works or not. Now that the 41 series is gone, I don't have to. But I'll bet that would have worked. I wish I would have thought of that before deleting the channel 41 series. Although from a usability standpoint, I still think that being able to type 41<Enter> is preferable.

comment:3 Changed 4 years ago by Peter Bennett

Entering 041 does not help.

How would one distinguish between channels 4.1, 4.11, 41.1 and 411 ? If we want to fix this we should have way to solve all of these issues. How important is this or do people have remotes with a period button to solve it?

comment:4 Changed 4 years ago by Roger Siddons

How about 4#1 (4, hash, 1) ? The spacers don't seem to be documented.

comment:5 Changed 8 months ago by Stuart Auchterlonie

Resolution: Unverified
Status: newclosed

Closing all old tickets in trac.

If your issue still persists, please open an issue in Github

and reference the existing trac ticket.

Note: See TracTickets for help on using tickets.