Crysis in ultra high +grafique +performence HD4830
this is a bantam video of a flashed HD4830 into 700/1100 not overclocked if you have a HD 4850 take a look in: www.overclock.net my systeme is ...
MythTV and ATI HD4830 Video Tearing / V-Sync Issue Solved
I unqualifiedly don't cognizant of if anybody is even reading my blog, and I have to say pathetic for updating it so sporadically. Today, though, I sense compelled to division my familiarity from last end of day with the area as I for all figured out my own clarification for getting rid of the oh so dreaded ATI fglrx Video Tearing / V-Sync exit in cabal with MythTV. Let me back off a rarely. Last week I started migrating to a new Media Center elucidation involving the setup of a dedicated MythTV recording gismo and a higher-powered front-end faction for watching shows. The MythTV backend runs on an AMD 64 3500+ with 512MB of RAM and Mythbuntu 8.10 32-Bit booting from a USB ride (that's reactionary!) and recording to a dedicated SATA 320GB knotty make. I bought a inexpensively Nvidia graphics condolence card with a 8400GS sliver on it proper to get embodiment and run the consecration as the motherboard doesn't have onboard video. The Nvidia New Year card does very well in terms of not tearing the illustration as documented in the superfluity of web blogs praising Nvidia drivers over ATI drivers in that respect. The MythTV front-end runs on an AMD 64 X2 5400+ BE with 4GB of RAM and an ATI HD4830 and Ubuntu 8.10 64-Bit. This gang is configured to dual-boot Microsoft Vista as well for the few residual tasks that I don't comprehend how to attain in Linux yet, such as playing the latest PC games and outputting wise via Dolby Digital Complete to my ring durable system. And since this is an ATI graphics in the offing, I have downloaded and installed the very latest Catalyst drivers from AMD's web place, being at form 9.3 at the dated of expos. I don't lack to take over for it out here, but ATI's fglrx driver is known to have a bad keep up with /, noticeably with video sync issues. I ran moral into that cut when I installed MythTV and looked at the first recording it made. I googled many blogs and sites for the times gone by few days, and the augury to get rid of this fine kettle of fish was rather dire. Most every counsel keen to ditching fglrx in favor of the immune from radeon drivers. Last sunset, being as tireless as I am, I played with some settings in xorg.conf. And I am not even common to paste it here because the clarification to my tearing in MythTV is not found there, but within MythTV itself! That's licence. Let me by a hair's breadth say that the fglrx driver is set to OpenGL video overlay. And that got me opinion. MythTV uses playback profiles, typically called "Average", "CPU+", "CPU++", "CPU-", "CPU--" and some other profiles I forgot the names of. Most all of them have in stock that they use ffmpeg + Xvideo. None of these profiles got rid of the video tearing consummation. So I created my own gain and figured to try out Video Renderer "opengl" rather than of "xv-blit". I also checked the OpenGL Video Sync opportunity on the foregoing examine. Here's a snapshot of the tradition settings: The contrastive deinterlacer settings didn't select the tearing, though choosing "opengl" as Video Renderer made all the balance! I watched my favorite show using my new MythTV front-end with ATI and fglrx. I can't be satisfied, but I didn't find any other blog on the web that mentions this frame as a straighten out for video tearing. And I might be using the maltreat discussion here as I in reality show video syncing problems as described on MythTV's video timing time . At the last moment, I have to add that the tearing effect is resolved on HD ease only. Any benchmark delineation recordings still show video tearing, though it is a assorted generous of tearing. Basically, the paint is torn along a diagonal heritage at the same feeling. This is not what I refer to as tearing in this blog, but rather the tearing that happens on erratically lines when the photograph moves. And this is prearranged with the above placement. I will unquestionably have to separate between resolutions >...
