madVR - high quality video renderer (GPU assisted)

[cyberbeing]

Lanczos3 anti-ringing for Luma does seem like a good option with madVRantiringing6. Still a bit softer than normal Spline36 on the 720p sample because of the issue ryrynz mentioned, but it retains fine contrast slightly better than Spline64 anti-ringing. Though both Spline36 and Spline64 seem considerably better at interpolation of gradients, at the expense of less fine contrast.

As madshi mentioned, both Lanczos4 & Lanczos8 do show residual dark/bright ringing with the test6 build.

@madshi
Would it be possible to add some sharper Spline interpolators to madVR for testing with anti-ringing?
Spline144 (6-tap 12x12) and Spline256 (8-tap 16x16)?
Related thread about calculating Spline coefficients & avisynth filter source code (http://forum.doom9.org/showthread.php?t=147117)

[Owyn]

Here's a new test build

I tried it and the resize crashing is still there :( Are my reports enought or would you need a full dump or something else?

[madshi]

@Owyn, I'm currently only working on anti-ringing, nothing else. Bugs etc have to wait until I find some time. To be honest, I shouldn't even work on anti-ringing. Just couldn't resist...

[chros]

On performance wise using Chroma Lanczos3 + antiringing on 1080p@24Hz:
- v6 is slower than v5, but a little faster than v4

Can you make faster the chroma antiringing function as it was with v5?
I have accidently copied back the original 0.82.5 files, and the chroma upsampling (eg. Mitchell-Netravalli) is way too faster than v6 and v5 builds without Antiringing! How could this be? :)
Tested on a 1080i@30fps clip too ...

[Netuser]

Hi,

I have pass to madvr and Lav filter setup and I have amazing quality and no more problem with Full HD playback :D

Thanks so much madshi :)

But I have 2 problem and I don't know if in futur version of madvr you can implement them.

1- I watch a lot of Vob of music videos and often old videos are 4/3 and boxed, before with ffdshow I use to use a script called LameAutoCrop which automatically crop the black border so that I can watch the clip in full screen and don't have to zoom each time. Is there anyway you can add this option ? or a way to adopt it ?

2- problem is that I can not take screenshot in MPC-HC when I use madvr :( i have to switch to other output option in MPC to do so. are you planning to add this option in future ?

Thanks a lot :)


Sorry for bumping

[ryrynz]

Madshi, if you're having to compromise anti-ringing quality for performance could you allow for a HQ option? I'm only interested in overall improving quality, I don't care about the performance hit, I'll upgrade if I need to.

[Boltron]

+1 to that

[Hprd]

Aye.

My preference is to have minimum amounts (although as accurate to the source as possible as well) of aliasing with modest (although as minimum as possible, if possible) amounts of artifacts (ringing, blockiness, etc.) while maintaining maximum sharpness and detail. The current anti-ringing (build 6) seems to be very good, while using LZ3 with it on for both chroma and luma (with my preferences, which seems to be similar to many others). But if it can be done better (in whatever way) with some performance loss, even if it's only a little better IQ, it'd be worth it to have some kind of "HQ" option ;)

[cyberbeing]

@ryrynz

I took a look at your sample, and it seems like the source frame does have faint areas on the lines. madVR anti-ringing appears to be preventing the dark ringing which actually had a positive effect on the lines of that sample, while the anti-ringing result may actually be a closer representation of the source pixels. I wonder if this is actually solvable without negative ringing side-effects on sharp high-contrast edges.

704x480 -> 1706x960 (800% crop):

Nearest Neighbor vs Spline36 (http://screenshotcomparison.com/comparison/140585/picture:0)

Nearest Neighbor vs Spline36 anti-ringing (http://screenshotcomparison.com/comparison/140585/picture:1)

Spline36 vs Spline36 anti-ringing (http://screenshotcomparison.com/comparison/140585/picture:2)

[ryrynz]

I think what we can take away from this is that when resizing the most accurate isn't always the best solution. It thus looks like a good sample to use for refining anti-ringing the result of which could address some of your concerns also. I hope something good can come from it, eagerly awaiting your progress Madshi.

[djfred93]

High bit-depth output. HTPCs are limited to 8-bit output with madVR right now, stand-alone players offer 10+bit output. (though many will "output" higher bit-depths than they are actually operating at internally) With madVR's 16-bit internal precision and dithering, I'd argue that it can still produce better results. It depends on the display device and the player you're comparing to. And hopefully at some point, madVR will output 10-bit or greater too.
Bitstreaming. PCs do not run their video and audio hardware off the same clocks, and so it's not possible to have them perfectly synced up. You either have to sacrifice bitstreaming (but if you're upsampling, this is moot) to have audio synced to the video without any dropped/repeated frames, or suffer dropped/repeated frames to have bitstreamed audio. This is a non-issue in my opinion, but some people love that light on their AVR and insist on wanting to bitstream.
3D support. I don't think there's any way to output 3D when running MPC-HC and madVR (though you can always have another player I guess?) I've had a 3DTV for close to two years now and I never use 3D any more so I don't really care.[/list]


- You can output in 10+bits with a pro video card like Firepro card or Quadro card.

- Bitstream is possible with ffdshow and other software.

- 3D support is possible in SBS... in MPC-HC. It's the MVC codec who isn't supported yet in MPC-HC.

[dansrfe]

What would 10bit actually provide or look like if not dithered down to 8bit? I know the benefits of encoding to 10bit (less banding, better compression, etc.) but since it gets dithered down to 8bit for the majority of displays which happen to be 8bit, I'm unsure about what I'm missing by not having a 10bit display.

[Keiyakusha]

What would 10bit actually provide or look like if not dithered down to 8bit?
if your source was 8 bit before encoding then nothing. less banding is all youre going to get regardless of what display you plug in.
with real 10bit source (not from bluray or dvd) you maybe will see better picture if your eyes can distinguish more than 17 million colors
though i'm not aware of such sources other than some artificially created stuff where 10 bits matters mostly during processing. or actually i use up to 32bitdepth sometimes. not that it matters after stuff was rendered...
Edit: btw afaik there is no software that will allow you not to dither. whatever dither or truncate.

[Andy o]

- You can output in 10+bits with a pro video card like Firepro card or Quadro card.With madVR? With any consumer player/renderer at all, for video?

- Bitstream is possible with ffdshow and other software.That's not what 6233638 meant at all. Of course it is possible, but s/he listed the downsides.

- 3D support is possible in SBS... in MPC-HC. It's the MVC codec who isn't supported yet in MPC-HC.
With madVR (this one is an honest question)?

What would 10bit actually provide or look like if not dithered down to 8bit? I know the benefits of encoding to 10bit (less banding, better compression, etc.) but since it gets dithered down to 8bit for the majority of displays which happen to be 8bit, I'm unsure about what I'm missing by not having a 10bit display.
The potential benefits of outputting in higher bit depth are mentioned by madshi in the first page. It may be better even if your display is still 8-bit (but accepts high-bit-depth input, like many modern TVs).

[Keiyakusha]

It may be better even if your display is still 8-bit (but accepts high-bit-depth input, like many modern TVs).
You mean if TV somehow accepts 10bit input and dithers it (or whatever these TVs do, cause they may do a lot) will bring some benefits over proper dithering like the one madvr does? How come, the only reason x264 creates 10bit if configured to do so is to put some noise there that it will otherwise throw away. leaving dealing with that to some quality improving (damaging?) algorithms of modern tvs doesn't sounds too good.

[strumf666]

Hi,

I am using potplayer, lav codecs and reclock audio and madvr video renderer. In madvr I use windowed mode (exclusive is jumping in and out when I go to the menu or if I want to use the bottom bar which is annoying) and from what I have read I should disable desktop composition, to avoid vsync problems, but that actually results in picture tearing (near the bottom of the screen). If I don't disable "aero" there is no tearing but I have a few dropped frames at the beginning of the playback and occasionally if I pause and restart the movie. Advice appreciated.

edit: I tried in MPC-HC as well and it behaves the same.

[Keiyakusha]

If I don't disable "aero" there is no tearing but I have a few dropped frames at the beginning of the playback and occasionally if I pause and restart the movie. Advice appreciated.

Maybe I'm wrong but I always though this is how it is and how it should work. Why would you care about drops if you pause anyway? And no surprise in aero actually helping. dunno why, but this is the case for many users (not only madvr). It have its own vsync

[Andy o]

You mean if TV somehow accepts 10bit input and dithers it (or whatever these TVs do, cause they may do a lot) will bring some benefits over proper dithering like the one madvr does? How come, the only reason x264 creates 10bit if configured to do so is to put some noise there that it will otherwise throw away. leaving dealing with that to some quality improving (damaging?) algorithms of modern tvs doesn't sounds too good.

It's in the first page of this thread, written by madshi. The basic idea is that if the player can output more than 8-bit, then it doesn't need to dither down to 8-bit after processing, so less downconversion is applied in the chain. Go read it for details though.

[Pat357]

What would 10bit actually provide or look like if not dithered down to 8bit? I know the benefits of encoding to 10bit (less banding, better compression, etc.) but since it gets dithered down to 8bit for the majority of displays which happen to be 8bit, I'm unsure about what I'm missing by not having a 10bit display.

Dithering is not only for 10bit->8bit, but also for color-space transformations like yuv420-> RGB32. If you do a 8 bit yuv420->RGB32 without dithering, you risk serious banding.
With a 10 bit yuv420 (same for 422 and 444) the banding would be much less and probably not noticeable any longer.
If you keep the whole chain from source -> display on 10 bit, you would have a more accurate image I guess, with no banding. This would require the monitor and video card to accept and output 10 bit (of course not 10bit RGB, asthis is nonsense)

[djfred93]

With madVR? With any consumer player/renderer at all, for video?

I don't know, i don't have 10 bits display yet. For a 10 bits display, you have to buy some Eizo or some korean display.

With madVR (this one is an honest question)?

For SBS & T&B video, yes. For MVC video, you probably need to wait a MVC codec.

[ajp_anton]

Madshi:

Do you remember when we talked about how to do an exact 2x upscale, for example 720p movie on a 1440p/1600p monitor?
Afaik, madVR preserves the center position so that every new pixel is interpolated, and I thought it would be better to center around a corner so that every source pixel is preserved. I tested the differences in Avisynth, and while there were differences, neither really looked better than the other.

I just thought about it again, and wouldn't it be much faster to preserve the source pixels? In case you're upscaling one dimension at a time, it would halve the number of interpolated pixels both times. Or if I'm missing something, at least 1/4 could be saved as that's the amount of untouched source pixels.
This might also help on other upscale factors because it pretty much guarantees that the maximum number of source pixels are still present.

[Keiyakusha]

It's in the first page of this thread, written by madshi. The basic idea is that if the player can output more than 8-bit, then it doesn't need to dither down to 8-bit after processing, so less downconversion is applied in the chain. Go read it for details though.
Here we are talking about 8bit source that was made to 10bit by x264. It is clear enough from dansrfe's post. What I say is that leaving it 10bit with no dithering doesn't give any benefits.
We don't care about "less downconversion", our 10bit source in this case is a fake. It will be downconverted anyway sooner or later. And if not, it won't look any better anyway.
Also higher than 8bit processing is good indeed but it doesn't means the source won't be dithered in the end.
Originally was a question, how it looks like, when not dithered. The answer is - it won't be any better. Lets not go any further.

[Andy o]

Still, once you've upconverted to higher bit depth, be it in encoding or in processing, it's ideal to leave it that way until final downconversion, which in this case happens on the monitor. Of course this can't be done yet, but still.

[strumf666]

Maybe I'm wrong but I always though this is how it is and how it should work. Why would you care about drops if you pause anyway? And no surprise in aero actually helping. dunno why, but this is the case for many users (not only madvr). It have its own vsync

Thanks for answering. Iirc I read that aero's vsync is messing with madvr vsync hence aero should be disabled. It is possible the information was incorrect or I misunderstood it and that's why I am asking.

[Keiyakusha]

Thanks for answering. Iirc I read that aero's vsync is messing with madvr vsync hence aero should be disabled. It is possible the information was incorrect or I misunderstood it and that's why I am asking.

Don't get me wrong, I'm not entirely sure myself. I recall something like that at early stages of madvr development but desktop composition shouldn't be an issue now. Also for example on Win8 you can't turn it off anymore so if you aware of some troubles with it, they probably need to be resolved...

[Keiyakusha]

Regarding AR calculation again.
As was reported before by few users 720x480 video with 32:27 SAR results incorrect resolution 1919x1080
Now 692x448 with 103:86 SAR results 1920x1058 resolution, while it should be 1920x1038 (20px error seriously? Oo)
Is there a way to improve something about it? I don't rectally care about 2nd case, this is one and only dvd i have with letterboxed 1.85 video, but how about 720x480 case?

[HauntingShock]

Newbie here...

May I know what's the difference if I enable or disable exclusive mode in fullscreen?

[cyberbeing]

Now 692x448 with 103:86 SAR results 1920x1058 resolution, while it should be 1920x1038 (20px error seriously?

Have you confirmed with screenshots that there actually is a 20px error? Normally it's just a case of madVR padding the video.
The first two numbers of madVR's Target Rectangle stats are horizontal and vertical padding.

I'd also be curious what resolution madVR uses when playing that video at 100% after anamorphic stretching.

According to the resolution and SAR you listed it, should be 829x448 (or 828x448) after anamorphic stretching, but according to what you say madVR is using @1920x1080, it would be 813x448 which doesn't make any sense. Are positive that your decoder is reporting the correct SAR to madVR?

[nx6]

Newbie here...

May I know what's the difference if I enable or disable exclusive mode in fullscreen?

In Fullscreen Exclusive mode you're pretty much dedicating the display output to interfacing with MadVR to provide the least chance of dropped frames or other playback issues. Other apps (or even the video player itself) trying to display other things that aren't part of your video playback like OSD displays, email arrival notifications, etc may have trouble in FSE mode or their appearance may cause MadVR to temporarily drop out of FSE mode.

If you don't have playback issues that you need FSE mode to overcome, there's no reason why you couldn't disable FSE mode if it allows these other programs to draw to the screen more easily or gets rid of the sometimes noticable "jump" to FSE mode when going to full screen on your video player.

[andybkma]

Greets, posting this to make sure that my new laptop's video card isn't broke... picked up a Lenovo Y480 Win7 64bit 8Gb Ram with Nvidia 640M-LE graphics card 2GB dedicated ram the other day.

I am using madVR with defaults with Zoom Player. When I set Zoom Player to be used with the onboard Intel 4000 graphics everything is fine with mVR in Fullscreen Exclusive Mode. But when I use Zoom Player with the Nvidia graphics card, and with "Present Several Frames In Advance" (I do believe that's default) checked, in FSE or without FSE, videos stop playing (they just pause by themselves) around 20 seconds after start but the sound continues. And then when I come out fullscreen (doesn't matter whether out of FSE or not) into window mode the video will look like its in Fast Forward by itself trying to catch up. If I uncheck "Present Several Frames In Advance " then it works fine in FSE or without FSE. Ummm... have any of you guys experienced this? Am worried that my new laptop's nvidia video card is hosed since this is new technology (compared to me old 8600M-GT) and ought to work right?

Edit: Doesn't matter what container or decoder, any vid I play using the nvidia graphics card with mVR "Present Several Frames In Advance" checked freezes playback after about 20 seconds. Reclock on or off doesn't matter either

[vivan]

andybkma,
that happens with all Optimus systems. Solution is to untick "use a separate device for presentation".

[makakam]

Hi everyone
I have this really important question that's been buggin' me for some time now. My HTPC (Radeon 6570) is connected to onkyo avr with hdmi and then to tv(panasonic vt30) with hdmi as well. I have been using full rgb pixel format and mpc-hc with madvr set to 16-235 (otherwise i get crushed blacks). I have calibrated my tv using htpc pattern generator and greyscale ramp in it looks like the one from avs hd calibration disc when I play it in mpc-hc which is not perfectly smooth. I have noticed that when I change pixel format to ycbcr 4 2 2 the ramp in htpc pattern generator becomes smooth but thin vertical lines are still there in mpc-hc. Am I doing sth wrong or is it just impossible to have it completely smooth in mpc-hc? Thanks in advance.

[fairchild]

Hi everyone
I have this really important question that's been buggin' me for some time now. My HTPC (Radeon 6570) is connected to onkyo avr with hdmi and then to tv(panasonic vt30) with hdmi as well. I have been using full rgb pixel format and mpc-hc with madvr set to 16-235 (otherwise i get crushed blacks). I have calibrated my tv using htpc pattern generator and greyscale ramp in it looks like the one from avs hd calibration disc when I play it in mpc-hc which is not perfectly smooth. I have noticed that when I change pixel format to ycbcr 4 2 2 the ramp in htpc pattern generator becomes smooth but thin vertical lines are still there in mpc-hc. Am I doing sth wrong or is it just impossible to have it completely smooth in mpc-hc? Thanks in advance.

I have mine smooth with slightly different settings. I use RGB Limited as the pixel format, then in MadVR I have it set to the default 0-255. I have my Radeon 7870 going from it's HDMI to the HDMI in on my Panasonic S2 42" plasma. Maybe it's something to do with your receiver.

[Ver Greeneyes]

Since it seems the deringing craze has died down a bit (very interesting stuff!), reposting this as I think it got lost at the end of a page. Can someone advise me on how this works?
I have a question with regards to the color correction built into madVR. My monitor is calibrated using an X-Rite ColorMunki Photo, using a LUT together with a v4 ICC profile. If I setup my monitor in madVR so that it's set to "this display is already calibrated", will it use the ICC profile assigned to my monitor? Or do I somehow need to convert my ICC profile to a 3DLUT file? The LUT itself should already be loaded into my GPU.

Oh, and should I "enable gamma processing" on the color & gamma tab? Would it do anything if it's set to the same gamma as my ICC profile (2.20)?

If there's a readme with detailed descriptions for each setting out there, I'd love to read it.

[pie1394]

Hi everyone
I have noticed that when I change pixel format to ycbcr 4 2 2 the ramp in htpc pattern generator becomes smooth but thin vertical lines are still there in mpc-hc. Am I doing sth wrong or is it just impossible to have it completely smooth in mpc-hc? Thanks in advance.

With 4:2:2, the chroma U/V are sampled with half horizontal resolution if compared to 4:4:4 video signal format. If you see the vertical line or color banding, it has the possibility that non-interpolated U/V pixel down-sampling is performed somewhere. I saw some similar problems when designing an ARGB 4:4:4 source to 4:2:2 UYVY+Alpha OSD frame buffer converting many years ago.

[blackjack12]

Generally, if you report problems with specific samples with LAV + madVR, please always check if madVR reports deinterlacing to be on/off, and whether overriding that decision by pressing Ctrl+Alt+Shift+D fixes things. You would noticably increase the usefulness of your reports if you mentioned right away what the real problem is. There are 3 basic possibilities:

(1) Image quality is bad with deinterlacing off, but good with deinterlacing on. The problem is that it's not turned on automatically.
(2) Image quality is bad with deinterlacing on, but good with deinterlacing off. The problem is that it's turned on automatically.
(3) Image quality is bad in any case, no matter if deinterlacing is activated or not.

For every problem you see, it would be nice if you could specify which of the 3 problems we're talking about. Also, it would be helpful to know if EVR plays the same file correctly with the same decoder settings.


Madshi,

MadVR deinterlacing: MPEG2 DVD “interlaced” issues with direct DVD material rips using MakeMKV ver 1.7.6 or 1.7.7 - Problem now understood
Seen and tested on both AMD Radeon and NVIDIA GPU systems

MadVR is “BAD”
Reports deinterlacing on : force off and is “GOOD” … (2)

EVR/EVR-CP is “GOOD”
Can actually see FPS jumps a little at beginning that looks like interlaced then goes to 24fps. An interlaced beginning blip that triggers MadVR and MediaInfo reads but EVR ignores or plays through.

MediaInfo shows material as interlaced but the reason that I did not include samples is because when I used MKVMerge to create clip of credits where easy to see, the clip now indicates progressive.

Even tried re-ripping with absolute newest MakeMKV to see if that was issue but all show same result.

So the interlaced flag that looks like is a quick blip in the beginning is being seen and responded to by MadVR but EVR “ignores”? and plays correctly.

Did not upload samples but here are some DVD’s that I had that easily showed the issues: (ripped with MakeMKV ver 1.7.7)

13 Going on 30
xXx
The Back to the Future Series
… Many, many more


I then used the latest MKVMerge and clipped the first 30 seconds off the ripped material for a quick test to see if could get rid of the “interlaced” blip and it did! Now the files tested play as progressive without issue.

The “interlaced” blip at the beginning causes the entire video to be seen as “interlaced” by MadVR when in fact it is not. ... A lot of issues in the beginning logo stuff.

Note:
See the exact same behavior with Radeon 6570 and NVidia/CUVID with 560Ti and GT525M systems.

UPDATE NOTE:
Clipping off 1.0-39 sec at the beginning of the MKV files got rid of the "interlace blip" on most files and they then indicated deinterlacing off with MadVR and progressive in MediaInfo in MPC-HC - and played without issue.

The "old" intro logos and stuff are crappy, have interlaced content and cause most of the problems ...

Chopping out is not practical but it worked.

Really need MadVR to accommodate this.

EVR/EVR-CP allows these same files to play correctly and there are a lot of them with a DVD direct rip to MKV using MakeMKV. If you process with something like HandBrake all is converted to progressive and you never see the issue ... but you do lose information.

The results when working are extremely good.

[pando2]

I have a question about yCMS in madVR:
How can we move to a target SMPTE-C while the concervant yCMS, the two can not be checked ??

[ThurstonX]

andybkma,
that happens with all Optimus systems. Solution is to untick "use a separate device for presentation".
Ah! Thank you very much :-) I have a Toshiba Qosmio with a GTX 560M and a Core i5 (HD 3000), and out of the box madVR didn't work, with playback being massively stuttered (EVR cp was fine). I checked the nVidia settings, and MPC-HC was set to use the nVidia. When I forced it to use the Intel GFX and switched LAV to Quick Sync, playback worked, but render times seemed pretty high.

Now I've switched back to forcing MPC-HC to use the nVidia, and set LAV to use CUVID. Render times improved greatly.

And I love the Anti-ringing switches in test build 6! I have a lot of low-res vids, mostly stuff dumped from a Comcast DVR to an old Hauppauge via S-Video (I know! I know! Don't laugh ;-) Just needed to preserve a lot of stuff :o ) madVR's ability to tweak the upscaling is bliss.

I'm a total noob to LAV and madVR, having been content with CCCP's implementation with ffdshow, but when reading they're going to ditch it eventually for LAV, I decided to be proactive.

My HTPC runs a Radeon HD 5670 and a Core i5, and all is perfect with LAV + madVR, whether I use no HW acceleration or DXVA2 copy-back. Actually, GPU-Z shows lower GPU % used with no HW acceleration, at least with a brief logging test. I'm not exactly clear if DXVA2 copy-back gives some benefit over no HW acceleration. But then I'm still reading, absorbing and learning.

Anyway, thanks a ton, vivan, for the quick fix, and of course madshi and nev for madVR and LAV. Y'all rule :-)

[pie1394]

The "old" intro logos and stuff are crappy, have interlaced content and cause most of the problems ...


This kind of trouble-some mixed fps contents did exist.

I remembered that interlaced title / introduction at the beginning and then fully progressive 24 fps FILM was seen on the old Region-1 DVDs.

It also happens to some Japanese broadcast anime programs encoded with MPEG-2MP@HL.
i.e. 29.97 fps Opening & Ending encoded with interlaced mode while the other parts are still 23.976 fps progressive.

If interlacing flag and frame duration information are correctly passed to the video post-processor(deinterlacer) per video frame, it should not be a problem to decide whether deinterlacing should be performed or not. (I had did that for the standalone media player + TV recorder products 6 years ago)

If the display refresh rate is set to 59.94 fields or frames per second, it is going to have the judder effect on the 24 fps progressive contents. Only the high-end LCD and PDP TV's engines can detect and perform IVTC and restore the 60 telecined fields back to 24 progressive frames. (On the cost-down TV models, it is claimed capable of such processing, but it often does not show good results.)

On the good LCD / PDP, the panel driving mechanism is also often adjusted for the 24 fps FILM content's display optimization.

[Thunderbolt8]

what is recommended for madvr, leaving vsync to application controlled in CCC settings or rather change it to always on?

[dansrfe]

I feel like we need to have an IRC channel for madVR. #madVR :D

[Mangix]

what is recommended for madvr, leaving vsync to application controlled in CCC settings or rather change it to always on?

application controlled

[Valdy]

Hi, i'm new to this forum and madvr. Is there a way to take advantage of my 10-bit display with regular (8-bit) blu-ray movies? I think something like 8-bit -> 10-bit on the fly conversion. Is this possible?
Anyway, every movie i have displays like this: h264(or vc-1) 8 bit 4:2:0 -> NV12 8-bit 4:2:0. Is this correct? Or is there a way to improve things?

Thanks.

[Trib]

Hi, i'm new to this forum and madvr. Is there a way to take advantage of my 10-bit display with regular (8-bit) blu-ray movies? I think something like 8-bit -> 10-bit on the fly conversion. Is this possible?
Anyway, every movie i have displays like this: h264(or vc-1) 8 bit 4:2:0 -> NV12 8-bit 4:2:0. Is this correct? Or is there a way to improve things?

Thanks.

From what I've understood from reading these threads is that a conversion from 8-bit -> 10-bit would just degrade the image quality and not make it better as 8-bit files should be played as 8-bit and 10-bit as 10-bit.

So yes, h264(or vc-1) 8 bit 4:2:0 -> NV12 8-bit 4:2:0 is correct.

[vivan]

"8 bit 4:2:0 -> NV12 8-bit 4:2:0" has nothing to do with output to display. It means that decoder decodes 8 bit 4:2:0 and ouputs it in 8 bit 4:2:0 format to madVR.
"conversion from 8-bit -> 10-bit" on that step can't hurt anything, because it's just adding zeros. However there's also no reasons to do this.

[nevcairiel]

Not to mention that a) madVR has no 10-bit output support, and b) only professional-grade GPUs support it (and those are pricey)

[Valdy]

Not to mention that a) madVR has no 10-bit output support, and b) only professional-grade GPUs support it (and those are pricey)

According to amd tech support, radeons can do 10-bit on displayport, hdmi and dual dvi.

Anyway, thanks for the answer for everyone.

[strumf666]

According to my projector, 6870 I had and 7750 I have connects with 10bit. Using hdmi in both cases.

[Valdy]

Under scaling algorithms, spline 4 taps is the best for image quality?

[makakam]

I've read that panasonic vt30 doesn't have full 4 4 4 reproduction but it subsamples it, so the question is should I still use 4 4 4 pixel format or ycbcr 4 2 2 with madvr?