Valts Posted August 3, 2008 Posted August 3, 2008 I am unsure if they are all caused by the DBV but here goes. System is Windows XP SP3, ATI HD3650 video, renderer VMR7 + VMR Fix, Cyberlink mpeg2 & H264 codec with DXVA active. 1) OSD is slow to respond in general, scrolling menu items takes at least 0.5sec per item. Can be eased by disabling OSD background display. This issue is present for a long time already with a previous videocard (8500GT) as well. 2) HD OSD skins - if used in conjuction with a HD channel it causes video to go out of sync - drop frames etc. Solved by using SD skins which naturally don't look that great on a HD TV screen. 3) OSD doesn't show up until the channel has properly tuned & started actually showing, which is a problem if channel doesn't tune for some reason (dead, encrypted, etc). Which means that once you got to such channel basically need to get a mouse, switch to window, get channel list, etc. Posted about this before but got 0 responses. support.zip Quote
Valts Posted August 13, 2008 Author Posted August 13, 2008 Bit of new information. HD OSD skins - seems the same problem is present on SD channels as well, just not as pronounced. Makes them still unwatchable tho. No idea why that happens As for tuning... I suspect the graph is not built that's why it's not showing, if that's the case maybe it's possible to show some notification that tuning is in progress etc in a seperate window like it's done for the bottom pop-up bar? Quote
SnoopyDog Posted August 13, 2008 Posted August 13, 2008 (edited) 1) OSD is slow to respond in general, scrolling menu items takes at least 0.5sec per item. Can be eased by disabling OSD background display. This issue is present for a long time already with a previous videocard (8500GT) as well. I also see this issue on one of my machines. Don't know so far, what may cause the problem. Lars gave the hint, if the resolution of the OSD skin does not match the display resolution very good, this may cause problems, especially in conjunction with "bad" OSD quality settings. Edited August 13, 2008 by SnoopyDog Quote
Valts Posted August 13, 2008 Author Posted August 13, 2008 I also see this issue on one of my machines. Don't know so far, what may cause the problem. Lars gave the hint, if the resolution of the OSD skin does not match the display resolution very good, this may cause problems, especially in conjunction with "bad" OSD quality settings. Hmm can you elaborate on not matching 'very good'? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.