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
WARNING: NVidia driver issue since 358.87
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: 1164936" data-attributes="member: 82144"><p>That is understood, but it doesn't really answer my question.</p><p>My question is: if you play the same file again, does the problem recur at the same time/point?</p><p>In other words: I'm trying to understand if the problem is repeatable, and therefore likely to be related to the file or codec... or if it is "random".</p><p></p><p>It also doesn't answer my other earlier questions at all.</p><p></p><p></p><p>To flesh these out...</p><p>I'm asking whether you use different codecs for videos and TV.</p><p>I'm asking whether your videos use different video and/or audio encodings to your TV content. For example, h.264/AVC vs. MPEG 2.</p><p>I'm asking whether your recordings might contain any corruptions (discontinuities, glitches etc.) due to signal strength/quality or other.</p><p>Please answer these questions.</p><p></p><p></p><p>Freezing while fast forwarding should be considered a different/separate issue, especially when you're talking about trying to FF at up to x16 speed (!!!).</p><p>You will get different FF/RW behaviour depending on the used codecs, DXVA config, and system processing power (ie. low end CPU/GPU vs. high end), etc.</p><p>According to your log file x2 speed worked fine, but x4 and higher gave HRESULT error code 0x80004005 (which means <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/aa378137%28v=vs.85%29.aspx" target="_blank">E_FAIL - Unspecified failure</a>):</p><p>[2015-12-09 18:03:53,967] [Log ] [MPMain ] [INFO ] - VideoPlayer<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />etRate to:2 0</p><p>...</p><p>[2015-12-09 18:03:54,883] [Log ] [MPMain ] [INFO ] - VideoPlayer<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />etRate to:4 80004005</p><p></p><p>Perhaps you think that x4 and higher were working, I'm not sure. Ultimately the one and only point I'm trying to make is that what you were seeing is a different issue. Evidence for my claim is that there are no "GPU_HUNG" or D3D/DirectX error messages in your latest set of log files like there were in your previous log files.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1164936, member: 82144"] That is understood, but it doesn't really answer my question. My question is: if you play the same file again, does the problem recur at the same time/point? In other words: I'm trying to understand if the problem is repeatable, and therefore likely to be related to the file or codec... or if it is "random". It also doesn't answer my other earlier questions at all. To flesh these out... I'm asking whether you use different codecs for videos and TV. I'm asking whether your videos use different video and/or audio encodings to your TV content. For example, h.264/AVC vs. MPEG 2. I'm asking whether your recordings might contain any corruptions (discontinuities, glitches etc.) due to signal strength/quality or other. Please answer these questions. Freezing while fast forwarding should be considered a different/separate issue, especially when you're talking about trying to FF at up to x16 speed (!!!). You will get different FF/RW behaviour depending on the used codecs, DXVA config, and system processing power (ie. low end CPU/GPU vs. high end), etc. According to your log file x2 speed worked fine, but x4 and higher gave HRESULT error code 0x80004005 (which means [URL='https://msdn.microsoft.com/en-us/library/windows/desktop/aa378137%28v=vs.85%29.aspx']E_FAIL - Unspecified failure[/URL]): [2015-12-09 18:03:53,967] [Log ] [MPMain ] [INFO ] - VideoPlayer:confused:etRate to:2 0 ... [2015-12-09 18:03:54,883] [Log ] [MPMain ] [INFO ] - VideoPlayer:confused:etRate to:4 80004005 Perhaps you think that x4 and higher were working, I'm not sure. Ultimately the one and only point I'm trying to make is that what you were seeing is a different issue. Evidence for my claim is that there are no "GPU_HUNG" or D3D/DirectX error messages in your latest set of log files like there were in your previous log files. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
WARNING: NVidia driver issue since 358.87
Contact us
RSS
Top
Bottom
