View Full Version : madVR - high quality video renderer (GPU assisted)
PhoeniXYZ
17th December 2009, 19:17
No joy on x64. madVR is only available in a 32-bit version, so you can only use it in the 32-bit version of MPC-HC, ffdshow, etc.
Thanks.
But now in the 32bit version of MPC I can select madVR but it is not used. I already tried disabling every output option of ffdshow other than YV12 but it didnt work.
flanger216
18th December 2009, 05:18
Thanks.
But now in the 32bit version of MPC I can select madVR but it is not used. I already tried disabling every output option of ffdshow other than YV12 but it didnt work.
I'd suggest giving us as much info as possible, on your video hardware and source media especially, as that statement is a tad broad for troubleshooting purposes.
PhoeniXYZ
18th December 2009, 12:36
The testfile were various mkv files with H.264 (x264) Video (720p) and DTS or AC3 Audio The hardware is a Mobility Radeon 4650 with Catalyst 9.11. Output per HDMI into an AVR and from that per HDMI to the television. OS is still Windows 7 x64.
namaiki
18th December 2009, 12:40
You are using 32-bit MPC-HC, and 32-bit FFDShow?
This should basically work with FFDShow default settings.. Make sure that Hardware Deinterlacing or anything like that is disabled, or just flush the settings and it should work.
When you say MadVR is not being used, you mean that you can't select it, or it is selected, but instead 'Video Renderer' is used?
PhoeniXYZ
18th December 2009, 12:41
You are using 32-bit MPC-HC, and 32-bit FFDShow?
Yes. In 64bit MPC-HC madVR is grayed out.
namaiki
18th December 2009, 12:48
But, FFDShow(or something) is definitely loading in MPC?
Check the 'pin info' for whatever video renderer is loading and search for "- Connection media type:" and under that is listed the colourspace.
PhoeniXYZ
18th December 2009, 12:51
But, FFDShow(or something) is definitely loading in MPC?
Check the 'pin info' for whatever video renderer is loading and search for "- Connection media type:" and under that is listed the colourspace.
Yes. The Filters loaded are the MPC-HC internal splitter, MPC-HC internal audio switcher, ffdshow audio and video decoder and the video and audio renderer.
Colorspace output by ffdshow is YV12.
This should basically work with FFDShow default settings.. Make sure that Hardware Deinterlacing or anything like that is disabled, or just flush the settings and it should work.
In the Catalyst Control Center I have everything in Avivo Video Section set to application settings.
What do you mean by flush the settings?
When you say MadVR is not being used, you mean that you can't select it, or it is selected, but instead 'Video Renderer' is used?
I can select it but standard video renderer is used instead.
namaiki
18th December 2009, 12:57
Colorspace output by ffdshow is YV12.
What do you mean by flush the settings?
That's what it reports under pin info?
Windows Registry Editor Version 5.00
[-HKEY_CURRENT_USER\Software\GNU\ffdshow]
- in a .reg file, which would delete all FFDShow Video Decoder settings.
PhoeniXYZ
18th December 2009, 13:09
That's what it reports under pin info?
Yes. Mediasubtype_YV12.
<e> deleting the ffdshow registry keys didnt work.
namaiki
18th December 2009, 13:14
Try select system default renderer in MPC.
PhoeniXYZ
18th December 2009, 15:37
Now the default renderer is used?
namaiki
18th December 2009, 15:42
Well, weird.. I thought the two might have switched around, like this guy who was having a problem running it on XP.
shadewither
18th December 2009, 16:57
How to use 3dlut in madvr?
I cannot find any settings for 3dlut except the enable/disable checkbox.
And no document either?
73ChargerFan
18th December 2009, 17:46
Yes. In 64bit MPC-HC madVR is grayed out.madVR works with 32-bit mpc-hc, not with the 64-bit version.
yesgrey
18th December 2009, 20:07
How to use 3dlut in madvr?
I cannot find any settings for 3dlut except the enable/disable checkbox.
And no document either?
There is a folder inside madVR's folder named cr3dlut. There you can find info about it.
leeperry
19th December 2009, 13:34
humm, KMP and its built-in MKV splitter can play 90' movies w/o a glitch on XP+Reclock@48Hz...mVR is so smooth! http://forum-images.hardware.fr/images/perso/fumble.gif
I've left "disable tearing fix" unchecked, but I've disabled "combined writing" in the windows display troubleshoot options(it's pointless nowadays anyway)...hope it's gonna last http://forum-images.hardware.fr/images/perso/zigg.gif
I can confirm that it really works like a treat, 90 mins in a row w/o any frame drop..goodness gracious! and 192kHz oversampling in Reclock sounds just as good as lossless to me(in bit-perfect KS) :cool:
Time to see if they fixed the CUDA initialization time in CoreAVC 2.0...and whether high bitrate h264 still hiccups in mVR.
joikd
19th December 2009, 23:02
I have quite a bit of stuttering with an ATI 5750 and Intel E5200. It's smooth when there isn't much movement. Do I need to upgrade one or both of these, or is the problem something else?
PhoeniXYZ
20th December 2009, 16:03
madVR works with 32-bit mpc-hc, not with the 64-bit version.
Yes... I know that...
leeperry
22nd December 2009, 13:44
it would appear that tearing still occurs w/ CoreAVC CUDA 2.0...OTOH, it's only a minor update and the problem seems to be on the mVR side.
namaiki
22nd December 2009, 14:10
it would appear that tearing still occurs w/ CoreAVC CUDA 2.0...OTOH, it's only a minor update and the problem seems to be on the mVR side.
How about if you use the CPU instead of CUDA?
I find that MadVR >> CUDA/DXVA
leeperry
22nd December 2009, 14:51
didn't try w/o CUDA, but in 1.95 only CUDA gave tearing(no tearing in HR)...prolly the same w/ 2.0, but if it's not for CUDA I prefer the DivX h264 decoder(its "low latency" option makes seeking very fast!)
namaiki
22nd December 2009, 15:08
I was using the DivX 7 H.264 decoder but I purchased CoreAVC 2.0 after hearing *somewhere* that DivX 7 has a possibility for non-bit perfect output in some *forgotten* scenario(not that I would notice, though). Well, and sometimes I need to change input levels to PC. :p
I used to care for CUDA, but now I know my graphics card is just way too weak to be pushing both video and video renderer. D:
Also, if I seek too much in MadVR, my media player(MPC-HC) will freeze up.
leeperry
22nd December 2009, 15:23
it usually freezes for me if I go windowed<>fullscreen a few times...it's like D3D exclusive in MPC, it learns you to stop messing around and watch the damn movie already :D
I leave h264 decoders in TV range, no levels problems here...well, except when the files were encoded in 0-255 or stuff like that.
namaiki
22nd December 2009, 15:35
OT
it usually freezes for me if I go windowed<>fullscreen a few times...it's like D3D exclusive in MPC, it learns you to stop messing around and watch the damn movie already :Dlol If only I could think like that..
<- has assigned Ctrl+Alt+Q to kill all instances of mpc-hc.exe, though, it never works when I want it to, and the [windows] shortcut dies (by itself?) every so often..
well, except when the files were encoded in 0-255 or stuff like that.
Yeah, I happen to have a few files like that.
I'll redo/convert them.. some day... well, actually I tried before, but some were VFR and went out of sync, and some others were CFR, but went out of sync anyways and besides, I'm a suck encoder with little time. D:
..oh well, random.
Scoty
23rd December 2009, 09:51
What is with a 64Bit Version? Can you make this please.
namaiki
23rd December 2009, 13:33
it usually freezes for me if I go windowed<>fullscreen a few times...
Funny this.. I tried Alt+Enter a few times, and then holding Alt+Enter, but it wouldn't freeze. Then I close MPC-HC, and then the screen freezes instantly (except for pointer) for about 5 mins..
leeperry
23rd December 2009, 14:52
oh yes, I've already encountered nasty freezes for several minutes that nothing could possibly stop...once w/ some beta nvidia drivers(that are getting worse by the hour when it comes to custom resolutions, I should prolly roll back to 185.x) and another time w/ the 195.x...exactly the same, I tried to close the player and major freeze! anyway, it's a beta and madshi said he'd improve stability at some point.
and about CoreAVC CUDA 2.0, small bitrate(<10mbit) files work just fine(only had tearing once), but for high bitrate 1080p there still seems to be some tearing happening from time to time.
iSeries
27th December 2009, 19:39
Hi,
I'm hoping someone can help me. I'm having terrible horizontal tearing about a quarter of the way up the screen when I set my TV refresh rate to 24hz. I don't get any tearing if I set the screen to 60hz, but then I get awful judder. When using EVR custom I don't get any tearing at 24hz. Is there any way I can get MadVR to work at 24hz? (XP SP3, ATI 4550).
Thunderbolt8
27th December 2009, 19:47
its a know problem and hopefully it gets fixed soon :P
Kazuya
27th December 2009, 20:32
No new release of madVR ? :)
ryrynz
27th December 2009, 21:52
Nope no new release yet, we know Madshi is working on one and that it's not far off.
iSeries
29th December 2009, 21:12
Hi,
Quick question - just wondered if its just me or if MadVR output levels are opposite to everything else?
leeperry
29th December 2009, 21:22
just wondered if its just me or if MadVR output levels are opposite to everything else?
in the bizzaro world yes! but madshi believes that's the other way around ;)
iSeries
29th December 2009, 21:52
So if I want to send limited RGB to my TV I select 0-255 in MadVR (with ATI 4550 also set to limited RGB)? Cos thats the way it seems to be!
namaiki
29th December 2009, 21:54
with ATI 4550 also set to limited RGB
That one doesn't have to change, if you're talking about overlay options.
iSeries
29th December 2009, 22:04
What I mean is, if I set my TV black level to 'Low' (which is limited range), and I set my ATI card to limited, with any other renderer I have to choose an output level of 16-235. With MadVR however, it seems I have to set 0-255 to get the same result?
leeperry
29th December 2009, 22:06
HR talks about the input when it allows you to choose the levels, and mVR about the output.
if you output 0-255 from mVR, and then set your ATI card to TV range, you should be fine as your drivers will convert from PC to TV.
73ChargerFan
30th December 2009, 07:26
if you output 0-255 from mVR, and then set your ATI card to TV range, you should be fine as your drivers will convert from PC to TV.
I thought that everything in the chain should be set the same way, all TV or all Full. At each stage, if output is set to TV then it clips off the top and bottom, not rescales.
Andy o
30th December 2009, 08:13
With ATI, I have never seen that option (RGB full/limited) work in CCC. It just outputs the same. With the 5000 cards only there is a new option in the AVIVO video settings for it, which does work.
lmaolmao
30th December 2009, 09:51
is it known if non mod8 resolutions dont work with coreavc? as thats the problem i'm having.
With MPCHC:
internal decoder - OK
ffdshow - OK
coreavc - CRASH
With Zoomplayer:
ffdshow - CRASH
coreavc - CRASH
one fix i have got is to have coreavc decode, and ffdshow resize to the next mod8 resolution, but I guess that kind of defeats the point of letting madVR do the resizing. Zoom player, although having the more crashy implementation can use subtitles with madVR, and has a better interface when using a remote control (has a nice seekbar for proper seeking and subtitle/audio selection).
edit2:
appears to be internal subtitles require mod8 for it to play. but without subtitles, it will play without mod8 resize, but still needs to go through ffdshows "raw processing" even with it all turned off.
namaiki
30th December 2009, 10:00
I just played a 1276x716 file just fine just then, however if I have VSFilter enabled, it will crash.
On EVR with VSFilter, 1276x716 will open as 1280x716 with a black bar down the right side of the video; MadVR will crash.
On EVR without VSFilter 1276x716 will open as 1276x716; MadVR will open as 1280x716, with black bar on right and left.
leeperry
30th December 2009, 12:20
I thought that everything in the chain should be set the same way, all TV or all Full. At each stage, if output is set to TV then it clips off the top and bottom, not rescales.
well, I've moved to the green side of the force a while ago, as the GF9600 was noticeably sharper than the HD3850 on my HC3100 DLP pj(some other ppl noticed the exact same thing on both HC1100/HC3100)...but AFAIR, going "RGB limited" in the ATi drivers does a levels shrink down from PC to TV.
iSeries
30th December 2009, 22:39
Setting either Limited or Full in CCC defintely makes a difference for my set up. I've settled for going full RGB all the way now, doesn't make sense to have the card shrink back to limited if I can just set my TV black level to full.
As an aside - I was getting terrible horizontal tearing with MadVR at 24hz on XP. I've just played around with Windows 7 again and managed to get MadVR playing perfectly with no tearing - by disabling the tearing fix and changing the vsync option in CCC to 'Always on - unless application specifies'.
THX-UltraII
31st December 2009, 09:04
Does MadVR still not supports subtitles?
Andy o
31st December 2009, 09:41
You can have subs with directvobsub, but not with the internal sub renderer. This works for most things, except bluray rip subs.
edison
31st December 2009, 11:34
The build-in sub renderer of Potplayer does support madVR.
lmaolmao
2nd January 2010, 10:45
well, I've moved to the green side of the force a while ago, as the GF9600 was noticeably sharper than the HD3850 on my HC3100 DLP pj(some other ppl noticed the exact same thing on both HC1100/HC3100)...but AFAIR, going "RGB limited" in the ATi drivers does a levels shrink down from PC to TV.
i'm sure that said red before!
leeperry
3rd January 2010, 02:44
i'm sure that said red before!
whaddayamean http://t3.gstatic.com/images?q=tbn:jbnLRUtO6drlaM
BTW, I think it'd be a lot clearer if the config panel simply said :
* keep levels untouched
* do TV>PC conversion
because some ppl input 0-255 video(whatever due to post-processing in ffdshow like me, or to FRAPS videos), and that'd be far less confusing...as most of the other renderers talk about levels from the input side, at least that'd be clear like this.
ryrynz
3rd January 2010, 04:13
Madshi, may I ask what your goals are for the next version and or future versions? Thanks.
pirlouy
3rd January 2010, 13:52
Stability notably:
http://forum.doom9.org/showthread.php?p=1333525#post1333525
http://forum.doom9.org/showthread.php?p=1333612#post1333612
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.