View Full Version : madVR - high quality video renderer (GPU assisted)
namaiki
2nd April 2010, 14:18
I'm running Windows 7 64-bit. It's a laptop with a GeForce 9600M GT.
In my experience, most 19x forceware don't work, except for 191.97 recently discovered :p, so I'm was actually using ForceWare 186.84 until some time ago.
Razoola
2nd April 2010, 16:16
That's very odd... WHich OS are you running?
I'm using my GF 8600GT with 196.21 and it works fine. In both XP x64 and W7 x64.
Im using win 7 x64. With 196.21 drivers and all I get is a player hang when I try to play a video the madVR renderer. This is in MPC-HC and Zoom player 7.
yesgrey
2nd April 2010, 20:45
Have you installed/updated DirectX 9?
I don't remember quite well, but I think I needed to install it in W7...
leeperry
2nd April 2010, 20:54
195.62 works fine here, apparently problems arise >196.x
Razoola
2nd April 2010, 22:31
Have you installed/updated DirectX 9?
I don't remember quite well, but I think I needed to install it in W7...
I ran the DX9 websetup after I first installed win7 and again in februray when the latest update for DX9 was released. I have just ran the update again now and it says my DX9 is up to date.
I still have the same problem as many others. If you have it working then maybe this is related to multi GPU cards or systems. I have a gtx295 and gt240 so I have 3 cores, maybe madVR is trying to output video on a core that is not displaying video (not active). I say this because the hang is the same as what happends in MPC-HC when you choose a D3D9 render device which is not the one that displays video.
peter0328
3rd April 2010, 01:29
Anyone know if this is still being developed?
I really don't want to downgrade my driver since I had Quad SLI with the 295s and when I do 3D gaming in the (hopefully near) future I will need the newer drivers for compatibility.
Can anyone else who has Quad SLI and Win 7 x64 chime in with drivers that work for them though?
yesgrey
3rd April 2010, 01:41
If you have it working then maybe this is related to multi GPU cards or systems.
Yes, that might be the problem... Have you tried disabling PhysX? I have it disabled.
Anyone know if this is still being developed?
Yes it is.
namaiki
3rd April 2010, 01:44
195.62 works fine here, apparently problems arise >196.x
There's a 195.62 driver for my laptop, so this I will try. I don't recall it working though.
Driver issue could probably be intertwined with GPU model.
cyberlolo
3rd April 2010, 01:47
yesgrey, are you still developing cr3dlut? If so, when do you expect to release a new version?
Thanks!
leeperry
3rd April 2010, 02:13
I'm really dying for a D3D exclusive mode, to end all those "VSYNC catch" nonsense...patience is indeed a virtue http://forum-images.hardware.fr/images/perso/arcadiaz.gif
yesgrey
3rd April 2010, 02:24
yesgrey, are you still developing cr3dlut? If so, when do you expect to release a new version?
Thanks!
I hope to be able to say something about this in one or two weeks...
Razoola
3rd April 2010, 09:28
Yes, that might be the problem... Have you tried disabling PhysX? I have it disabled.
I get the same problem with PhysX disabled. I tried disabling one of the cores on the gtx295 but for some reason I could not and both were disabled and windows look to put the display into some kind of compatability mode (no aero). When the system was like this madVR started but I see a red D3D9 no render device error.
cyberlolo
3rd April 2010, 11:30
I hope to be able to say something about this in one or two weeks...
Ok, that's great news. We'll be waiting for it. Thank you for your work!
:thanks:
namaiki
3rd April 2010, 11:50
195.62 works fine here, apparently problems arise >196.x
I tried Forceware 195.62 on my laptop which has a 9600M GT + Windows 7 64-bit and MadVR hung on startup. Really weird.
yesgrey
3rd April 2010, 14:21
windows look to put the display into some kind of compatability mode (no aero).
Have you tried disabling aero? I used the Windows Classic style, hence no aero enabled.
Razoola
3rd April 2010, 14:37
Have you tried disabling aero? I used the Windows Classic style, hence no aero enabled.
Just tried, have the same problem still, player hang on trying to play video.
yesgrey
3rd April 2010, 18:33
Just tried, have the same problem still, player hang on trying to play video.
What H264 decoder are you using? If it's CoreAVC try with ffdshow.
Razoola
4th April 2010, 07:54
What H264 decoder are you using? If it's CoreAVC try with ffdshow.
Im using MPC-HC internal decoders. With Zoomplayer Im already using ffdshow (tried both DVVA and ff-mpeg-mt) yet the issue still happens.
Looking back through this thread there are many many people with nvidia cards in the same boat as myself and namaiki. Maybe its more a case of something on your PC that is making it work with the newer nvidia drivers.
yesgrey
4th April 2010, 12:23
Looking back through this thread there are many many people with nvidia cards in the same boat as myself and namaiki. Maybe its more a case of something on your PC that is making it work with the newer nvidia drivers.
The only thing that seems to be different is my card, an old 8600GT...
Are you sure that you're feeding YV12 to madVR? Some decoders output in YUY2 or in NV12, but madVR only supports YV12.
Let's try one last thing: tell me exactly your setup with mpc-hc so I can be able to test it and see if it works with me...
Razoola
4th April 2010, 21:06
The only thing that seems to be different is my card, an old 8600GT...
Are you sure that you're feeding YV12 to madVR? Some decoders output in YUY2 or in NV12, but madVR only supports YV12.
Let's try one last thing: tell me exactly your setup with mpc-hc so I can be able to test it and see if it works with me...
I'm simply trying MPC-HC with its own internal encoders. There is no option to choose between RGB etc when the madVR output is selected that I can see. Other than that Im using reclock.
yesgrey
5th April 2010, 00:34
I'm simply trying MPC-HC with its own internal encoders.
Disable mpc-hc internal decoders, and try with ffdshow checking only YV12 in its output tab.
Also, are you using the latest Haali splitter? If yes, try disabling its workaround for bypassing the microsoft avc decoder.
Razoola
5th April 2010, 07:59
Disable mpc-hc internal decoders, and try with ffdshow checking only YV12 in its output tab.
Also, are you using the latest Haali splitter? If yes, try disabling its workaround for bypassing the microsoft avc decoder.
Tried, I get the same freeze still. What I actually get is reclock, haali and ffdshow video and audio icons in the taskbar and then freeze.
Im using the 27.03.10 build of haali but im not sure what you mean by 'disabling its workaround for bypassing the microsoft avc decoder'. If you mean disabling the gabest's splitter, I did that.
Raz
namaiki
5th April 2010, 08:10
Razoola: Try install some 18x forceware drivers.
Razoola
5th April 2010, 10:41
Razoola: Try install some 18x forceware drivers.
Yes it works fine with 186.18. The problem is that driver does not support my gt240, even modding the driver inf I cannot get the gt240 working.
The brings it full circle back to a nvidia driver situation amd me on 196.21.
namaiki
5th April 2010, 10:44
Maybe you can try 191.05 or 191.07 old drivers.
yesgrey
5th April 2010, 11:03
Im using the 27.03.10 build of haali but im not sure what you mean by 'disabling its workaround for bypassing the microsoft avc decoder'. If you mean disabling the gabest's splitter, I did that.
Haali splitter creates a custom FourCC as a workaround. I don't remember the exact name of it, and I can't tell you because I don't have that version installed. I'm still using the 2009-01-10 build because it's the last that works with WVC1 interlaced files.
You can also try to install that version of Haali...
Razoola
5th April 2010, 11:38
Maybe you can try 191.05 or 191.07 old drivers.
195.62 is the first driver to correctly support the gt240. It dosent work with that driver.
Razoola
5th April 2010, 11:40
Haali splitter creates a custom FourCC as a workaround. I don't remember the exact name of it, and I can't tell you because I don't have that version installed. I'm still using the 2009-01-10 build because it's the last that works with WVC1 interlaced files.
You can also try to install that version of Haali...
I have tried that version now. Still get the problem.
namaiki
5th April 2010, 11:41
195.62 is the first driver to correctly support the gt240. It dosent work with that driver.
As far as I can tell, those two drivers support your graphics card.
Supported products
GeForce 200 series:
GTX 295, G210, GTX 275, GTX 280, GTX 285, GTS 240, GTX 260, GTS 250, GT 220
and more..
Did you try the driver?
edit: hmm.. unless you meant it installs but doesn't correctly work. :p
Razoola
5th April 2010, 11:51
As far as I can tell, those two drivers support your graphics card.
Did you try the driver?
edit: hmm.. unless you meant it installs but doesn't correctly work. :p
Neither support the gt 240, only the 240gts which is a different card. I'll edit the ini and give the 191.07 a try now though.
Razoola
5th April 2010, 13:16
Ok, I can get my GT240 with my GTX295 plus madVR working with the 191.07 drivers. It did take a little inf mod though to add the GT240 to the driver list. The next official driver release of 195.62 (which is the first driver to support the GT240) I cannot get working at all with madVR.
So in my case the driver issue that breaks madVR happens between these two WHQL driver releases.
Whats also nice is the fact that I had a minor glitch issue over nvidia HDMI which caused the bottom 10th of the screen to flash black few seconds after changing resolution etc. That seems to have fixed itsself with these older drivers. I think I'll be keeping these installed for some time.
namaiki
5th April 2010, 13:45
ooh brilliant :D
Razoola
5th April 2010, 14:36
ooh brilliant :D
Yup, I'm really happy. I just wish I knew how yesgrey is getting 196.21 to work. Would also be nice if MPC-HC's disable desktop composition (aero) option worked with madVR (or haali for that matter).
namaiki
5th April 2010, 14:44
Even more for me, since yesgrey has a GeForce 8600GT and I have a 9600M GT, which are very similar in specifications as far as I can tell. :p
My setup:
9600M GT
Windows 7 64-bit
Media Player Classic Homecinema 32-bit svn1281
Haali Media Splitter
Reclock (latest) - WASAPI
ffdshow audio
ffdshow video or CoreAVC 2.0 (CUDA video acceleration disabled)
VSFilter, sometimes
MadVR v11 (I think v9 will run on the newer forceware versions, but it lacks the queue and I get stuttery/jumpy video playback)
yesgrey, could you post up your setup? :3
yesgrey
5th April 2010, 17:51
Yup, I'm really happy. I just wish I knew how yesgrey is getting 196.21 to work.
Sorry, but I don't know what's happening... I'm just glad that it works for me. I think I will not rush up to upgrade my GPU...;)
yesgrey, could you post up your setup?
My setup:
8600 GT - drivers 197.13 (I update always, so all previous drivers worked too)
Windows XP x64 SP2
Media Player Classic Homecinema 32-bit 1.3.1771.0
Haali Media Splitter 2009-01-10
Reclock 1.8.6.7 - Kernel Streaming
ffdshow 3336 or madFlac audio
ffdshow 3336 video or CoreAVC 2.0 (CUDA video acceleration disabled)
MadVR v11 using 3DLUT
Now I'm running XP x64 because my W7 x64 RC1 has expired and I preferred not to buy W7 yet. With W7 it worked ok too. I used 195.62 drivers.
I only had a small problem with W7, which was one of the reasons to go back to XP. When using my projector I got some tearing. It was a strange thing, because the exact same timings give me a perfect image with XP...
namaiki
5th April 2010, 17:55
mm I get tearing on MadVR when I have Aero disabled. I didn't notice until I watched some random scenery pans.
damn, I thought you were going to have some exotic setup. XD
edit: Windows XP 64-bit is a bit wild though. d;
yesgrey
5th April 2010, 18:19
mm I get tearing on MadVR when I have Aero disabled. I didn't notice until I watched some random scenery pans.
I got tearing only when using my projector (1360x768@48Hz), with or without aero did not matter. Though, when I used my CRT monitor (1280x960@72) I got no tearing, no matter if aero was enabled or not, hence my conclusion that it would've been due to the timings used...
damn, I thought you were going to have some exotic setup. XD
edit: Windows XP 64-bit is a bit wild though. d;
It's great! Previously I used XP SP3 32, but after working with W7 x64 I did not want to return to 32bit, I wanted to use all my 4GB of RAM, and I don't regret the decision. As a bonus, I keep my favorite Windows GUI (Windows 2000).:)
Grmpf
5th April 2010, 18:32
I still have the 23.976+24.000hz tearing problem with madVR (i am not the only one, there were others here in this thread and on other boards aswell) - so is there a chance for a fixed madVR version anytime soon ? Yes i know madshi has a "real" live outside of ths board, i just want to know wether he already knows what causes the problem and how to fix it inside madVR, so that i know the next version may/will fix it.
Its basicly the only thing that holds me back from fulltime using madVR (and boy i want to use it), i can't easily setup different renderers for different hz (50hz + 59.94hz work perfect with madVR) in zoomplayer, so i am stuck without madVR - i can't use 48/72hz as a workaround either, my projector does only support 24/50/60hz.
If i can be of any help (testing versions, what ever) - please just contact me.
System: CPU:Q9550 + ATi 4770 (Win XP SP3/Zoomplayer/CoreAVC/ffdshow) -> JVC DLA HD100/RS2
Razoola
5th April 2010, 19:35
Now I'm running XP x64 because my W7 x64 RC1 has expired and I preferred not to buy W7 yet. With W7 it worked ok too. I used 195.62 drivers.
I only had a small problem with W7, which was one of the reasons to go back to XP. When using my projector I got some tearing. It was a strange thing, because the exact same timings give me a perfect image with XP...
That could be it then as you were not using the final W7 x64 which I take namaiki is and I can confirm I am also (x64 ultimate).
yesgrey
5th April 2010, 19:56
That could be it then as you were not using the final W7 x64 which I take namaiki is and I can confirm I am also (x64 ultimate).
When I find some free time I will give it a try to see what happens...
janos666
6th April 2010, 19:22
Sorry, but I don't know what's happening... I'm just glad that it works for me. I think I will not rush up to upgrade my GPU...;)
I can use MadVR on my desktop PC with a Radeon HD5850 but I can not use it on my notebook. I have the same softwares (Win7 x64, FFDShow and MPC-HC builds with the same settings...) on both machines. Both of them are based on the Intel Core2 platform. The notebook has a mobile 8600GT (it has the same GPU as the desktop SKU).
So, I wonder how you can use MadVR with any new nvidia drivers. :cool:
Do you change some specific option in advanced driver settings? Do you make some uncommon changes in FFDShow or MPC-HC config? Are you the next Jesus (:D:D), or...?
Razoola
6th April 2010, 19:35
I can use MadVR on my desktop PC with a Radeon HD5850 but I can not use it on my notebook. I have the same softwares (Win7 x64, FFDShow and MPC-HC builds with the same settings...) on both machines. Both of them are based on the Intel Core2 platform. The notebook has a mobile 8600GT (it has the same GPU as the desktop SKU).
So, I wonder how you can use MadVR with any new nvidia drivers. :cool:
Do you change some specific option in advanced driver settings? Do you make some uncommon changes in FFDShow or MPC-HC config? Are you the next Jesus (:D:D), or...?
You can't, you will need to use older drivers. 191.07 is the oldest standard driver that worked for me (non mobile gfx card) but namaiki mentioned the mobile drivers 191.97 worked for him with his mobile cart.
yesgrey
6th April 2010, 21:57
So, I wonder how you can use MadVR with any new nvidia drivers.
The only "BIG" difference with my setups is that I've only used W7 x64 RC1, so it might be some problem in the retail W7... I will try the retail as soon as I have some free time. Stay tuned...
yesgrey
8th April 2010, 19:29
OK, I've found some time and I tried the W7 x64 ultimate retail, and madVR is working with my GF 8600GT and 197.13 drivers.
First, it didn't, but after some tries it did. Though, I still have a small problem with it. If I stop the movie, or if I quit mpc-hc without the video ending, my system becomes very slow with the cpu usage almost at 100%. If the video plays completelly until it reaches the end, no problem.
Now what everybody would like to know... How?
Well, I don't know for sure...
First, I tried it right after install W7. It didn't work. I only got a black screen.
Then, I installed DirectX, and it still did not work.
Finally, I updated W7 via Windows update, and I don't remember if after that it started working or not... I also changed some settings in madVR "settings.ini", but then I reverted them back and it still worked, so I can't say for sure if it was that.
I also used the Classic Theme, disabled hibernation, superfetch, and the page file.
I don't know if you will need all these changes, though. I only set it up like I usually use it.
I hope this helps...
Razoola
8th April 2010, 22:20
OK, I've found some time and I tried the W7 x64 ultimate retail, and madVR is working with my GF 8600GT and 197.13 drivers.
First, it didn't, but after some tries it did. Though, I still have a small problem with it. If I stop the movie, or if I quit mpc-hc without the video ending, my system becomes very slow with the cpu usage almost at 100%. If the video plays completelly until it reaches the end, no problem.
Now what everybody would like to know... How?
Well, I don't know for sure...
First, I tried it right after install W7. It didn't work. I only got a black screen.
Then, I installed DirectX, and it still did not work.
Finally, I updated W7 via Windows update, and I don't remember if after that it started working or not... I also changed some settings in madVR "settings.ini", but then I reverted them back and it still worked, so I can't say for sure if it was that.
I also used the Classic Theme, disabled hibernation, superfetch, and the page file.
I don't know if you will need all these changes, though. I only set it up like I usually use it.
I hope this helps...
Did you change any settings in the nvidia driver?
namaiki
9th April 2010, 01:19
I still have a small problem with it. If I stop the movie, or if I quit mpc-hc without the video ending, my system becomes very slow with the cpu usage almost at 100%.
Same thing for me, but I can close the application fine if I pause it first (and wait 5 secs or so) or via "taskkill /F /IM mpc-hc.exe /T" ..cough. :p
yesgrey
9th April 2010, 01:31
Did you change any settings in the nvidia driver?
Yes, what I usually use, but then I restored the default ones just to be sure and it also worked, so the problem is not in any drivers settings...
Same thing for me, but I can close the application fine if I pause it first (and wait 5 secs or so) or via "taskkill /F /IM mpc-hc.exe /T" ..cough. :p
So, can you watch movies? I thought you also only got a black screen...
namaiki
9th April 2010, 01:38
So, can you watch movies? I thought you also only got a black screen...
I can watch movies and I have been using MadVR on a daily basis. I get a black screen somewhere around above ForceWare 191, and much more easily if I have Aero disabled. I've always had the above freezing/high CPU problem (or similar) in my 'working' configuration. I'm pretty sure I've posted about it before.
I'm currently again using ForceWare 186.84
yesgrey
9th April 2010, 02:06
I get a black screen somewhere around above ForceWare 191, and much more easily if I have Aero disabled.
Sorry, but after so much posts it's a bit hard to remember all of them...
So, you cannot use nothing above 191, but I was able to get 197.13 to work. Now if I just knew how!...
DigitalLF
11th April 2010, 19:33
Yesgray: sorry for missing out on stuff... but are you talking a incompability with MadVR or cr3dlut when it comes to never nvidia drivers then 191?
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.