MP1.16 Remote Client Unable to Play: B43534E1 error watching Recorded TV (2 Viewers)

[RonD]

@mm1352000 @Owlsroost any idea what/why Win10 is doing stuff with Drive-K?

Bottom line, using ProcessMonitor see multiple times with long delays over 500 milllisec access to Drive-K. This matches earlier comments looking at tvserver* log files. My guess is Drive-K does spin down when idle even though I’ve disabled Win10 “turn off drive”, but not 100% sure

Setup ProcessMonitor to capture events Path begins with K: include and Duration less than 0.0001 exclude. This captures all MP and Windows Drive-K accesses and gets rid of lots of short access. Exported data to csv, see attached spreadsheet, 12360 rows.

Trace starts at 9:14 and shows MP reading recording from Drive-K while I watched a recording. All “durations” at 1 to 20 millisec, normal disk access, stopped video. Left ProcessMonitor running while I did other stuff. Starting at 9:19 and repeating about every five minutes, Win10 system/pid=4 goes out to Drive-K and plays with files for a few seconds. This repeats every 5 minutes up to 10:29 am when I stopped ProcessMonitor.

DriveK_all.PNG shows “duration” in millisec vertical from 9:14 to 10:29 AM, multiple spikes above 500
DriveK_949am.PNG shows zoomed view of events around 9:49 am

Spreadsheet LogfileDiskRD.zip has ProcessMonitor info, 3 sheets have the following
LogfileDiskRD: raw data
Charts: where I made charts
SpikeDetails: copy/pasted about 9 rows of data for each “duration spike” event

Spoiler: Spike Durations if you want to search in spreadsheet

Row Duration
862 0.6550818
982 0.6848836
983 0.6375816
1662 0.5376831
1763 0.5478966
1764 0.5469040
6961 0.6428508
7228 0.5337842
7229 0.5324635

 

[RonD]

installed the TsReader_v4.2.2.33.zip on remote client. did quick test of Recorded TV. Did not see any immediate problems or trigger the "unable to play" error. Will do more testing of this version. Seems like this is a "moody" problem, if its in the mood to fail it fails, otherwise do not see problem.

 

[mm1352000]

any idea what/why Win10 is doing stuff with Drive-K?

If you mean the access to "K:\$...", I think you'll find at least some of that is related to file system (ie. NTFS) maintenance. For example, $Mft stands for master file table. Some of it could also be related to indexing [for search etc.].

 

[RonD]

Do not know W10 NTSF file system gory details, some of that looks like background housekeeping to keep file system running. I turned indexing off on drive-K, so I would hope that is not running. But I also used W10 Power Settings do disable "Turn Off Drive". But with long 0.5 to 0.8 second disk drive delays, sure looks like drive-K is shutting down and needs time to spin back up to speed.

 

[Owlsroost]

@RonD - just checking that the modified TsReader is OK? Are you getting any 'Unable to play' problems?

 

[RonD]

Ran with updated TsReader_v4.2.2.33.zip for 7+ days, have not seen either “Remote Client Unable to Play” or “VideoExit error just after start” problem. So I’d recommend using the longer “UpdateDuration() - increased to 2 seconds (from 0.5s)”.

When I looked at the “streaming server.Log” I still see long 0.8 sec seektime for 1st access to idle drive-k: so I guess the WD “blue everyday” 3.5 inch desktop HDD has internal drive stop/start based on activity. If I use CrystalDiskInfo, the WD-Blue (WD30EZRZ) and WD-Green (WD20EARX) HDDs do not have options to enable/disable HDD APM (Advance Power Management). Did not find any WD tools to modify APM settings.

just checking that the modified TsReader is OK? Are you getting any 'Unable to play' problems?

sorry for the delay, I wrote this earlier in the week, forgot to press "post" so it never got added. my post was still sitting in the edit window

 

[Owlsroost]

OK, good - thanks for the feedback

 

[Owlsroost]

Attached is a new version of TsReader.ax for testing - version 4.2.2.35

This has the RTSP timeout changes plus some other changes related to an issue in another thread - MP 1.16 MPAR Broken/Bug

(To install, replace TsReader.ax in C:\Program Files (x86)\Team MediaPortal\MediaPortal with the new version)

 

[mm1352000]

Owlsroost, are you thinking to include the increased RTSP timeout in a future version of MP?

 

[RonD]

put TsReader_4.2.2.35.zip on all 3 systems. Quick test shows no problems. Will try for rest of week and look for problems. This time I will make sure I press reply "post" when I do a thread update.