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
Area 51 - Testing Area
5154: MediaPortal 1 - x64 - SharpDX
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="Pablik" data-source="post: 1294754" data-attributes="member: 106554"><p>Hi, nothing unusual in the log except the call to display uninit (when MP is closing) won't return. This is the reason why you have to close the proxy from task manager. I gonna have to put some timeout for executing this command becouse it blocks everything.</p><p>Anyway, it seems to me that driver is somehow busy with processing of the data. Question is why this is not happening in x86 version. Only difference between the platform versions is that native call to the driver is executed in proxy app (in MP x86 version directly from MiniDisplay plugin) and I don't see anything wrong in communications between MiniDisplay plugin and proxy(over socket). I'll try to more investigate this issue...</p><p>For the start, can you try larger time values in "Scroll delay (ms)" and "Update (ms)" in MiniDisplay config? For example 500ms or even bigger. This should slow down sending the pixel data to the display driver.</p><p>Thanks for the logs.</p></blockquote><p></p>
[QUOTE="Pablik, post: 1294754, member: 106554"] Hi, nothing unusual in the log except the call to display uninit (when MP is closing) won't return. This is the reason why you have to close the proxy from task manager. I gonna have to put some timeout for executing this command becouse it blocks everything. Anyway, it seems to me that driver is somehow busy with processing of the data. Question is why this is not happening in x86 version. Only difference between the platform versions is that native call to the driver is executed in proxy app (in MP x86 version directly from MiniDisplay plugin) and I don't see anything wrong in communications between MiniDisplay plugin and proxy(over socket). I'll try to more investigate this issue... For the start, can you try larger time values in "Scroll delay (ms)" and "Update (ms)" in MiniDisplay config? For example 500ms or even bigger. This should slow down sending the pixel data to the display driver. Thanks for the logs. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Area 51 - Testing Area
5154: MediaPortal 1 - x64 - SharpDX
Contact us
RSS
Top
Bottom