View Full Version : madVR - high quality video renderer (GPU assisted)
ryrynz
28th July 2018, 00:19
I’m using it with anime content only. It gets rid of the poor motion of some 24p content without adding the soap opera effect.
I don't like the loss of motion resolution which is noticeable to me just to improve panning so I keep frame creation on low instead which is a suitable trade off.
Clammerz
28th July 2018, 06:57
I thought of overheating, but I don't think: without madVR I get no crash at all with the same room temp for weeks.
Temperature isn't the only symptom of failing hardware. It could be that the silicon is already failing in some ways that only certain workflows use.
Try using very demanding graphics benchmarking software like Furmark, or like Asmodian suggested "Heaven" or even Superposition (https://benchmark.unigine.com/superposition)
franketto
28th July 2018, 07:55
Those are really low temps for a GPU at 80% load, do you have aftermarket cooling or a model with extreme cooling? I notice you quote CPU max temps, which seem like max values you might expect given those average temps. Are you sure those are your GPU temps?
How about other GPU heavy loads, maybe Heaven (https://benchmark.unigine.com/heaven)?
It's the stock i7 dissipator, I used GPU-Z to read GPU temp and SpeedFan to read CPU Temp. Temporarily I have an open case, maybe this contribute to lower the temp, as the hot air goes directly towards the ceiling.
Anyway I'll try your suggestions on heaven or furmark and I'll tell you.
silicon is already failing in some ways that only certain workflows use.
But, suppose it's true, when using madVR should be always put to stress, instead I get a BOD only let's say one time in 2 weeks (and also with very poor demanding videos like an old SD), all the other videos play fine.
franketto
28th July 2018, 08:17
I'm sorry, the previous AVG GPU temp was not precise because it mixed with lower temp of previous 1080 and SD videos...
Now I did one longer test only 4k and these are the results:
2160p GPU 81%: AVG=59,6° MAX=70° CPU: MAX(by eye)=64°
franketto
28th July 2018, 08:41
After 15' furmark test, I have these stable values:
GPU 100% AVG=64,4° MAX=72°
Should I continue or is this ok to say there is no HW cooling problems?
huhn
28th July 2018, 11:43
check the event manager to see what is causing this.
i have no clue why someone is limiting this to the GPU.
you can try the newest windows version together with the newest driver or even a fresh OS.
franketto
28th July 2018, 11:53
What exactly should I do in the event manager? I have never used it...
Clammerz
28th July 2018, 15:46
What exactly should I do in the event manager? I have never used it...
Event Viewer will show the BugCheck (blue screen) but also other events around the same time. Perhaps there is something else going on.
Unlikely though as that particular bugcheck should only be caused by bad hardware or bad drivers.
Have you tried other driver versions?
Unfortunately intermittent issues such as these are the hardest to diagnose when they only show up after a few weeks at a time. If you can find a temporary replacement CPU to use it will at least rule out if the GPU is at fault or not.
el Filou
28th July 2018, 17:25
Agree with huhn, if it's crashing more often when seeking or fast-forwarding then I would look more for a software or driver issue.
Edit: maybe try a test with DXVA Checker benchmark, playback performance mode, selecting your screen definition as display definition, with many loops. That will stress the video decode block (and the GPU a little bit)
franketto
28th July 2018, 19:35
So, for now I looked at "Reliability Monitor"
and I found this "Windows" Hardware error:
Nome evento problema: LiveKernelEvent
Codice: 141
Parametro 1: ffffac0fd3ead4a0
Parametro 2: fffff8084e7d57e0
Parametro 3: 0
Parametro 4: 395c
Versione sistema operativo: 10_0_17134
Service Pack: 0_0
Prodotto: 256_1
Versione SO: 10.0.17134.2.0.0.256.48
ID impostazioni locali: 1040
Followed by 9x DesktopWindowManager errors:
Origine
Desktop Window Manager
Riepilogo
Ha smesso di funzionare
Descrizione
Percorso dell'applicazione che ha generato l'errore: C:\Windows\System32\dwm.exe
Firma del problema
Nome evento problema: APPCRASH
Nome applicazione: dwm.exe
Versione applicazione: 10.0.17134.1
Timestamp applicazione: f5178e97
Nome modulo con errori: d2d1.dll
Versione modulo con errori: 10.0.17134.112
Timestamp modulo con errori: 65837bda
Codice eccezione: c0000005
Offset eccezione: 00000000000eaa44
Versione SO: 10.0.17134.2.0.0.256.48
ID impostazioni locali: 1040
Informazioni aggiuntive 1: da31
Ulteriori informazioni 2: da311bbfa44fbd893fa24c18ea3cb53a
Ulteriori informazioni 3: 7b74
Ulteriori informazioni 4: 7b743590ad6b9157ad1f1e27362006d9
Ulteriori informazioni sul problema
ID bucket: 2e851f1fecb62a46778a1fa4eaa778a3 (1696203002830354595)"
Timestamp applicazione: f5178e97
Nome modulo con errori: d2d1.dll
Versione modulo con errori: 10.0.17134.112
Timestamp modulo con errori: 65837bda
Codice eccezione: c0000005
Offset eccezione: 00000000000ea0fc
Versione SO: 10.0.17134.2.0.0.256.48
ID impostazioni locali: 1040
Informazioni aggiuntive 1: 0a51
Ulteriori informazioni 2: 0a51e9079ac7b4ef18dd6a88476bbc68
Ulteriori informazioni 3: 2acd
Ulteriori informazioni 4: 2acd14112c3488803847dde3fd4c4488
Ulteriori informazioni sul problema
ID bucket: bd03157bd87841582a40fa780bfe0201 (1891787236999823873)
and so on.
Then Explorer Crash, always on d2d1.dll,
then another Hardware Error "Windows":
Nome evento problema: LiveKernelEvent
Codice: 141
Parametro 1: ffffac0fd3ead4a0
Parametro 2: fffff8084e7d57e0
Parametro 3: 0
Parametro 4: 395c
Versione sistema operativo: 10_0_17134
Service Pack: 0_0
Prodotto: 256_1
Versione SO: 10.0.17134.2.0.0.256.48
ID impostazioni locali: 1040
Then again Explorer.exe stop working:
Nome evento problema: APPCRASH
Nome applicazione: explorer.exe
Versione applicazione: 10.0.17134.165
Timestamp applicazione: 4031a9f8
Nome modulo con errori: twinui.pcshell.dll
Versione modulo con errori: 10.0.17134.165
Timestamp modulo con errori: 350701a7
Codice eccezione: 80270233
Offset eccezione: 0000000000306063
Versione SO: 10.0.17134.2.0.0.256.48
ID impostazioni locali: 1040
Informazioni aggiuntive 1: 5c88
Ulteriori informazioni 2: 5c880f455e72d48ff2d252df01593dd2
Ulteriori informazioni 3: 7ddc
Ulteriori informazioni 4: 7ddc2dbaaa8270b132e584817378c7fd
Ulteriori informazioni sul problema
ID bucket: 5f78eab1a62fdc63368baa245de5a632 (1624579163768071730)
Last: Wacom tablet stopped working, and overall crash (I don't remember if here I got also BSOD: sometimes I got it, sometimes I got a general freeze with black screen frozen, so I must press power button to force the restart).
I don't know if this can be useful to detect the problem...
Now, I'll look to System Events and I'll tell you what I find.
franketto
28th July 2018, 20:15
So, in the Events of the last 3 months, I found out 9 critical errors, but only one BSOD with the hex code 119 Video_scheduler as I wrote before.
And I know of this BSOD in this date because I did the pic of it :), I'll post the log on the next post.
Anyway, the non-BSOD event, the same I found in Reliability Monitor, starts with:
the igfx driver stops working:
- Provider
[ Name] Display
- EventID 4101
[ Qualifiers] 0
Level 3
Task 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2018-07-15T20:14:39.635676800Z
EventRecordID 10355
Channel System
Followed by 17x Warnings Win32k 263 err code, of "pointing device", not having info on connected monitor.
Provider
[ Name] Win32k
- EventID 263
[ Qualifiers] 32768
Level 3
Task 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2018-07-15T20:14:51.254358500Z
EventRecordID 10356
Channel System
Then a warning not been able to start again the video driver.
Provider
[ Name] Display
- EventID 4115
[ Qualifiers] 0
Level 3
Task 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2018-07-15T20:14:55.891991800Z
EventRecordID 10373
Channel System
Then 12x Error of Service Control manager, 7031 Err code,
service OneSyncSvc_2f064 blocked abruptely, reboot it in 10000ms.
Provider
[ Name] Service Control Manager
[ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
[ EventSourceName] Service Control Manager
- EventID 7031
[ Qualifiers] 49152
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x8080000000000000
- TimeCreated
[ SystemTime] 2018-07-15T20:15:05.786066400Z
EventRecordID 10375
Correlation
- Execution
[ ProcessID] 988
[ ThreadID] 18112
Channel System
EventData
param1 OneSyncSvc_2f064
param2 1
param3 10000
param4 1
param5 Riavvia il servizio
4F006E006500530079006E0063005300760063005F00320066003000360034000000
Then:
PimIndexMaintenanceSvc_2f064
UnistoreSvc_2f064
UserDataSvc_2f064
CDPUserSvc_2f064
WpnUserService_2f064
followed by timeout of the services blocked that don't reboot.
and finally... the crash-freezing.
franketto
28th July 2018, 20:16
Instead the BSOD one has these:
3x Warning Kernel-PnP:
cannot load driver \Driver\VMSP for the device ROOT\VMS_VSMP\0000
then for ROOT\VMS_VSMP\0001 and ROOT\VMS_VSMP\0002
Provider
[ Name] Microsoft-Windows-Kernel-PnP
[ Guid] {9C205A39-1250-487D-ABD7-E831C6290539}
EventID 219
Version 0
Level 3
Task 212
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2018-06-15T11:57:47.536750800Z
EventRecordID 6018
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 420
Channel System
- Security
[ UserID] S-1-5-18
- EventData
DriverNameLength 18
DriverName ROOT\VMS_VSMP\0000
Status 3221226092
FailureNameLength 12
FailureName \Driver\VMSP
Version 0
Then the Warning of pointing device not knows the monitor,
then an error Hyper-V-VmSwitch:
Failed to get Device VlanID Regkey for Physical NIC /DEVICE/{3E39B7FB-8071-4D58-A3CE-E6F29F1786E6}. vSwitch will be created on this Physical NIC without VlanID being inherited by HostVNic. Status = can't find object name.
Then another Warning of pointing device not knows the monitor,
Then again 4x Errors Hyper-V-VmSwitch:
-) The operation 'Get Info' failed on nic 37044452-FBC8-4E5B-B8BD-D5B3060C51F5 (Friendly Name: ). Status = Parametro non valido passato ad un servizio o ad una funzione..
-) The operation 'Get Info' failed on nic 37044452-FBC8-4E5B-B8BD-D5B3060C51F5 (Friendly Name: ). Status = Parametro non valido passato ad un servizio o ad una funzione..
-) Failed to connect NIC 37044452-FBC8-4E5B-B8BD-D5B3060C51F5 (Friendly Name: Opzione predefi) to port (Friendly Name: ) on switch C08CB7B8-9B3C-408E-8E30-5E16A3AEB444 (Friendly Name: Opzione predefinita), status = Impossibile trovare il nome dell'oggetto..
-) Failed to enable miniport NIC 37044452-FBC8-4E5B-B8BD-D5B3060C51F5 (Friendly Name: Opzione predefi), status = Impossibile trovare il nome dell'oggetto..
And finally the BugCheck:
Il computer è stato riavviato da un controllo errori. Controllo errori: 0x00000119 (0x0000000000100000, 0x0000000000000001, 0x0000000000000000, 0xffffe00a4b512000).
I dettagli sono stati salvati in: C:\WINDOWS\MEMORY.DMP. ID segnalazione: 77ea78e5-3300-41b2-887c-6fef0cb21c72.
Sadly I have not looked at the memory.dmp and I don't find it now...
So, that's all, let me know if you have some ideas or request some more details of these events and I'll post them.
Thank you a lot fot the patience and the support, I'm really upset with these crashes that don't let me use madVR!
franketto
28th July 2018, 20:17
Unlikely though as that particular bugcheck should only be caused by bad hardware or bad drivers.
Have you tried other driver versions?
Unfortunately intermittent issues such as these are the hardest to diagnose when they only show up after a few weeks at a time. If you can find a temporary replacement CPU to use it will at least rule out if the GPU is at fault or not.
No, I haven't tried any other drivers apart W10 automatic updates.
I cannot use another CPU...
franketto
28th July 2018, 20:19
I'll try an intense DXVA checker, but I see it does not use madVR as a renderer, so I think it will not cause anything wrong...
veggav
28th July 2018, 20:20
Anyone noticed that Nvidia Control Panel when using custom resolution timming by Madvr you only get 8bits output? Or am I don't something wrong here?
The 10 and 12bpc option is gone.
Even the OSD showing D3D11 Windowed full screen (10bits).
EDIT: Nevermind, you have to enable 12bits before going into custom timming.
franketto
28th July 2018, 21:08
Did the DXVA checker: nothing wrong.
Asmodian
28th July 2018, 22:54
I believe this is not directly the fault of madVR. Please create a new thread, maybe in this sub-forum, to keep this thread on topic.
Also, try installing the newest drivers for your GPU. :)
veggav
29th July 2018, 00:04
Well, it worked for 5 minutes and suddenly it's gone.
How do you guys get 12bpc with custom timing?
jkauff
29th July 2018, 00:06
No, I haven't tried any other drivers apart W10 automatic updates.
I cannot use another CPU...
The graphics drivers from Intel for your CPU/GPU are what you need (found on intel.com in the Downloads section). The generic Windows drivers are old and far less capable.
Asmodian
29th July 2018, 00:17
How do you guys get 12bpc with custom timing?
I don't think anyone has gotten it to work through a reboot. :(
veggav
29th July 2018, 00:25
That sucks, for the first time I was able to get my TV to recognize 23p as 24hz if I use CVT CRT timings.
But giving up on 12bpc it's not a good trade off.
One idea would be actually change the timing for 23hz based on the findings with MadVR and put those on CRU (custom resolution utility).
But I don't know how to modify timings of specific hertz like 3840x2160.
EDIT: Got 12bpc to stick after a reboot.
Used CRU with the timings I wanted, added as a detailed resolution, moved it up to be together 3840x2160@60 and after rebooting I selected 23hz, changed to 12bpc and the 24hz (23.976) I had as 12bpc.
Rebooted once more, changed resolutions and still 12bpc.
So, yay! :)
el Filou
29th July 2018, 10:47
@franketto other things to try:
- change LAV hardware decoding mode (DXVA2/D3D11) or madVR rendering mode (D3D9/D3D11, Full Screen Exclusive/Windowed)
- temporarily remove your 3DLUT from madVR
franketto
29th July 2018, 12:10
@franketto other things to try:
- change LAV hardware decoding mode (DXVA2/D3D11) or madVR rendering mode (D3D9/D3D11, Full Screen Exclusive/Windowed)
- temporarily remove your 3DLUT from madVR
Thank you, I'll try.
I also installed the latest Intel drivers.
I have not installed LAV: should I install it?
pirlouy
29th July 2018, 12:57
You should open your own thread, as you were told. Not everybody is interested in your problem which could result in 50 other posts.
Zaoshi
29th July 2018, 14:33
My render queue fails to fill up and sometimes I get frame drops (even though OSD reports low render times), however in FSE mode there are no frame drops and queue is full (although it reports significantly higher render time).
I heard this is an issue with Windows 10 version 1803. I tried searching this thread but failed to find any fix. Perhaps anyone remembers what it is, assuming it exists?
Vincent Vega
29th July 2018, 17:07
its weird i just noticed dx11 exclusive fullscreen no longer works here.
OSD says dx11 windowed despite the setting to exclusive.
and i did not change a thing, no new software or settings, or drivers.
must of been another shitty win10 weekly update or something.
does anyone else have this issue?
Warner306
29th July 2018, 17:51
My render queue fails to fill up and sometimes I get frame drops (even though OSD reports low render times), however in FSE mode there are no frame drops and queue is full (although it reports significantly higher render time).
I heard this is an issue with Windows 10 version 1803. I tried searching this thread but failed to find any fix. Perhaps anyone remembers what it is, assuming it exists?
The rendering times are artificially low in windowed mode after the Windows 1803 update. Only FSE is reporting the correct rendering times. A couple have had trouble filling the present queue when using NGU.
Warner306
29th July 2018, 17:53
its weird i just noticed dx11 exclusive fullscreen no longer works here.
OSD says dx11 windowed despite the setting to exclusive.
and i did not change a thing, no new software or settings, or drivers.
must of been another shitty win10 weekly update or something.
does anyone else have this issue?
It is not uncommon. It happens all the time. Not all systems work well with fullscreen exclusive mode in Windows 10. Try another media player. Updates and drivers can change things.
Vincent Vega
29th July 2018, 18:55
It is not uncommon. It happens all the time. Not all systems work well with fullscreen exclusive mode in Windows 10. Try another media player. Updates and drivers can change things.
just rebooted pc and problem went away, at least for now -)
next time will try to just restart gpu driver with devmanview.
ryrynz
29th July 2018, 23:48
Please don't quote in entirety a post directly above yours it's pointless.
madjock
30th July 2018, 07:54
To be honest this whole thread seems to be pointless now.
As some of us are aware there is a thread in the AVS forum with a group working with test builds and Projectors.
For me personally, it now looks a little clique who are obsessed about certain frames of certain films and it seems to be stuck in a loop.
Nothing is spoke about in this thread other than the usual culprits of 23.976 or trying to get 12 Bit.
Just my thoughts obviously, but it seems to have gone quite stale.
LigH
30th July 2018, 08:28
I agree; "advanced" issues with HDR and HBD and frame rate fine tuning, affecting only a part of the users, would have deserved a separate thread a lot earlier. Almost 52,000 replies now...
Vincent Vega
30th July 2018, 12:55
Please don't quote in entirety a post directly above yours it's pointless.
good catch lil man, and welcome to doom9 forum!
i checked CP menu again and there doesnt seem to be an option to be notified if someone quoted your post. its either notify of all replies or dont notify at all. perhaps webmaster could consider to do something about it. in most other forums quoting is a way to attract the quoted user's attention by this specific kind of event.
@ryrynz
dont push your luck though with this sort of trolling. not everyone around here is as open-minded and forgiving as me.
ryrynz
30th July 2018, 12:58
Ain't trolling bro, I suggest you read up on what that actually is and understand how it easily doesn't apply here in particular this situation.
Nobody needs to be notified, everyone here is browing this forum on a near daily anyway.. so don't play that card.
It's a terrible waste of space and on other forums mods will tend to delete such posts.. use your head, it's not smart.
Maybe I should quote your entire post just so you know I'm talking to you.
Just my thoughts obviously, but it seems to have gone quite stale.
Yeah, it's turned towards trouble shooting mostly. The software is quite mature and the development talk is on AVS right now.
mclingo
30th July 2018, 13:07
chaps, , by all means quote but if its quite a long post just delete out the main body of text, this way the quoted knows they are the target of the response and the thread doesnt get junked up.
Asmodian
30th July 2018, 22:24
dont push your luck though with this sort of trolling. not everyone around here is as open-minded and forgiving as me.
It really is quite pointless here, there aren't any "you have been quoted" notifications or anything. If you are replying to the last post please just start typing in the quick reply without hitting quote. It really is more pleasant and less redundant to read.
If you want to type inline replies to individual points feel free to quote those points but there is no need to quote entire posts if you are replying to them as a whole (especially annoying when there are images in the quoted post).
I am not sure why you responded to this simple request with such hostility. :(
I agree; "advanced" issues with HDR and HBD and frame rate fine tuning, affecting only a part of the users, would have deserved a separate thread a lot earlier.
What should we be discussing in this thread? This is supposed to be madVR development and issues, what is there to figure out except HDR, custom resolutions, and high bit depth support? What topic is the discussion around these issues obscuring?
I am not opposed to a seperate thread for HDR, custom resolutions, and high bit depth support, if people would use it, but it doesn't seem off topic here either.
jkauff
30th July 2018, 23:34
We should keep it all in this thread, so madshi can find us whenever he comes back. :)
ryrynz
31st July 2018, 04:13
I am not opposed to a seperate thread for HDR, custom resolutions, and high bit depth support, if people would use it, but it doesn't seem off topic here either.
This thread has always been covering all manner of topics not directly related to MadVR usage, there's just not really much in the way of discussion outside of issues during MadVR down time to keep many interested. We've covered so much over the years, no need to trend old ground until new paths are laid, things are okay as they are IMO.
madjock
31st July 2018, 08:57
A new HDR thread would not be much of a success I think.
Ironically it is the main use for me for madVR, but everyone either said it is a work in progress, and to be honest since there are so many variables with nit ratings of different films, displays, equipment and the likes, they are very hard questions to answer.
One has only to look at the AVS thread to see there may never be a good outcome or rather a use this for all films, and even with it now going to a 3 option scenario, there are still issues, so I actually think I was better off being more ignorant, as like them I seem to think things look off sometimes, or wonder what colours I should be seeing, when I never thought too much about it before.
strumf666
31st July 2018, 09:20
Having specific threads for let's say development, hdr, 12 bit, known issues, ... would make finding an answer a lot easier, especially if there were a faq or table of content with links in the first posts. It wouldn't solve everything, because there are always people that don't bother to read even one post above and maintaining those threads would also be more work, but for most it would probably be helpful.
Asmodian
31st July 2018, 09:49
I actually think I was better off being more ignorant, as like them I seem to think things look off sometimes, or wonder what colours I should be seeing, when I never thought too much about it before.
So true. Once you start down that path displays will never be the same again. :devil:
madjock
31st July 2018, 10:32
Having specific threads for let's say development, hdr, 12 bit, known issues, ...
Yeah you could be right, but then you end up with people asking the wrong questions in the wrong thread.
The trouble with HDR is as I said earlier, different equipment and the likes, so unlike the party line of it is how you like it, or whatever looks best to you, the default settings will work for the majority, but depending on your preference for NIT levels, or what model of TV you have, or what film it is, the whole situation is endless.
I started looking at 4k TVs, but after a couple of days I realised I could not afford what was classed as a decent one, so I think the more you know the less well off you are. :)
Unlike certain settings for Anime for example, the whole HDR to SDR seems to be a minefield, I understand why they are doing it on another forum now with a limited selection of people giving their thoughts, but since it is mostly based on projectors I am unsure if there will be much more support other than that thread, as it again will all be down to personal choice and equipment again.
hannes69
31st July 2018, 10:42
Having specific threads for let's say development, hdr, 12 bit, known issues, ... would make finding an answer a lot easier, especially if there were a faq or table of content with links in the first posts.
Yes :)
I´m following this thread for many years now, it is a great thread, definitely, but the structure could be improved in my opinion. The all-in-one concept is sometimes really annoying, especially when:
- always the same questions again and again
- people searching for personal help - the solution is often enough of no use for anyone else
- general HTPC / computer stuff like "the best GPU", how big has my PSU to be, what CPU do I need...
- mixing up development view with end-user view
- mixing of stable / beta / experimental stuff
Many of these "annoyances" could be overcome at least partially with an alternative thread structure, like subthreads:
- FAQ: answers many of these "same questions over and over again"
- help: people can ask here for personal help, advanced users can do this "job"
- hardware section with subsections: discussing new hardware on the market, performance, price, experiences,...
- driver section: discussion room for "new driver is released", "driver x has these errors/flaws/faults", "driver y has this bug fixed", "driver z is my favorite driver"
- feature request: "madVR should contain..."
- research & development: discussing white papers, studies, recent approaches, alternatives, computer algorithms, neuronal networks,...
- test area: asking people for testing new features and deliver feedback
- vote section: making votes when making decisions for a majority of the community
....
Maybe not all of these sections are needed, maybe there are other, maybe they could be labeled in another way, but it should be useful.
Some guy only interested in help for a personal problem like "my blacks crush, why is that?" would not have to deal with active development of a new scaling algorithm. And the rest of the community outside of the help section would not have to deal with this guy ;)
And another experienced / advanced guy is maybe only interested in the "test area", "research & development" and "feature requests" and doesn´t want to deal with the "plain rest".
The fact of 50000+ posts in this thread should be an indication for such a splitting ;)
Not being able to explain things in a short manner, see above, I try to sum it up:
"This thread needs some structure" :)
chros
31st July 2018, 10:52
I agree with those who wants separate threads for different stuff: all you have to do is just create them and instruct newcomers to use them :)
hannes69
31st July 2018, 10:57
It´s madshi´s thread so it´s madshi´s decision :)
Solution: madshi creates these subthreads, this thread here is closed, newcomers and oldies can only use the new subthreads. Simple. :)
madjock
31st July 2018, 11:07
All these things are available if people Google..
https://wiki.mikejung.biz/MadVR
https://forum.doom9.org/showthread.php?p=1709584
and all other threads...
Like all FAQs and Guides, they are only as good as the Version they were written for, and with Windows 10 issues, Driver issues as these get updated, and indeed new options in madVR, you can't really blame people coming to an "active" thread.
I was guilty of it myself, yes I read the FAQs, but when they are x amount of Revs behind, or the settings that were supposed to be the best were not even in the Guide, you do want to try and get what is the best settings that people have found for the latest Rev.
The HDR to SDR is never really explained anywhere, well it is in the excellent 2nd Guide, but with the variations and the issues we know about now and only a finite few seem to know how it works, and that was Revs ago, so unless someone who understands it can make a new guide (and keep it updated), there will always be questions, especially if someone has a C7 or a C8 etc...:D
giulianoprs
31st July 2018, 14:52
Hello, I am a "foreign" user, I write from Italy, the forum is very useful, the best for madvr, there are no others like that !!!! however, put yourself in the shoes of a user who uses for the first time madvr, I in Italy could not find a forum with explanations valid to understand the fining here, with the help of google translator with 5/6 messages and thanks to users kind and prepared I understood many things, in the future maybe come back to ask for advice on HDR, when I buy a new 4k tv, for now thanks forum, thanks madshi and users like asmodian and warner306 that always give good recommend all !!! Hello everyone and good evening .
Warner306
31st July 2018, 16:14
To be honest this whole thread seems to be pointless now.
As some of us are aware there is a thread in the AVS forum with a group working with test builds and Projectors.
For me personally, it now looks a little clique who are obsessed about certain frames of certain films and it seems to be stuck in a loop.
A final build was provided, so development just reached an end point. It didn't stall. I posted in that thread and didn't receive much of a response, but I wasn't offended. There is no limit to who can post there. I'm sure other topics will become relevant in the future in this thread after tone mapping is complete.
If you want to talk about alternative topics in here in the meantime, make a feature suggestion and others will likely discuss it.
veggav
31st July 2018, 18:12
I actually learned a lot from this thread and I just recently started participating asking questions and I hope in the feature I could be of any help.
I'm very thankful for the patience people like Asmodian and Warner have with my questions.
pirlouy
31st July 2018, 19:13
IMO, madVR deserve a forum, not a thread in order to avoid repeating same thing. I hoped Madshi would create a subforum on his website or he would have his own subforum here or somewhere else, but despite soon-to-be 10 years, it does not look like it will happen. GL with those having patience to repeat themselves. :)
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.