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
Input / Output interfaces
Mini Display
Zalman HD135 VFD (VlSys Mplay)
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="Herr R aus B" data-source="post: 230953" data-attributes="member: 62807"><p><strong>Testing 20080201b</strong></p><p></p><p></p><p>Well, I can report something similar. Switching the plugin off in the configuration results in a CPU load of approx 1-2% when running MP in idle. Switching the plugin on results in a CPU load of some 53% where one CPU core is almost at 100% and the other up to 10% here (athlon dual core, 2,4GHz win XP pro X64) what about adding some milliseconds sleep to the thread loop? usually that should decrease CPU load - if these .NET threads behave the same as java threads (they should, as the basically are windows threads). btw - turning of the EQ doesn't have any effect - at least not on my machine here. I definately have to turn off the plugin</p><p></p><p></p><p>Getting even worse but the L/R indicators are helpful in a way. At least one can see, that obviously (obviously seems to be one of my favourite words... as "basically" was for my georgia peach ex gf from atlanta who has the name allison, which implied calling her "basic ally" as literally every 5th word she said basically was "basically"... I am drifting away from test reporting I guess...)</p><p></p><p><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite4" alt=":mad:" title="Mad :mad:" loading="lazy" data-shortname=":mad:" /> where did I get here? Oh yes...</p><p></p><p>obviously just the custom characters are affected by this effect. I did some new video clips showing the mono EQ and the VU meter both set to 1 rsp. 5 maximum updates per second. Especially with the VU meter one can see, that the regular characters (R and L) are absolute stable as the rest is wobbling or whatever that behaviour would be called... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p></p><p>Are you transferring the custom character bitmaps periodically (this language reminds me of my ex too much - I suggest continuing in danish, if that's OK...) or just once on VU/EQ initialization?</p><p></p><p>Anyway - I would like everybody to look at these video clips and do the same testing with their displays, as it might also be a general problem with my display - not very likely, but one never knows. Could you please then report the behaviour of your displays? Thanks...</p><p></p><p></p><p>In desperate need of new enemies? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p></p><p>A little bit more optimism regarding your coding capabilities please<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /> Looking at your output and the assiociated progress I don't expect THAT much versions until then <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>Being an old man I have a very reflected personality <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p></p><p>This would make the community being able to configre the device somewhat special <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /> AND I WAS KIDDING! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>As for the fan control. I did some testing with the manual settings using fan 1 from 10% through 100% - find the logs attached. Then I did two runs to test the AFC functionality. Doing these tests the heat sensors should report 32/33°C for sensor 1 and 37/38°C for sensor 2. In the first run I set the minimum temperature to switch of the fans to 26°C and the maximum temperature to set the fans to 100% to 65°C. In the second run i left the minimum temperature at 26°C and set the maximum temperature to 31°C. At least in the second run the fans were supposed to be VERY loud - but obviously (again!) they didn't run at all. I didn't bother to open the case as the case is buildt into a shelf and removing it from there would be some major effort... Let's put it like this: AFC doesn't seem to work at all... Find the extensive logs attached.</p><p></p><p>And here some minor issues:</p><p></p><ul> <li data-xf-list-type="ul">Testing the VU/EQ with extensive logging crashed MP on shutdown - see attached log, maybe it's helpful</li> <li data-xf-list-type="ul">There is a little bug in the config dialogue - resetting all values (using the RESET button) resets the remote repeat frequency to 0 but the label still shows the previous value</li> <li data-xf-list-type="ul">The two shutdown lines that can be configured in the main config dialogue don't seem to have any effect as in not being displayed on MP shutdown</li> <li data-xf-list-type="ul">The contrast slider in the main config dialogue doesn't have any effect on the display - I guess, the display doesn't support that...</li> </ul><p></p><p>And then I had to realize, that I accused you of typos where there were no typos - the damn display indeed is called MP300 and not MR300 - I am embarassed <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> I hope you'll tolerate, that I am not willing to through myself in the dust as I am too old for that shit <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /> And as I stopped smoking almost one year ago there also are no overflowing ashtrays available to pour some ashes on my head... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p></p><p>And as I wrote this test report you already put a new version online... but as I can see, it just affects other displays... Maybe there will be much more versions if it goes on like that <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p></p><p>Greets</p><p></p><p>Axel</p></blockquote><p></p>
[QUOTE="Herr R aus B, post: 230953, member: 62807"] [b]Testing 20080201b[/b] Well, I can report something similar. Switching the plugin off in the configuration results in a CPU load of approx 1-2% when running MP in idle. Switching the plugin on results in a CPU load of some 53% where one CPU core is almost at 100% and the other up to 10% here (athlon dual core, 2,4GHz win XP pro X64) what about adding some milliseconds sleep to the thread loop? usually that should decrease CPU load - if these .NET threads behave the same as java threads (they should, as the basically are windows threads). btw - turning of the EQ doesn't have any effect - at least not on my machine here. I definately have to turn off the plugin Getting even worse but the L/R indicators are helpful in a way. At least one can see, that obviously (obviously seems to be one of my favourite words... as "basically" was for my georgia peach ex gf from atlanta who has the name allison, which implied calling her "basic ally" as literally every 5th word she said basically was "basically"... I am drifting away from test reporting I guess...) :wtf: where did I get here? Oh yes... obviously just the custom characters are affected by this effect. I did some new video clips showing the mono EQ and the VU meter both set to 1 rsp. 5 maximum updates per second. Especially with the VU meter one can see, that the regular characters (R and L) are absolute stable as the rest is wobbling or whatever that behaviour would be called... :D Are you transferring the custom character bitmaps periodically (this language reminds me of my ex too much - I suggest continuing in danish, if that's OK...) or just once on VU/EQ initialization? Anyway - I would like everybody to look at these video clips and do the same testing with their displays, as it might also be a general problem with my display - not very likely, but one never knows. Could you please then report the behaviour of your displays? Thanks... In desperate need of new enemies? ;) A little bit more optimism regarding your coding capabilities please:D Looking at your output and the assiociated progress I don't expect THAT much versions until then :) Being an old man I have a very reflected personality ;) This would make the community being able to configre the device somewhat special ;) AND I WAS KIDDING! :) As for the fan control. I did some testing with the manual settings using fan 1 from 10% through 100% - find the logs attached. Then I did two runs to test the AFC functionality. Doing these tests the heat sensors should report 32/33°C for sensor 1 and 37/38°C for sensor 2. In the first run I set the minimum temperature to switch of the fans to 26°C and the maximum temperature to set the fans to 100% to 65°C. In the second run i left the minimum temperature at 26°C and set the maximum temperature to 31°C. At least in the second run the fans were supposed to be VERY loud - but obviously (again!) they didn't run at all. I didn't bother to open the case as the case is buildt into a shelf and removing it from there would be some major effort... Let's put it like this: AFC doesn't seem to work at all... Find the extensive logs attached. And here some minor issues: [LIST] [*]Testing the VU/EQ with extensive logging crashed MP on shutdown - see attached log, maybe it's helpful [*]There is a little bug in the config dialogue - resetting all values (using the RESET button) resets the remote repeat frequency to 0 but the label still shows the previous value [*]The two shutdown lines that can be configured in the main config dialogue don't seem to have any effect as in not being displayed on MP shutdown [*]The contrast slider in the main config dialogue doesn't have any effect on the display - I guess, the display doesn't support that... [/LIST] And then I had to realize, that I accused you of typos where there were no typos - the damn display indeed is called MP300 and not MR300 - I am embarassed :) I hope you'll tolerate, that I am not willing to through myself in the dust as I am too old for that shit :D And as I stopped smoking almost one year ago there also are no overflowing ashtrays available to pour some ashes on my head... :D And as I wrote this test report you already put a new version online... but as I can see, it just affects other displays... Maybe there will be much more versions if it goes on like that :D Greets Axel [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Input / Output interfaces
Mini Display
Zalman HD135 VFD (VlSys Mplay)
Contact us
RSS
Top
Bottom
