It would be nice to have the OSD timeouts and fade
lengths be configurable.
Particularly, I find that it often takes nearly as long
for XDS info to come in as the OSD timeout is. Being
able to tweak the timeout so that there is time for the
XDS info to arrive and to read it would be a definite plus.
Logged In: YES
user_id=153320
This request has come up before from someone else who used XDS data.
I know for the stations I got, the XDS data came quite quickly so this
was never really an issue. I don't think we should make it configurable if
we're really just hiding the usability issue - maybe the appropriate fix is
to have the OSD timeout reset if new XDS information arrives?
Logged In: YES
user_id=40778
That sounds like a good idea, with one caveat: what if it
takes longer than the osd timeout + fade length for the XDS
info to come in (happens on some channels I get)? Does one
pop the osd back up every time the XDS info changes? I'm
not sure if that's a good idea or not. Perhaps just pop the
OSD up again and/or reset the timer the first time the XDS
info changes after the last channel switch. I think that
would work.
Logged In: YES
user_id=153320
Why are you using XDS anyway over XMLTV? I was honestly considering
trying to get rid of it, since it complicates our code a lot and is so
unreliable.
Logged In: YES
user_id=40778
Well, XMLTV requires submitting your email and a "what
should we spam your sorry ass with" survey, which annoyed
me. XDS is just there, though its information does often suck.
Anyways, I'll try XMLTV.
Still, I'd like to increase the timeout delay :)