Hi Claw,He might not use some features, or it might be based on older builds (performance requirements have gone up over the last few weeks). I agree with the performance recommendation: RTX 2080. Maybe he meant a 2060 minimum for tonemapping and nothing else, to override his other minimum? Not sure what his last line means. Please don't mention me if you question this in his thread, the last thing I want is a debate with Onkyoman
Are you referring to the screenshots I provided that DO provide contradictory evidence? Without the menu up, I'm seeing 35ms render time with NGU on high, black bar detection enabled and Error Diffusion 1 enabled with my RTX 2070. I'm not saying you don't know what you're talking about, but yes, I would say you don't know everything. I had to explain three times that I'm using software decoding and you insisted that I was using copyback twice. That was wrong as was my RTX 2070 not being fast enough for the settings you said it couldn't do. It's mostly the attitude you have when posting. It's a patronizing attitude as if you're talking down to people as if they have no idea what they're doing. But maybe I'm reading your posts wrong.
I think sending it back is the right move. If you want to use some of the better settings in madVR I think at least a 2070 is needed with the 2080 being an even better choice if you don't mind spending the extra money.
Hopefully the the Envy device means you won't have to. It can be a pain in the neck not knowing which hardware to buy let alone which settings are appropriate for the hardware you end up buying. Envy should make things a lot more plug'n play.
Yep, the Envy is what I am interested in. I have already gone the HTPC route and it seemed to be too much work to maintain, when microsoft decided to make changes.
After purchasing an RTX 2060 and returning it, then waiting for pricing announcements for the Envy that were more than I am willing to pay at this time... I purchased an RTX 2080 Super which is still about half the price of a 2080 TI.Instead of building a new HTPC, I decided to install the 2080 into an older HTPC that was formerly used to play Blu-Ray backups with Total Media Theater. Not a high spec build at all:LGA1155 micro ATX motherboard with a single PCIe 2.0 slotSandy Bridge I3-2100 low wattage CPU.8 GB DD3 memory.Early generation Samsung SSD.Silverstone GD05B-USB3.0 HTPC CaseWindows 8.1I did replace the PSU as it was rather low powered and I needed one with both 6-pin and 8-pin connectors for the RTX card.Even with this low end build, the RTX 2080 is able to support JRiver Red October HQ with MadVR with almost no compromises to get zero dropped frames. I will eventually upgrade the motherboard, CPU, and memory. Just wanted to point out that a high end PC build is not needed to run MadVR. Spend the money on the best GPU you can afford instead.Even in this desktop style HTPC case, the 2080 Super idles at 35-40 degrees. After MadVR tone mapped a two-hour UHD movie, it reached 65 degrees. Stopped playback and temps returned quickly to 42 degrees.
Glad you're happy with the 2080. jRiver Red October HQ is very low tech though, so doesn't represent a current use. AFAIK Red October HQ simply installs the latest public build of madVR, with lots of compromise in the settings. The release version needs a lot less resources than the latest beta builds, which produce significantly better results but at the cost of a more GPU resources.You should still be okay with a 2080, but the 2060 will definitely struggle with these, even at 23p.At 60p, even a 2080ti needs to compromise some settings It's definitely better to put more in the GPU than in the rest of the build. As long as your CPU/memory isn't a bottleneck, it's money well spent (and saved). Depending on the decoding, the CPU/memory will have more or less of an impact though. So depending on the features you actually need, you might see a bigger CPU use. For example, if you can't use D3D11 native because you want UHD Bluray menus in jRiver or black bar detection, the impact of your low end build might be more visible.In any case, you need to test the latest beta builds (assuming you haven't installed them yet manually).
I have been copying the test builds over the 92.17 release that Red October installed, including the 111 build. And I am able to enable disc menus without impacting performance. I match up my MadVR settings with what I see you and others using in the improvement thread.I should make another attempt to use external Lav filters rather than those installed by Red October so I have more control over the option settings.Now that I am getting good results with no dropped frames, I probably need to create a custom refresh mode to try to eliminate repeated frames that are occurring every 4 minutes or so.The one trade performance restriction that I must keep enabled is the one for chroma luminance channel. If I uncheck it, render times go from 30 ms to over 40 ms with stutter. Perhaps that option is using more CPU and/or PCIe interface resources than I have available with my old motherboard and CPU.
32 Replies
16790 Views