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
Watch / Listen Media
watch/edit Videos
MP1.16 Remote Client Unable to Play: B43534E1 error watching Recorded TV
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: 1221184" data-attributes="member: 82144"><p>[USER=83973]@Owlsroost[/USER] </p><p>I'm discovering that the missing duration entry for the first recording in the streaming server log is not necessarily an indication that the server hasn't received a request.</p><p></p><p>The streaming server log file shows earlier interactions for both recordings. Those earlier interactions are the reason for the difference in duration logging. For the second recording, the interaction immediately prior to the failed playback attempt was a seek followed by a manual stop, whereas for the first recording it was a playback completion (end of file reached). That difference affects the value of m_iDurationCount which in turn determines whether the duration will be logged before the next playback attempt.</p><p></p><p>In my opinion it would be nice to have the duration logged before playback starts (ie. as per the second recording).</p><p></p><p>All this is to say that more investigation is required. Wireshark may give us the best picture of what's going on.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1221184, member: 82144"] [USER=83973]@Owlsroost[/USER] I'm discovering that the missing duration entry for the first recording in the streaming server log is not necessarily an indication that the server hasn't received a request. The streaming server log file shows earlier interactions for both recordings. Those earlier interactions are the reason for the difference in duration logging. For the second recording, the interaction immediately prior to the failed playback attempt was a seek followed by a manual stop, whereas for the first recording it was a playback completion (end of file reached). That difference affects the value of m_iDurationCount which in turn determines whether the duration will be logged before the next playback attempt. In my opinion it would be nice to have the duration logged before playback starts (ie. as per the second recording). All this is to say that more investigation is required. Wireshark may give us the best picture of what's going on. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Watch / Listen Media
watch/edit Videos
MP1.16 Remote Client Unable to Play: B43534E1 error watching Recorded TV
Contact us
RSS
Top
Bottom