3.5.7 choppy on pause/ resume/skip forward/skip back

[2leftfeet]

I have been noticing choppy response when pausing/resuming and skip forward and skip backward since upgrading to 3.5.7 Using 3.4.8 was much smoother and quicker by comparison.

If I pause liveTV, I am seeing stuttering for a few seconds before pause actually happens, same if I resume, it stutters for a few seconds then starts playing normally.

If I try to skip forward, the screen freezes for around 3-4 seconds before the skip occurs, same if I skip back. Again, with 3.4.8, these skips were smooth and quite near instantaneous.

Anyone else notice this?

[2leftfeet]

Anyone else notice this?

I guess not

[mikeh49]

No problem for me on Win7 with the MS DTV decoder.

[2leftfeet]

Hmmm, after more testing everything has much slower response after the upgrade - from starting NPVR, navigation and channel change.

I am also noticing that the scheduled EPG updates are taking much longer - and often the server goes into sleep mode before EPG update completes.

Previously EPG updates were taking around 12 minutes (Schedules Direct); but now over 20 minutes.

Using:
HDHR Prime
Server - Windows 7 , 4-core AMD
Client - Windows 10, core 2 duo

all was working fine before upgrade.


HELP!

[sub]

Previously EPG updates were taking around 12 minutes (Schedules Direct); but now over 20 minutes.

Can you do an 'update epg' on the server, then post the log? I'd like to see where it's spending the time.

[2leftfeet]

will do - just started the update but right off the bat I can see that the requests for blocks of 10 channels is taking much longer than normal - i will post logs when finished

[2leftfeet]

ok, the update took ~38 minutes, yikes! The channel fetch took over 30 minutes alone.

could db be corrupt? I notice that it is near double in size as it was 2 days ago!

[sub]

Approximately how many channels do you have?

[2leftfeet]

364 - same as before - did you see my edit above that the db grew to almost double in size in the last two days? from 46.2MB to 80.9MB - corrupt DB?

[sub]

Did you hit 'empty epg' prior to hitting 'update epg'? You shouldn't need to with Schedules Direct, and it'll just make the process a lot slower.