Any way to improve skipping performance with .ts files?

[cncb]

Still, I will have a look to see if it is something I can even do on the client.

Thanks but don't waste any time on it because unfortunately it looks like I'm going to have to give up on the NMT. I'm just having too many general problems with it (not related to NPVR). I turned it on this morning and it would not connect to my server until I rebooted the server. Also, my kids were watching a DVD today and the video just froze up requiring a Stop and then it didn't resume when restarted. Minus the maintenance headaches, my client PCs have turned out to be more reliable.

[BrettB]

The skipping patches shouldn't make any difference on an NMT. They're only about the PC.

My issue/problem on the NMT which seems to be improved wasn't about the "accuracy" but rather the "response time" to a user requested (i.e. remote button pressed) pause or skip. Without these latest patches, when I would press pause on the NMT, it would typically take NPVR 5-10 seconds to respond and actually pause the recording. With these latest patches, it seems to be averaging about 1-2 seconds. So it "feels" much more responsive.

[mvallevand]

Thanks but don't waste any time on it because unfortunately it looks like I'm going to have to give up on the NMT. I'm just having too many general problems with it (not related to NPVR). I turned it on this morning and it would not connect to my server until I rebooted the server. Also, my kids were watching a DVD today and the video just froze up requiring a Stop and then it didn't resume when restarted. Minus the maintenance headaches, my client PCs have turned out to be more reliable.

It's not a waste of time but I will probably look anyway, That's too bad that you are having these issues but thanks for letting me know. For the connection problem the you get more reliability if you use the IP and don't depend on the master browser for the name but freezing in the middle of a DVD is totally the NMT unless you restart the recording service while it is playing.

Martin

[mvallevand]

My issue/problem on the NMT which seems to be improved wasn't about the "accuracy" but rather the "response time" to a user requested (i.e. remote button pressed) pause or skip. Without these latest patches, when I would press pause on the NMT, it would typically take NPVR 5-10 seconds to respond and actually pause the recording. With these latest patches, it seems to be averaging about 1-2 seconds. So it "feels" much more responsive.

It sounds like your system might having trouble rendering the OSD quickly for the 5-10 second case. Pauses can seem a bit sluggish because sub sends some OSD updates to the NMT before the actual pause command and they do take time on the NMT. plus sometimes 2 or 3 of these can be sent. If the pause request came first it would be faster,

Martin

[BrettB]

It sounds like your system might having trouble rendering the OSD quickly for the 5-10 second case. Pauses can seem a bit sluggish because sub sends some OSD updates to the NMT before the actual pause command and they do take time on the NMT. plus sometimes 2 or 3 of these can be sent. If the pause request came first it would be faster

I would definitely prefer to have the playback actually pause closer to the time that I press the button. If that meant that the recording would first pause, and then a (few) second(s) later the OSD with the guide info would display, I would be OK with that situation.

[mvallevand]

Here's an update to address a few things in this thread.

- Skip while Paused enabled
- Video paused before sending request to NextPVR

There is a chance that mvpmcx2 and NextPVR will be out of step with mvpmcx2 taking a bit more control, so let me know if this works better and I will update the wiki.

Martin

[BrettB]

Here's an update to address a few things in this thread.

- Skip while Paused enabled
- Video paused before sending request to NextPVR

There is a chance that mvpmcx2 and NextPVR will be out of step with mvpmcx2 taking a bit more control, so let me know if this works better and I will update the wiki.

YES! The pause is instant now. Much improved! I think that there is an "issue" with NextPVR because when it (eventually) puts up the OSD with the program info and the timeline, they immediately go away. FYI, my config.xml settings for those timeouts are:

Code:

<OSDTimeoutInfo>1000</OSDTimeoutInfo>
    <OSDTimeoutInfoOnPause>1000</OSDTimeoutInfoOnPause>
    <OSDTimeoutStatus>6000</OSDTimeoutStatus>
    <OSDTimeoutTimeline>10000</OSDTimeoutTimeline>

[mvallevand]

I use the defaults and after a short pause the details and the timeline come up quickly (I don't understand your delay) and after a five count, the details disappear and the timeline only stays on for another 5 seconds before blanking completely. Visually the time is the same for me as the PC except the detail/art don't disappear on the PC, they stay on for the full configured 10 seconds.

Your first value is shorter than the default 4000 all the others are longer. I don't really understand what they do, which is why I leave them alone.

Martin

[BrettB]

(I don't understand your delay)

Yeah, I know that we have worked on it before and never really figured out what the issue is. And, sometimes it's pretty quick, but other times it's a few seconds for the OSD to come up. If I pause, resume, then pause again immediately, it seems to come up quickly. I wonder if sub is querying the database/media directory each time the program OSD is being displayed. If so, it's possible that either that drive is spinning down or the data is going out of cache or something between longer periods between pausing. (My recordings are store on a different drive than the database and the media art.)

[stustunz]

turn off check for name changes and check for missing recordings and see if its better(in config.xml)
oops i dont think it will help you but i was getting delays in things showing up and it fixed it for me