Media Player Classic Home Cinema (MPC-HC) - DXVA! [Archive] - Page 112

madshi

7th January 2009, 08:18

you can use reclock without any resampling. Just set media adaptation speed to "original speed" and check the " slave reference clock to audio" option. The resampler is completelly bypassed, you can see the "bit exact" words appear in reclock's dialog.
Oh cool. Is that a new feature implemented by SlySoft? I don't remember having seen this in the ogo builds.

I can run MPC HC in Fullscreen mode (EVR custom) on my secondary monitor with Reclock working fine. I watched Hellboy in this configuration the other night - to see if Fullscreen mode is smoother than Haali in MPC HC or Zoom Player.
Thanks, I guess I'll have to retry a SlySoft ReClock build then...

tetsuo55

7th January 2009, 10:17

Well the interlaced flag is not necessary : fps it ok using mediatype on GetInputCurrentType.
But if you have another solution it's ok ;)

Maybe we should give the interlace flag a try, seeing as almost all deinterlacing tests are failing with almost every decoder

yesgrey

7th January 2009, 11:45

Oh cool. Is that a new feature implemented by SlySoft? I don't remember having seen this in the ogo builds.
No, the ogo's 1.7beta4 already had it and worked fine. It only had a small cosmetic bug, because the "bit exact" words only appeared when checking the options in a certain sequence.
I guess I'll have to retry a SlySoft ReClock build then...
Don't forget to download the new resampler (in a separate thread 0.1.5pre2). The Excellent mode is a lot better and faster than the included in ogo's version, and than kmixer.;)
It's the same quality as libsamplerate 0.1.3, which you can see here (http://src.infinitewave.ca/).

About the tearing, have you tryed setting the Vertical Sync always On in your graphics card drivers? VMR9 need it.

madshi

7th January 2009, 11:59

Don't forget to download the new resampler
No need for resampling on my side. I'll try ReClock only in bit exact mode.

About the tearing, have you tryed setting the Vertical Sync always On in your graphics card drivers? VMR9 need it.
I've tried everything. VSync on/off. ReClock on/off. Different renderers. And every possible combination of all these options. Some combinations work for a while. But the only thing that in my setup killed tearing once and all is FullScreen mode. I've never seen any hint of tearing since I switched to using FullScreen mode...

yesgrey

7th January 2009, 12:15

I'll try ReClock only in bit exact mode.
Remember that reclock's bit exact mode is only internal, it means he's outputting what he receives at the input. If you don't use Kernel Streaming for PCM, and keep using DirectSound, it will not bypass kmixer, even if it shows bit exact...

But the only thing that in my setup killed tearing once and all is FullScreen mode. I've never seen any hint of tearing since I switched to using FullScreen mode...
Let me try to understand, you are talking about FullScreen mode, when you select Direct3D Fullscreen in VMR9 Renderless or EVR Custom? or just when you switch from MPC-HC in a window to fullscreen?

Mercury_22

7th January 2009, 12:45

After
Revision 949 - Directory Listing
Modified Sun Jan 4 10:50:01 2009 UTC (3 days ago) by casimir666
Fixed : VC1 software playback with M2TS files
All my M2TS / VC-1 are out of sync with EVR Custom + WMVideo Decoder DMO + all audio AC3, DTS, DTS-HD, ... ! (All the other renders are on sync but the image it's very very choppy !) With internal VC-1 filter (DXVA or NO DXVA) I have just a black screen no audio no video with all renders :confused:
Can anyone confirm this ?

Leak

7th January 2009, 14:02

I've never seen any hint of tearing since I switched to using FullScreen mode...
It's just not 100% possible to get tearing-free video in a window UNLESS you're using a video overlay, which VMR9 most of the time doesn't.

The D3D renderers of course manage to be tearing free as they use the same "wait for VSync" mechanism that games use, but again - only in fullscreen.

The problem here is that usually in Windows you there's no double-buffering going on (might be different with Aero, but I don't have Vista) so you have to copy the new image directly into the framebuffer. And if this happens at the same time that the graphics card is reading the frame buffer to send data to your monitor - you get tearing, because the image changes in the middle of being displayed.

Sure, you should also be able to wait for VSync, but if you're unlucky the OS schedules some other tasks first and then it takes than the player long enough to update the video image that this again happens while the image is being displayed.

Beliyaal

7th January 2009, 14:17

After

All my M2TS / VC-1 are out of sync with EVR Custom + WMVideo Decoder DMO + all audio AC3, DTS, DTS-HD, ... ! (All the other renders are on sync but the image it's very very choppy !) With internal VC-1 filter (DXVA or NO DXVA) I have just a black screen no audio no video with all renders :confused:
Can anyone confirm this ?

This is because of incorrect timing of the frames output by the decoder. It happens both with the internal and external Decoder DMO. It might be that the splitter is giving the decoder incorrect times?

Anyway I have implemented a workaround for this in my patch for the Custom EVR.

leeperry

7th January 2009, 14:19

The D3D renderers of course manage to be tearing free as they use the same "wait for VSync" mechanism that games use, but again - only in fullscreen.
I've never ever had any tearing except with regular EVR on XP, as this thing relies on Aero for the VSYNC correction I think.

it would appear that the most common cause for tearing would be some buffering speed problem in the motherboard/BIOS/chipset.....data would not be copied fast enough...or maybe some "magic"/hidden setting that some manufacturers enable in their BIOS by default.

it would seem that some motherboard(Asus?)/graphic card combinations are more prone to tearing than others.

I've got a Gigabyte P31 mobo, and I've tried a lot of nvidia/ati cards....never got any tearing with any EVR/VMR/HR flavor in windowed modes only(I can't stand the exclusive stuff where all the menus vanish :D )

Beliyaal

7th January 2009, 14:21

It's just not 100% possible to get tearing-free video in a window UNLESS you're using a video overlay, which VMR9 most of the time doesn't.

The D3D renderers of course manage to be tearing free as they use the same "wait for VSync" mechanism that games use, but again - only in fullscreen.

The problem here is that usually in Windows you there's no double-buffering going on (might be different with Aero, but I don't have Vista) so you have to copy the new image directly into the framebuffer. And if this happens at the same time that the graphics card is reading the frame buffer to send data to your monitor - you get tearing, because the image changes in the middle of being displayed.

Sure, you should also be able to wait for VSync, but if you're unlucky the OS schedules some other tasks first and then it takes than the player long enough to update the video image that this again happens while the image is being displayed.

In my Custom EVR patch I have changed the method for VSync in both VMR9 and Custom EVR. I'm not sure if it works for all graphics drivers, but it works in Windowed mode at least. I'm still trying to fix a glitch that seems to appear randomly however that can cause a small tear (about 10 pixels from top).

moshmothma

7th January 2009, 14:42

Hey guys,

I have to correct myself. I claimed earlier that it's not possible to get full BTB and WTW output with VMR/EVR with an ATI card. I was wrong. Feeding VMR/EVR with RGB32 does make BTB and WTW work. I'm sorry for the confusion.

Hmm, I am using rgb32 with no btb or wtw. How did u accomplish this madshi? thx

yesgrey

7th January 2009, 14:46

never got any tearing with any EVR/VMR/HR flavor in windowed modes only(I can't stand the exclusive stuff where all the menus vanish :D )

Remember there is a difference between using a software player in a window, and using it fullscreen with VMR9 windowed.
Leak was referring to the first, and you are referring to the last.
There are 3 VMR9 possible modes of operation (More details here (http://msdn.microsoft.com/en-us/library/ms788090(VS.85).aspx)):
-VMR9 Windowed
-VMR9 Windowless
-VMR9 Renderless

You can use all this 3 modes in a window, or full screen, but only renderless allow the fullscreen exclusive access mode, like the games do.
The question is if madshi tearing is when using mpc-hc in a window (when you have the borders, menus, title bar, etc. showing) and when activate fullscreen it disappears, or if it disappears only when he selects the exclusive access mode.

leeperry

7th January 2009, 14:50

Remember there is a difference between using a software player in a window, and using it fullscreen with VMR9 windowed.
Leak was referring to the first, and you are referring to the last.
There are 3 VMR9 possible modes of operation (More details here (http://msdn.microsoft.com/en-us/library/ms788090(VS.85).aspx)):
-VMR9 Windowed
-VMR9 Windowless
-VMR9 Renderless

You can use all this 3 modes in a window, or full screen, but only renderless allow the fullscreen exclusive access mode, like the games do.
The question is if madshi tearing is when using mpc-hc in a window (when you have the borders, menus, title bar, etc. showing) and when activate fullscreen it disappears, or if it disappears only when he selects the exclusive access mode.
oh yeah, well I still rest my case. I've never had any tearing in any mode(windowed/windowless/renderless/exclusive D3D), except for regular EVR on XP(as it relies on Aero natively to fix the VSYNC)

anyhow, from what I've seen only HR does realtime jitter correction...the other software renderers simply drop frames if they're too late :rolleyes:

clsid

7th January 2009, 14:57

SPDIFER is just a subset of AC3FILTER, in other words, a simplified version that just outputs to SPDIF:

http://ac3filter.net/projects/spdifer

Vorbis loads a filter that converts to PCM and also AC3FILTER itself that takes the PCM and outputs it to the spdif.

SPDIFER is used literally hundreds of times by my HT-PC and MPC to playback videos with never one problem.

PS VLC includes internal selection of multiple audio streams, and can select either the Vorbis or the DTS stream in this file, but cannot pass the DTS intact to the spdif.
I already know what SPDIFER is, that was not my question. Don't output to SPDIF and you'll probably discover that things start working again. Why stream switching doesn't work with SPDIF? I don't know, I don't have a receiver myself. You could try with ffdshow, maybe using the same filter for all audio formats works better with SPDIF. ffdshow can do AC3/DTS passthrough, decoding/processing, and even re-encoding to AC3.

madshi

7th January 2009, 14:59

Remember that reclock's bit exact mode is only internal, it means he's outputting what he receives at the input. If you don't use Kernel Streaming for PCM, and keep using DirectSound, it will not bypass kmixer, even if it shows bit exact...
Yes, I understood that. My only reason for giving ReClock another try is that I want to check whether I can get Kernel Streaming to work without resampling.

Let me try to understand, you are talking about FullScreen mode, when you select Direct3D Fullscreen in VMR9 Renderless or EVR Custom? or just when you switch from MPC-HC in a window to fullscreen?
"Direct3D Fullscreen". Simple fullscreen doesn't help.

It's just not 100% possible to get tearing-free video in a window UNLESS you're using a video overlay, which VMR9 most of the time doesn't.
Maybe I didn't express myself clearly. I'm not talking about tearing in a window. I'm getting tearing even in normal fullscreen mode. It goes away only when using MPC HC's special "Direct3D fullscreen" mode.

leeperry

7th January 2009, 15:01

I'm getting tearing even in normal fullscreen mode. It goes away only when using MPC HC's special "Direct3D fullscreen" mode.
and what are your mobo/graphic cards again ?
does GPU-Z say "16X PCI-E@16X" ?

madshi

7th January 2009, 15:02

Hmm, I am using rgb32 with no btb or wtw. How did u accomplish this madshi? thx
Does your display want PC levels (black at 0) or video levels (black at 16)? In the first case there's no way to get BTB/WTW. In the 2nd case you have to set ffdshow to RGB32 and in the "RGB conversion" tab under "contrast" you have to use "Full range".

yesgrey

7th January 2009, 15:05

I want to check whether I can get Kernel Streaming to work without resampling.
Also note that some sound cards drivers don't accept 24bit pcm, only 16bit or 32bit. So, if when using KS with 24bit pcm you get no sound try using ffdshow audio to output 32bit pcm. This happenned to me and it's not a reclock bug. With other renderers this is not an issue because kmixer resamples and changes the bit depth to 16bit...:(

It goes away only when using MPC HC's special "Direct3D fullscreen" mode.
What's your OS? Have you tryed with an NVidia card?

Mercury_22

7th January 2009, 15:07

This is because of incorrect timing of the frames output by the decoder. It happens both with the internal and external Decoder DMO. It might be that the splitter is giving the decoder incorrect times?

Anyway I have implemented a workaround for this in my patch for the Custom EVR.
It's undoubtedly the splitter because when using other splitter everything it's ok !

P.S. Also the subtitles are flickering with internal splitter and vc-1 / DMO !

madshi

7th January 2009, 15:10

and what are your mobo/graphic cards again ?
Mobo: AOpen i945GTm-VHL (MoDT).
Graphics card: Club3D 3850 and Gigabyte 2600 Pro

does GPU-Z say "16X PCI-E@16X" ?
Yes. 53GB/s bandwidth. Should be plenty.

What's your OS? Have you tryed with an NVidia card?
XPSP2 Professional. Had a XFX 7600GS once. But that's long time ago. I *think* I had the same problems with it, too, but I don't remember for sure. I also once had a Fujitsu-Siemens mainboard. Same problems, as far as I remember...

tetsuo55

7th January 2009, 15:14

Does your display want PC levels (black at 0) or video levels (black at 16)? In the first case there's no way to get BTB/WTW. In the 2nd case you have to set ffdshow to RGB32 and in the "RGB conversion" tab under "contrast" you have to use "Full range".

I'm not sure i understand what you guys are talking about.
Commercial video data does not contain BTB/WTW

BTB/WTW is only needed for desktop

leeperry

7th January 2009, 15:19

Mobo: AOpen i945GTm-VHL (MoDT).
Graphics card: Club3D 3850 and Gigabyte 2600 Pro

Yes. 53GB/s bandwidth. Should be plenty.
humm tearing is neither normal or acceptable!
you might try to fiddle around with your motherboard BIOS(disabling all unused ports, disable/enable spread spectrum etc), or simply change to a newer model...you could try with a cheap GA-EP31-DS3L it works perfectly fine, and is a complete steal :D

madshi

7th January 2009, 15:44

I'm not sure i understand what you guys are talking about.
Commercial video data does not contain BTB/WTW
Sometimes it does. E.g. I've once read that a studio intentionally used BTB in a specific scene to make a specific red tone appear "correct". Anyway, it doesn't really matter whether BTB/WTW is actually used by DVD/Blu-Ray discs. Potentially it *could* be used, but a properly calibrated display would hide most of the BTB/WTW data. ISF calibrators usually calibrate so that one step below BTB is still barely different to BTB. And calibration test discs intentionally contain BTB/WTW information to allow for proper display calibration. With ffdshow setup as I said above, you do get BTB/WTW with a TV/projector which supports it. That means if you turn TV brightness too high, you will see the BTB information in a calibration DVD. If you let ATI do the YCBCr -> RGB conversion, you won't see the calibration DVD's BTB information.

humm tearing is neither normal or acceptable!
you might try to fiddle around with your motherboard BIOS(disabling all unused ports, disable/enable spread spectrum etc), or simply change to a newer model...you could try with a cheap GA-EP31-DS3L it works perfectly fine, and is a complete steal :D
Well, with all my past hardware, tearing was normal. Of course it's not acceptable. But Direct3D fullscreen mode fixes it for me. So I'm not in need to change my hardware right now. BTW, I have a mobile CPU because I hate noise. So I can't just use any mainboard.

tetsuo55

7th January 2009, 15:47

Sometimes it does. E.g. I've once read that a studio intentionally used BTB in a specific scene to make a specific red tone appear "correct". Anyway, it doesn't really matter whether BTB/WTW is actually used by DVD/Blu-Ray discs. Potentially it *could* be used, but a properly calibrated display would hide most of the BTB/WTW data. ISF calibrators usually calibrate so that one step below BTB is still barely different to BTB. And calibration test discs intentionally contain BTB/WTW information to allow for proper display calibration. With ffdshow setup as I said above, you do get BTB/WTW with a TV/projector which supports it. That means if you turn TV brightness too high, you will see the BTB information in a calibration DVD. If you let ATI do the YCBCr -> RGB conversion, you won't see the calibration DVD's BTB information.
Totally forgot those out of spec dvd's exist.
You're right!

mark0077

7th January 2009, 15:48

These methods of stopping tearing.... I still don't see them as being a perfect answer if your looking for smooth playback. OK no tearing but it doesn't mean the frames from your video content are synced with your refresh rate correctly....

Maybe reclock is the only answer to tearing + proper syncing?

yesgrey

7th January 2009, 17:28

XPSP2 Professional.
I was thinking that would be that... and let me guess, have you ever opened and initialized the Windows media player after upgrading to SP2?

I use ZoomPlayer and mpc-hc. When I had XP SP2, sometimes I had several problems when playing my media files. After a few minutes of playing, the video and audio started loosing sync. One time, I tryed reinstalling the SP2, and it fixed it. After a while it appeared again. I reinstalled SP2 and it fixed it again. I then realized that the problem was the Windows Media Player. It could not be used, not even initialized (after the SP2 update, if we run WMP always appear a brief tutorial of settings, this must be allways closed). I even had removed the shortcut from my quick launch bar because I could click it by mistake.
I don't know if it would fix your tearing, but you could always give it a try and re-install SP2. Currently I use SP3, but before you try with SP3 do it with SP2. That, I am certain worked for me, SP3 I don't know. Now I realize that I should try re-installing SP3, because the last time I saw a movie the jerkiness was back... Yes, due to VC1 decoder, I have updated to WMP11, and have opened it...:o

Commercial video data does not contain BTB/WTW
Remember that commercial video is YUV, and our displays are RGB. Only Y is limited to 16-235, UV is limited to 1-254, so, when you convert to RGB, you could get RGB lower than [16,16,16] and higher than [235,235,235] even if the YUV data is inside spec...

Totally forgot those out of spec dvd's exist.
And yes, some dvd's could have Y values out of those, but they are not out of spec, because it's not a hard limit, it's just reference values...

yesgrey

7th January 2009, 17:34

And calibration test discs intentionally contain BTB/WTW information to allow for proper display calibration.

Yes, it's the easiest way of knowing if our brightness is correctly setup... Too high, you see the black bellow the reference black, too low, you don't the the less darker blacks above the reference black.

leeperry

7th January 2009, 18:56

Well, with all my past hardware, tearing was normal. Of course it's not acceptable. But Direct3D fullscreen mode fixes it for me. So I'm not in need to change my hardware right now. BTW, I have a mobile CPU because I hate noise. So I can't just use any mainboard.
all I can say is that my previous mobo was a cheap 945PL from MSI, and I used MSI 8600GT/PNY 8600GTS/Gigabyte 2600Pro on it and I never got any tearing.
a wild guess would be that your mobo BIOS is either not properly configured, or badly optimized by the manufacturer himself.

any change if you set the PCI-E speed to 115/120/125Hz ?
reclock is the only answer to tearing + proper syncing
sure is :D

madshi

7th January 2009, 19:19

all I can say is that my previous mobo was a cheap 945PL from MSI, and I used MSI 8600GT/PNY 8600GTS/Gigabyte 2600Pro on it and I never got any tearing.
Did you use the secondary graphics card output port, like I do? But this is really getting OT. We should continue this dicussion in PM, if you want to.

leeperry

7th January 2009, 19:24

Did you use the secondary graphics card output port, like I do? But this is really getting OT. We should continue this dicussion in PM, if you want to.
CRT on primary, DVI pj on secondary and switching back and forth between the two.
well maybe you could create another topic ? I really wonder where that tearing comes from, and the more testimonials the better....probably video data is not copied fast enough by the chipset, so your only option is to get a new mobo...

Casimir666

7th January 2009, 19:53

sneaker_ger

7th January 2009, 20:17

rack04

7th January 2009, 20:25

Are the Matroska and Ogg souce filters stable enough to use or should I continue to us Haali Media Splitter?

Also, what should the renderer under filters say when it's connected to Haali Renderer? Mine says "Video Renderer" and this is the filter properties:

http://i11.photobucket.com/albums/a199/rack04/untitled-1.jpg

tetsuo55

7th January 2009, 20:49

Casimir666,

Would it be a good idea if someone (non-programmer) took the role of project manager.
You would still have the end vote in everything, but this person could take care of making sure all the bug/feature request reports are added to the bug/feature trackers.

This same person would keep the bug/feature tracker clean and give everything priorities/groups/assignee's and so forth.

This way you can focus your time on the long term goals, reviewing code others submit and coding yourself.

STaRGaZeR

7th January 2009, 20:59

I suppose a lot of people are waiting to test Beliyaal patch, so you can download a test build from thoses links (patch is not included in SVN yet)

32 bits :
http://www.zshare.net/download/538107912316050a/

64 bits :
http://www.zshare.net/download/53810877dc0daac4/

@Beliyaal
Good job for the ProcessHdmvLPCM fix, i have scratch my head a long time to fix the 24 bits bug without success (wasn't looking at the right place...)

What are the specific changes in this build? Can you explain the different graph lines in Display Stats, and why even the red one is different from the non patched build? 1080i50 and 1080i60 Blu-ray content stutters like hell with 75Hz refresh rate, it's like 2 times each second one already displayed frame is displayed again. Well it's more like 2 times each second a frame moves to the right, and the next one is back in place. Weird. Seeking is way slower than before. 24p content goes in little jumps, following the jumps of the graph lines, same with 30p. The only mode that works flawlessly is obviously 25p.

On a side note, if you're going to merge all those patches discussed in this thread I think it should be done one by one, with the proper testing of each one to see if there are problems.

flanger216

7th January 2009, 21:21

flanger216

7th January 2009, 21:23

And one request: since FLAC support has been added, is there any chance for WavPack support as well?

STaRGaZeR

7th January 2009, 21:53

Holy crap, it's smooth as silk for me. Great job! I've only found a couple issues:

When using ffdshow, seeking causes major problems... looks almost like everything is losing sync, so the video stutters like crazy and you get repeating frames. This also happens if you tic the 'Set Interlace Flag in Output Media Type' option under ffdshow's output settings.

Otherwise, perfect. I've had jitter/judder/smoothness problems on this machine since day one, and now they're finally all gone. Sweet.

Oh, and should we still be using the 'Lock Back-Buffer' feature in MPC-HC, or is that now unnecessary?

Removing the 'Set Interlace Flag in Output Media Type' option fixes the stuttering indeed. Seeking slowness is still there. I'm now testin at 60Hz and with 24p content there is a little but obvious at the same time audio desync. Judder is as present as always.

leeperry

7th January 2009, 21:54

I suppose a lot of people are waiting to test Beliyaal patch, so you can download a test build from thoses links (patch is not included in SVN yet)
now I'm getting some tearing on the very top of the screen in custom VMR9 on XP SP3, which I definitely don't get with your versions :confused:

also seeking a number of times with a 23.976 MKV in 48.000Hz doesn't give a stable 24.000fps like your versions....it's constantly oscillating between 23.99x & 24.00x :

http://pix.nofrag.com/7/d/0/ea593da6b311702cb21f3f5ec146ett.jpg (http://pix.nofrag.com/7/d/0/ea593da6b311702cb21f3f5ec146e.html)

anyhow I'm not sure these fixes were supposed to help support Reclock....and HR still works fine so nvm :)

I've given this build to duckyy from HCFR(who was constantly getting the seeking deadlock with Reclock+HR), we'll let you guys know if it's fixed for good :cool:

Mercury_22

7th January 2009, 22:02

wOxxOm

7th January 2009, 22:02

since this is a popular MPCHC thread...
Am I the only one who misses these in MPCHC like a cut hand:

AUTO-RELOAD OF SUBTITLE UPON FILE-MODIFICATION is detected (like VobSub's checkbox)

DEFAULT LANGUAGE FOR non-DVD SUBTITLES (e.g. exactly like Haali's: eng,rus)

DEFAULT LANGUAGE FOR non-DVD AUDIO

SHORTCUT for DefaultSubtitleStyle

and btw, it's a about year since Ctrl-D (open DVD) is broken and does not automatically open the DVD if only one (drive/disc) is present. Instead it shows a filebox AND EVEN DOES NOT expand the first DVD drive in the system or MyComputer at the very least! (I know winapi's SHBrowseForFolder may be taught to do it by defining a simple callback, 1-5 lines of code).

thousands of subbers would be happy!

clsid

7th January 2009, 22:10

Are the Matroska and Ogg souce filters stable enough to use or should I continue to us Haali Media Splitter?Haali Media Splitter is still the best choice.
And one request: since FLAC support has been added, is there any chance for WavPack support as well? Use CoreWavPack. It is free and way better than anything MPC could offer (because WavPack support is incomplete in FFmpeg).

ADude

7th January 2009, 22:38

I already know what SPDIFER is, that was not my question. Don't output to SPDIF and you'll probably discover that things start working again. Why stream switching doesn't work with SPDIF? I don't know, I don't have a receiver myself.

At this point, would you say the problem is in MPC-HC or in Haali Splitter ? (The problem being that different filters are not loaded when the audio stream is changed in Haali Splitter.)

Rille

7th January 2009, 22:41

[QUOTE=Casimir666;1233718]I suppose a lot of people are waiting to test Beliyaal patch, so you can download a test build from thoses links (patch is not included in SVN yet)

32 bits :
http://www.zshare.net/download/538107912316050a/

64 bits :
http://www.zshare.net/download/53810877dc0daac4/
QUOTE]

I'm using Reclock to speed up to 25fps as my TV's will only handle 50/60Hz correctly.

Using this version with Vista/EVR/DXVA i get alot more stutter in nonD3D. Using D3Dfullscreen it's just perfect :) I get a nice flat line in stats and it's smooth as silk. I do however get that same constant tear at the top of the screen as leeperry.

Edit: Using a Radeon HD3450 running on 2:nd monitor.

clsid

7th January 2009, 22:51

At this point, would you say the problem is in MPC-HC or in Haali Splitter ? (The problem being that different filters are not loaded when the audio stream is changed in Haali Splitter.)Hard to say. It is probably more a general DirectShow issue.

Casimir666

7th January 2009, 23:00

now I'm getting some tearing on the very top of the screen in custom VMR9 on XP SP3, which I definitely don't get with your versions :confused:

I have heavy tearing on XP too, but I think to know where it came from (will do some more tests on this subject next week end).

What are the specific changes in this build? Can you explain the different graph lines in Display Stats, and why even the red one is different from the non patched build?
Look first Beliyaal post he explain all changes. Blue line represent audio jitter.

ByeByeBluRay

8th January 2009, 00:23

Mixed results with the new build for me. I'm playing back on a monitor that can only at 60Hz, and I'm not using Reclock.

As others have found, VC1 in M2TS containers is playing back perfectly (in previous builds it was massively jerky).

However, with M2TS containing H264, I'm finding that every five seconds or so, the movie goes into fast forward for roughly a quarter of a second. It's not a jump, just a speed up, as if the difference in movie and display framrates is being dealt with every few seconds instead of being spread over all the frames. This doesn't happen on the older builds.

BBBR

Jay Bee

8th January 2009, 00:30

YES ! FINALLY VC-1 IN M2TS IT'S WORKING ! :D

THANKS ! :thanks:

Is that interlaced VC-1? Or was there another problem?

EDIT: just tested, no, interlaced VC-1 still doesn't work.

tetsuo55

8th January 2009, 00:33

I tested the new build.

this is WinXP SP2 with VMR9 renderless fullscreen exclusive mode

Case 1:
Built in decoder, ffdshow for audio and haali splitter.
VC1 with E-AC3 mkv remux with SRT subs.

Seeking is instantanious, both video and audio play directly, just 1 garbled frame.
Subs lag for about 5 seconds before showing after seek, but this happens in the older build too.

although there are still random mini-looping frames and macroblocks the problem is much less than with the old build.

Case 2:
Built in decoder, ffdshow for audio (did not check the splitter).
Bluray m2ts file, main movie, h264.

Extreme macroblocking and mini looping, video is completely unwatchable (with the old build it happens from time to time during scene changes)
Heavy tearing in the top half of the screen even in fullscreen exclusive mode

These bugs also occur in the old build and the new build:
Subtitles where selectable but did not show at all.
If i try to change the audio stream the screen goes black and i have to exit and restart mplayerc (which means i cannot choose the other track).

---------------------------

The EXTREME difference in macroblocking behaviour for both VC1 and h264 seem to prove that we're going in the right direction with these fixes. We're just not there yet.