View Full Version : madVR - high quality video renderer (GPU assisted)
huhn
10th January 2015, 14:24
anyone please kindly help how to fixed the error? thanks. guys did u noticed when open mpc got some delay? around 2-3 sec
about the delay try to disable DXVA. this helped someone with an AMD card.
@james calm down X-)
khanmein
10th January 2015, 14:26
about the delay try to disable DXVA. this helped someone with an AMD card.
@james calm down X-)
bro i didn't use DXVA & i'm not using AMD. everything u said wrong. i'm nvidia fan not amd so impossible i'm using AMD. omg can u really help don't simply said.
James Freeman
10th January 2015, 14:26
@james calm down X-)
:p
How come nobody posted this news on this board yet?
Qaq
10th January 2015, 14:29
guys did u noticed when open mpc got some delay? around 2-3 secPerhaps. 2-3 sec is not a problem for me at all. There is a whole bunch of filters and they need to fill their buffers/queues etc.
khanmein
10th January 2015, 14:33
Perhaps. 2-3 sec is not a problem for me at all. There is a whole bunch of filters and they need to fill their buffers/queues etc.
i keep facing the error. i del madvr or even reset to defaults still the same.
huhn
10th January 2015, 14:33
bro i didn't use DXVA & i'm not using AMD. everything u said wrong. i'm nvidia fan not amd so impossible i'm using AMD. omg can u really help don't simply said.
i should have known all this. sorry but my mind reading is pretty bad...
khanmein
10th January 2015, 14:38
i should have known all this. sorry but my mind reading is pretty bad...
if u can't help don't simple answer here thanks. i need pro guy or expert not someone simply bash around & treat me like a fool.. thanks!
James Freeman
10th January 2015, 15:17
I have a question about range and what will yield the best results.
Currently my arrangement is as follows:
Nvidia output RGB Full 0-255
MadVR Limited 16-235
TV Limited 16-235
This way I preserve the BTB and WTW data and calibrate via the TV controls and AVSHD709 calibration patters in mp4 format with MPC-HC.
The image behaves as though it is a good Blu-Ray player but in RGB instead of YCbCr.
Plus, the image stays in its native limited 16-235 range and no Luma dithering is used, hence calmer image.
More so, no range conversion stages at all, everything stays in its native range so no conversion errors.
My actual question is should I clip the WTW, BTB and Chroma?
Like so:
Nvidia output RGB Limited 16-235 (range conversion: Full to Limited)
MadVR Full 0-255 (range conversion: Limited to Full)
TV Limited 16-235
This will result in two range conversion stages and added dithering, but it will clip the unnecessary data.
Or so:
Nvidia output RGB Full 0-255
MadVR Full 0-255 (range conversion: Limited to Full)
TV Full 0-255
This will result in one range conversion stages (an excellent one I should add :D) and added dithering, but it will also clip the unnecessary data.
BUT, my Panasonic ST60 creates banding in RGB Full and 4:4:4 chroma, with my Nvidia card (I don't have ATI card to try).
The PS3 has no banding at all in RGB Full Range 4:4:4 setting, with the same "Grey Ramp 0-255" image loaded via USB.
michkrol
10th January 2015, 15:30
I'm jus thinking about something. Why do the video profiles have to be configured manually? Thinking about it, it could be auto-configured pretty easily.
(...)
madVR could do these tests and build these profiles itself.
There are many possible resolution and FPS (after deinterlacing) combinations and that's not all you need to take into account.
What if you use madvr on two (or more) different screens for example?
Another problem would be the subjectivity of some settings, for which you would need user input anyway. To make a few examples:
what is a "better" scaling algorithm - do you want lanczos with anti-ringing or jinc without ar?
is it better to have debanding or error diffusion if you have performance only for one of them?
is it better to have NNEDI luma doubling with 64 neurons or luma doubling with 32 neurons and chroma doubling with 32 neurons?
do you really need NNEDI doubling with 256 neurons for anything (assuming your GPU can handle it)?
Most importantly: at what point is the added energy consumption or rather heat and noise not really worth the miniscule quality gains?
To sum up, in my opinion it's not worth the time invested in developing such feature, especially if to make it really worth it you need user input which kind of defeats the purpose of automation ;)
So you can't replicate madVR lowering render time after exiting out of, and then back into fullscreen?
Are you sure it's not simply because you reset the stats when you toggle full screen mode?
It does happen for me because I have the decoder queue empty at first, then it gets full before I toggle full screen.
The render times do lower over time for me also without doing anything, since it's an average value.
To make sure, reset the stats with CTRL+R instead of toggling the full screen and see what happens.
i keep facing the error. i del madvr or even reset to defaults still the same.
If I understand you correctly and this problem occurs without madvr, please contact the player's/codecs' developers - this is madvr's thread for madvr's discussion.
If I understand you wrong, please check with other video renderers (e.g. EVR) and report back, if the problem still occurs.
huhn
10th January 2015, 15:36
http://www.avsforum.com/forum/139-display-calibration/1471169-madvr-argyllcms.html#post23274961
Originally Posted by madshi View Post
There are 3 possible HTPC level configurations, when using madVR:
(1) Display wants 0-255. GPU and madVR are consequently also both set to 0-255.
This is the most recommended setup because it doesn't (shouldn't) have any banding problems, and still has all video, desktop and games with correct black/white levels. In this case test patterns need to have black at 0,0,0, obviously.
(2) Display wants 16-235. GPU is set to 16-235. madVR has to be set to 0-255.
This is not recommended, because the GPU stretches the madVR output, probably in 8bit without dithering, so banding could be introduced. However, this is not a big problem for ArgyllCMS. Argyll still needs to create test patterns with black at 0,0,0. The GPU will then stretch the test patterns from 0-255 to 16-235, so the display will get 16,16,16, although Argyll rendered 0,0,0. So the levels are correct.
(3) Display wants 16-235. GPU is set to 0-255. madVR is set to 16-235.
This is the recommended setup for best image quality if your display can't do 0-255. This setup results in banding-free madVR image quality. However, levels for desktop and games will be incorrect, because desktop and games will render black at 0,0,0, while the display expects black at 16,16,16. This is a problem for ArgyllCMS, because Argyll will create test patterns with black at 0,0,0, and the display will also receive these at 0,0,0. So basically Argyll test patterns will have wrong levels, which will screw up the whole calibration.
It is my understanding that Graeme implemented the -E switch specifically for (3), because without the -E switch Argyll test patterns would send wrong levels to the display. Basically the -E switch tells Argyll to render test patterns with black at 16,16,16 and white at 235,235,235, which Argyll never had to do before. When using VMR/EVR, you usually switch your GPU to 0-255 or 16-235. In both cases Argyll can render test patterns with black at 0,0,0, and they will still be sent to the display with the correct levels. However, due to my recommendation to use (3) if your display doesn't support 0-255, Argyll suddenly needs to render test patterns differently. Hence Graeme implemented the -E switch.
So my understanding is that -E should be used only for (3) and in no other situation. If you use the -E switch for (1), Argyll will create test patterns with black at 16,16,16 which would be incorrect!
should be option 3 for you. this feels like a Déjà-vu.
James Freeman
10th January 2015, 15:43
should be option 3 for you. this feels like a Déjà-vu.
Thanks huhn.
No its not a Déjà-vu, or an error in the matrix.
I tend to ask the same question from time to time to reassure myself that I made the right choice.
:D
khanmein
10th January 2015, 15:50
There are many possible resolution and FPS (after deinterlacing) combinations and that's not all you need to take into account.
What if you use madvr on two (or more) different screens for example?
Another problem would be the subjectivity of some settings, for which you would need user input anyway. To make a few examples:
what is a "better" scaling algorithm - do you want lanczos with anti-ringing or jinc without ar?
is it better to have debanding or error diffusion if you have performance only for one of them?
is it better to have NNEDI luma doubling with 64 neurons or luma doubling with 32 neurons and chroma doubling with 32 neurons?
do you really need NNEDI doubling with 256 neurons for anything (assuming your GPU can handle it)?
Most importantly: at what point is the added energy consumption or rather heat and noise not really worth the miniscule quality gains?
To sum up, in my opinion it's not worth the time invested in developing such feature, especially if to make it really worth it you need user input which kind of defeats the purpose of automation ;)
Are you sure it's not simply because you reset the stats when you toggle full screen mode?
It does happen for me because I have the decoder queue empty at first, then it gets full before I toggle full screen.
The render times do lower over time for me also without doing anything, since it's an average value.
To make sure, reset the stats with CTRL+R instead of toggling the full screen and see what happens.
If I understand you correctly and this problem occurs without madvr, please contact the player's/codecs' developers - this is madvr's thread for madvr's discussion.
If I understand you wrong, please check with other video renderers (e.g. EVR) and report back, if the problem still occurs.
it related to madVR got dump file. http://www54.zippyshare.com/v/27530580/file.html
DragonQ
11th January 2015, 00:28
It seems that not only is FreeSync more flexible, but according to various CES articles, the first FreeSync monitors are limited to 40Hz at the minimum, or else they will flicker. Not sure if that's because of the pixel matrix / panel driver firmware that just isn't able to go lower, but that's the only info that I came across. More in-depth stuff seems to be still rare.
At least theoretically, 9-240Hz seems to be perfect for our needs.
The minimum refresh rate thing is strange to me. For technologies like CRT, plasma and OLED, it totally makes sense that refresh rates need to be high enough to avoid flicker. Indeed, my plasma displays 50 Hz inputs as 100 Hz and 24 Hz inputs as 96 Hz for this reason. However, don't LCDs use sample-and-hold? If so, why would there be flicker with any refresh rate?
I suppose it's largely irrelevant anyway since you can always reshow the previous frame if a new one isn't ready. For example, if your minimum refresh rate was 10 Hz (0.1 s between frames) but no frame is sent within 0.1 s, then just reshow the previous frame and wait for a new frame in the next 0.1 s. The only minor problem would be if a new frame was sent very soon after a previous frame was re-used. Whether that would cause a delay to that new frame depends on the maximum refresh rate of the monitor.
ktsbkt
11th January 2015, 00:51
I have a question and I'd like to report a bug as well.
I'm using a Radeon R9 290 + catalyst 14.12 on Windows 8.1 64-bit, with 2 monitors. And I've found this strange behaviour with madVR:
http://i.imgur.com/pbGHNSb.png
I don't know if you are aware of this, but I'm reporting it here in case you weren't.
And then I have a question regarding madVR's GPU usage.
Please have a look at this screenshot: http://i.imgur.com/tTjmXId.jpg
It shows that madVR is ignoring the Clockspeed limits set by MSI Afterburner. The GPU just runs at full clockspeed, and this hurts the video, since my low voltage levels forced by Afterburner still applies even on full clockspeed.
Is there a way for me to configure madVR so it respects MSI Afterburner?
Asmodian
11th January 2015, 01:12
The minimum refresh rate thing is strange to me. For technologies like CRT, plasma and OLED, it totally makes sense that refresh rates need to be high enough to avoid flicker. Indeed, my plasma displays 50 Hz inputs as 100 Hz and 24 Hz inputs as 96 Hz for this reason. However, don't LCDs use sample-and-hold? If so, why would there be flicker with any refresh rate?
Even with LCDs the pixel is not stable over time, it takes some time to get to the correct value and it will only stay at that correct value for a specific amount of time. They need to be "refreshed" (like volatile memory) or the pixels start to drift to other values. This refresh interval is the minimum frame rate.
If you don't refresh quickly enough you can notice the next refresh as a flicker because colors that were supposed to be static between the two frames changed to other values before the second frame was displayed. It is a very different mechanism for flickering (and a very different flicker) but it is still unpleasant.
I have a question and I'd like to report a bug as well.
I'm using a Radeon R9 290 + catalyst 14.12 on Windows 8.1 64-bit, with 2 monitors. And I've found this strange behaviour with madVR:
I don't know if you are aware of this, but I'm reporting it here in case you weren't.
See the first post in this thread. :)
known problems / limitations:
- rotated displays (portrait vs landscape orientation) don't work yet
And then I have a question regarding madVR's GPU usage.
Please have a look at this screenshot: http://i.imgur.com/tTjmXId.jpg
It shows that madVR is ignoring the Clockspeed limits set by MSI Afterburner. The GPU just runs at full clockspeed, and this hurts the video, since my low voltage levels forced by Afterburner still applies even on full clockspeed.
Is there a way for me to configure madVR so it respects MSI Afterburner?
madVR is a game to the GPU drivers, anything they do if you launch a game they will do for madVR. There is nothing you can change in madVR to effect this. It is not madVR that is not respecting MSI Afterburner but the GPU drivers.
nevcairiel
11th January 2015, 01:13
Rotated screens are not supported by madVR, known issue.
And personally I doubt madVR can influence the clockspeed that the GPU uses.
DragonQ
11th January 2015, 01:28
Even with LCDs the pixel is not stable over time, it takes some time to get to the correct value and it will only stay at that correct value for a specific amount of time. They need to be "refreshed" (like volatile memory) or the pixels start to drift to other values. This refresh interval is the minimum frame rate.
If you don't refresh quickly enough you can notice the next refresh as a flicker because colors that were supposed to be static between the two frames changed to other values before the second frame was displayed. It is a very different mechanism for flickering (and a very different flicker) but it is still unpleasant.
Thanks for the explanation. So what is the generally agreed minimum refresh rate for modern LCDs to avoid flicker then? Is G-Sync's 30 Hz minimum about right here? Or perhaps it's different for TN/MVA/IPS?
I know that my laptop screen is capable of reducing to 40 Hz to conserve power, although I turned this feature off because the difference is noticeable to me.
Mr Alpha
11th January 2015, 18:07
Thanks for the explanation. So what is the generally agreed minimum refresh rate for modern LCDs to avoid flicker then? Is G-Sync's 30 Hz minimum about right here? Or perhaps it's different for TN/MVA/IPS?
I know that my laptop screen is capable of reducing to 40 Hz to conserve power, although I turned this feature off because the difference is noticeable to me.
I've seen people complain about flickering with G-SYNC when the game stalls and the framerate drops. I suspect 30Hz might be cutting it too low.
a8213711
11th January 2015, 19:12
did you used print screen?
and is your TV using PC mode there is a huge change your TV can't do PC mode in any other refresh rate than 60 hz (most samsung can't do this for what ever reason)so this may trigger the issue with the saturation. and if this is the case and you want to use PC mode think about 60 HZ only and smooth madVR motion.
Yes, print screen and no difference. Also I see there are more settings (no more greyed out) in my TV after I enter this "mode".
Do PC mode means 0-255 color range and no overscan? Because changing refresh rate doesn't seem to change those.
Also let's remember it enters in this mode only after switching back from Windows Media Center.
The problem is that I suppose the preferable rate (50Hz from 25fps source) is enabled only entering this mode, but colors get worse.
As the smooth option I can't use it because I can't handle it.
huhn
11th January 2015, 23:41
Yes, print screen and no difference. Also I see there are more settings (no more greyed out) in my TV after I enter this "mode".
a PC mode usually disables most settings in a TV to lower input lag and give it the possiblity to show a pixel perfect image.
Do PC mode means 0-255 color range and no overscan? Because changing refresh rate doesn't seem to change those.
the change in saturation sounds like your TV needs full range but only gets limited.
a TV normally doesn't enter PC mode on it's own. so you should know if you set it up for this or not.
Also let's remember it enters in this mode only after switching back from Windows Media Center.
The problem is that I suppose the preferable rate (50Hz from 25fps source) is enabled only entering this mode, but colors get worse. [quote]
what refresh rate is madVR reporting be for you enter WMC and what after?
[quote]As the smooth option I can't use it because I can't handle it.
can you say why? for example you see ghosting or your GPU can't handle it or what is the issue?
XMonarchY
12th January 2015, 15:08
Madshi, thank you so much for fixing madTPG. I couldn't get the 0.87.11 version to work with HCFR Calibration no matter what I tried. 0.87.10 worked, but there were some issues with using FullScreen, where patterns would play in FullScreen mode behind the madTPG window!
Now madTPG is very responsive and plays all the patterns without any issues at all! 3DLUT calibration is hassle-free once again, thanks to your excellent work and support!
madVR FTW - nothing beats it! Yet, I hope there will be more quality-improving goodies in the future!
Does G-Sync benefit film playback @ 23.976Hz with madVR or @ whichever other refresh rate (120Hz? 144Hz?) ? I figured it would run the film and screen at perfect 23.976Hz/Fps, making it the smoothest solution for film playback on compatible PC monitors, such as ASUS ROG Swift.
a8213711
12th January 2015, 16:57
a PC mode usually disables most settings in a TV to lower input lag and give it the possiblity to show a pixel perfect image.
the change in saturation sounds like your TV needs full range but only gets limited.
a TV normally doesn't enter PC mode on it's own. so you should know if you set it up for this or not.
[quoteAlso let's remember it enters in this mode only after switching back from Windows Media Center.
The problem is that I suppose the preferable rate (50Hz from 25fps source) is enabled only entering this mode, but colors get worse. [quote
what refresh rate is madVR reporting be for you enter WMC and what after?
can you say why? for example you see ghosting or your GPU can't handle it or what is the issue?
With this "mode" I didn't mean PC mode, but this special mode in which enters after switching back from Media Center to a 25fps interlaced file, but actually I just realized it is enabled when my TV is set at 50Hz or 23.9Hz.
And is set at 50Hz: directly if I play a 25fps progressive file, and using the "alt+tab" method when I play a 25fps interlaced file (otherwise is at 59.9Hz).
As PC mode I think I enabled it once and for all; I can't say if it's actually enabled only at those 2 frequency.
Before and after WMC the refresh rate is always at 25.000 fps.
As Smooth Option: is too much power hungry for my low budget PC.
I just want my HTPC to always show the correct color gamma and to be always set to the properly refresh rate!
vazel
12th January 2015, 21:31
I'm getting green pixel artifacts with NNEDI3 enabled. I tried taking a screenshot but these artifacts don't show up in screenshots. Does anyone know what it could be and how to fix it?
Edit: Ok I was able to capture the artifacts in a screenshot by using printscreen instead of mpc-hc's built-in screenshot function. http://i.imgur.com/d2CkvKM.jpg
e-t172
12th January 2015, 23:36
Does G-Sync benefit film playback @ 23.976Hz with madVR or @ whichever other refresh rate (120Hz? 144Hz?) ? I figured it would run the film and screen at perfect 23.976Hz/Fps, making it the smoothest solution for film playback on compatible PC monitors, such as ASUS ROG Swift.
madVR doesn't support G-Sync. Enabling G-Sync with madVR will not gain you anything, and it won't make the video smoother. It will behave as if G-Sync is disabled, or maybe worse.
nevcairiel
13th January 2015, 00:51
Note that G-Sync on many screens has a minimum refresh rate of 30 or 40 fps (depending on screen), so for full G-Sync compat at 24 fps, madVR would need to draw each frame at least twice, or the screen would drop out of G-Sync mode and re-draw the frame itself.
DigitalLF
13th January 2015, 19:33
What card would be best for MadVR?
I need to change my 280x i use in my HTPC.. that computer is used for well movie/series/web/mail no gaming. but PQ is priority 1 on that computer and the 2th priority is "heat vs performance"
What card would be best for MadVR? NNEDI3 128 neurons seems to demand a lot of the poor card :P
michkrol
13th January 2015, 20:11
I'm getting green pixel artifacts with NNEDI3 enabled. I tried taking a screenshot but these artifacts don't show up in screenshots. Does anyone know what it could be and how to fix it?
Edit: Ok I was able to capture the artifacts in a screenshot by using printscreen instead of mpc-hc's built-in screenshot function. http://i.imgur.com/d2CkvKM.jpg
Try updating your drivers.
Check if the GPU is not overheating - run GPU-Z or similar to check temps while using NNEDI.
Try disabling DXVA decoding (if applicable).
Check if the GPU is not otherwise "bad" - run OCCT GPU test with error checking or similar tool.
Do post details of your config (hardware + software), if none of the above helps.
What card would be best for MadVR?
We don't ask for "best" on this forum - read the rules ;)
Sometimes integrated GPU can be good enough.
I'd rather ask what GPU can run smoothly with given setting, on given screen resolution, with given video format (resolution + fps + deinterlacing(on/off)), with minimum noise/heat or similar question.
Especially since 280x should be able to do NNEDI3 with 128 neurons for image luma doubling or chroma upscaling for SD content.
IronRush
14th January 2015, 00:31
Hello guys!
I need some help please.
I don't know if madvr here is doing his job. I think it isn't upscalling properly.
I formatted my PC yesterday. Now I am using Windows 8.1.
I always used madvr. Older version. And now with new OS and rig, I want to bring more quality to the table.
When I open a video file in windowed mode, the file is always same resolution than default, nothing change.
Madvr calibration tab I set 1080p24 and 1080p60.
I think normal if I open a 480p file, it need to open with 1080p resolution for properly upscalling, no?
Could you guys give me some tips please?
If important, my rig is i5-3570k/gtx 970.
Thanks in advance!
Asmodian
14th January 2015, 04:46
madVR doesn't support G-Sync. Enabling G-Sync with madVR will not gain you anything, and it won't make the video smoother. It will behave as if G-Sync is disabled, or maybe worse.
If you enable g-sync with madVR the screen flickers constantly. It is not watchable.
BetA13
14th January 2015, 05:00
I'm getting green pixel artifacts with NNEDI3 enabled. I tried taking a screenshot but these artifacts don't show up in screenshots. Does anyone know what it could be and how to fix it?
Edit: Ok I was able to capture the artifacts in a screenshot by using printscreen instead of mpc-hc's built-in screenshot function. http://i.imgur.com/d2CkvKM.jpg
had teh same problem, its the Driver...
ether dont use nnedi3 and use jinc or ´revert back to older driver..
http://forum.doom9.org/showpost.php?p=1703366&postcount=27880
http://forum.doom9.org/showpost.php?p=1704001&postcount=27912
huhn
14th January 2015, 15:54
With this "mode" I didn't mean PC mode, but this special mode in which enters after switching back from Media Center to a 25fps interlaced file, but actually I just realized it is enabled when my TV is set at 50Hz or 23.9Hz.
And is set at 50Hz: directly if I play a 25fps progressive file, and using the "alt+tab" method when I play a 25fps interlaced file (otherwise is at 59.9Hz).
As PC mode I think I enabled it once and for all; I can't say if it's actually enabled only at those 2 frequency.
Before and after WMC the refresh rate is always at 25.000 fps.
As Smooth Option: is too much power hungry for my low budget PC.
what programs are running in the background when you try to use madVR?
the only potinal madVr bug i see here is that madVR stays at 60 hz and doesn't switch to 50 hz that's it. a simple screen from the OSD would have shown most of these issue.
Before and after WMC the refresh rate is always at 25.000 fps.
refreshrate and FPS are 2 different things.
I just want my HTPC to always show the correct color gamma and to be always set to the properly refresh rate!
you just have to setup your TV correctly if you switch back from 60 HZ to something else like 50 hz and the picture looks strange that is a huge indicator you are using PC mode and your TV is leaving it.
Fullmetal Encoder
15th January 2015, 02:26
Has anyone else had any persistent issues with UAC pop-ups upon running a video asking if I want to allow madHcCtrl.exe to make changes to my computer? On my original install of madVR I hadn't had this issue but have been receiving this response ever since upgrading to the latest version. I'm not sure what I could be doing differently. I unzipped the madVR download, selected and dragged and dropped the files into my current madVR folder location, "Program Files (x86)", then right-clicked the install.bat file and chose to run with administrator privileges. I'm using the latest Windows 8.1 Professional. Before copying the files over I did make sure to uninstall it properly.
Asmodian
15th January 2015, 02:47
Thanks for the explanation. So what is the generally agreed minimum refresh rate for modern LCDs to avoid flicker then? Is G-Sync's 30 Hz minimum about right here? Or perhaps it's different for TN/MVA/IPS?
It is different for different screens, both the major technologies (TN/MVA/IPS) and for the individual panels (slow or fast IPS for example). It even varies for the color displayed, some colors will change faster than others.
Update rate is similar in that the starting and ending color has a huge impact on the speed of the transition. I have noticed that even fast MVA or IPS panels still have some color transitions that take well over 20 ms.
This is another reason variable frame rate is a little more tricky to get right even if it was possible to present frames with very accurate timing (without Windows stalling madVR for 10s of milliseconds randomly).
peplegal
15th January 2015, 16:43
Hi guys, some little help here...
I have a HD4850/512 and a HD6450/1GB.
I've successfully installed both in my HTPC, but switching between them is tricky due to 2 different version of drivers (HD6450 => Catalyst 14.4...and HD4850 => Catalyst 13.1)
Not sure if I did a good thing. I need to keep the old one for games, but I've heard the new one seems to be better for movies (using madVR)...is that right ?
Strangely, the old 4850 is showing better rendering times ( 6mS for lanczos upscaling 720p -> 1080p) , comparing to 29mS for HD6450.
Could anyone else confirm those times ?
If they are consistent, then it's better uninstall the HD6450...right ?
Thanks for any help.
Asmodian
15th January 2015, 19:46
The 4850 was a fairly high end card (why you want it for games) while the HD6450 was very low end. MadVR uses the same hardware games do so it makes sense the 4850 runs madVR faster. Also users have reported that 13.2 runs madVR better than Catalyst 14.4, they are speaking about NNEDI3 performance but maybe the older driver helps here as well.
I recommend you uninstall the the HD6450.
ikakun
15th January 2015, 19:51
I've heard the new one seems to be better for movies (using madVR)...is that right ?
In using EVR with DXVA maybe, but not when using madVr.
kalston
16th January 2015, 08:59
If you enable g-sync with madVR the screen flickers constantly. It is not watchable.
It doesn't do that for me. It flickers for like 2 seconds (just like when starting a game) and then it's perfectly stable and not flickery at all.
But yes, it doesn't do anything since madVR is adjusting the framerate it sends based on the monitor refresh rate it reads...
Also, on my machine with two different GPUs (gtx 670 and gtx 970) it results in abnormal 100% GPU usage (only with video playback and madVR as a renderer) resulting in very low performance (insufficient for upscaling properly with jinc 3 for example). That's purely a G-Sync/madVR bug though, maybe it doesn't even happen with all driver versions. But it's not worth trying to fix it for reasons explained above.
egandt
17th January 2015, 20:17
I'm trying to Calman access the madTPG remotely, to generate a 3DLUT, however I can not get it to connect, I disabled all firewalls (source/destination) and even started the madHcCtrl to see if that helped, while I can access a local copy without issues, I can not access a remote copy, its as if it is not running or is not running on a port other than 127.0.0.1. I'm using the latest 87.13 release.
Any suggestions?
Thanks,
ERIC
Got it to work, you need to have madvrCtrl running and enable network access, I assume that madTPG communicates through madvrCtrl.
egandt
18th January 2015, 02:27
I found that enabling the 3Dlut help with the color and gamma, but introduces a large number of artifacts when watching shows with large amounts of constant flat color for instance Anime (Sky, faces, buildings, ...), and close ups of faces. For now I have disabled it while looking for the cause and a solution.
I used the default which contained about 1800 samples to create the 3Dlut, I'm thinking of trying with more samples, but also wanted to ask is this expected?
Thanks,
ERIC
vivan
18th January 2015, 06:20
but introduces a large number of artifacts when watching shows with large amounts of constant flat color for instance Anime (Sky, faces, buildings, ...), and close ups of faces.You mean banding? If yes, try debanding (processing -> artefact removal). If it helps then the problem is in source (it contains banding which is less noticeable without your 3Dlut).
huhn
18th January 2015, 11:37
I found that enabling the 3Dlut help with the color and gamma, but introduces a large number of artifacts when watching shows with large amounts of constant flat color for instance Anime (Sky, faces, buildings, ...), and close ups of faces. For now I have disabled it while looking for the cause and a solution.
I used the default which contained about 1800 samples to create the 3Dlut, I'm thinking of trying with more samples, but also wanted to ask is this expected?
Thanks,
ERIC
this should not happen (dithering is enabled right?). gamma & color is not used too right?
if you have a problem with your calibration results you may ask your question here:
: http://www.avsforum.com/forum/139-display-calibration/1471169-madvr-argyllcms.html
a8213711
18th January 2015, 12:50
what programs are running in the background when you try to use madVR?
the only potinal madVr bug i see here is that madVR stays at 60 hz and doesn't switch to 50 hz that's it. a simple screen from the OSD would have shown most of these issue.
refreshrate and FPS are 2 different things.
you just have to setup your TV correctly if you switch back from 60 HZ to something else like 50 hz and the picture looks strange that is a huge indicator you are using PC mode and your TV is leaving it.
In background: MPC-HC and WMC.
OSD: http://imgur.com/319PabC
I can't even understand if PC Mode is always enabled, or if it's only enabled (or actually disabled) when switching back from WMC.
Is here someone with a Samsung TV that can explain me how to see when this PC Mode is enabled?
egandt
18th January 2015, 15:59
Thanks for the responses, found something I was doing wrong, selected LCD and not Plasma for screen type. Also thanks for the link, however I'm using Calman for generating the 3Dlut, which is why we have seen the changes to the APIs lately. Using calman I can generate a 3Dlut directly and using thousands of data points, very cool actually.
I'm going to give it another try right now and see where I get.
Thanks,
ERIC
huhn
18th January 2015, 16:03
this picture can help
http://madshi.net/madVR/ChromaRes.png
watch it unscaled @ 100 % zoom. without PC mode you shouldn't be able to see the 4:4:4.
i guess something is blocking madVR from switching to 50 hz. try it without any other program in the background.
vomanci
18th January 2015, 17:11
In background: MPC-HC and WMC.
Is here someone with a Samsung TV that can explain me how to see when this PC Mode is enabled?
In Samsung TV's, PC mode is available only at 60hz and when you select the HDMI (or the input you are using) to be called PC or rename it PC. The picture above should clear things up.
StinDaWg
19th January 2015, 08:58
I'm trying to play a 1080i29.97 H.264 video with force film mode and output at 23hz. madVR says cadence is 4:4:4:2 but it's just continuously repeating frames and stuttering. Sometimes if I skip back in the file it will start playing smoothly even though it says frames are repeating. I can IVTC it with tfm().tdecimate() to 23.976 and encode it with x264 and it plays perfect. Any suggestions? Is this a limitation of madVR not being able to play 4:4:4:2 correctly?
huhn
19th January 2015, 11:31
I'm trying to play a 1080i29.97 H.264 video with force film mode and output at 23hz. madVR says cadence is 4:4:4:2 but it's just continuously repeating frames and stuttering. Sometimes if I skip back in the file it will start playing smoothly even though it says frames are repeating. I can IVTC it with tfm().tdecimate() to 23.976 and encode it with x264 and it plays perfect. Any suggestions? Is this a limitation of madVR not being able to play 4:4:4:2 correctly?
4:4:4:2 doesn't work AFAIK and this would be ~17.14 FPS something strange. to see what the files cadence is a ~30 sec sample is needed.
did you maybe mean 4:2:2:2 or 2:2:2:4? if yes this is already reported http://bugs.madshi.net/view.php?id=201
StinDaWg
19th January 2015, 14:59
Ya, I meant 4:2:2:2. Hmm, no action on that bug in 7 months. Hopefully it can be looked at eventually.
huhn
19th January 2015, 19:50
Ya, I meant 4:2:2:2. Hmm, no action on that bug in 7 months. Hopefully it can be looked at eventually.
he said something like it is not high on his "list" but sample are always welcome.
gebla
19th January 2015, 19:55
I am trying to set a 3dlut file to correct my display. I added my measurement values in the settings and pressed apply. Madvr asks if I want to downlaod and install yCMS now? I press yes download starts and madvr reports
Downloading yCMS failed.
How can I get yCMS installed? (windows 7 32bit)
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.