Error while tuning: timeout after 7000 ms

[Alberto Mattea <support.intranet@…>]

On slow tuners/drivers, tuning can take more than 7000 ms (kMythSocketShortTimeout). Currently this makes mythfrontend hang. In the logs it is written: MythSocket(887ddd8:40): readStringList: Error, timed out after 7000 ms. I've experienced this, for example, while switching from DVB-T to DVB-S with a Hauppauge HVR-4000. The quick solution is to raise the value of kMythSocketShortTimeout in mythtv/libs/libmythdb/mythsocket_cb.h (17000 ms worked for me), but it would be best to make it an option in mythtv-setup. This bug applies to all version I tested, up to current trunk. I'm attaching a very simple patch that raises the timeout to 20000 ms.

[Alberto Mattea <support.intranet@…>]

Simple patch to raise the timeout to 20000 ms

[robertm]

Bumping to unknown, please don't set the milestone.

[Alberto Mattea]

Ok, sorry. But is it there a chance it will be solved in next version? It is so simple to solve :-) Thanks

[Alberto Mattea]

0.23 rc1 is out. Is it too late for a fix? It is so annoying to recompile it every time...

[robertm]

Read. The. Ticket Howto.

[danielk]

This is the wrong thing to be "fixing". The DVB tuners using a signal monitor which respond within a few milliseconds. If this isn't working we'll need to diagnose and fix that problem, not allow mythfrontend to lockup for 20 seconds.

[Alberto Mattea]

Sorry, maybe I wasn't clear. The issue here is not when tuning to a different channel (which takes only a second or so), but when switching between DVB-T and DVB-S. Since it is the same card that handles both, it must be completely reinitialized by the driver, which can take up to 10-12 seconds. I think there is nothing MythTV can do about that. Please don't take offence iif I reopen the ticket, and tell me if I understood your comment wrong.