Call for tester for 1.4.0 features and fixes (1 Viewer)

[Scythe42]

Glitch related to the SplashScreen. If I make this go away other might see a black screen later on. Tried different variations, but didn't really work out so far. Cannot reproduce any of the variants. Root cause is that the Splash Screen is a different form run in its own thread. Pain to sync both properly.

Does this only happens when using the fullscreen splashscreen? Always on top enabled or disabled? Minimize to Tray on Startup set?

Videos would help. Logs do not show such an issue.

Also please try with 15c above.

 

[FreakyJ]

@elliotmc
I can't confirm... I used another system (my normal Test system), this one also has a vga monitor attached.
I see the normal splash screen, than for a brief second a black screen with cursor and taskbar than mp appears

 

[FreakyJ]

a video what I see on my vga setup:

 

[disaster123]

I still have the problem that when i send the htpc to hibernate the minidisplay does not go offline. It stays online. Is this known? If not I'll post logs today. Thanks!

 

[Lightning303]

@Lightning303: could you also do a test? I know from your logs that the Volume Handler threw some errors. Also want to make sure that I didn't break the fix I added for your scenario (freezing after multiple hibernate/resume cycles).

Sure.
Everything worked for me. Did the hibernate/resume tests first. All good. After that i did what @FreakyJ described and i could change the volume after turning on my avr again without problems. I attached logs.
While testing i accidently pressed channel down instead of volume down, when i saw that a immediatly pressed channel up again, so it wouldnt change the channel. It seems that just pressing channel up or down also throws exceptions, and not just pressing a number. Dont know if you were aware of that, i wasnt ;p.

 

[elliottmc]

@Lightning303: could you also do a test? I know from your logs that the Volume Handler threw some errors. Also want to make sure that I didn't break the fix I added for your scenario (freezing after multiple hibernate/resume cycles).

Sure.
Everything worked for me. Did the hibernate/resume tests first. All good. After that i did what @FreakyJ described and i could change the volume after turning on my avr again without problems. I attached logs.
While testing i accidently pressed channel down instead of volume down, when i saw that a immediatly pressed channel up again, so it wouldnt change the channel. It seems that just pressing channel up or down also throws exceptions, and not just pressing a number. Dont know if you were aware of that, i wasnt ;p.

Same problem as zapOSD ?

 

[Lightning303]

@Lightning303: could you also do a test? I know from your logs that the Volume Handler threw some errors. Also want to make sure that I didn't break the fix I added for your scenario (freezing after multiple hibernate/resume cycles).

Sure.
Everything worked for me. Did the hibernate/resume tests first. All good. After that i did what @FreakyJ described and i could change the volume after turning on my avr again without problems. I attached logs.
While testing i accidently pressed channel down instead of volume down, when i saw that a immediatly pressed channel up again, so it wouldnt change the channel. It seems that just pressing channel up or down also throws exceptions, and not just pressing a number. Dont know if you were aware of that, i wasnt ;p.

Same problem as zapOSD ?

Well for me as a user there was no problem in changing the channel by channel up or down. So that works, but i noticed afterwards when checking the logs, that there ware errors and they showed a problem with TVZapOSD (look at the end of my error.log). I just wanted to point that out.

 

[Scythe42]

a video what I see on my vga setup:

Then let's start to work on that glitch. I think I know what's causing it after seeing it. Next time, please record with more fps.

[2013-04-07 20:45:22,541] [6937  ] [MPMain  ] [DEBUG] - Main WM_SIZE
...
[2013-04-07 20:45:22,619] [7016  ] [MPMain  ] [DEBUG] - RENDER

As yo can see there are 78ms between the time when the main form was made active and the first frame rendered. If no frame is rendered in fullscreen you do not see anything. Everything is transparent. No window controls nothing, even though the form is active and visible. But nothing had been rendered to it yet.

But why are frames not yet rendered automatically? Welcome to the nice world of WinForms and its magical OnSomething() methods. Yeah, the form is not active and therefore all the nice methods do nothing.

I just don't care. Let's call the Render Loop and and see what's happening.

[2013-04-07 21:00:11,558] [6876  ] [MPMain  ] [DEBUG] - Main: Auto play start listening
[2013-04-07 21:00:11,559] [6877  ] [BassAudio] [INFO ] - BASS: Initialize BASS environment ...
[2013-04-07 21:00:11,559] [6877  ] [MPMain  ] [INFO ] - Main: Initializing volume handler
[2013-04-07 21:00:11,584] [6902  ] [MPMain  ] [DEBUG] - Main: Registering for Device Notifications
[2013-04-07 21:00:11,587] [6905  ] [MPMain  ] [DEBUG] - RENDER
[2013-04-07 21:00:11,651] [6969  ] [MPMain  ] [DEBUG] - D3D: ShowLastActiveModule active : False
[2013-04-07 21:00:11,663] [6980  ] [MPMain  ] [DEBUG] - Main WM_SIZE

Elvis has left the building! Got my frame. That should take care of this visual glitch (there are other of course in regards to the Splashscreen)

Will sort out the code a bit (added tons of debugs logs and broke some other stuff while testing) and provide build 15d for a quick test by @FreakyJ and @elliottmc as they can reproduce the issue and know what to look for. I cannot see it. It is going to fast on my GPU. Maybe the VGA connection plays some role here that this is more visible.

 

[Scythe42]

While testing i accidently pressed channel down instead of volume down, when i saw that a immediatly pressed channel up again, so it wouldnt change the channel. It seems that just pressing channel up or down also throws exceptions, and not just pressing a number. Dont know if you were aware of that, i wasnt ;p.

That's the ZapOSD regression I somehow introduced. I guess I changed some methods too much and know TVPlugin needs some adjustments.

Always report what feels strange to you if you are not sure I am aware of it.

That will be the main fix for Build 16 during the coming week, when I got DVB-T working. Getting no channels at the moment. Maybe need to spend a night in the office.

 

[Scythe42]

I still have the problem that when i send the htpc to hibernate the minidisplay does not go offline. It stays online. Is this known? If not I'll post logs today. Thanks!

Logs will not tell me anything here. Such stuff is not logged.

But should not Windows itself turn it off?

If not, and it must be controlled by MP, then I need to know how MP activates, deactivates it. Should only be a matter of adding some turn on/turn off calls, preferable in a try and catch statement to be on the safe side.

I do not have a MiniDisplay, so I cannot do much at the moment.

We have to options here:

• Someone tells me how to control the MiniDisplay from MP in regards to turning it off and on .
• Someone sends me a MiniDisplay I can connect to an external USB port for fixing this issue. Just temporarily, I send it back afterwards. Anyone with a spare in the EU interested in getting this fixed?