ATI Radeon 4350 no hi-def?

[keith_leitch]

Discovered here:

http://www.xpmediacentre.com.au/communit...on-15.html

that the latest driver may not suit this card. These symptoms are consistent with my experience (audio and even video vanishing until a restart). I will be rolling back to 9-9 to try to deal with it.

However, this card with the Avivo codecs (and the CoreAVC h.264 decoder) was working very well until this afternoon, when suddenly I lost the ability to watch 1080i. I have checked very carefully, and none of my codecs or decoders have changed. Any ideas?

[pBS]

what cat version were you running?
i do have a workaround for the disappearing video tho...auto-restart hdmi connection, causing windows to set it up just like a fresh power on..
running hdmiOn upon resume from suspend...
http://thydzik.com/tag/hdmion/
[if you use HIP can use it's scheduler to run upon resume/suspend]
or i made a util to run stuff on resume..not sure how it works in win7 tho..

or if you just close gbpvr before suspend and restart upon resume, it'll probably fix this also..[shouldn't suspend while running a fullscreen d3d app]

also may want to check the lastgraph.grf [enable in config.xml]
to see if anything has really changed...[tho logs should also show actual codecs used also..]
oh and what os? os is critical to diagnosing video problems cuz the drivers are not created equal..
[xp has been left out in the cold, little progress in drivers]

[keith_leitch]

what cat version were you running?

Was 9-12...now 9-9. The situation may have improved with the downgrade, but I have had a similar problem once (below).

i do have a workaround for the disappearing video tho...auto-restart hdmi connection, causing windows to set it up just like a fresh power on..
running hdmiOn upon resume from suspend...

This may help if it works for XP. Althought the disappearing video hasn't been nearly as m much of a problem since upgrading to this adapter, I noticed this morning that my Catalyst decided it was looking at a DVI connection; thus, the audio vanished. I am using HIP, so that is no problem.

[pBS]

yea, i think most of these problems are cuz with a media playing app open when suspend happens, it locks up the hdmi audio, making it not work when coming back in..

but if the app is closed before suspend, then everything should be ok..
[of course then you have to restart it yourself upon resume, but that's better than no sound]
shouldn't need hdmiOn app if you close gbpvr b4 suspend..
after enough suspend/wakes, even video will suffer if app left open during..so always best to close it before..

[keith_leitch]

yea, i think most of these problems are cuz with a media playing app open when suspend happens, it locks up the hdmi audio, making it not work when coming back in..

I agree. I have been auto-closing PVRx2 on suspend since about day two. Still, something is haunting my memory and causing similar problems. Sapphire's response was quite hilarious: "reformat your hard driver and reinstall the O/S and drivers."

(Not that this wouldn't work, necessariy, but it seems draconian).

[stustunz]

yes but alot of the time its quicker and you get a fresh system that runs better

[pBS]

re-installing usually does yield good results...but what a pain..

yea, it's always helpful when the people making a product don't know how it works...

that's one of the main reasons i'm here, you can actually request help and the original author will reply...within minutes no less...
unlike the rest of the entire world where they have no idea where the original programmer is, he left years ago and now it's maintained by flunkies that don't really understand it fully..
so as the software matures, it gets more and more unstable, and fixes get next to impossible to realize or take years...

what i don't get is, you can't legally sell a car that doesn't work, but you can put out software and hardware that you know don't work properly..no easy recourse..[sometimes requiring class action lawsuit to get any satisfaction]

[pBS]

anyways...i'd look at the deinterlacing settings again...[make sure you select the appropriate monitor when adjusting as they keep different settings per monitor]
3d settings can also affect it, and maybe changing logon/profiles also...
that's why i make an image of the windows drive and keep gbpvr on it's own drive...
so i can get windows exact config back without disturbing gbpvr..
but ya got to get it working first..

[keith_leitch]

anyways...i'd look at the deinterlacing settings again...[make sure you select the appropriate monitor when adjusting as they keep different settings per monitor]

I only noticed an hour ago that Catalyst 9-9 is correctly identifying my TV by its model number. This was NOT the case with 9-12, so I guess 9-9 really is a better choice for this adapter.

I also believe that this caused the ITC option to appear, so that I can finally get my TV to do some of the work it was designed for (like deinterlacing). It's too early to tell, but there seems to be a performance improvement as a result.

Stu, I will reinstall...but on my terms, not theirs. I first want to know that all of my new hardware is co-operating, so that I can reinstall it (and only it) with optimal drivers, without "uninstalling" and "rollling back" and otherwise leaving junk behind.

[keith_leitch]

I've encountered the same problem at least four times now. This card seems to encounter something it "doesn't like" in video files, at which point it freezes for about five seconds, then blanks the video. The system is still alive, and I can poke around until I get it restarted gracefully. However, it's really an unacceptable problem.

I'm not sure what to do, as the 9-12 drivers caused this and other problems, and from what I've read, the 9-9 drivers I am using are the best fit for this card. I am fairly confident that changing resolution and changing it back again will kick-start the card...but that really shouldn't be necessary, should it?

Edit: Changing resolutions DOES work, but the driver crash seems to hang the system for much longer than I thought. It is about 5 seconds until the screen goes blank, then another 20-30 seconds before I can successfully change resolutions. (The many attempts bank up in the typeahead buffer).

I also tried disabling VPU Recovery in Catalyst. This had the effect of restarting the computer upon encountering the error, rather than blanking the video.