home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
Tv Recordings Broken Video and Audio
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1194125" data-attributes="member: 82144"><p>Stephen, I'm sticking to the power theory.</p><p></p><p>The tvserver_TsWriter.bak that I think you were intending to refer to does indeed show continuity errors starting at 20:35:27:</p><p>[2016-08-21 20:00:03,996] [4588130] [6c0] - mhw reset</p><p>[2016-08-21 20:35:27,033] [4588130] [19c0] - Recorder<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue :p" loading="lazy" data-shortname=":p" />id 65 Continuity error... 8 ( prev 1 ) - bad signal?</p><p></p><p>...and stopping at 20:40:34 when you claim to have started viewing the recording:</p><p>[2016-08-21 20:40:34,690] [4588130] [19c0] - Recorder<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue :p" loading="lazy" data-shortname=":p" />id 66 Continuity error... 6 ( prev 4 ) - bad signal?</p><p>[2016-08-21 21:02:07,820] [4588130] [403c] - Recorder: RECORD Stop 'E:\Recorded TV\BBC TWO HD\Robot Wars\Robot Wars - 2016-08-21.ts'</p><p></p><p>(Note: I have no way to check that 20:40 was when you started viewing the recording, but I have no reason to doubt you.)</p><p></p><p>There are two things that stand out for me.</p><p></p><p>First, the recording starts at 19:58:</p><p>[2016-08-21 19:58:03,568] [4588130] [403c] - Recorder: RECORD Start 'E:\Recorded TV\BBC TWO HD\Robot Wars\Robot Wars - 2016-08-21.ts'</p><p></p><p>The TsWriter log file doesn't show any continuity problems between 19:58 and 20:35. This suggests that there were no problems during that time, and that only the section between 20:35 and 20:40 was damaged.</p><p>Can you confirm?</p><p></p><p>Second, the Windows application event log file shows a power event at 20:34:</p><p>"2016-08-21 20:34:46";"TV Server";"(0)";"Information";"PowerEvent handled successfully by the service.";"0"</p><p></p><p>The corresponding entries in the TV service log:</p><p>[collapse]</p><p>[2016-08-21 20:34:46,294] [Log ] [PowerEventThread] [DEBUG] - TV service PowerEventThread received WM_POWERBROADCAST 7</p><p>[2016-08-21 20:34:46,295] [Log ] [PowerEventThread] [DEBUG] - OnPowerEvent: PowerStatus: ResumeSuspend</p><p>[2016-08-21 20:34:46,296] [Log ] [PowerEventThread] [DEBUG] - OnPowerEventHandler: PowerStatus: ResumeSuspend</p><p>[2016-08-21 20:34:46,297] [Log ] [PowerEventThread] [DEBUG] - PS: RESUMESUSPEND</p><p>[2016-08-21 20:34:46,307] [Log ] [23 ] [DEBUG] - Detecting BDA/WDM devices...</p><p>[2016-08-21 20:34:46,308] [Log ] [23 ] [DEBUG] - Detect legacy AM filter devices</p><p>[2016-08-21 20:34:46,340] [Log ] [23 ] [DEBUG] - Detect AM KS crossbar devices</p><p>[2016-08-21 20:34:46,341] [Log ] [23 ] [DEBUG] - Detect AM KS TV tuner devices</p><p>[2016-08-21 20:34:46,341] [Log ] [23 ] [DEBUG] - Detect BDA source devices[/collapse]</p><p></p><p>This ties into my previous observation. If the 19:58 to 20:35 section is fine, something must have happened at or around 20:35 which explains why the continuity errors start. The only possible explanation I can see in any log file is this power event (...which signals the system's transition from being in away mode to being fully awake).</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1194125, member: 82144"] Stephen, I'm sticking to the power theory. The tvserver_TsWriter.bak that I think you were intending to refer to does indeed show continuity errors starting at 20:35:27: [2016-08-21 20:00:03,996] [4588130] [6c0] - mhw reset [2016-08-21 20:35:27,033] [4588130] [19c0] - Recorder:Pid 65 Continuity error... 8 ( prev 1 ) - bad signal? ...and stopping at 20:40:34 when you claim to have started viewing the recording: [2016-08-21 20:40:34,690] [4588130] [19c0] - Recorder:Pid 66 Continuity error... 6 ( prev 4 ) - bad signal? [2016-08-21 21:02:07,820] [4588130] [403c] - Recorder: RECORD Stop 'E:\Recorded TV\BBC TWO HD\Robot Wars\Robot Wars - 2016-08-21.ts' (Note: I have no way to check that 20:40 was when you started viewing the recording, but I have no reason to doubt you.) There are two things that stand out for me. First, the recording starts at 19:58: [2016-08-21 19:58:03,568] [4588130] [403c] - Recorder: RECORD Start 'E:\Recorded TV\BBC TWO HD\Robot Wars\Robot Wars - 2016-08-21.ts' The TsWriter log file doesn't show any continuity problems between 19:58 and 20:35. This suggests that there were no problems during that time, and that only the section between 20:35 and 20:40 was damaged. Can you confirm? Second, the Windows application event log file shows a power event at 20:34: "2016-08-21 20:34:46";"TV Server";"(0)";"Information";"PowerEvent handled successfully by the service.";"0" The corresponding entries in the TV service log: [collapse] [2016-08-21 20:34:46,294] [Log ] [PowerEventThread] [DEBUG] - TV service PowerEventThread received WM_POWERBROADCAST 7 [2016-08-21 20:34:46,295] [Log ] [PowerEventThread] [DEBUG] - OnPowerEvent: PowerStatus: ResumeSuspend [2016-08-21 20:34:46,296] [Log ] [PowerEventThread] [DEBUG] - OnPowerEventHandler: PowerStatus: ResumeSuspend [2016-08-21 20:34:46,297] [Log ] [PowerEventThread] [DEBUG] - PS: RESUMESUSPEND [2016-08-21 20:34:46,307] [Log ] [23 ] [DEBUG] - Detecting BDA/WDM devices... [2016-08-21 20:34:46,308] [Log ] [23 ] [DEBUG] - Detect legacy AM filter devices [2016-08-21 20:34:46,340] [Log ] [23 ] [DEBUG] - Detect AM KS crossbar devices [2016-08-21 20:34:46,341] [Log ] [23 ] [DEBUG] - Detect AM KS TV tuner devices [2016-08-21 20:34:46,341] [Log ] [23 ] [DEBUG] - Detect BDA source devices[/collapse] This ties into my previous observation. If the 19:58 to 20:35 section is fine, something must have happened at or around 20:35 which explains why the continuity errors start. The only possible explanation I can see in any log file is this power event (...which signals the system's transition from being in away mode to being fully awake). [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Tv Recordings Broken Video and Audio
Contact us
RSS
Top
Bottom