Timing delay DVB card

[mgf@…]

In Mythtv setup, when you add one DVB card, the timing delay parameter set isn't memorized. If you reopen the new input card, the timing delay parameter is zero.

[JYA]

why assign it to me ?

[jasonh@…]

I can vouch for this. It can still be a useful function for cards with dual tuners that need more than 1000ms delay as provided by the new concurrent delay.

The symptom is any value set in the setup screen doesn't make it into the database. Manually putting a tuning_delay into the database shows that the setup screen does read the value though.

Also, please increase the hard upper limit to 10000ms.

[J.Pilk@…]

I currently have a single twin-tuner USB device (704J) set up as 2x(4-multi-rec), cardids 1 to 8. When non-zero delay values are entered via mythtvsetup for adapters 0 and 1 the only non-zero value read directly from the DB table 'capturecard' is for cardid 5. That value is also displayed for adapter 1.

I have directly updated the 'dvb_tuning_delay' values for cardids 1 to 4 to 150 ms, and cardids 5 to 8 to 200 ms and hope for more reliable locking. Those are just test values.

The 'failure to stick' has been around for a long time; it doesn't seem to affect my 290e device.

v0.28-pre-2348-gb327d14

[Stuart Auchterlonie <stuarta@…>]

In 267c890baf1d06cb0ed7e2454da6784881b65b99/mythtv:

Error: Processor CommitTicketReference failed

GIT backend not available

[Stuart Auchterlonie <stuarta@…>]

In 5aeccac88f424f000a11d1a648a8b9b6b659fef2/mythtv:

Error: Processor CommitTicketReference failed

GIT backend not available