madVR - high quality video renderer (GPU assisted)

[andybkma]

Hmmmmm... It seems that the OS in this scenario doesn't tell applications about these changes. If you use an application (e.g. MonInfo) which lists the EDID block of the display, do you get different EDID blocks when you switch displays?

Hmm, I guess your right. I installed MonInfo and it always showed the Acer external monitor as the video device even when I had the internal laptop display selected. When I unplugged the Acer external then MonInfo showed the BenQ projector as the video device. Only when I unplugged both the external monitor and the projector from the laptop ports then MonInfo showed my internal laptop display as the correct and proper device.

I guess it really doesn't matter does it? They are all pretty much digital devices and I don't think I would get a better picture on my projector vs the Acer external monitor even if madVR would recognize it properly, right?

[madshi]

Hmm, I guess your right. I installed MonInfo and it always showed the Acer external monitor as the video device even when I had the internal laptop display selected. When I unplugged the Acer external then MonInfo showed the BenQ projector as the video device. Only when I unplugged both the external monitor and the projector from the laptop ports then MonInfo showed my internal laptop display as the correct and proper device.

I guess it really doesn't matter does it? They are all pretty much digital devices and I don't think I would get a better picture on my projector vs the Acer external monitor even if madVR would recognize it properly, right?
If you can use the same settings for all then it shouldn't matter. Of course the purpose of the device/display management in madVR is to allow you to use different settings for different displays. If you can live without that, everything's fine.

Any suggestions/recomendations on an affordable meter?
I'm not really an expert on this. Maybe someone else can help out. If not, you could ask in the yCMS thread.

[cyberlolo]

Hi madshi.

Thanks for the new build. But I have a problem with it. Until now, I've been using 3dlut files (generated with yCMS) in madvr, and was using this command for color correction:

Gamut_Measurements 0.6350 0.3321 0.2890 0.6007 0.1528 0.0647 0.3127 0.3294

just as it was intended to be:

Gamut_Measurements redx redy greenx greeny bluex bluey whitex whitey

But now, with the new builds (and with the new madvr version), this is not possible, and the procedure seems to be as in this example:

Gamut_Measurements 1
21.26 0.676 0.321
71.52 0.308 0.685
7.22 0.144 0.045
100.00 0.3127 0.3290

yesgrey told me that the first column (bold) was the Luminance, but when the calibrator did his job on my TV, he gave me the xy coordinates and they were 2 numbers for each component, not 3!! So I don't have that info. Is there any way to generate 3Dluts or use madvr color correction without luminance? How can I solve this?

Thanks in advance.

[madshi]

@cyberlolo, you really only need to ask in one thread. yesgrey and I are reading both. I'm sure you'll get a reply from yesgrey in the yCMS thread. Personally, I don't know the answer, but I'm pretty sure there is one.

[SamuriHL]

there is no reason other than i dont know how :)
i just have the latest mpc and madvr installed, thats it. sounds like i need more. please could you enlighten me?
i suppose there is no way to use the HW acceleration and it must be done in software?

i only rip the main movie so all my rips have just one m2ts file. ( are subtitles here too? i havnt looked)
again how do you play them with mpc and madvr please?

thanks, sory if this is a dumb question

Personally I highly recommend the following:

LAV Splitter
LAV Audio
Your favorite video decoder based upon your hardware (LAV CUVID for nVidia to do GPU decoding and for me Cyberlink Video Decoder for HAM mode for GPU decoding to offload decoding to your video card)
ffdshow raw video filter for subs *UNLESS* you're using MPC-HC in which case use their internal sub renderer

With that combination you can just load the index.bdmv file in your BD folder and it will play the main movie. Or you can open an MPLS file. Or you can open your m2ts file. However you wanna do it.

[cyberlolo]

@cyberlolo, you really only need to ask in one thread. yesgrey and I are reading both. I'm sure you'll get a reply from yesgrey in the yCMS thread. Personally, I don't know the answer, but I'm pretty sure there is one.

Ok, I didn't know you read both. Please sorry.

[janos666]

@madshi

Was your fix for the sync problem of the interlaced display mode that you disabled 1080i59? :D
I mean... was it the problem that my display doesn't really support it? :(
I kept these settings for v0.63: 1080p23, 1080i50, 1080i59
and now my display mode remains progressive 60.000Hz with 29.970fps materials. Could you explain it please?

[madshi]

Was your fix for the sync problem of the interlaced display mode that you disabled 1080i59? :D
I mean... was it the problem that my display doesn't really support it? :(
I kept these settings for v0.63: 1080p23, 1080i50, 1080i59
and now my display mode remains progressive 60.000Hz with 29.970fps materials. Could you explain it please?
Can I have a log (once again), please?

[janos666]

This time it switches but the display mode is 1080p59, not 1080i59 (the setup is still: 1080p23, 1080i50, 1080i59) -> log (http://www.mediafire.com/?i9e3b86pryxb7xb) (1080i50 works)

But I found this: http://www.100fps.com/, and now it sounds like a bad idea to output interlaced signal (see "resized before deinterlacing" -> the chroma map is resized by madvr...)

Could somebody recommend a high quality deinterlacer filter? (Or which one is the best out of the many in FFDShow?)

[nevcairiel]

Could somebody recommend a high quality deinterlacer filter? (Or which one is the best out of the many in FFDShow?)

If you're stuck with software deinterlacing, then yadif.
If you have an NVIDIA card, yu can use my LAV CUVID to use hardware decoding & hardware deinterlacing (best quality deinterlacing you can achieve with madVR, IMHO)

[madshi]

This time it switches but the display mode is 1080p59, not 1080i59 (the setup is still: 1080p23, 1080i50, 1080i59) -> log (http://www.mediafire.com/?i9e3b86pryxb7xb) (1080i50 works)
Windows reports "bad mode" when madVR tries to switch to 1080i59. Does that mode really exist?

[janos666]

Oh, SORRY! I accidentally left the MPC-HC autochanger on. Here is a new log without it and without display mode change: log2 (http://www.mediafire.com/?l8f5l0z8di4thep)

[e-t172]

Ideally(and I made this feature request to madshi a while back), we'd need some automatic rules like:
-23.976: SMPTE-C(that you could always change to EBU using a hotkey if it was mastered in Europe)
-25: EBU(it could also be HDTV, so you could always swap it if need be)
-29.97: SMPTE-C(it's most likely SD VIDEO NTSC, but it could also be HDTV if it's HD)

You'll find some food for thoughts in this thread: http://www.avsforum.com/avs-vb/showthread.php?t=1038602

I've just read this thread from beginning to end, and have not reached your conclusions. It seems the general consensus is that HD material is in fact mastered for 709 gamut. According to most professionals in this thread, they're using SMPTE-C monitors when mastering, but at the end of the chain (after the SMPTE-C monitor) there is always a gamut conversion to 709 using a 3dlut. Most of the thread is about whether it is possible to properly grade video material using a monitor with insufficient gamut ; but this discussion has nothing to do with the fact that, in the end, the result is always meant to be displayed using 709 gamut.

Because of this, I think it is best to follow the standard and use 709 gamut for HD content.

[janos666]

Windows reports "bad mode" when madVR tries to switch to 1080i59. Does that mode really exist?

I am not sure, I initially thought I need 1080i30 or 1080i29 (one of them) but I found it (1080i59) in your example list.
And I don't know what happened with v0.62 but madvr reported 59.xxHz with 1080i30 materials and I couldn't see the signs of the interlace on the display.
1080i50 works for sure, I will play with the numbers.

[madshi]

Oh, SORRY! I accidentally left the MPC-HC autochanger on. Here is a new log without it and without display mode change: log2 (http://www.mediafire.com/?l8f5l0z8di4thep)
Same, "bad mode".

[janos666]

This time I tried to list these modes:
1080i29, 1080i30, 1080i59, 1080i60
Nothing happens, the display mode remains 1080p60 and it is obviously not deinterlaced by the TV.
The TV deinterlaced the same material correctly before the sync problem occurred with v0.62 -> What was my exact display mode then with DX9?

[nevcairiel]

I've just read this thread from beginning to end, and have not reached your conclusions. It seems the general consensus is that HD material is in fact mastered for 709 gamut. According to most professionals in this thread, they're using SMPTE-C monitors when mastering, but at the end of the chain (after the SMPTE-C monitor) there is always a gamut conversion to 709 using a 3dlut. Most of the thread is about whether it is possible to properly grade video material using a monitor with insufficient gamut ; but this discussion has nothing to do with the fact that, in the end, the result is always meant to be displayed using 709 gamut.

Thats what i would've thought.
Why would a professional mastering studio master for a gamut which is only used on their screens, totally ignoring the Blu-ray spec which says you're supposed to use Rec. 709?

Sure, they are using SMPTE-C screens, that doesn't mean they master for them.

[madshi]

This time I tried to list these modes:
1080i29, 1080i30, 1080i59, 1080i60
Nothing happens, the display mode remains 1080p60 and it is obviously not deinterlaced by the TV.
The TV deinterlaced the same material correctly before the sync problem occurred with v0.62 -> What was my exact display mode then with DX9?
I don't know what was before. But it's pretty obvious that madVR can not switch your GPU to 1080i59, because then Windows reports "bad mode". So better remove 1080i59 from your mode list. I'd suggest putting only one mode in there at a time to check if it works. Probably your GPU wants 1080i29 and not 1080i59, although it's really the same. There's a bug in madVR, though, so maybe you should delay testing until the next version is out.

[janos666]

Oh god, it was a "syntax error" again.
It works if I list the 1080i29 alone. madVR reports 59.940Hz and the TV does the deinterlacing.
I wonder why 1080i50 triggers the interlaced 50Hz and 1080i29 the interlaced 59.94Hz

It's not only testing. I would actually watch some episodes from a TV Show tonight. :)

[janos666]

And the sync problem is still there. (Here is the last log if logging was turned on anyway: log3 (http://www.mediafire.com/?a66ab13cpi1kkkb)

[cyberlolo]

@madshi, yesgrey has answered that yCMS is not yet using the luminance values, so the values on the first column are not important.

ok, but what about those values in madvr? are they ignored as well?

[madshi]

madVR just passes the values on to yCMS. Other than that madVR doesn't care. So you should be fine using "dummy" values.

[oddball]

I only wish for two things from MadVR right now. A fix for the seekbar issue and the ability to screencap.

[cyberlolo]

madVR just passes the values on to yCMS. Other than that madVR doesn't care. So you should be fine using "dummy" values.

Ok, thanks.

By the way, when trying to use an external 3dlut file, madvr says: "this 3dlut file does not match the input format required by madVR"

This is the file used for generating the 3dlut with yCMS:

# Set input format
Input_Format HD YCbCr 8

# Set output format
Output_Format HD RGB_Video 16

Gamut_Measurements 1
21.26 0.6350 0.3321
71.52 0.2890 0.6007
7.22 0.1528 0.0647
100.00 0.3127 0.3294

[pie1394]

Oh god, it was a "syntax error" again.
It works if I list the 1080i29 alone. madVR reports 59.940Hz and the TV does the deinterlacing.
I wonder why 1080i50 triggers the interlaced 50Hz and 1080i29 the interlaced 59.94Hz

It's not only testing. I would actually watch some episodes from a TV Show tonight. :)

Just tried 1080i50 and I get the same result like you. It only gets correct switching with 1080p50 mode for 1080i50 material.

If you have used LAVCUVID to perform Deinterlace + Frame-rate doubler, it is better to choose progressive video mode instead of the interlaced one.

I ever tried LAVCUVID w/o deinterlace option + madVR + interlaced video mode. But it shows some "judder" like motion object's visual problems. Don't know if it is due to the madVR's presentation logic on Frame image to video driver's interlaced mode because one field is not observed on quickly motioned scenes.

[pacemaker1000]

Personally I highly recommend the following:

LAV Splitter
LAV Audio
Your favorite video decoder based upon your hardware (LAV CUVID for nVidia to do GPU decoding and for me Cyberlink Video Decoder for HAM mode for GPU decoding to offload decoding to your video card)
ffdshow raw video filter for subs *UNLESS* you're using MPC-HC in which case use their internal sub renderer

With that combination you can just load the index.bdmv file in your BD folder and it will play the main movie. Or you can open an MPLS file. Or you can open your m2ts file. However you wanna do it.

apologies for not understanding but could you explain more or point me to a link?
i have an ati 4650 card and use TMT at the moment for bluray
looks like i need to have hardware acceleration but how?
i prefer not to use ffdshow and only use mpc with madvr plus ac3filter set to spdif passthrough for aac audio files

i need to go back to basics as i thought all bluray playing was done using the gpu and powerdvd/tmt etc :confused:

i really like the madvr auto refresh feature and want to get my bd rips playing like my avi/mkv files with minimum fuss. that is just madvr renderer and HW acceleration if this is possible

thanks

ps what is HAM mode?

[leeperry]

the result is always meant to be displayed using 709 gamut.

Because of this, I think it is best to follow the standard and use 709 gamut for HD content.
well, that's the theory...and yes, some mastering houses are said to use some 3DLUT's at the very last stage to convert the gamut from SMPTE-C to HDTV...but some/most don't(depending on who you ask :p). I personally trust Joe Kane and the ISF more than some random opinions on a random forum.

But yes, your average movie goes through a lot of proprietary 3D LUT's before making it to BD: www.color.org/ICC_Chiba_07-06-19_PM_DMP_Float.pdf

A real world experiment is to calibrate your display w/ a good sensor(ΔE <1), then roll the gamuts and see for yourself...I personally have never seen a US or EUR BD that looked better w/ an HDTV gamut. And the whole idea of those automatic rules would be that you could set them all to HDTV if you like it better. It's more a matter of personal perception than anything else.

JVC pj's are known to have wide gamuts and makes movies look terribly oversaturated(it might have changed w/ their latest models)...SMPTE-C orangey red becomes ferrari red, ppl look over-tanned...but JVC did this after many real world experiments coz most ppl expect HD to look oversaturated: they find SMPTE-C dull and washed out(and it is).

The same way most ppl hate 24p and whine for 48p/60p when they actually watch their movies in 60Hz. I'll take the "Battle: Los Angeles" movie as an example, that would make anyone dizzy if watched in 60Hz as pretty much the whole movie was shot using an hand-held camera. D65/2.4 in a 24Hz multiple ensures that you're watching the movie as it's meant to be seen. Now, roll the gamut from SMPTE-C to HDTV a few times and decide which one you prefer, as there's no practical hard rule....and tbh, only the most OCD'ed videophiles really give a damn whether the hero of CARS is orangey red or deep red :p

[SamuriHL]

apologies for not understanding but could you explain more or point me to a link?
i have an ati 4650 card
looks like i need to have hardware acceleration but how?
i prefer not to use ffdshow and only use mpc with madvr plus ac3filter set to spdif passthrough for aac audio files

i need to go back to basics as i thought all bluray playing was done using the gpu and powerdvd/tmt etc :confused:

i really like the madvr auto refresh feature and want to get my bd rips playing like my avi/mkv files with minimum fuss

thanks

ps what is HAM mode?

There's 2 types of "hardware acceleration". DXVA is the traditional way where all video decoding is done on the GPU and the decoded frames stay there. All post processing has to be done in the GPU. Another way to take advantage of the GPU is to use their API to offload the decoding of the video to the GPU, but, then copy it back into system memory. This allows for post processing to be done on the CPU. This is what madVR requires. HAM mode is Cyberlink's implementation of the AMD APP API that allows them to offload the video decoding to the GPU and get the frames back to system memory. It basically acts like a software decoder, but, uses the GPU to do the heavy lifting so your CPU can concentrate on other tasks. For blu-ray, your audio setup isn't really all that adequate. Personally I'd use LAV Audio with TMT's dtsdecoderdll.dll and let it decode all audio for you. This will give you bit perfect PCM. Output that to your receiver over HDMI and you basically have one powerful little setup. :) So skip ffdshow, that's fine, but, LAV filters (splitter/audio) really would be beneficial IMO. Just disable all the MPC internal filters and add LAV Audio to the external filters list and set to prefer. LAV Splitter should just work. If not you can add that and set to prefer, as well. In MPC, set the auto load subtitles option and you should be good to go. madVR will take care of autorefresh rate changing if you configure that correctly. It's really a wonderful setup IMO.

[madshi]

madVR v0.64 released

http://madshi.net/madVR.zip

* changed a couple of calibration related texts
* Ctrl+Alt+Shift+C toggles gamma curve type now instead of Ctrl+Alt+Shift+T
* Ctrl+Alt+Shift+M toggles decoding matrix
* Ctrl+Alt+Shift+P toggles source primaries
* fixed: disabling gamma processing didn't show immediate effect
* fixed: one more display mode changer bug
* added support for switching to 59i/60i display mode for 59p/60p content
* Windows key now only stops exclusive mode when running on primary monitor
* seekbar is now shown only if mouse cursor is on playback monitor
* when the PC is locked (Windows Key + L) madVR now pauses playback
* fixed: D3D11 playback on secondary monitor could result in window size bug

[pacemaker1000]

There's 2 types of "hardware acceleration". DXVA is the traditional way where all video decoding is done on the GPU and the decoded frames stay there. All post processing has to be done in the GPU. Another way to take advantage of the GPU is to use their API to offload the decoding of the video to the GPU, but, then copy it back into system memory. This allows for post processing to be done on the CPU. This is what madVR requires. HAM mode is Cyberlink's implementation of the AMD APP API that allows them to offload the video decoding to the GPU and get the frames back to system memory. It basically acts like a software decoder, but, uses the GPU to do the heavy lifting so your CPU can concentrate on other tasks. For blu-ray, your audio setup isn't really all that adequate. Personally I'd use LAV Audio with TMT's dtsdecoderdll.dll and let it decode all audio for you. This will give you bit perfect PCM. Output that to your receiver over HDMI and you basically have one powerful little setup. :) So skip ffdshow, that's fine, but, LAV filters (splitter/audio) really would be beneficial IMO. Just disable all the MPC internal filters and add LAV Audio to the external filters list and set to prefer. LAV Splitter should just work. If not you can add that and set to prefer, as well. In MPC, set the auto load subtitles option and you should be good to go. madVR will take care of autorefresh rate changing if you configure that correctly. It's really a wonderful setup IMO.

thanks for taking the time to write this explanation
i have downloaded lavfilters0.28 and will try tonight to get it working :thanks:

[SamuriHL]

thanks for taking the time to write this explanation
i have downloaded lavfilters0.28 and will try tonight to get it working :thanks:

No problem at all. If you have any issues, just shoot me a PM so we don't take up more space in this thread. I can definitely help you get it setup and configured if you have issues.

@madshi, man, I didn't even get to try 0.63 yet and now you've released a new one! Thanks!!

[n3w813]

First of all you may want to re-create your preferred video output mode as a custom mode, because with current NVidia drivers that's the only way to force the driver to output proper 0-255 levels. Once you've done that, get yourself one of those cheap calibration DVDs, or download the free AVSForum calibration disc. With these discs you should be able to double check whether you have to set madVR to 0-255 or 16-235 output. Since your display is a TV, it will *probably* want TV levels, but better double check with a calibration DVD.


Thanks for the reply Madshi.

One more question, so once I create the custom resolution in the Nvidia drivers, Windows desktop will be outputting 0-255 to HDMI. In Madvr, I should select to output PC levels, which will expand the default TV levels of the videos from 16-235 to 0-255. Then on the TV, I should set the RGB Dynamic Range option to Full (instead of Limited)?

If I do this, can I assume....
-BTB/WTW information is lost when MadVR expands the levels from TV > PC
-My TV will most likely take the full RGB 0-255 info and convert back to 16-235

:thanks:

n3w813

[Hprd]

Well v64 didn't fix my problem. Although if i were you, i wouldn't worry about it for now, as i found a workaround for it, it's just that i have to enable some things (check run presentation in seperate thread, and flush and wait (sleep) after copy to backbuffer on top of overshoot latency) for when playing stuff back on 48/59hz otherwise it could lead to massive frame drops on 24/30hz (or it did on previous versions, i'll try testing more later to see if it still does, so far in somewhat limited playback testing, it was fine.).

[madshi]

In Madvr, I should select to output PC levels, which will expand the default TV levels of the videos from 16-235 to 0-255. Then on the TV, I should set the RGB Dynamic Range option to Full (instead of Limited)?
Can't say, just try what looks better. Of course your TV setting should match the madVR setting.

[noee]

* seekbar is now shown only if mouse cursor is on playback monitor
* when the PC is locked (Windows Key + L) madVR now pauses playback
* fixed: D3D11 playback on secondary monitor could result in window size bug

confirmed! thx.

[tschi]

Hi Madshi Thank for the new version. :)
Where the gamut measurements are stored ?
I deleted madVR folder, and re install all, but, there is still my gamut measurement, I guess the values are stored somewhere else ?
Yesterday, I test 0.62 w/o any issue, and remake a new calibration. Today that I mistook when I put my new gamut values, and now I had very very bad gamut correction even if I put corrected gamut measures. I would like to re initialize all madvr information. Thanks

edit, I have also a question : in colorHCFR I have XYZ and xyz values, I think XYZ in madVR is xyz in colorHCFR (my red x= 0.653 <-> X=26.219) Am I wrong ?

[madshi]

I deleted madVR folder, and re install all, but, there is still my gamut measurement, I guess the values are stored somewhere else ?
Yesterday, I test 0.62 w/o any issue, and remake a new calibration. Today that I mistook when I put my new gamut values, and now I had very very bad gamut correction even if I put corrected gamut measures. I would like to re initialize all madvr information.
They're stored both in "settings.bin" and in the registry. Simply double click "restore default settings.bat" to restore the default settings.

in colorHCFR I have XYZ and xyz values, I think XYZ in madVR is xyz in colorHCFR (my red x= 0.653 <-> X=26.219) Am I wrong ?
Not sure, that's a question for yesgrey to ask.

[alph@]

very good build madshi, the speed of rendering is improving
(W7 64, ati 5660)
to have an idea,what the time of rendering and presentation on average.

[tschi]

ok thanks, I didn't see "restore default settings.bat" (missing in 0.64)

[Andy o]

madVR v0.64 released

http://madshi.net/madVR.zip


* fixed: one more display mode changer bug
* added support for switching to 59i/60i display mode for 59p/60p content

Hi madshi, this build is better than 0.63, but it's very similar as 0.62. I could find two main differences.

One was that 1080i29 on 0.64 works similarly as 1080i59 on 0.62, meaning that when 1080p24, 1080p50 and 1080i29 are on the list, my display switches to 1080p24 with 60p content.

The other difference is that 1080i29 when is alone in the options, does switch to 1080i29 for 60p content (whereas with 0.62, 1080i59 didn't do anything with 60p content)

Here's the two logs. "Bad" is for when it changes to 1080p24.

http://www.megaupload.com/?d=CDB8QL75

Another thing, 1080i59 doesn't work at all now, just like with 0.63. It was working with 0.62 (for 60i/30p content) if you recall from my log (http://forum.doom9.org/showthread.php?p=1505997#post1505997), don't know if you missed it cause I posted it right after you had posted 0.63. With both 0.63 and 0.64, if I add it, it disables the switch even if I also have 1080i29 in the options.

[madshi]

to have an idea,what the time of rendering and presentation on average.
Is that a question? Rendering and presentation times are very dependent on the movie and especially the GPU. So I can't give you any average times.

ok thanks, I didn't see "restore default settings.bat" (missing in 0.64)
Argh, you're right. I've just re-uploaded v0.64, this time with the "restore default settings.bat".

http://madshi.net/madVR.zip

Hi madshi, this build is better than 0.63, but it's very similar as 0.62. I could find two main differences.

One was that 1080i29 on 0.64 works similarly as 1080i59 on 0.62, meaning that when 1080p24, 1080p50 and 1080i29 are on the list, my display switches to 1080p24 with 60p content.

The other difference is that 1080i29 when is alone in the options, does switch to 1080i29 for 60p content (whereas with 0.62, 1080i59 didn't do anything with 60p content)
Argh, how stupid can I be? The "bad" log clearly shows that madVR is still not doing things correctly. Hopefully I'll have that *finally* fixed with v0.65. Sorry for taking so long... :(

Another thing, 1080i59 doesn't work at all now, just like with 0.63. It was working with 0.62 (for 60i/30p content) if you recall from my log (http://forum.doom9.org/showthread.php?p=1505997#post1505997), don't know if you missed it cause I posted it right after you had posted 0.63. With both 0.63 and 0.64, if I add it, it disables the switch even if I also have 1080i29 in the options.
Could you use a different file host next time, if possible? filesonic is awful. I have to wait 13 minutes to get this log.

[Andy o]

No prob, it's not really a big problem since there's not much 60p content. Yeah sorry about filesonic, I just figured out about the wait time, so I re-uploaded to megaupload. Is there one you prefer? I did filesonic cause most of the others I tried had popups and some scam donwload links.

Here's the 0.62 log where 1080i59 was working for 30p/59i content.

http://www.megaupload.com/?d=UC2ESXF0

[nevcairiel]

People should use multiupload more, then everyone can pick their favorite download place. :p

[Andy o]

right, noted. megaupload doesn't seem to have a one file per xx time limit, maybe just bandwidth limit, which is OK for this stuff I guess.

[madshi]

Is there one you prefer?
Any which doesn't make me wait.

Here's the 0.62 log where 1080i59 was working for 30p/59i content.

http://www.megaupload.com/?d=UC2ESXF0
Ah yes, due to a bug in v0.62 madVR actually switched to 1080i29 although you specified 1080i59. v0.64 does not do that, anymore. The simple thing to learn from this log is that 1080i59 definitely doesn't work.

[iSunrise]

Thanks for 0.64 madshi.

I did some tests switching between source primaries and color matrixes and noticed that when the OSD appears there´s an "(auto detect)" shown after BT.709.

Does this mean that madVR "auto-detected" both the source primaries and the color matrix from the current playing file or are you actually applying some rules now, which assume what is correct?

I´m asking since no matter what videos or movies I play, it always shows "BT.709 (auto detect)" for both the source primaries and the color matrix, even when playing SD content (NTSC or PAL).

[madshi]

I did some tests switching between source primaries and color matrixes and noticed that when the OSD appears there´s an "(auto detect)" shown after BT.709.

Does this mean that madVR "auto-detected" both the source primaries and the color matrix from the current playing file or are you actually applying some rules now, which assume what is correct?

I´m asking since no matter what videos or movies I play, it always shows "BT.709 (auto detect)" for both the source primaries and the color matrix, even when playing SD content (NTSC or PAL).
Seems that the first detection is correct, but then every video afterwards reuses the first detection. If you restart the media player, the first detection after that will be correct again. Will be fixed in the next build.

[yesgrey]

There is indeed a REC.709 gamut, but to avoid confusion it's better to call it HDTV.

OTOH, there is no REC.601 gamut...NTSC SD is always using SMPTE-C.

As you can see in this animated gif (http://www.homecinema-fr.com/forum/download/file.php?id=54246), sRGB/REC.709/HDTV are several names for the very same gamut...and "PAL" should really read "EBU". There's no "PAL" gamut per se.
@yesgrey?
Yes, the real name of the primaries set is not PAL, but I still think we should call it PAL. Everybody knows what is PAL, but very few know what is EBU. Furthermore, even DVDs use the word PAL, where to be more exact the word PAL should be used only for analog broadcast... and if PAL use those primaries, there's nothing wrong in naming them like that.

[madshi]

madVR v0.65 released

http://madshi.net/madVR.zip

* fixed: decode matrix + source primaries detection only worked once
* fixed: yet another bug in the automatic display changer
I hope that the display mode changer will now finally work. It seems that GPUs require modes to be named 1080i29 instead of 1080i59. I have removed matching support for 1080i59 now. Hopefully that won't break anything.

Ok, probably last version for a couple of days.

[leeperry]

well, European BD's are known/said to use the EBU gamut(even though they're 23.976)...they're not quite "PAL" ;)

anyway, maybe it'd be a good idea to have a thread about calibration related to mVR, not technically related to yCMS...simply about discussing how to get the most out of mVR for HTPC purposes. I already told madshi that I would be happy to make a FAQ about that: what's the best/most affordable colorimeter, where to get the gamut coordinates, what to aim for, etc etc.

I believe there isn't much interest in gamut mapping atm because most ppl dunno what they're missing...it's like Reclock, once you've watched a movie in 24.000fps in the right gamut: hell breaks loose :D

Dumbing down "EBU Tech. 3213 (http://www.google.com/search?hl=en&source=hp&q=EBU+Tech.+3213&aq=f&aqi=&aql=&oq=)" to "PAL" is not going to help anyone IMHO. A proper FAQ w/ the right terms will be about learning ppl how to fish, more than anything else.

Anyway, I plan on creating a 100MB ramdisk (again) to host the new LUT..I want to leave the gamut on SMPTE-C and the decoding matrix on BT.709. I guess these options will be remembered? I'll manually switch to HDTV when need be(I don't really care for EBU, as I seldom watch european stuff). I will keep the "settings.bin" read only so it'll always revert to SMPTE-C when I close the player...hopefully mVR won't try reading the registry.

I guess my last problem is that I feed PC levels to mVR?! But I'll try some test patterns to ensure that everything's cool :o