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
Line at bottom of screen
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: 1187121" data-attributes="member: 82144"><p>Thanks - got 'em.</p><p></p><p>A couple of notes...</p><p></p><p>First, due to your log verbosity setting and the fact that you used Watchdog option 3 ("export..."), there's only one MediaPortal log file that's of any use for the reported problem. It covers 5 to 6 June.</p><p></p><p>2. Though you said that you're running MP 1.13, the log file reports MP 1.12:</p><p>[2016-06-05 20:29:26,607] [Log ] [MPMain ] [INFO ] - Build: 1.12.0.0</p><p></p><p>3. You mentioned you'd tried adjusting overscan in MP settings. I'm not sure if the available log file is meant to show that, but from what I can see there was no custom calibration applied:</p><p>[2016-06-05 20:29:52,449] [Log ] [MPMain ] [WARN ] - GraphicContext: NO screen calibration file found for resolution 1920x1080!</p><p></p><p>4. The DirectX diagnostic program provided by Microsoft and run by the Watchdog has reported failure to acquire system information:</p><p>DxDiag Previously: Crashed in system information (stage 1). Re-running DxDiag with "dontskip" command line parameter or choosing not to bypass information gathering when prompted might result in DxDiag successfully obtaining this information</p><p></p><p>That's a bad sign.</p><p></p><p>Ultimately, I can't see anything that would cause the reported problem. Right from the start it looks like MP is aware that your screen resolution is 1920x1080, and so MP sets its size accordingly.</p><p></p><p>If you want people to dig further I'd suggest you provide more information:</p><ol> <li data-xf-list-type="ol">Use the Watchdog <strong>with option 1 </strong>to collect new log files.</li> <li data-xf-list-type="ol">Specify the date/time and name of the movie you play to illustrate the problem.</li> <li data-xf-list-type="ol">Provide details about the video output for this system. In particular:<ul> <li data-xf-list-type="ul">What is the vendor and model of TV you're using, and how is it connected?<br /> </li> <li data-xf-list-type="ul">Do you have an AV receiver? If yes, what is the vendor and model, and how is it connected?</li> <li data-xf-list-type="ul">Are there any other devices - for example, HDMI splitters - connected along the way?</li> </ul></li> </ol></blockquote><p></p>
[QUOTE="mm1352000, post: 1187121, member: 82144"] Thanks - got 'em. A couple of notes... First, due to your log verbosity setting and the fact that you used Watchdog option 3 ("export..."), there's only one MediaPortal log file that's of any use for the reported problem. It covers 5 to 6 June. 2. Though you said that you're running MP 1.13, the log file reports MP 1.12: [2016-06-05 20:29:26,607] [Log ] [MPMain ] [INFO ] - Build: 1.12.0.0 3. You mentioned you'd tried adjusting overscan in MP settings. I'm not sure if the available log file is meant to show that, but from what I can see there was no custom calibration applied: [2016-06-05 20:29:52,449] [Log ] [MPMain ] [WARN ] - GraphicContext: NO screen calibration file found for resolution 1920x1080! 4. The DirectX diagnostic program provided by Microsoft and run by the Watchdog has reported failure to acquire system information: DxDiag Previously: Crashed in system information (stage 1). Re-running DxDiag with "dontskip" command line parameter or choosing not to bypass information gathering when prompted might result in DxDiag successfully obtaining this information That's a bad sign. Ultimately, I can't see anything that would cause the reported problem. Right from the start it looks like MP is aware that your screen resolution is 1920x1080, and so MP sets its size accordingly. If you want people to dig further I'd suggest you provide more information: [LIST=1] [*]Use the Watchdog [B]with option 1 [/B]to collect new log files. [*]Specify the date/time and name of the movie you play to illustrate the problem. [*]Provide details about the video output for this system. In particular: [LIST] [*]What is the vendor and model of TV you're using, and how is it connected? [*]Do you have an AV receiver? If yes, what is the vendor and model, and how is it connected? [*]Are there any other devices - for example, HDMI splitters - connected along the way? [/LIST] [/LIST] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Line at bottom of screen
Contact us
RSS
Top
Bottom
