2012-04-02, 02:14 AM
I ran into a problem on the NMT today when I wanted to seek 3 minutes back but for some reason my system was very non-responsive.
In this situation I thought I lost an important piece of the hockey game I was watching when the channel changed, fortunately the bug that keeps live tv files around allowed me to watch it.
Trying again, later all seemed normal so I can't explain why NPVR was so non-responsive processing the key and sending the update earlier. It might be worth digging into why the PC can slow this much.
At the end of it all I would like an option like GBPVR had
<ChannelChangeWithoutEnterKey>false</ChannelChangeWithoutEnterKey>
or perhaps it could do like my cable box, when I type one or two leading zeroes, enter isn't required and the 3000 ms would probably be okay.
Martin
Code:
2012-04-01 17:40:37.818 [DEBUG][3] User pressed: D3
2012-04-01 17:40:38.872 [DEBUG][3] OnKeyDown() complete
...
2012-04-01 17:40:39.782 [DEBUG][3] incremental frame sent
...
2012-04-01 17:40:41.213 [DEBUG][3] auto changing channels after 3085ms
...
2012-04-01 17:41:03.179 [DEBUG][3] User pressed: Left
In this situation I thought I lost an important piece of the hockey game I was watching when the channel changed, fortunately the bug that keeps live tv files around allowed me to watch it.
Trying again, later all seemed normal so I can't explain why NPVR was so non-responsive processing the key and sending the update earlier. It might be worth digging into why the PC can slow this much.
Code:
2012-04-01 18:23:26.123 [DEBUG][3] User pressed: D3
2012-04-01 18:23:26.124 [DEBUG][3] OnKeyDown() complete
...
2012-04-01 18:23:26.457 [DEBUG][3] incremental frame sent
...
2012-04-01 18:23:29.126 [DEBUG][3] auto changing channels after 3003ms
At the end of it all I would like an option like GBPVR had
<ChannelChangeWithoutEnterKey>false</ChannelChangeWithoutEnterKey>
or perhaps it could do like my cable box, when I type one or two leading zeroes, enter isn't required and the 3000 ms would probably be okay.
Martin