difficulty enter channel numbers during Watch TV - What should I be loggging?

Have a MythTV related problem? Ask for help from other MythTV users here.

Moderator: Forum Moderators

Post Reply
larry5b6
Junior
Posts: 17
Joined: Tue Dec 27, 2022 3:08 am
United States of America

difficulty enter channel numbers during Watch TV - What should I be loggging?

Post by larry5b6 »

I'm in the process of bringing up both ends of mythtv on a Raspberry Pi and I'm having trouble selecting channels while in Watch TV

If I use the up or down arrows, I can scan the channels, but I must hit ENTER to select the new channel - the arrow-selected channel never times out to selecting.

If I enter a new channel number on the keypad, it never takes effect, whether I hit ENTER or wait for timeout - the displayed numbers just fade away without taking effect.

I've been reviewing the various logging options for mythfrontend and so far haven't found any that have resulted in relevant information in the logging stream.

Can anyone a set of command line arguments for mythfrontend that would help me troubleshoot this?

thanks,
User avatar
bill6502
Developer
Posts: 2299
Joined: Fri Feb 07, 2014 5:28 pm
United States of America

Re: difficulty enter channel numbers during Watch TV - What should I be loggging?

Post by bill6502 »

Looks like a duplicate of: viewtopic.php?f=36&t=5221&p=25125#p25124
Didn't that answer help?
larry5b6
Junior
Posts: 17
Joined: Tue Dec 27, 2022 3:08 am
United States of America

Re: difficulty enter channel numbers during Watch TV - What should I be loggging?

Post by larry5b6 »

Unfortunately I'm still struggling with the issue (probably should have stayed in the same thread - sorry). I've done some more experimenting and logging, and have caught something potentially of interest in the log:

Code: Select all

2023-01-22 16:28:05.987771 D [17225/17242] SSDP portchecker.cpp:75 (checkPort) - PortChecker::checkPort(): host 192.168.1.15 port 6544 timeLimit 5000 linkLocalOnly 0
2023-01-22 16:28:06.488815 D [17225/17242] SSDP portchecker.cpp:193 (checkPort) - PortChecker::checkPort(): socket state 3
2023-01-22 16:28:06.513359 D [17225/17242] SSDP portchecker.cpp:75 (checkPort) - PortChecker::checkPort(): host 192.168.1.13 port 6547 timeLimit 5000 linkLocalOnly 0
2023-01-22 16:28:06.541779 D [17225/17360] HttpServer101 portchecker.cpp:75 (checkPort) - PortChecker::checkPort(): host localhost port 3306 timeLimit 30000 linkLocalOnly 1
2023-01-22 16:28:07.014473 D [17225/17242] SSDP portchecker.cpp:193 (checkPort) - PortChecker::checkPort(): socket state 3
2023-01-22 16:28:35.926404 I [17225/17225] CoreContext tv_play.cpp:5967 (ChangeChannel) - TV::ChangeChannel(): (0, '2')
2023-01-22 16:28:35.937361 I [17225/17225] CoreContext tv_play.cpp:6007 (ChangeChannel) - TV::ChangeChannel(): CheckChannelPrefix(2, pref_cardid 0, 1, '') cardid 1
2023-01-22 16:28:35.943313 I [17225/17225] CoreContext tvremoteutil.cpp:138 (RemoteRequestFreeInputInfo) - RemoteRequestFreeInputInfo excluding input 1
2023-01-22 16:28:35.943345 D [17225/17225] CoreContext mythcorecontext.cpp:1407 (SendReceiveStringList) - MythCoreContext::SendReceiveStringList(): SendReceiveStringList(GET_FREE_INPUT_INFO 1) called from UI thread
2023-01-22 16:28:35.947336 I [17225/17225] CoreContext tvremoteutil.cpp:156 (RemoteRequestFreeInputInfo) - RemoteRequestFreeInputInfo got input 1 (0/0)
2023-01-22 16:28:35.947356 I [17225/17225] CoreContext tvremoteutil.cpp:161 (RemoteRequestFreeInputInfo) - RemoteRequestFreeInputInfo got 1 inputs
2023-01-22 16:28:35.947379 I [17225/17225] CoreContext tv_play.cpp:6693 (IsTunableOn) - TV::IsTunableOn(): ChanId (4294967295) - no
2023-01-22 16:28:40.044154 I [17225/17225] CoreContext tv_play.cpp:1961 (HandleStateChange) - TV::HandleStateChange(): Attempting to change from WatchingLiveTV to None
2023-01-22 16:28:40.044237 I [17225/17225] CoreContext platforms/mythscreensaverx11.cpp:161 (RestoreScreenSaver) - ScreenSaverX11: Uninhibited screensaver
2023-01-22 16:28:40.046232 I [17225/17225] CoreContext platforms/mythscreensaverx11.cpp:138 (RestoreDPMS) - ScreenSaverX11: DPMS Reactivated 1
2023-01-22 16:28:40.669589 I [17225/17225] CoreContext tv_play.cpp:2193 (HandleStateChange) - TV::HandleStateChange(): Changing from WatchingLiveTV to None
2023-01-22 16:28:40.676835 I [17225/17225] CoreContext tv_play.cpp:366 (StartTV) - TV::StartTV(): Exiting main playback loop. 
I watched the system time pretty closely while testing and selected channel 2 by pressing the 2 key at 16:28:30, and then the ENTER key at 16:28:33.

From the log, I can see the attempt to change channels at 16:28:35.926404, which would roughly correspond to the timeout, as though the ENTER key wasn't received (I tried both the primary and numeric pad enter keys, and ^M).

Then, at 16:28:35.947379, I see TV::IsTunableOn(): ChanId (4294967295) - no

Is there something I need to turn on to make the tuner tunable? (It's an HDHomerun) When I searched for IsTunableOn in the forum I found nothing.

Or is there something else visible in the log that could be my problem?

Thanks in advance /lr
User avatar
kmdewaal
Developer
Posts: 640
Joined: Wed Dec 07, 2016 8:01 pm
Netherlands

Re: difficulty enter channel numbers during Watch TV - What should I be loggging?

Post by kmdewaal »

If I use the up or down arrows, I can scan the channels, but I must hit ENTER to select the new channel - the arrow-selected channel never times out to selecting.
This is the intended behavior.
If I enter a new channel number on the keypad, it never takes effect, whether I hit ENTER or wait for timeout - the displayed numbers just fade away without taking effect.
The behavior as observed here is that when the first character of the channel number is entered this is shown on the screen and a timer is started. This timer will expire after about 5 seconds; at that moment all characters entered are used as the channel number.
If a channel is found then it switches to that channel; if the channel is not found then the on-screen display just fades away and nothing happens.
Comparing the channel number as entered with the channel number in the database is done with string comparison and both strings must be exactly equal.
Pressing ENTER to terminate channel number input before the timer expires has been implemented last week in master/pre-v34 but in v33 you just have to wait until the 5 seconds have passed.
Post Reply