New beta/experimental OSD rendering resolution for HD300 ?

[voidpt]

Just saw the new beta 20101022 0 firmware for HD300. One bullet I found interesting:
» 5. Increase resolution of the osd plane (experimental)

Anybody know what we are talking about ? Think we are at 1024x576 now (or is it 960x540). Is the HD300 now trying for 1280x720 ?

Any setting we need to perform. Or will the upgrade in itself default to it ?

[jaminben]

I guess thats what it means..... no other setup required.

Cheers

Ben

[Opus4]

The System Info menu will display the current extender UI resolution; the new experimental resolution is 1280x720.

- Andy

[voidpt]

Originally Posted by Opus4

The System Info menu will display the current extender UI resolution; the new experimental resolution is 1280x720.

Forgot that one. Took a look, and yes:
» Display: 1920x1080p@50, Window: 1280 x 720

Nice Guess there is at least one happy duck on the forum

PS: Respect that it is experimental, so could go back. Just makes it so much more logical to have 720p, especially for those using native 720p displays.

[peternm22]

Andy,

Is there any noticeable slowdown on the HD300 running it at the higher resolution?

[PLUCKYHD]

Originally Posted by peternm22

Andy,

Is there any noticeable slowdown on the HD300 running it at the higher resolution?

There is a little but I wouldn't say it is noticable and the trade offfor crisper text and ui is well worth it. I am one happy duck over this looks so much better.

[drewg]

I just submitted a bug. Basically, I have malore menus enabled. The HD300 locked up twice in exactly the same way -- when closing a malore recording menu (select recording, then hit cancel). The menu does its shrinking animation and the extender locks solid. It stopped responding to the remote, and the only way to reboot it was to hard power-cycle or telnet in and reboot. I think it might be some kind of kernel bug, as this was in dmesg when I telnet'ed in:

Connected to 172.31.193.165.
Escape character is '^]'.

tango3 login: root
tango3[~]# dmesg
2a48>] vfs_ioctl+0xcc/0xe8
[<840c2c44>] do_vfs_ioctl+0x9c/0x73c
[<840c3328>] sys_ioctl+0x44/0x94
[<84005d64>] stack_done+0x20/0x3c

---[ end trace 7be2de7b6422a5f3 ]---
------------[ cut here ]------------
WARNING: at kernel/irq/manage.c:274 enable_irq+0x5c/0xe0()
Unbalanced enable for IRQ 31
Modules linked in: em8xxx(P) llad(P) irkernel rt2870sta sigmablock(P) [last unloaded: llad]
Call Trace:
[<840095bc>] dump_stack+0x8/0x34
[<84034a5c>] warn_slowpath_common+0x70/0x98
[<84034ac4>] warn_slowpath_fmt+0x24/0x30
[<8406ffc0>] enable_irq+0x5c/0xe0
[<c0295c2c>] minor_ioctl+0xf8/0x1f20 [llad]
[<840c2a48>] vfs_ioctl+0xcc/0xe8
[<840c2c44>] do_vfs_ioctl+0x9c/0x73c
[<840c3328>] sys_ioctl+0x44/0x94
[<84005d64>] stack_done+0x20/0x3c

---[ end trace 7be2de7b6422a5f4 ]---
------------[ cut here ]------------
WARNING: at kernel/irq/manage.c:274 enable_irq+0x5c/0xe0()
Unbalanced enable for IRQ 31
Modules linked in: em8xxx(P) llad(P) irkernel rt2870sta sigmablock(P) [last unloaded: llad]
Call Trace:
[<840095bc>] dump_stack+0x8/0x34
[<84034a5c>] warn_slowpath_common+0x70/0x98
[<84034ac4>] warn_slowpath_fmt+0x24/0x30
[<8406ffc0>] enable_irq+0x5c/0xe0
[<c0295c2c>] minor_ioctl+0xf8/0x1f20 [llad]
[<840c2a48>] vfs_ioctl+0xcc/0xe8
[<840c2c44>] do_vfs_ioctl+0x9c/0x73c
[<840c3328>] sys_ioctl+0x44/0x94
[<84005d64>] stack_done+0x20/0x3c

I've submitted a bug with this information & reverted to the release firmware..

Drew

[PLUCKYHD]

Do you have any plugins installed that modify the malore menus? That is where I would start.

[drewg]

Originally Posted by PLUCKYHD

Do you have any plugins installed that modify the malore menus? That is where I would start.

Just the Pheonix fan art for malore. But from the dmesg, it looks like a driver problem. According to /proc/intgerrupts irq31 is tangox_irq gfx. I don't have time right now to disable plugins, and need it to work for today/tomorrow.

Drew

[_Demo_]

Could you give me your overscan settings from your client properties file?

Thanks

[drewg]

Originally Posted by _Demo_

Could you give me your overscan settings from your client properties file?

Thanks

Eeek... My intent was for them to be 0 -- I run my TV in full pixel mode, but I seem to be off by 2 pixels:

ui/ui_overscan_correction_offset_x=2
ui/ui_overscan_correction_offset_y=0
ui/ui_overscan_correction_perct_height=1.0
ui/ui_overscan_correction_perct_width=0.9979986

Should I fool with the overscan settings until they are 0, then re-try the beta?

Thanks,

Drew

[voidpt]

Originally Posted by drewg

... The HD300 locked up twice in exactly the same way -- when closing a malore recording menu (select recording, then hit cancel). The menu does its shrinking animation and the extender locks solid. It stopped responding to the remote, and the only way to reboot it was to hard power-cycle or telnet in and reboot. ...

Just about the same here, except using Serenity as theme. Had 3 lockups in in one day. With about same behavior as you describe. Locks solid, power-cycle to get working again. Have also reverted to previous firmware.

Here are my overscan settings:
» ui/ui_overscan_correction_offset_x=0
» ui/ui_overscan_correction_offset_y=1
» ui/ui_overscan_correction_perct_height=0.999
» ui/ui_overscan_correction_perct_width=0.9999986

Just occurred to me watching these settings. Why haven't I set these through properties file before ? And why don't SageTV give us an option to force/set 0,0,1,1 at once ? For those of us who know we have 1:1 pixel mapping on HDMI input on TV. Probably going to send a feature request on that one, when time.

[_Demo_]

I have not been able to reproduce the issue so far. Let me know if you find an easy way to do it.

For the exact 1:1 overscan settings it doesn't matter much since the osd plane doesn't match the output resolution exactly.

[PLUCKYHD]

I am wondering if it is the phoenix plugin overloading it and making it crash.

[Fuzzy]

Originally Posted by voidpt

Just about the same here, except using Serenity as theme. Had 3 lockups in in one day. With about same behavior as you describe. Locks solid, power-cycle to get working again. Have also reverted to previous firmware.

Here are my overscan settings:
» ui/ui_overscan_correction_offset_x=0
» ui/ui_overscan_correction_offset_y=1
» ui/ui_overscan_correction_perct_height=0.999
» ui/ui_overscan_correction_perct_width=0.9999986

Just occurred to me watching these settings. Why haven't I set these through properties file before ? And why don't SageTV give us an option to force/set 0,0,1,1 at once ? For those of us who know we have 1:1 pixel mapping on HDMI input on TV. Probably going to send a feature request on that one, when time.

Nevermind that if you actually had a true 1:1 1080p display, and used 0,0,1,1 overscan correction, your UI would be about 10-15% outside the screen. You aren't supposed to see the full 1920x1080 frame.

[drewg]

Originally Posted by _Demo_

I have not been able to reproduce the issue so far. Let me know if you find an easy way to do it.

For the exact 1:1 overscan settings it doesn't matter much since the osd plane doesn't match the output resolution exactly.

Ugh. So you're saying that setting the overscan to perfect full pixel should not matter?

I wonder if you could find the bug by inspection..? Do you have the source to the llad module? From the kernel messages I saw, there are unbalanced calls to disable_irq()/enable_irq() (eg, the llad irq was enabled when it should not have been). I'd suspect either a race, or some kind of bad error path left the llad irq enabled when it should not have been.. No matter whether or not there is an error in SageTV, there's certainly an error in the llad kernel module.

Drew

[drewg]

I edited the properties (w/sagetv server stopped) and set overscan to 0/1.0 I also disabled malore impacting ui mods (phoenix fanart, imdb search, fuzzy's malore tweaks) & updated to the hd300 beta f/w. I still managed to lock my hd300 (still with unbalanced enable_irq() scrolling in dmesg) within seconds of entering the malore recordings..

I flashed it back to the release f/w for now.

Drew

[drewg]

Originally Posted by Fuzzy

Nevermind that if you actually had a true 1:1 1080p display, and used 0,0,1,1 overscan correction, your UI would be about 10-15% outside the screen. You aren't supposed to see the full 1920x1080 frame.

Huh? I've got a true 1:1 1080p display, and with 0/1.0 settings, the UI goes right to the edge of the screen. I think you must be thinking of something with overscan built in, like a CRT or RPTV or something. What you describe is exactly how my circa 2004 1080i CRT would behave.

Drew

[voidpt]

Originally Posted by _Demo_

I have not been able to reproduce the issue so far. Let me know if you find an easy way to do it.

I'll go back to the beta in between. Will try to find a consistent action to reproduce it.

Originally Posted by PLUCKYHD

I am wondering if it is the phoenix plugin overloading it and making it crash.

Think you are in the clear. Have to admit (in shame), not using any Phoenix parts yet

Originally Posted by Fuzzy

Nevermind that if you actually had a true 1:1 1080p display, and used 0,0,1,1 overscan correction, your UI would be about 10-15% outside the screen. You aren't supposed to see the full 1920x1080 frame.

From my perspective we can both be right in this I do have a true 1:1 pixel mapped 1080p display. My Sony KDL-52X2000 has the following option:
» Menu / Settings / Screen / Display Area: Full Pixel (default: Normal)
Although, I used my display a few years before finding it What I do agree on is that much material, TV airings, are formated for always being shown on overscan'ed mode. But this messes up new material that is really made with the intention of showing the full frame (trailers, newer movies, so on). And to make it all messed up. We have older/newer LCD TV'es that per-default are set with overscan or 1:1 mapping. We have video cards in PC'es that per-default does 'reverse' overscan to be sure whole Windows UI (Start Menu) is shown on TV's having overscan on per-default. Just to be sure. Then we have HD300 who have video material sent '1:1 on cable', but the UI OSD can have its overscan adjusted. So bright new future we're living in That is at least my view on it. Probably more to it. But how I have experienced it so far.

[drewg]

Originally Posted by voidpt

I'll go back to the beta in between. Will try to find a consistent action to reproduce it.

For me at least, all it takes is opening (by hitting enter on the remote) a malore recording menu, then selecting close on the menu. If I repeat that a few times, I'm sure to lock up the box.

Drew
PS: Full pixel mode is getting better. I've had this TV (Sony KDL-46V3000) for a few years, and things have gradually gotten better (anybody remember the green line down the side on some NBC broadcasts). The only time I don't run in full pixel mode is one SD show my wife watches that has VBI data in the top few pixels. Aside from that, full pixel looks perfect on everything I watch. Especially BD rips.