Log in

View Full Version : Media Player Classic Home Cinema (MPC-HC) - DXVA!


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 [190] 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410

G_M_C
31st August 2009, 22:50
[...]
ConvertToRGB32()
[...]


Try / see if using another colormatrix helps;

ConvertToRGB32 (clip [, string "matrix"] [, bool "interlaced"])
matrix: Default Rec601. Controls the colour coefficients and scaling factors used in RGB - YUV conversions.
* "Rec601" : Use Rec.601 coefficients, scaled to TV range [16,235].
* "PC.601" : Use Rec.601 coefficients, keep full range [0,255].
* "Rec709" : Use Rec.709 coefficients, scaled to TV range.
* "PC.709" : Use Rec.709 coefficients, keep full range.

73ChargerFan
31st August 2009, 23:41
I checked the MadVR thread, and the current problem is ... shock ... tearing.

And I remembered that the gotcha of MadVR is that it does everything using the GPU, in a strangely hypocritical fashion.
Please try not to insult every developer at doom9.

leeperry
31st August 2009, 23:58
while watching you see a coloring issue with madVr ?
what do you mean? http://tbn3.google.com/images?q=tbn:jbnLRUtO6drlaM

ADude
1st September 2009, 00:40
Please try not to insult every developer at doom9.

There is nothing wrong with developing video stuff and putting it out there for people to try.

But, if you put something out, you must expect some examination of what you are doing, i.e. does it make sense.

On the one hand, you have people like Casimir666 and others who are dedicated to a project like MPC-HC, and they are willing to deal with whatever is needed for the sake of the project.

On the other hand, there seem to be people fascinated with the idea " if only we could correct this one thing in digital video, then it would be fine. "

Over and over again, they seem to not understand that digital video is lossey and is a chain of elements. So, you cannot perfect digital video just by getting one parameter right.

You end up with two extremes, the amateur developers who think that just getting the renderer right or just getting the sync right will make everthing look good, and on the other extreme, the ATI and Nvidia and MS developers who have to balance 100 different factors, and so end up with 100 different compromises.

The fact that both Beliyaal's EVR code and MadVR cause tearing is testament to the fact that it is not as simple as it looks.

Mangix
1st September 2009, 01:44
the vsync code is pretty strange indeed. I get tearing with mpc ONLY when i resize the window(ie enter full screen) and when i press alt + enter again, no tearing. d3d exclusive mode doesn't have the problem since you can't resize. Happens with both GothSync and Beliyaal code.

yesgrey
1st September 2009, 02:06
The fact that both Beliyaal's EVR code and MadVR cause tearing is testament to the fact that it is not as simple as it looks.
I know I will repeat myself... But have you tryed with a decent graphics card? Maybe it's that simple...;)

avivahl
1st September 2009, 02:39
I know I will repeat myself... But have you tryed with a decent graphics card? Maybe it's that simple...;)Huh? his graphics card worked fine b4 the code changes. It had no tearing. Why would he even consider upgrading just because of some half-working piece of code?

Btw, I say this as a person w/ geforce 8800GT and no tearing problems what-so-ever.

THX-UltraII
1st September 2009, 07:54
Activate auto-loading of subtitles and name the .srt file like your .mkv file (with different extensions of course).

thanks for your reply. I ll try this tonight. But I wonder if it will work, because I also have Haali Media Splitter installed. In the settings of Haali Splitter I have set subtitle language priority to dut,eng. Did this because this way MPC-HC shows Dutch subtitles when available and when NOT available MPC shows English subtitles (all this is for files which have subtitles baked in).

ar-jar
1st September 2009, 08:03
the vsync code is pretty strange indeed. I get tearing with mpc ONLY when i resize the window(ie enter full screen) and when i press alt + enter again, no tearing. d3d exclusive mode doesn't have the problem since you can't resize. Happens with both GothSync and Beliyaal code.

When you tearing with gothsync, what sync option do you use and what value does Target sync offset have? If you show the statistics graph, where is the green line on that graph? Is it pretty stright?

Gothsync claims to eliminate tearing when you keep the green line (the actual execution of the image rendering code) far enough from vsync so that the rendering code has plenty of time to execute before the video buffer switch. If it executes too close to vsync, you get tearing.

Using "exclusive mode" fullscreen (called D3D in MPC) seems to eliminate tearing with any renderer due to factors that I guess only the driver developers know.

I myself never get tearing (I have one cheap ATI board and one 7000 series NV board) when the sync options in gothsync are correctly set so I would very much like to hear about how to induce it. Thanks! -A

_xxl
1st September 2009, 08:37
Btw, I say this as a person w/ geforce 8800GT and no tearing problems what-so-ever.
I had tested latest MPC-HC with 8600GT no tearing, 6600GT no tearing and FX5200 I get tearing and no code gothsync, beliyaal's or mpc's fixes it. Only exclusive mode" fullscreen fixed my problem.

THX-UltraII
1st September 2009, 10:09
I use XBMC as movie browser and MPC-HC starts as external player when selecting a movie. For XBMC I need to set wait for vertical sync to ALWAYS ON to remove tearing problems in XBMC. I used to have it set to OFF, unless application needs it. Now that I set it to ALWAYS ON, will this have any (negative) side-effects on MPC-HC?

I use MPC-HC with EVR Custom and Reclock.

mark0077
1st September 2009, 10:17
I use the same setup as you. For me it has no negative effects, I believe XBMC uses openGL. With the latest versions, my video still plays perfectly in sync as when xbmc loses focus, my windows desktop returns to AERO mode....

Unsure how well mpc-hc works outside of aero mode but I also believe that should be tear free..

THX-UltraII
1st September 2009, 10:23
I use the same setup as you. For me it has no negative effects, I believe XBMC uses openGL. With the latest versions, my video still plays perfectly in sync as when xbmc loses focus, my windows desktop returns to AERO mode....

Unsure how well mpc-hc works outside of aero mode but I also believe that should be tear free..

How did you set up XBMC to let it work with MPC-HC. Since I installed the latest (non-official) version of XBMC a few hours ago my advancedsettings.xml script does not work anymore.

I use XP with SP3 btw.

mark0077
1st September 2009, 11:33
Ya the newer versions don't use that file, its changed to a different xml file now, you'll have to check their site, I can't remember off hand. The contents are almost identical to the old one though, a few extra features relating to window focus etc.

yesgrey
1st September 2009, 12:21
Huh? his graphics card worked fine b4 the code changes.
Belyiaal did more than just adding new vsync code, he also corrected the bicubic resizer using the pixel shaders. The previous code was performing bilinear resizing instead of the bicubic, and that's easier for the GPU; it would be more helpful if he tests it using the bilinear resizer and let us know if it still tears.
Why would he even consider upgrading just because of some half-working piece of code?
He seems to be the only one that reports the tearing problems, and his motherboard x1250 gpu it's not very powerfull.
I could also say that H264 decoders sucks compared with MPEG2 ones because I have lot's of dropped frames with my old P4@2.4GHz, or that the people developing the software decoders are not very good...;)
I also have a 8600GT and don't have any tearing problems. With a current $40 or $50 he could probably correct his tearing problem, but it's a lot easier to blame the code developers.

avivahl
1st September 2009, 12:22
I had tested latest MPC-HC with 8600GT no tearing, 6600GT no tearing and FX5200 I get tearing and no code gothsync, beliyaal's or mpc's fixes it. Only exclusive mode" fullscreen fixed my problem.Well, one cannot expect every graphics card setup to work problem-free. I'm sure older cards also have driver issues that mpc-hc cannot help with (as Nvidia and ATI don't update drivers for old products). But notice: ADude's problem was NOT there before the Beliyaal changes, which can only mean one thing.

Leak
1st September 2009, 13:28
But notice: ADude's problem was NOT there before the Beliyaal changes, which can only mean one thing.
If by the "one thing" you mean that the now corrected bicubic scaler code needs more GPU power - absolutely.

np: Nine Inch Nails - The Beginning Of The End (Year Zero)

avivahl
1st September 2009, 13:59
If by the "one thing" you mean that the now corrected bicubic scaler code needs more GPU power - absolutely.Huh? And who says he's (ADude) even using the bicubic scaler? Or am I missing something? (I thought "bilinear" is default)
EDIT: Are you saying that the corrected bicubic code is the source for the tearing?

yesgrey
1st September 2009, 14:38
Huh? And who says he's (ADude) even using the bicubic scaler?
He did not answer it, and this was already stated several times. He prefers to keep pointing the finger to Beliyaal.

EDIT: Are you saying that the corrected bicubic code is the source for the tearing?
No. We are saying that the lack of gpu shader power of his pretty old and basic onboard gpu could be the source of the tearing.

clsid
1st September 2009, 14:50
The default is "Bilinear" (no pixelshaders). That is a sane default and the default should stay that way.

fastplayer
1st September 2009, 15:00
Is there any chance that Beliyaal's resizer fixes end up in the "old" MPC?

clsid
1st September 2009, 15:06
If there is anyone willing to backport such fixes, he/she can get SVN access to commit such patches.

fastplayer
1st September 2009, 15:19
If there is anyone willing to backport such fixes, he/she can get SVN access to commit such patches.
I assumed it was a simple "copy & paste". Apparently, it is not:
A quick diff between the old and new DX9AllocatorPresenter.cpp shows that both don't have a lot in common anymore...

avivahl
1st September 2009, 15:31
@ADude: did you modify any option (from its defaults) other then the renderer?

nlnl
1st September 2009, 15:33
Is there any way to smoothly play interlaced video (1080i, VC-1, H264) in MPC-HC (Vista32, Nvidia 9400) using Nvidia Purevideo hardware deinterlacer?
Can not smoothly play in software (and hardware) deinterlacing mode using internal MPC decoders/Arcsoft/ffdshow/CoreAVC/internal Vista VC-1 decoder.
Can anybody help?

yesgrey
1st September 2009, 16:20
The default is "Bilinear" (no pixelshaders).
Thanks. Sorry for the misinformation, I already edited my post.

Casshern
1st September 2009, 17:18
Well, one cannot expect every graphics card setup to work problem-free. I'm sure older cards also have driver issues that mpc-hc cannot help with (as Nvidia and ATI don't update drivers for old products). But notice: ADude's problem was NOT there before the Beliyaal changes, which can only mean one thing.

But Beliyaal's changes also fix a lot of stuff for many people:
Frame stutter with AGP boards
bicubic resizer
tearing with some nvidea boards
smoothness of playback when framerates do not match display framerates

Following your logic this could also mean "ONLY ONE THING".

I see the whole as follows:
1) MPC is a work in progress
2) The beliyaal changes fix a lot of bugs and sadly also introduce some new bugs for some
3) The basic idea behind the changes is sound and push mpc forward - they allow a much better access to vsync-control, even if not perfect
4) The normal way of software-development, would be to file bug reports and try to fix the bugs if possible AND NOT to go back to the stoneages. I bet MS-DOS also works for ADUDE why ever change....
5) Some bugs on certain configuration probably never get fixed, as the critical mass of users is to low or they can be avoided by modest hardware upgrades.
6) In instances when i was affected by 5 i always tried to be polite to developers point at the problem and provide as much info as possible, even digging into technical details. Mostly per PM.

This worked pretty good - and that's also the reason why i react strangely to people attacking the devs for the stuff they do for free. Especially i do not feel that the devs owe anybody, and certainly not when ADUDE could just be polite or buy a new gfx board for $40.

Mercury_22
1st September 2009, 17:52
Is there any way to smoothly play interlaced video (1080i, VC-1, H264) in MPC-HC (Vista32, Nvidia 9400) using Nvidia Purevideo hardware deinterlacer?
Can not smoothly play in software (and hardware) deinterlacing mode using internal MPC decoders/Arcsoft/ffdshow/CoreAVC/internal Vista VC-1 decoder.
Can anybody help?

Try this
1 - reset MPC-HC's settings
2 - enable frame time correction
3 - for vc-1 i use Microsoft's WMVideo decoder DMO (disable MPC-HC's VC-1 internal filters, and make sure that WMVideo decoder DMO has the highest merit)

PS: Really really :) don't skip first one (see http://sourceforge.net/apps/mediawiki/mpc-hc/index.php?title=Troubleshooting_guidelines) and really really :) use only mpc-hc's splitters ( and filters EXCEPT FOR VC-1 !!!)

w0rd™
1st September 2009, 19:34
Hi, I have winxp pro, ati3800series card with latest drivers, and the latest MPC-HC.

I've had a problem for a while now, and I'm not sure when it started, as I've been using MPC, then MPC-HC for a long time now.

Some of my recorded programs with dvbviewer dont play right in mpchc. There is one show I record every week, and it happens with this show every single time, so it's repeatable.

Basically, when I play it, the seekbar/time left shows double the time, so instead of say 1hr, it shows 2hrs remaining. Now when I watch the show, and I'm 20mins into it for example, when the commercials come, and I press the skip button, the video returns to an earlier time, for example it will jump to the 5min mark.

Previously, I tried unchecking "MPEG PS/TS/PVA" source in mpchc, and it solved the problem, because it somehow started using the main concept splitter(but this wasn't as smooth for seeking in other recordings which don't have this problem).

Now though, with latest mpc-hc, I'm still having this problem, I tried unchecking the mpeg source again, but it just uses MPEG source (gabest) instead.
I tried intalling haali and checking the MPEG PS option, but it still uses it's own.

I'd like to just get the mpc-hc internal source to work if possible.

here is the mediainfo of the file that gives me trouble:




Format : MPEG-PS
File size : 6.97 GiB
Duration : 1h 15mn
Overall bit rate : 13.2 Mbps

Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@High
Format settings, Matrix : Default
Duration : 1h 15mn
Bit rate mode : Variable
Bit rate : 12.2 Mbps
Width : 1 440 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 25.000 fps
Colorimetry : 4:2:0
Scan type : Interlaced
Scan order : Top Field First
Bits/(Pixel*Frame) : 0.313
Stream size : 6.46 GiB (93%)

Audio
ID : 128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Format profile : Dolby Digital
Duration : 1h 15mn
Bit rate mode : Constant
Bit rate : 448 Kbps
Channel(s) : 2 channels
Channel positions : L R
Sampling rate : 48.0 KHz
Video delay : -439ms
Stream size : 243 MiB (3%)







Oh and just one other thing, how can I get mpchc to open my files automatically, if I go to "open with" option in windows and browse for mpc-hc, it just refuses to add it to the list, so I can choose it?

tetsuo55
1st September 2009, 20:27
@ w0rd™ > Sample please.

@ everyone > Adude already tried every setting available (bicubic actually fixes some issues, but overall its still a mess for him)

Adude's problems are probably caused by minute refreshrate difference between reported and actual.

@ Adude > Could you post a screenshot of the latest gothsync build with CTRL+J enabled, while playing a file that is a multiple of your screen refresh rate?

Settings have to be EVR CP / 0-255 / syncnearest.

The new stats might show us exactly what is wrong with the frame timing.

Latest gothsync private build here: http://www.ostrogothia.com/?page_id=1213

yesgrey
1st September 2009, 21:29
@ everyone > Adude already tried every setting available (bicubic actually fixes some issues, but overall its still a mess for him)
But have he tryed with a graphics card instead of his onboard old gpu?
I don't say that it's not caused by minute refreshrate difference between reported and actual, as you say, but it seems to be a very complex cause compared with the simpler one of low gpu power...;)

Piyoko
1st September 2009, 22:17
Is there any way to smoothly play interlaced video (1080i, VC-1, H264) in MPC-HC (Vista32, Nvidia 9400) using Nvidia Purevideo hardware deinterlacer?
Can not smoothly play in software (and hardware) deinterlacing mode using internal MPC decoders/Arcsoft/ffdshow/CoreAVC/internal Vista VC-1 decoder.
Can anybody help?
I don't know if it's the same issue, but on XP and with the ATI hardware de-interlacing (HD4670) I get jerkiness/stuttering with 1080i video.

It seems like it might be a VSync issue, and I've tried to find one good combination that works out of all aspects, but I just can't do it. Here's what I have so far:

VMR9 (renderless), VMR9 mixer mode enabled:
No tearing, but stuttering.

VMR9 (renderless), VMR9 mixer mode disabled:
No tearing, no stuttering, but then the hardware de-interlacing doesn't work.

VMR9 (renderless), VMR9 mixer mode enabled, Alternative VSync enabled:
No stuttering, but tearing instead.

VMR9 (renderless), VMR9 mixer mode enabled, D3D Fullscreen w/ GUI Support:
No tearing, but stuttering.

VMR9 (renderless), VMR9 mixer mode enabled, D3D Fullscreen:
No tearing, no stuttering, everything works perfectly.

So essentially the D3D Fullscreen mode with no GUI is the only way I can properly play 1080i files, which is a shame as that mode is seriously annoying.

clsid
1st September 2009, 23:05
But have he tryed with a graphics card instead of his onboard old gpu?
I don't say that it's not caused by minute refreshrate difference between reported and actual, as you say, but it seems to be a very complex cause compared with the simpler one of low gpu power...;)If no pixelshaders are used, then there is no need for a powerful GPU.

ADude
2nd September 2009, 01:57
@ Adude > Could you post a screenshot of the latest gothsync build with CTRL+J enabled, while playing a file that is a multiple of your screen refresh rate?

The problems occur just as often, if not more often, with files that are not a multiple of my refresh rate.

PS When I first tried Beliyaal's version, the first thing suggested (by Testuo55 IIRC) was to not use bicubic, and actually the direction of resizing is such that bilinear is not a problem, so I switched permanently to that.

PPS I have nothing against Beliyaal and acknowledged that he has fixed a number of things. My only problem with him is that he has vanished, with still some remaining issues in the code.

hdboy
2nd September 2009, 03:57
is there any way to get OSD (vol, position, etc) with haali's renderer? it's the one that gives me least trouble but I miss the OSD.

St Devious
2nd September 2009, 04:03
is there a subtitle editor or subtitle resync function in MPC HC ?

tetsuo55
2nd September 2009, 06:33
But have he tryed with a graphics card instead of his onboard old gpu?
I don't say that it's not caused by minute refreshrate difference between reported and actual, as you say, but it seems to be a very complex cause compared with the simpler one of low gpu power...;)
There is a very good chance that a newer more powerfull videocard will solve his problems, personally i think we should try to solve the problem in MPC-HC, his system is a good edge case sample.
But we need the screenshot to be able to take any further steps.

The problems occur just as often, if not more often, with files that are not a multiple of my refresh rate.

PS When I first tried Beliyaal's version, the first thing suggested (by Testuo55 IIRC) was to not use bicubic, and actually the direction of resizing is such that bilinear is not a problem, so I switched permanently to that.

PPS I have nothing against Beliyaal and acknowledged that he has fixed a number of things. My only problem with him is that he has vanished, with still some remaining issues in the code.it has to be multiple for the new code to do something, non multiple disables it(for now)

NanoBot
2nd September 2009, 07:24
Hi,

is there a subtitle editor or subtitle resync function in MPC HC ?

yes, mpc-hc includes such a function. But it is only available if the subtitles are read from a seperate file. It is not available for subtitles which are already muxxed into the container used.

C.U. NanoBot

Astrophizz
2nd September 2009, 08:12
is there any way to get OSD (vol, position, etc) with haali's renderer? it's the one that gives me least trouble but I miss the OSD.

I still have the OSD with Haali's renderer - does it work with other renderers for you?

Snowknight26
2nd September 2009, 08:17
yes, mpc-hc includes such a function. But it is only available if the subtitles are read from a seperate file. It is not available for subtitles which are already muxxed into the container used.

There is the ability to add a delay to subtitles on the fly, even if they're muxed subs.

Mercury_22
2nd September 2009, 08:27
Revision 1267 - Directory Listing
Modified Wed Sep 2 03:00:53 2009 UTC (4 hours, 23 minutes ago) by aleksoid

ADD : Support S263(mobile phone) video codec;

:thanks:

hdboy
2nd September 2009, 14:15
I still have the OSD with Haali's renderer - does it work with other renderers for you?

yes OSD works for me with VMR9 and EVR. I'm using MPC-HC 1.3.1265.0, but earlier builds did not give me OSD in haali either.

I wonder what the difference is. I have a nvidia 7600GT. haali media splitter installed (don't know if that matters.) The OSD does not show with any type of media.

bozek
2nd September 2009, 14:33
Hallo and thanks for great player.
I wonder if is possible to use MPC-HC in M$ Visual Studio 2008 similarly like windows media player or for example VLC
via COM components.
Im sorry if this subject was discussed earlier, but I didn't find it.

matthew_eli
2nd September 2009, 15:42
Hi, as I reported before, I have artifacts with some video (with external subtitle) and I tried various program settings (as suggested here: http://nunnally.ahmygoddess.net/watching-h264-videos-using-dxva/) but with no result...then I wanted to see if it is a driver problem and it was: with Catalyst 9.4 (DNA) and Catalyst 9.5 there is no problem...so what is the thing that generates artifacts with newer driver???:confused:

I'm very confused...

MPC-HC 1249 gold release tested

yesgrey
2nd September 2009, 15:57
personally i think we should try to solve the problem in MPC-HC, his system is a good edge case sample.
Are you sure it's a problem in MPC-HC? Could also be a drivers issue...
I remember that, with my previous PC, I had some stuttering problems that were caused when I simply opened the WMP. After that, I had to re-install the SP2 of XP to solve the problem, because it reset WMP and everything worked fine again (I used Zoomplayer for my viewings).
Currently, with my more powerfull cpu and graphics card, the problem disappeared. Maybe SP3 also helped a little, but in the end, I think the problem is related to living in the edge...;)

ADude, don't you know someone that could borrow you a graphics card just for ruling that out?

ADude
2nd September 2009, 19:22
There is a very good chance that a newer more powerfull videocard will solve his problems, personally i think we should try to solve the problem.

You guys sound like you are 16 years old. In other words, anything prior to this year is "old". :D

ATI x1250 is a newer more powerful videocard. It is rated to play Blu-Ray discs.

I bought it brand new, as a recent product, after the release of MPC-HC.

Previously, I had been playing 720p HD videos just fine with MPC-HC with an ATI mobile Radeon 7500, also with no tearing.

Tearing has nothing to do with processor speed of any sort, and MPC-HC build 1043 has no tearing. Or is build 1043 now considered "old" ?? :D

ADude
2nd September 2009, 19:35
it has to be multiple for the new code to do something, non multiple disables it(for now)

If that is true, then it confirms my suspicion that Beliyaal removed code that deals with timing for situations that do not "sync", but never added his own code for those situations.

For example, if I play a video where the display rate cannot be a multiple of video fps, then:

- Build 1043 does not tear
- Later builds (with Beliyaal's sync code) tears
- Gothsync tears
- Gothsync with recent code for situations that are not a multiple ("Present at Nearest Vsync") does not tear.

I am hoping that ar-jar can spare enough time to verify that build 1043 and earlier did have such code that was removed.

ADude
2nd September 2009, 19:40
The 690G chipset is 2 years old, obsolete and outdated, whether you like it or not.

Five years from now, I wlil send you that quote, and you will laugh with me.

2 years is sometimes less than the amount of time that a product is delayed by a minor series of bugs.

It is also less than the amount of time this thread has been going:

3rd March 2007, 03:29

clsid
2nd September 2009, 23:00
Guys, please stop this nonsense discussion about hardware. GPU performance is clearly NOT the issue. Tearing is all about timing and can even occur with the next generation uber-powerful cards.

CruNcher
2nd September 2009, 23:07
@Casimir666
MPC Video Decoder doesn't fallback to libavcodec (Software Decoding) when playing x264 lossless bitstreams (G92/VP2) :(

Result =

http://s1.directupload.net/images/090902/8lny66mq.png