[madshi]

Originally Posted by Plutotype

Just a hint - noticed, if you enable the madVR internal decoders and let ffdshow as preffered external video decoder ( you want to use ffdshow ), the CPU usage doubles. So it looks like the internal decoders are still on, inspite of the fact they should be blocked by the ffdshow video decoder, if ffdshow video decoder is set to prefer in the external filter list. Could you pls test this?

Just tested that, can't reproduce it. Doesn't make any sense, either, cause when ffdshow decodes, madVR isn't even getting the video bitstream, so the madVR internal decoder doesn't have any feed to work on.

Originally Posted by Plutotype

ffdshow video 3949:
MPEG2 - no A/V issues ( libavcodec )
VC-1 - occasional A/V issues ( libavcodec ), but no A/V issues with wmv9
H.264 - no A/V issues ( libavcodec )

madVR 0.71 internal decoders:
MPEG2 - no A/V issues ( libavcodec )
VC-1 - no A/V issues ( libavcodec )
H.264 - no A/V issues ( libavcodec )

Looks goo to me...

Originally Posted by leeperry

Oh, I've hardly ever encountered freezes between mVR and PotPlayer

Lemme know if you want me to whine about anything on the official korean forum.

Not needed, already fixed in my sources.

Originally Posted by leeperry

OK, neato! the only 2 things I would currently need in mVR are:
-proper colors in PC range RGB32(just like in 0.67)
-a way to get automatic PC range YV12(w/ proper colors of course), either through an "assume PC range for YCbCr" or "remember last YCbCr levels range".

In the next build you'll be able to create an empty file named "force full range input" in the madVR folder, which will make madVR always auto select full range input. You can still change input range via keyboard shortcut, of course. Before you ask: No similar hacks coming for gamut, though.

Originally Posted by Plutotype

when using internal decoders and playing MPEG2 video, OSD via CTRL+J shows @ "every frame repeat" numbers like 41.67s or 41.57 etc. The playback is smooth.

Im asking because...

Maybe I missed something, but where is your question?

Originally Posted by azaze1

Is this the 'Microsoft DTV-DVD Video Decoder' in the external filters?

No, in XP it's named "WMVideo Decoder DMO". Don't recall right now what the name is in win7.

Originally Posted by azaze1

If not, how can I ensure the decoder you're referring to is used for VC-1 content?

By setting it to "preferred" in the MPC-HC external filter list.

Originally Posted by azaze1

More importantly, is there a way to make sure it's used for VC-1 and NOT h264 should I choose to use madVR's h264 decoder....

The WMVideo Decoder DMO only decodes VC-1, not h264, so there's no conflict.

Originally Posted by jmone

FYI the "delay playback start..." option in V0.71 causes video playback to stall in MC16

Works just fine here. Can anybody else reproduce the problem?

Originally Posted by andybkma

Yes, I have tried different splitters, decoders (Win decoders vs 3rd party), renderers, players, different video formats, different hard drives, even different laptops. All lead to the same conclusion, it only occurs with madVR and even when I lower the scaling algorithms.

That was the first thing I noticed when I moved to Win7 from XP this month, that video playback with madVR was not nearly as smooth. But like I mentioned before, it's just something to live with....

I'm confused. Originally you reported a problem only during playback *START*. Now you're saying video playback is generally not as smooth??

Originally Posted by azaze1

I did have a crash instantly while watching particular movies, so I'd like to provide logs, but I never see any...

If you have crashes, logs don't help as much. In that case a sample with which I can reproduce the crash would help MUCH more.

Originally Posted by ryrynz

I've enabled MPEG2 decoding with MadVR and found when opening a VOB from any of my DVD rips the audio ends up being out of sync and after seeking the video speeds up and stutters.
I'm using Lav splitter/audio 0.30 and I'm having no issues with playback when switched to ffdshow for decoding.

Which madVR version did you use? v0.70 contains an improvement for MPEG2 which might already have fixed this (if you tested with an older madVR build).

Originally Posted by cyberbeing

Once you find and fix this bug, maybe you should make it an optional feature.
I'm actually beginning to like videos opening paused, since it gives me a chance to enter fullscreen before starting playback.

I don't consider an option "make media player start paused". Such features should be provided by the media player, not by madVR.

Originally Posted by cyberbeing

On another note, madshi could you make ISubRender subtitles get scaled with with the selected madVR luma/chroma resizers?

Originally Posted by nevcairiel

All madVR does is tell MPC-HC to draw the subs onto the (otherwise finished) image. MPC-HC does all the subtitle scaling.

Yep. madVR doesn't do *anything*. All the work is done by MPC-HC. So there's nothing I can do to improve subtitle quality.

Originally Posted by cyberbeing

madshi, there appears to be a very slight inaccuracy in your 10-bit to 32/64-bit to 8-bit conversion using 10-bit input from the madVR internal decoder (either that or x264 has an issue with 8-bit to 10-bit conversion).

I've double checked. The raw unprocessed YCbCr output of the h264 decoder is:

8 bit black, Y: 16, Cb: 128, Cr: 128
8 bit white: Y: 235, Cb: 128, Cr: 128
10 bit black, Y: 64, Cb: 514, Cr: 514
10 bit white: Y: 943, Cb: 514, Cr: 514

Now let's check what the BT.709 specification says:

Black level, 8bit: 16, 10bit: 64
Achromatic, 8bit: 128, 10bit: 512
Nominal peak, 8bit: 235, 10bit: 940

Seems to me the 8bit -> 10bit conversion you've done is broken.

Originally Posted by Volfield

Is the Intel 3150 is supported? I have "creating Direct3D device failed (8876086c)" error when trying play movie.

madVR needs PixelShader 3.0 hardware support. Seems the Intel 3150 can't do that.

Originally Posted by rahzel

I'm playing around with the luma scaling options and I'm kind of confused. I have 1080p and 720p versions of the same clip and my display's native resolution is 1360x768, so madVR has to scale both videos right? And would I be right in assuming that madVR would apply luma upscaling to the 720p video and luma downscaling to the 1080p video? If so, this is what confuses me... tweaking the luma upscale option seems to have no affect on the 720p video -- changing the luma downscale option, however, does affect the 720p video. With luma downscaling set to bilinear, the 720p video looks noticeably softer than the 1080p video, but with luma downscaling set to bicubic, the 720p video is almost indistinguishable from the 1080p video.

What does the madVR OSD (Ctrl+J) say about source resolution and target rectangle when playing your 720p video?