Yeah youre totally right on both counts Boiler. Yes, it is a timing issue; and, I didnt even think that the proxy would have no effect on a non-sageTV setup... but, hey.. thats one more thing to cross off the list of troubleshooting.
I personally would prefer to try to avoid having to add delays after exhausting all possibilities first. I was successful in stopping the weird intermittent timing issues dead in its tracks... which is why I suggested to try some things first before giving up and adding extra timings. Lets face it, not everyone needs to add these timing values for it to work. What make's their setups different? I tried several different things to stop the inconsistent timings; and, admittedly, I have no idea which specific action actually did it...so, I just mentioned everything I did.
We're a rather small family here, it would be great to put our minds together since we have enough sharp people here that have this issue; and, see what's common among our setups. We have nothing to lose by trying. This is something that not even Nextcom Wireless had the resources to trouble shoot. However, we do. It's not some ambiguous unsolvable issue; and, I'm sure some of us have troubleshot possibly tougher issues in the past. The only thing I can think of right now is not having enough free physical memory driver/software functions to work correctly. I guess it could be a software component....but, we would all have to have the same thing in memory.
I am sitting here on the same setup that I once thought I would never get rid of the issue... now, with the same hardware and OS.. it just works.. and tunes into channels quickly on all 4 unlike cableboxes; the way it was designed to work (EDIT: with the exception of adding hugo's proxy; which I'm guessing might not have done a whole lot.. but didnt hurt either). The fact that this occurs on both dish and cableboxes is a good thing.. its yet another piece to the puzzle.
Of course, this is considering that there isn't more than one thing that can have the same adverse effect on timing. What do you think? I guess it might be hard for both of us who have perfectly working setups to be motivated to fix an issue we dont have anymore. The only difference is I was able to somehow stop the issue instead of working around it.
Anyhow, just a suggestion...
Originally Posted by boiler11
I'd love to know the root cause also, but I believe it's simply a timing issue. The nextcom folks probably just make it flexible with the delay to allow for differences in set top boxes.
I can assure you that guho's proxy does not solve the problem. He sent me the source long ago, and I also messed with that extensively. His proxy has no more granularity of channel changes than SageTV does. The R5000 app only accepts channel change commands as a single atomic command. It's after it receives that command that it goes through it's paces of pre-code, inter-digit, and new stream delays.
Besides, cosdod isn't even using SageTV, so isn't guho's proxy irrelevant? Unless scheduling via TitanTV uses the same TCP interface as SageTV.