madVR - high quality video renderer (GPU assisted)

[seiyafan]

doubling does exactly what it says; it doubles the luma/chroma resolution. If your source resolution is more than half of your screen resolution, then image upscaling doesn't do anything.


I think I didn't make myself clear. My GPU is not strong enough to do 32 neurons, so either I enabled 16 neurons doubling with a weaker upscaling algorithm, or disable it and use a strong upscaling algorithm such as the Jinc 4.

[SamuriHL]

If I recall correctly madhsi did mention that it would be somewhat easy to let madvr load a shader from the registry or a text file, which would probably be an easier fix. He also mentioned that it should be incredibly easy for the jRiver devs to add pixel shader support for MadVR.

If only we knew a JRiver dev who could do this. LOL! We should address this on the JRiver forum.

[Boltron]

If only we knew a JRiver dev who could do this. LOL! We should address this on the JRiver forum.

+1

I hope it happens soon.

[seiyafan]

I found out why my 270x cannot do 32 neurons. :stupid:
The video I've been testing is encoded at 30 fps. I have no issues with 23.976 fps videos.

[SamuriHL]

I finally got some time to sort out some of my htpc issues tonight. I will say that having 3d enabled is not good for madvr. Once I shut it off in the nvidia control panel things went back to normal. Just one of those things I guess. I do watch 3d quite a bit so I'll have to remember to toggle it.

Sent from my SM-P600 using Tapatalk

[StinDaWg]

I think I didn't make myself clear. My GPU is not strong enough to do 32 neurons, so either I enabled 16 neurons doubling with a weaker upscaling algorithm, or disable it and use a strong upscaling algorithm such as the Jinc 4.
If you are upscaling 1080p to 1440p then the upscaling algorithm you choose doesn't matter because you are doubling past your target resolution. The downscaling algorithm you choose will matter though. NNEDI3 doubling is significantly better than Jinc so just use 16 neurons and a cheap upscaling algorithm like bicubic.

[matthewn4444]

Does MadVR support capture devices such as webcams or capture cards (from game consoles)? I tried to use MPC to show the device and the webcam sometimes works. When I turn on smooth motion, the image freezes (and fails) to function. Does smooth motion not work with capture devices?

[Procrastinating]

I think I didn't make myself clear. My GPU is not strong enough to do 32 neurons, so either I enabled 16 neurons doubling with a weaker upscaling algorithm, or disable it and use a strong upscaling algorithm such as the Jinc 4.

Unless you are talking about chroma upscaling, I think you might be misunderstanding.

Say your source video is 1920x1080, then image doubling will turn the luma portion of the source into 3840x2160. It's not a matter of "not needing" image upscaling, in this case the image actually needs downscaling.

But to answer your question, 80% of the time it makes more sense to use 16 neurons and cut down on the other settings, yeah.

[hozes]

i am %90 percent watcging 1080p 23,976 or 24 movies...my computer is i2500k@4500mhz and an overclock 7850@1150-1300..my tv is pioneer 428xd 1024x768@60hz(i cannot set it or 72 with cru, i donot know why, it says the signal is unsupported)

my settings are,
debanding medium medium
chroma upscaling nnedi 32 neutrons( with 64 neutrons i have dropped frames)
image doubling no
image upscaling lancoz 3 tab with ar
image downscaling ct-ar-ll
ditherig error diffisuion option2
smotth motion on

with 87,9, rendering times are 30ms, no dropped frames
both test 1 and test 2 no dropped frames, but 2-3presentation glitch(i donot know what are this either)


i try with a720x480 23,976 movie
the same settings above with image dounbling luma 128neutrons, no dropped frames with both test1 and test2, but with 87,9, i couldnot pass 64netrons...

[Asmodian]

Hmmm... Interesting. Are you sure these improvements come from the interop optimizations and not from the new windowed mode (which 87.9 doesn't have yet)?

I did all my tests using "Windowed Overlay", it seemed to be working based on the behavior of the VideoLUTs and reported in the OSD.

[JohnLai]

Few days ago, I bought Spyder4 Elite and calibrated my desktop's display accordingly.
80 cd/m2, gamma 2.2. The software showed a graph that my display is 84% of sRGB which is okay by me.
SpyderUtility.exe automatically applies the generated ICC profile on startup.

Now, the question on madvr configuration.

What setting do I need to select at 'devices'-->'Dell XXXXX something'-->'Calibration'?
Should I select 'disable calibration control for this device' or 'this display already calibrated'?
Next, how about the checkbox 'disable GPU gamma ramps'?

[Ver Greeneyes]

SpyderUtility.exe automatically applies the generated ICC profile on startup.

Now, the question on madvr configuration.

What setting do I need to select at 'devices'-->'Dell XXXXX something'-->'Calibration'?

madVR does not support ICC profiles, though it will be affected by any gamma ramps that the ICC profile loads into your GPU. To get the most out of your profile, you should make a Rec.709 3DLUT out of it using ArgyllCMS (coupled with dispcalGUI if you don't like console commands). For more instructions see this thread (http://www.avsforum.com/t/1471169/madvr-argyllcms) (though the first post is a bit out of date). You can use ArgyllCMS for calibration and profiling as well, but your existing profile should work fine for making a 3DLUT.

The 'disable GPU gamma ramps' option is for when your 3DLUT already includes the calibration, either integrated into the values or appended. This will disable the calibration loaded into your GPU, so other programs will look different while madVR is active. The exception to this is when you use the windowed overlay mode, but I forget what the right settings are for that :)

[wOxxOm]

Is it possible to make madVR read matroska tags (http://matroska.org/technical/specs/tagging/index.html) in addition to "tags" with madVR settings in the file name?

[James Freeman]

madshi,

Can you please explain how Source Levels work?
For example; when I cut the Black Source Level to -5, does madVR actually clip the blacks or rolls off gradually (in 16-bit) like the brightness slider?

I use Black Source Level to emulate BT.1886 curve to my taste, instead of using the Brightness control.
Brightness control effects too much of the middle shades, while Black Source Level only the few critical shades where it matters the most for Great vs Not so great movie experience.
These first few shades of black are where the difference between BT.1886, sRGB or Power 2.2 lies, it also where a good vs poor apparent contrast lies.

In other words it'd be nice to have better control over the dark shades like a Black Offset Control on a high quality TV without the need of work around tricks.

[bozokaydin]

What do you have set for your dithering method? I found that when I tried any type of Error Diffusion my GPU couldn't handle it, but if I set it to Ordered dithering (random should work too) I was then able to get NNEDI3 to run without dropping frames.

Yes i am using error diffusion type 2. now as you say i am gonna try ordered dithering. thanks!

[Audionut]

I don't understand why the image upscaling has any effect, when using nnedi3. If I'm using nnedi3 to upscale 720p with a display resolution of 1080p, why is the image upscaling effecting performance?


I use Black Source Level to emulate BT.1886 curve to my taste, instead of using the Brightness control.

You probably shouldn't be using the brightness control to emulate anything. Use it to set your (display) black level.

[renethx]

4:2:0 in 720p -> 4:4:4 in 720p by chroma upscaling algorithm, then 4:4:4 in 720p -> 4:4:4 in 1080p by image upscaling algorithm.

[Audionut]

Of course, thankyou.

[ryrynz]

I've used the madVR levels tweaker for my HD4000 and am unsure if I need to set PC levels on input or not.

If I set madVR to TV levels for output which is what's recommended, I have to set TV levels for input to have black >16 to flash with a test pattern.
Alternatively if I have it set to PC levels for input which is what I would expect given I've forced 0-255 output I require PC levels set for output to see black >16 flash with a test pattern.
If I set PC levels as input and TV as output (what I would expect the correct settings to be) I have black >2 flash, which isn't what I would expect given output is supposed to be 16-235.

What is the correct setting here? Thanks.

[James Freeman]

You probably shouldn't be using the brightness control to emulate anything. Use it to set your (display) black level.

Its not what I've meant.

I want to elevate or lower only the first 3-10 black steps without effecting the other steps, its called Black Offset control on some TV's.
I intentionally crush the blacks (but not clip them) to make the image look more contrasty.
Custom Range Gamma/Brightness Control (in 16-bit) is what I'm striving for.

JanWillem32 has written a shader for this once, but the shader is 8-bit thus creating a lot of banding, ffdshow is also 8-bit.

[James Freeman]

If I set madVR to TV levels for output which is what's recommended, I have to set TV levels for input to have black >16 to flash with a test pattern.
Alternatively if I have it set to PC levels for input which is what I would expect given I've forced 0-255 output I require PC levels set for output to see black >16 flash with a test pattern.
Both Correct.
If I set PC levels as input and TV as output (what I would expect the correct settings to be) I have black >2 flash, which isn't what I would expect given output is supposed to be 16-235.
This is also normal behavior.
You are sending (output) limited range signal, but the TV expects full range signal thus showing all the shades.
I've used the madVR levels tweaker for my HD4000 and am unsure if I need to set PC levels on input or not.
It depends if your TV has this range setting effect all the inputs.
If the TV input range setting effects all the inputs of your TV, set the Input and the tweaker to 16-235 because most probably than not your satellite box is 16-235 too.
If it effects only this single input and you use your HTPC/PC not only for movies but also for internet and games, you should set 0-255 for this input and at the tweaker output.
In both cases madVR range setting in its control panel should be set to full range 0-255.

Remember that there is also a range setting in madVR control panel, and that the Range Tweaker software is only for HDMI.
In any case, your TV Input, Tweaker (HDMI) Output should always match, unless... purpose.

[ryrynz]

In both cases madVR range setting in its control panel should be set to full range 0-255.


So in this case with my HTPC being the only device connected, I should set the tweaker to 0-255 input to PC and output in madVR to TV, having blacks >2 flash. Correct?

The levels changed in the madVR control panel "devices-> TV-> this display expects following RGB levels" affect output levels but there's nothing for input levels.

If this is the case, shouldn't madVR ideally set the source levels to PC automatically after using the tweaker? I don't want to have to use the keyboard shortcut to change this each time.

[nevcairiel]

madVR handles the input levels automatically, you don't need options or anything for them. You can override it on a per-file basis, but its only useful if madVR detects the wrong input level. The input level is defined by the file, not any setup in your display chain.

For the level settings, there is basically 3 combinations of settings:

(1) TV accepts PC/Full levels: Set madVR to PC/Full, set GPU to PC/Full - This is usually considered the better option, if your TV can do it.

(2) TV accepts only TV/Limited levels:
(a) Set GPU to PC/Full and set madVR to TV/Limited
(b) Set GPU to TV/Limited and set madVR to PC/Full

In the second case, both a and b have small drawbacks.
With (a), you get crushed black/white on the desktop, but everything is perfect in madVR.
With (b), you get proper colors everywhere, except that the GPU is doing the PC range -> TV range conversion, which may not be the highest quality and end up in banding.

NEVER set both madVR to TV/Limited AND GPU to TV/Limited, you get double range compression.

Because of these drawbacks with either a or b, its usually recommended to use (1) if your TV accepts it. Its only "downside" is that BTB/WTW are lost, but its arguable if those are even worth keeping. If you insist on WTW/BTB, the 2a setting is probably the next best for video quality, if you can live with crushed black/white on the Desktop.

However you set it up, the test patterns should only show 16-235 after calibration.

[James Freeman]

So in this case with my HTPC being the only device connected, I should set the tweaker to 0-255 input to PC and output in madVR to TV, having blacks >2 flash. Correct?

Not correct.
You should NOT see below 16 and above 235.

Remember this:
In Video 16 is absolute black & 235 is absolute white.
In PC 0 is black & 255 is white.
If you want the video to show correctly, 16 needs to be absolute black anywhere.
madVR needs to be aware of these settings to display the correct image.

1. madVR setting -> Devices - (Your Display) -> Properties -> PC levels (0-255).
2. madLevelsTweaker.exe -> Force PC Levels (0-255).
3. Set you TV to PC Levels 0-255.

What the "this display expects following RGB levels" does is:
When set to PC range it stretches the video content range (16-235) to PC range (0-255).
While in TV range it does nothing and leaves the video content range untouched.

[ryrynz]

With (b), you get proper colors everywhere, except that the GPU is doing the PC range -> TV range conversion, which may not be the highest quality and end up in banding.


Cheers Nev, James, I got it now.

It would be cool if someone could check if the current cards do introduce any banding with 16-235 output.

[hozes]

madVR handles the input levels automatically, you don't need options or anything for them. You can override it on a per-file basis, but its only useful if madVR detects the wrong input level. The input level is defined by the file, not any setup in your display chain.

For the level settings, there is basically 3 combinations of settings:

(1) TV accepts PC/Full levels: Set madVR to PC/Full, set GPU to PC/Full - This is usually considered the better option, if your TV can do it.

(2) TV accepts only TV/Limited levels:
(a) Set GPU to PC/Full and set madVR to TV/Limited
(b) Set GPU to TV/Limited and set madVR to PC/Full

In the second case, both a and b have small drawbacks.
With (a), you get crushed black/white on the desktop, but everything is perfect in madVR.
With (b), you get proper colors everywhere, except that the GPU is doing the PC range -> TV range conversion, which may not be the highest quality and end up in banding.

NEVER set both madVR to TV/Limited AND GPU to TV/Limited, you get double range compression.

Because of these drawbacks with either a or b, its usually recommended to use (1) if your TV accepts it. Its only "downside" is that BTB/WTW are lost, but its arguable if those are even worth keeping. If you insist on WTW/BTB, the 2a setting is probably the next best for video quality, if you can live with crushed black/white on the Desktop.

However you set it up, the test patterns should only show 16-235 after calibration.

for watching movies, which option is best, not for descopt or etc, just for watching movies for true color level..
i think option 2(a) is best, cause ovies handed at 16-235, right..

[QBhd]

I am sure the consensus is that (1) is always best if your TV is able to do it. nev clearly lists the drawbacks of (2).

QB

[James Freeman]

If one uses his HTPC strictly for movie watching, Nev's option (2a) is best, just because it eliminates the need of Dithering and range conversion in madVR (or any other video software, or GPU driver/settings), and retains BTB & WTW.
The output would be like what you expect to see in a top-notch Blu-Ray Player, no range conversion or dithering anywhere (not that I can see any of them with my naked eye with madVR).
Then use your TV's Brightness & Contrast like you normally would for calibration (this will crush/clip the blacks and whites outside the video range).
This option is best if you want the absolutely most pristine video signal out of your HTPC, and don't care about how Desktop software will look like.

If the HTPC and your display are not only for movie watching, option (1) is best.
Make sure you always use Dithering with this option.

I myself am on option (1), I use a PC monitor.

P.S
I'm back with my trusty old Dell U2410 IPS monitor, gave the AMVA away.

[seiyafan]

Happy Easter every one!

What does fullscreen exclusive mode do? I found that if I check enable automatic fullscreen exclusive mode, rendering queue struggles to go past 0, however with it unchecked the queue fills to full in one second and there is no frame drop.

[nevcairiel]

If one uses his HTPC strictly for movie watching, Nev's option (2a) is best, just because it eliminates the need of Dithering

That's not true. The chroma scaling and the rgb conversion already make dithering mandatory. Range conversion just slightly changes the coefficients used for the rgb conversion, it doesn't add a new step in the process.

[hozes]

That's not true. The chroma scaling and the rgb conversion already make dithering mandatory. Range conversion just slightly changes the coefficients used for the rgb conversion, it doesn't add a new step in the process.

i just ask about the color production and blacks...

which option gives the truest color production and blacks for movies

[James Freeman]

That's not true. The chroma scaling and the rgb conversion already make dithering mandatory.
@nevcairiel
I learn something new everyday.
Can you please elaborate (loosely) how Dithering is needed for Chroma Scaling and YUV -> RGB conversion?

Thanks

@hozes
Use Nev's option (1).

[huhn]

@nevcairiel
I learn something new everyday.
Can you please elaborate (loosely) how Dithering is needed for Chroma Scaling and YUV -> RGB conversion?

Thanks

@hozes
Use Nev's option (1).

chroma upscaling is done in 16 bit, so the hole picture is 16 bit. do you need more informations?

and at giving a tv limited that can do both limited and unlimited, don't you think the tv has to do limited -> unlimited conversation and i don't think a tv does this in 16 bit. and black is still 0 so even with a 16 input the pixel has to be 0.

[James Freeman]

chroma upscaling is done in 16 bit, so the hole picture is 16 bit. do you need more informations?

I don't think UPscaling is what nevcairiel meant.
As far as I understand, Upscaling does not need Dithering at all.
There is probably some kind of YUV->RGB conversion/extraction that needs dithering to be accurate.


and at giving a tv limited that can do both limited and unlimited, don't you think the tv has to do limited -> unlimited conversation and i don't think a tv does this in 16 bit.
IMO the quality of the range conversion (resulting banding or not) depends on the quality of the TV.
Most likely than not, the native range of HDMI is Limited TV range (16-235) and it is band-less, unless the TV is really crappy.
Most of the Satellite boxes and Blu-Ray/DVD players are also 16-235 range.


and black is still 0 so even with a 16 input the pixel has to be 0.
If the TV is in PC/Full range, this statement is true.

One thing you have to know; You have to understand TV's visible (displayed) black and input signal black.
When you select Limited/TV range in the TV, the displayed black that the TV shows you will be expected at step 16 of the input signal.
When you select Full/PC range in the TV, the displayed black that the TV shows you will be expected at step 0 of the input signal.

[hozes]

is btb/wtw is important for color production or for blacks...
i am wanna learn whats is the truest option for watching movies...

for eq, movies lik batman dark knight, blacks areimportant and full rgb and limited rgb affects too much, with limited rgb the screen seems to dark, with full rgb the screen seems brighter, blacks are less black...

which one is correct for true production of black

[vivan]

I don't think UPscaling is what nevcairiel meant.
As far as I understand, Upscaling does not need Dithering at all.
There is probably some kind of YUV->RGB conversion that needs dithering to be accurate.No, after any scaling you'll end up with floating point values. And to represent those fp values as integers you'll need dithering.
Let's take simple 1.5x bilinear scaling. You had 10 and 11, after scaling you'll have 10, 10.5 and 11.

[James Freeman]

No, after any scaling you'll end up with floating point values. And to represent those fp values as integers you'll need dithering.
Let's take simple 1.5x bilinear scaling. You had 10 and 11, after scaling you'll have 10, 10.5 and 11.

You are absolutely right!
Thanks.

But how a Blu-Ray player does this (Chroma upscaling) without complicated dithering, and without introducing error?

If I'm not mistaken, the native output of a Blu-Ray player is YCbCr 4:4:4 (or 4:2:2), 16-235.
The question is can a PC (HDMI) + madVR output the same "kind" of signal like a stand alone blu-ray player without overprocessing it?

@hozes
No, BTB & WTW are NOT important for 100% full quality movie watching.
Use Nev's option (1).

[huhn]

I don't think UPscaling is what nevcairiel meant.
As far as I understand, Upscaling does not need Dithering at all.
There is probably some kind of YUV->RGB conversion/extraction that needs dithering to be accurate.
ok i try it again.

chroma upscaling/up sampling is needed this creates flat point data stored at 16 bit integar so every bd gets up sampled and the picture is now 16 bit.
RGB -> YCrCb creates 32 bit float point too if a colorspace conversation is needed.

in any case you get 16 bit data and the best way to get this to 8 bit is dithering not rounding

IMO the quality of the range conversion (resulting banding or not) depends on the quality of the TV.
Most likely than not, the native range of HDMI is Limited TV range (16-235) and it is band-less, unless the TV is really crappy.
Most of the Satellite boxes and Blu-Ray/DVD players are also 16-235 range.

hdmi doesn't care if the data is limited or full range the bit are all the same it is tranfered as it is. if you change from unlimited to limted the tv gets now a stream with 16-235 but all information are in the stream even the 0-15/236-255.

and bd/dvd player aren't limited the source is limited and they simply decode it and change it to YCbCr 4:2:2/4:4:4 (this should be done with dither too...) so the tv gets the "same picture"/same range like it decodes the picture it self.

all non gaming consols/pc should always send limited because normal broadcast/DVD/BD even live stream from twitch/youtube are all limited and it should be excepted to be limited.
But how a Blu-Ray player does this (Chroma upscaling) without complicated dithering, and without introducing error?
they don't do this in 16 bit. but this can change from dvd/bd players maybe some use 10 bit bit if some of them dither i don't think so

and they can't send it untouched in 4:2:0 (now possible with hdmi 2.0) so they need it too.


If I'm not mistaken, the native output of a Blu-Ray player is YCbCr 4:4:4 (or 4:2:2), 16-235.
The question is can a PC + madVR output the same "kind" of singnal like a stand alone blu-ray player?
no MADVR can't do this MADVR output 8 bit RGB to the GPU.
you can send 4:2:2 or 4::4:4 YCbCr but this just make the picture worse are at least not better.
MADVR does a lot of this a lot better then every DVD/BD player
(1) TV accepts PC/Full levels: Set madVR to PC/Full, set GPU to PC/Full - This is usually considered the better option, if your TV can do it.

@hozes
nevcairiel provided all information you need to setup your pc/tv

1 is best then 2 (a) followed by 2 (b)

(2) TV accepts only TV/Limited levels:

(a) Set GPU to PC/Full and set madVR to TV/Limited
(b) Set GPU to TV/Limited and set madVR to PC/Full

nevcairiel provided all information you need to setup your pc/tv

1 is best then 2 (a) followed by 2 (b)

[hozes]

ok, i have a pioneer 428xd and it accepts all kind of colors...

is the full rgb in lav filter have any effect? it has also these settings, 16-255, 0-255 or untouched...

so i have set all of them to 0-255 full rgb full best and truest clolr production..thanks...

there is only one thing left, qb uses his plasma(lg) 1024x768@72hz.. my pioneer has also the same native resolution, but with cru, i cannot set it to 72hz whatever i do..does anybody advice how to set it 72hz, how another way?

[huhn]

ok, i have a pioneer 428xd and it accepts all kind of colors...

is the full rgb in lav filter have any effect? it has also these settings, 16-255, 0-255 or untouched...

so i have set all of them to 0-255 full rgb full best and truest clolr production..thanks...

there is only one thing left, qb uses his plasma(lg) 1024x768@72hz.. my pioneer has also the same native resolution, but with cru, i cannot set it to 72hz whatever i do..does anybody advice how to set it 72hz, how another way?

The lavfilter settings have no effect on MADVR with normal contend, just leave them as they are.
the only thing you may need to change is HW decoding. you can enable ayuv but only if xy vsfilter and a unusual 4:4:4 8 bit source is used with subtitle.

[nevcairiel]

@nevcairiel
I learn something new everyday.
Can you please elaborate (loosely) how Dithering is needed for Chroma Scaling and YUV -> RGB conversion?


Like others already pointed out, the conversion results in floating point data.

Simplified, and only for one color matrix, YUV -> RGB works like this: (without range change)

R = Y + 1.54 * (V - 128)
G = Y - 0.183 * (U - 128) - 0.45 * (V - 128)
B = Y + 1.81 * (U - 128)

(No guarantees for the exact coefficients, I just cobbled them together quickly)

As you can see, its quite odd values which are used here, which are guaranteed to produce odd results in 16-bit float.
If you want to convert that back to 8-bit integer for RGB output, you need to round, or better, dither!

Now if you want to do range expansion, the values used here just change slightly, and it looks like this:

R = 1.16 * (Y - 16) + 1.79 * (V - 128)
G = 1.16 * (Y - 16) - 0.213 * (U - 128) - 0.532 * (V - 128)
B = 1.16 * (Y - 16) + 2.11 * (U - 128)

No change in functionality, just a few changes in coefficients.

[vivan]

But how a Blu-Ray player does this (Chroma upscaling) without complicated dithering, and without introducing error?Who said that they don't introduce errors? ;)
I doubt that they could be visible to a human eye, though.

[John Carmack]

Who said that they don't introduce errors? ;)
I doubt that they could be visible to a human eye, though.

This. People sometimes forget that DVD or Blu-ray players are just tiny computers with RISC CPUs.

[James Freeman]

...in any case you get 16 bit data and the best way to get this to 8 bit is dithering not rounding

Can you please elaborate (loosely) how Dithering is needed for Chroma Scaling and YUV -> RGB conversion?

Like others already pointed out, the conversion results in floating point data.



But how a Blu-Ray player does this (Chroma upscaling) without complicated dithering, and without introducing error?

Who said that they don't introduce errors? ;)
I doubt that they could be visible to a human eye, though.


Thank You !
I realize Dithering is MUCH more important than I thought.

[Procrastinating]

I had not considered this, and I'm not sure how you would search for it, but does madVR select the most "ideal" of the input refresh rates? Ie will it choose 48hz for 24fps content, 47.952 for 23.976, 60hz for 30fps and so on? Assuming these are all indicated refresh rates in the settings.

In other words, does madVR select choose the refresh rate with the lowest remainder when starting the video?

[nevcairiel]

In other words, does madVR select choose the refresh rate with the lowest remainder when starting the video?

Yes, it does.

Easy enough to test for yourself as well, if you don't trust it. ;)

[Procrastinating]

Yes, it does.
Easy enough to test for yourself as well, if you don't trust it. ;)

Thanks, I didn't have enough sources at the time to test it :)

[huhn]

Thanks, I didn't have enough sources at the time to test it :)

you don't have mkv merge and a video file? X-)

[annovif]

Hello everyone, a friend of mine told me he is sure that our video card output can be 10 bit because hdmi 1.3 . To do so, i have to select ybcr 4:2:2 in the catalyst control panel. I'm not sure he is right , but i'm interested in it because my Sony panel are 10 bit native. He has a radiance too setted in that way , supported by Lumagen creator.
Another friend of mine has hacked an nvidia card to transform it in a Quadro card with 10 bit output. So is it true? Our video card are really 10 bit output?

Thanks

[James Freeman]

I wonder what madshi is cooking...