madVR - high quality video renderer (GPU assisted)

[madshi]

madshi, there's a typo in OSD. It says "limited range (says bistream)" instead of bitstream.
Thanks, fixed.

Unfortunately it supports nothing besides 60Hz, or I would have tried. It's an 32" LCD TV with an analogue VGA (RGB) input, I watch everything video related there. It used to have HDMI, but the inputs failed at some point and it's out of warranty for years now. I want to replace it but cannot afford it really, recession...
To be honest, I'm not sure about the "magnitude" of the judder you're seeing. It could be a real problem caused by a bug in madVR or a bug in the GPU drivers. But it could also be just the result of the fact that madVR is not yet optimized for 24fps @ 60Hz playback. I would have to see it with my own eyes to judge that, I guess. Since you did managed to get smooth 30fps @ 60Hz playback, my best guess is that the problem you're seeing will go away once I spend some time to optimize 24fps @ 60Hz. Actually after I did that, madVR should be much smoother than any other renderer with 24fps @ 60Hz. But I don't know when exactly I'll find time for that. I've so many other important things on my to do list.

Yes I'm using exclusive mode.

Here are 4 logs file
Thanks. I've seen 2 weird things in the logs:

(1) madVR does some funny things, which I think I've now fixed in my sources. So the next madVR build might already solve the problem for you. Or maybe not.

(2) The splitter you're using ("AVI Splitter") creates very bad timestamps. Practically there are always 2 frames which have identical timestamps. That makes it difficult for madVR to achieve smooth motion. madVR tries, and fails, which I might have just fixed (see (1)). But ideally the splitter should not create such bad timestamps.

having some issue with Nvidia GT 550M with Optimus.

when used with MPC-HC v1.5.2.3456 or PotPlayer v1.5.29917, after a while video will freeze but audio continue.

When used with intergrated Intel HD 3000, playback is error free.
A freeze is weird. I'd suggest to try updating to the latest MPC-HC/PotPlayer versions, just to be safe. Then it might make sense to reset the madVR options to default. Furthermore make sure you that you've disabled (or set to application preference) anisotropic filtering and anti-aliasing in your GPU settings. Finally, make sure your GPU clocks don't jump around during playback and try without Reclock, just as a test.

The glitches never were a problem on the old exclusive mode, and everything was running perfectly fine as well. People also reported that going back to it solves their problem (in the case when glitches are actually visible).
The old exclusive mode worked well for many people, but not for all. The new one should in theory be much better, but practically it isn't for some people, while it is for others. Personally, the old exclusive mode never worked well on my NVidia 9400 HTPC when playing back 25fps @ 50Hz, while I can get the new one work well (with special settings).

So maybe its also doing something that is not "normal" for a "game" to do?
Actually the old exclusive mode is less like what games do than the new one. The new one does in large parts do what games do. However, madVR doesn't use double buffering or triple buffering, but instead 8-times-buffering (by default). Games don't do that. You can simulate double-buffering or triple-buffering by settings the number of pre-rendered frames to 2 or 3 and by disabling all exclusive mode tweak options. That way madVR should behave quite similar to a game. All the tweak options move madVR away from what a game usually does.

[HeadlessCow]

Why upscale it ?
Let it at 20 in window mode, and 20 in Full Screen.


If you just do that, anything that is positioned over the video (like a sign), will not look correct.

[sneaker_ger]

New nVidia WHQL drivers are up! Working great with mpc-hc + lav filters + madvr.

http://www.nvidia.com/object/win7-winvista-64bit-285.62-whql-driver.html

Did they fix any issue you were having with the previous driver?

[6233638]

OK, with the new 285.62 WHQL drivers, things may have been fixed.
I was definitely seeing less presentation glitches than with the betas without making any changes. (there definitely seems to have been more with most beta drivers I've tried)

EDIT: Nope, didn't work, still glitching.

I need to do longer testing to be sure though, and want to see if all of those settings are necessary.
"run presentation in a separate thread" did not have any benefit previously (may actually have been detrimental) but seems to have helped this time.

I wish things weren't so tempermental.

[madshi]

madVR v0.77 released

http://madshi.net/madVR.zip

* added support for ffmpeg/libav h264 4:2:2 decoding
* optimized ffmpeg/libav compiling options
* fixed: madVR disliked getting 2 frames with identical timecodes all the time
* modified autodetect priorities slightly

[cca]

To be honest, I'm not sure about the "magnitude" of the judder you're seeing. It could be a real problem caused by a bug in madVR or a bug in the GPU drivers. But it could also be just the result of the fact that madVR is not yet optimized for 24fps @ 60Hz playback. I would have to see it with my own eyes to judge that, I guess. Since you did managed to get smooth 30fps @ 60Hz playback, my best guess is that the problem you're seeing will go away once I spend some time to optimize 24fps @ 60Hz. Actually after I did that, madVR should be much smoother than any other renderer with 24fps @ 60Hz. But I don't know when exactly I'll find time for that. I've so many other important things on my to do list.


Patience is one thing that I do have, I'll test it when the time comes.

[Peuj]

Thanks. I've seen 2 weird things in the logs:

(1) madVR does some funny things, which I think I've now fixed in my sources. So the next madVR build might already solve the problem for you. Or maybe not.

(2) The splitter you're using ("AVI Splitter") creates very bad timestamps. Practically there are always 2 frames which have identical timestamps. That makes it difficult for madVR to achieve smooth motion. madVR tries, and fails, which I might have just fixed (see (1)). But ideally the splitter should not create such bad timestamps.

Thanks madshi.

I didn't test the new version yet but just to say about the "2 frames" problem, it's most probably due to an option in PotPlayer called "Motion Blur".
If you want to make some tests it's under Preference=>Video=>Video Processing: Motion Blur.

[Budtz]

* fixed: madVR disliked getting 2 frames with identical timecodes all the time
* modified autodetect priorities slightly

What does these two points do?

[whitestar999]

@peuj,disable all video post processing options in potplayer & then see if it helps with madvr.personally i prefer ffdshow raw filter for post processing instead of using pot player's internal ones.

[nevcairiel]

OK, with the new 285.62 WHQL drivers, things may have been fixed.

Things definitely changed, i needed to tweak my settings some.
"Limit rendering times to avoid glitches" is now off, however i had to set "flush & wait (sleep)" for ".. after D3D presentation".
This is combined with 12 buffers and "use separate device for presentation"

Running strong both for 24@24 and 25@50.

[gerhard.kiels]

Good day to you all! I couldn't find this mentioned anywhere else no matter how hard I tried, so here it goes:

I would like to report an inconvenience bug:

I use madVR v0.77 in mpc homecinema v1.5.2.3456.

Whenever I set "use 10bit chroma/luma buffer instead of 16bit" in the "trade quality for performance" tab in madvr options, I get a periodically flashing OSD message that says "madVR reports: creating 10bit render texture failed, used 8bit instead".

Now, about the fact that madVR uses 8bit instead of 10bit - I couldn't care less, because my eyes can't tell the difference. What bothers me is that it constantly flashes on the screen! What I mean by that is that when I press "ctrl+j" i get that OSD message displayed all the time in the upper left side corner of the screen (whitch is unaccaptable while watching anything), and when I turn off the OSD by pressing the same "ctrl+j" again it disappears only to start periodically flashing on the screen. It's like disappearing, displaying and then disappearing again 2 times a second, then it disappears for like 40 seconds and then starts flashing again 2 times a second (these are only estimates). Sometimes it helps to press "ctrl+j" twice to remove the flashing, but every time it comes back after a while. And just to clarify: I use these options because I have an old system with a poor Geforce 7 7600GS, whitch can't handle 720p videos in 16bit processing modes. Besause of that I do appreciate the existence of those options very much.

On top of that, I can't see the actual stats that the OSD should show when I press "ctrl+j" - only that message is displayed.

So I would like to ask: is that message so important? Can't it simply be removed or moved to only the debug-version?

Other than that - a really splendid renderer!

[madshi]

Patience is one thing that I do have, I'll test it when the time comes.
Good. Just check back every couple of weeks/months. Sooner or later I hope to get special support in for 24fps @ 60Hz.

* fixed: madVR disliked getting 2 frames with identical timecodes all the time
* modified autodetect priorities slightly

What does these two points do?
Nothing but 2 small bug fixes, which you shouldn't notice, unless you had these exact specific problems before.

Things definitely changed, i needed to tweak my settings some.
"Limit rendering times to avoid glitches" is now off, however i had to set "flush & wait (sleep)" for ".. after D3D presentation".
This is combined with 12 buffers and "use separate device for presentation"
Interesting. I'm really wondering why different driver versions need different madVR settings. I guess I should finally post a proper bug report to NVidia with some source code.

Whenever I set "use 10bit chroma/luma buffer instead of 16bit" in the "trade quality for performance" tab in madvr options, I get a periodically flashing OSD message that says "madVR reports: creating 10bit render texture failed, used 8bit instead".

Now, about the fact that madVR uses 8bit instead of 10bit - I couldn't care less, because my eyes can't tell the difference. What bothers me is that it constantly flashes on the screen!
I understand. Haven't seen a GPU yet which couldn't do 10bit textures. Have you tried updating to the latest drivers for your GPU? There should be a visible difference at least with test patterns. 8bit is really too low to avoid banding in certain situations. But I understand that the madVR message doesn't make much sense. I mean either madVR supports 8bit textures or it doesn't. If it does, you should be able to use it that way. However, I at least wanted to let the user (you) know that something isn't as it should be. Oh well.

[gerhard.kiels]

@madshi

Yes, I always have the latest version of drivers installed (in fact, today I installed Forceware version 285.58). I run windows XP, and weather I enable or disable "use managed upload textures" has no effect on the phenomenon. Could it be that because my graphics card is in an AGP socket it can't do 10-bit textures?

Can you remove the message then nonetheless?

[Plutotype]

Hi,
I have the latest versions of MPC-HC 3794, LAVfilters 0.38RC, Reclock and madVR 0.77. With following video file I experience dropped frames and can not find the cause for this. The frames are dropping because the present que is not stable. If I have buffer set to 12 ( exclusive mode ), the present que goes from 10-11 to 0 and at that moment it causes frames to drop:
http://www.mediafire.com/?1rja6beiptppzq8

What makes this video file special that it causes madVR to drop frames in my setup?

Thanks for help.

[Gary.M]

I've updated to the new Nvidia driver, and latest madVR, and under Jriver 16 I still have the presentation glitches...

Nevcairiel could you list exactly all the settings you're now using? My usage is almost exclusively PAL 25 fps on a 50Hz projector. I have resorted to the old presentation path at the moment as is "seems" to not glitch.

I also have ordered an AMD 6670 to see if the "other side" can deliver the glitch free playback I am looking for.

Things definitely changed, i needed to tweak my settings some.
"Limit rendering times to avoid glitches" is now off, however i had to set "flush & wait (sleep)" for ".. after D3D presentation".
This is combined with 12 buffers and "use separate device for presentation"

Running strong both for 24@24 and 25@50.

[06_taro]

Crash when decoding 10-bit 4:2:2 AVC using madVR's internal libav decoder, LAV Video decoder (outputs P210) and madVR's renderer plays fine.

Crash decoding environment:
mpc-hc 1.5.3.3755 xvidvideo BEmod x86
LAV Splitter git-r1380(be78b9e) ( can be downloaded here (http://forum.doom9.org/showthread.php?p=1533936#post1533936) )
madVR 0.77 internal libav decoder and renderer
Windows 7 SP 1 x64 Ultimate

8-bit 4:2:2 works fine with madVR's internal libav decoder.

[cyberbeing]

Haven't seen a GPU yet which couldn't do 10bit textures.
Sure you have, my 7800 GTX 512 is unable to do 10bit textures with madVR, and I've told you that a few times before. gerhard.kiels has a Geforce 7600GS, another NVIDIA 7-series card, so it's unsurprising that he can't get it working either.

Edit: I found the info below in an NVIDIA PDF for reference.
http://img822.imageshack.us/img822/9649/fmtlimits7series.png (http://developer.download.nvidia.com/GPU_Programming_Guide/GPU_Programming_Guide.pdf)

[madshi]

Can you remove the message then nonetheless?
Will do. Or maybe replace it with a one-time-only (and self removing) warning.

What makes this video file special that it causes madVR to drop frames in my setup?
The sample runs fine on my HTPC (XPSP3, Radeon 6850). You can upload a log, maybe I can see something.

Crash when decoding 10-bit 4:2:2 AVC using madVR's internal libav decoder, LAV Video decoder (outputs P210) and madVR's renderer plays fine.
Do you have a sample for me? That would be great, I don't have a 10bit 4:2:2 file here. Thanks!

Sure you have, my 7800 GTX 512 is unable to do 10bit textures with madVR, and I've told you that a few times before.
I don't remember. But your GPU is fast enough to use 16bit textures, right? Probably that's why it didn't stick with me that your GPU can't do 10bit.

[The Seeker]

Is it okay to install new versions over the top, or I do have to uninstall the old version first?

[madshi]

In most cases you can even simply replace the files without having to reinstall at all. If you do feel the need to install, it might make sense to also uninstall first, but neither is usually needed.

[cyberbeing]

I don't remember. But your GPU is fast enough to use 16bit textures, right? Probably that's why it didn't stick with me that your GPU can't do 10bit.
Well since the last time I told you was probably back when you first added the checkbox for 10bit textures (a long time ago...), I don't blame you for not remembering. I've been using madVR happily for a long time now, so I'd 16-bit textures work well enough. That said, I've never even considered ever using madVR with 8-bit textures as a valid option because you were strongly against it for quality reasons, and it meant a big fat red warning was on the screen permanently.

If you've had a change of heart and are willing to make the 8-bit textures setting usable (with OSD stats), I'd be interested to see if there was any significant performance gain to be had with heavy duty processing.

Will do. Or maybe replace it with a one-time-only (and self removing) warning.
Why not make it simpler and just add a drop-down box to choose between 10-bit and 8-bit buffers for those two settings? It doesn't make any sense to have a temporary warning, since it could lead people to believe 10-bit textures are actually working when they're not.

On another note, ever since you added those extra stats to the OSD, it's now 4 lines too tall to display at 360p. Since that is the smallest size I'd ever want to read stats at, hopefully you don't mind fixing it. A) shrink the font, B) put the least important stats on the very bottom, C) scale the OSD to resolution, and/or D) change the OSD to double column from single column.

[The Seeker]

In most cases you can even simply replace the files without having to reinstall at all. If you do feel the need to install, it might make sense to also uninstall first, but neither is usually needed.

Thanks mate. Thanks also for madVR itself, it's really something else.

[6233638]

Update: This is fixed for me now, have spent more time testing and haven't encountered a single presentation glitch. :D
----------

OK, I think I may have my presentation glitch problems sorted, though I've only played back two videos that are just over 40 minutes long, so far.

What I did earlier today, to see if this was actually a Nvidia driver issue, or if it was possibly something introduced with newer versions of madVR, was to go back to v0.60

Why 0.60? It was the first version where I could get glitch-free playback on my GTX 570, thanks to the addition of the "limit rendering times to avoid glitches" option.

So I reset to the defaults, and ran v0.60 with the settings from that post.

Perfect playback.


Some time between then and now, those settings "broke" and I could no longer get glitch-free playback, which resulted in me trying most combinations of settings without any luck, and deciding to leave for a while. Most of my playback at the time was 24p@24Hz which was fine, but recently I've been watching a lot more 30p@60Hz content.

Today, with the 285.62 drivers and madVR 0.77, I seem to have glitch-free playback again.

The only change from the default settings, is upping the present queue to 16 and enabling "limit rendering times to avoid glitches", all the other rendering settings have been left alone.

I am using my preferred scaling settings, and 3DLUTs/Gamma correction as well, which seems to be working fine.

Things definitely changed, i needed to tweak my settings some.
"Limit rendering times to avoid glitches" is now off, however i had to set "flush & wait (sleep)" for ".. after D3D presentation".
This is combined with 12 buffers and "use separate device for presentation"It's strange that your settings are always so different from mine. When I try out your flush options, the present queue drops to 0–2 and I get a lot of glitches.

It must be a generational thing. (I suspected as much, as settings that worked fine on my 9400 did not work at all on my GTX570)

[nevcairiel]

It's strange that your settings are always so different from mine. When I try out your flush options, the present queue drops to 0–2 and I get a lot of glitches.

It must be a generational thing. (I suspected as much, as settings that worked fine on my 9400 did not work at all on my GTX570)

My settings are always against a GTS450. I also have a GTX570 in my main PC, however i don't use it for video watching, and therefor never really bothered with checking its madVR behaviour.
The funny thing is, before this latest WHQL version, that flush mode also caused the queue drop and lots of glitches, but now its perfect playback with full queues.

[SamuriHL]

My settings are always against a GTS450. I also have a GTX570 in my main PC, however i don't use it for video watching, and therefor never really bothered with checking its madVR behaviour.
The funny thing is, before this latest WHQL version, that flush mode also caused the queue drop and lots of glitches, but now its perfect playback with full queues.

I didn't get a chance to try it on my 450 last night. Will hopefully do so today.

[jovovick]

A freeze is weird. I'd suggest to try updating to the latest MPC-HC/PotPlayer versions, just to be safe. Then it might make sense to reset the madVR options to default. Furthermore make sure you that you've disabled (or set to application preference) anisotropic filtering and anti-aliasing in your GPU settings. Finally, make sure your GPU clocks don't jump around during playback and try without Reclock, just as a test.



i tried MPC-HC_r3792_x86, and using MadVr 0.77, with Nvidia notebook driver 280.26.

anisotropic and anti-aliasing is disabled, and not using Reclock.

The freeze still occurs, i think it is not caused the movie file, as the point where it freezes, might not freeze again when reopen the video file.

[vivan]

Same problem that jovovick has (video freezes after some time (about 60-90 seconds) when using nVidia card on Optimus system).
Updated to 285.62 nVidia notebook driver... Problem still occurs. Plus now it's impossible to use discrete graphics (choice is disabled) for mpc-hc.exe, so I had to rename exe file in order to use it.
Seems that problem is in Optimus...

[06_taro]

10-bit 4:2:2 sample:
BBB422p10-rr3.rar (http://www.mediafire.com/file/3n64vyvlrqduhg1/BBB422p10-rr3.rar)

[Plutotype]

The sample runs fine on my HTPC (XPSP3, Radeon 6850). You can upload a log, maybe I can see something.


Hi madshi,

The issue with my dropped frames is not related only to the video I posted. Today I watched other videos, there were 10-15 dropped frames. Again I have everything up to date: MPC-HC 3794, LAVfilters 0.38RC, Reclock 1.8.7.7. and madVR 0.77.

Here you can find a log for the same video I posted here.
I installed the same SW setup on different computer with HD6570 (fresh win7 install ), also 11.9 Catalyst and the result was the same also there. Even under 24p setup.

Excl. mode HD5670, 3 frames in advance:
http://www.mediafire.com/?yeepbtt836xwt31

Eclusive mode HD5670, 8frames in advance:
http://www.mediafire.com/?399sz3d2q56fx3t

Increasing to presenting 16 frames in advance under exclusive mode does not help. What can you see in the log please?

Thanks
Pluto

EDIT: PROBABLY FOUND THE CAUSE. As frame dropping occured on different hardware but with Catalyst 11.9, tried uninstall them, cleaned the registry via Driver Sweeper and installed 11.10 RC3. With 8 pre-frames set, the presentation que stays 8-8 or 7-8 and keeps these levels. Every frame drop stat is back to almost 2hours ( was 2-6 minutes when the frames dropped with 11.9 ). I remember - both installations of CCC 11.9 on both computers failed on installing Microsoft Visual C++ 2010 Redistributable package. 11.10 RC3 not. Maybe somebody will know more about this issue.

EDIT2 False alarm, the updated CCC driver didnt solve the issue, the frames are still dropping. On 24p Bravia, HD6570 via Yamaha receiver ( no processing ), 1080p23 = one frame drop in 5-6 minutes. 8 frames present que. The weird thing is, if I set 16 frames for exclusive mode, Presentation que stays max on 6-7. GPU max load (GPU-Z) 35percent, CPU i5 25percent at peak.
Flush
Flush and Wait (sleep )
Dont flush
Dont flush

HD6570 ( different computer ), log with 2 dropped frames in approximately 10 minutes of video: http://www.mediafire.com/download.php?b60u90yxo6u80ss

[dansrfe]

Hi madshi,

I'm having a similar issue to Plutotype yet I can't figure out why. 8 frames queue limit on decoder, upload, render, and backbuffer. About 2-3 frames drop every 10-15 seconds. Some frames are also delayed. I'm not sure if it is for this specific file I;m playing or it happens on other files as well.

I've uploaded a log for you to check out the problem.

http://www.sendspace.com/file/5kz8zd

[Mikey2]

I was reading an updated version of one of my favorite HTPC configuration GUIDES (http://www.homecinema-hd.com/ffdshow-video-avisynth_en.html)

and it is now updated to suggest to upscale 720P material in aviSynth (spline64resize function) instead of in madVR so that the aviSynth function LimitedSharpenFaster can correctly perform the sharpening on the upscaled material. I completely understand the reasoning behind this; however, what is your opinion on the benefits of this vs. the quality of the madVR upscaler (which I still find to be unsurpassed, including aviSynth-scripts...)

[Note: the aforementioned script takes a lot of CPU processing power; however, since I have a very fast machine and am going for the absolute best quality, for the purposes of this question let's just assume that we have limitless CPU and GPU power...]

Thanks much!

[pirlouy]

@Dansrfe: Strange, you know how to register on a forum and write posts, but you haven't heard of ZIP stuff ! o_O

[dansrfe]

@Dansrfe: Strange, you know how to register on a forum and write posts, but you haven't heard of ZIP stuff ! o_O

I want to hit myself on the head now.... :o

Link updated and about 20 times smaller now.

[THX-UltraII]

Just sold my ATI HD5450 and bought a NVIDIA GTX 460 card to be able to use CUVID in LAV Video decoder.

First thing I just noticed is that madVR reports a display refrash rate of 23,971xx (NVIDIA 23Hz setting) while madVR reported a display rate of 23,975xx which is far more close to EXACTLY 23,976 which it should be ideally.

Do you guys also get 23,971xx reported by madVR and if so, will this result in far more dropped frames during a movie? With my ATI 5450 I got about 1-3 dropped frames during a 2-3 hour movie which was pretty satisfying to me.

[nand chan]

I was reading an updated version of one of my favorite HTPC configuration GUIDES (http://www.homecinema-hd.com/ffdshow-video-avisynth_en.html)

and it is now updated to suggest to upscale 720P material in aviSynth (spline64resize function) instead of in madVR so that the aviSynth function LimitedSharpenFaster can correctly perform the sharpening on the upscaled material. I completely understand the reasoning behind this; however, what is your opinion on the benefits of this vs. the quality of the madVR upscaler (which I still find to be unsurpassed, including aviSynth-scripts...)

[Note: the aforementioned script takes a lot of CPU processing power; however, since I have a very fast machine and am going for the absolute best quality, for the purposes of this question let's just assume that we have limitless CPU and GPU power...]

Thanks much!

Avisynth is limited to 8-bit precision, unless you some functions with specific workarounds (eg. flash3kyuu), but the internal resize functions and limitedsharpenfaster will produce 8-bit results, which is horrible in precision compared to the 16-bit madVR uses.

madVR's upscaling will produce much, much nicer results than anything you will be able to get from avisynth scripts. As an alternative work-around, you could try using EVR-CP and implement your own pixel shaders for upscaling and sharpening, which EVR-CP will support using on 16-bit or 32-bit floating point textures.

[Andy o]

Just sold my ATI HD5450 and bought a NVIDIA GTX 460 card to be able to use CUVID in LAV Video decoder.

First thing I just noticed is that madVR reports a display refrash rate of 23,971xx (NVIDIA 23Hz setting) while madVR reported a display rate of 23,975xx which is far more close to EXACTLY 23,976 which it should be ideally.

Do you guys also get 23,971xx reported by madVR and if so, will this result in far more dropped frames during a movie? With my ATI 5450 I got about 1-3 dropped frames during a 2-3 hour movie which was pretty satisfying to me.

madVR will tell you pretty reliably how many minutes between dropped frames. I think with NV I get one every several minutes. But I just use ReClock and everything's working great.

[RBG]

Hello madshi.

I've got a weird bug with madVR, when I turn off/on(shift+X by default) audio processing filter in Daum Potplayer, video hangs or player crashes. First I thought that this problem occurred due to some kind of splitter incompatibility, I tried various combinations of splitter/decoder pairs, haali/lav + CoreAVC/LAVcuvid/LavVido with cuvid implementation/Built-in Decoder in renderless mode, and got same result, then I tried to change render to EVRcp, and it helped. Is it possible to fix it?

Here is my crash log:

Problem signature:
Problem Event Name: APPCRASH
Application Name: PotPlayerMini.exe
Application Version: 1.5.29795.0
Application Timestamp: 4d252720
Fault Module Name: madVR.ax
Fault Module Version: 0.77.0.0
Fault Module Timestamp: 4ea5a08d
Exception Code: c0000005
Exception Offset: 00007610
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1049
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

http://www.filefactory.com/file/ce98df3/n/ufo_ultramaiden_valkyrie_ep01.mkv - video sample.

[dansrfe]

What does present queue mean? For some reason I start getting dropped frames sometimes because the present queue shows 0-2/8. I don't know what the problem is and how to fix it.

[Plutotype]

What does present queue mean? For some reason I start getting dropped frames sometimes because the present queue shows 0-2/8. I don't know what the problem is and how to fix it.

Dansrfe,
I have exactly the same problem. I have tested this on 2 computers today, one of them is fresh new DELL computer with HD6570 and Core i5. The second one is my custom ( see signature ) with HD5670. Both computers show exactly the same behaviour. Exclusive mode is dropping frames. The number is changing from 20 to 200 during the 2 hour movie.. Dont know if I should downgrade to older Catalyst version. During past year, I have never had simillar issues with my setup.
Pluto

[THX-UltraII]

madVR will tell you pretty reliably how many minutes between dropped frames. I think with NV I get one every several minutes. But I just use ReClock and everything's working great.

thanks for your reply.

But ReClock has no sense (/will make no difference) when I only bitstream correct?

[Andy o]

Yeah, but there's not much reason to bitstream when you can already fully decode all formats.

[THX-UltraII]

Yeah, but there's not much reason to bitstream when you can already fully decode all formats.
Thats my problem. I need itstreaming because I own a D-Box system

[Andy o]

If you need a Dolby Digital stream, then ReClock can encode to DD on-the-fly. Better use the lossless tracks, decode them, and let ReClock do its thing and encode to DD.

[THX-UltraII]

If you need a Dolby Digital stream, then ReClock can encode to DD on-the-fly. Better use the lossless tracks, decode them, and let ReClock do its thing and encode to DD. I don t fully understand this, sorry. :stupid:

I ll try to explain what I want/need so you can tell if this is possible:

A D-Box decoder needs the core DD/DTS track that comes on a BR-disc to be able to 'read'. For years all D-Box owners thought that enjoy both D-Box AND high res. (DTS-MA/True-HD) audio to receiver simultanously was not possible due to windows limitations. So most D-Box users use a Dune media player. With this player audio is send out over both HDMI (lossless) and SPDIF (lossy core) simultanously.

But there has been a new D-Box user who developed an MPC-HC and LAV audio decoder which makes it possible to have two audio streams send out. One with the DTS-MA track send through the HDMI audio out of a NVIDIA/ATI card and one with the core DTS/DD track over a second audio device (a plain simple external USB audio device with just a regular SPDIF output on it). This works good until now; there are some minor fixes on his to-to list but the main feature works.

So what we would need is to be able to get the UNALTERED lossy core signal send over via the external USB audio device and at the same time send the lossless DTS-MA/True-HD that is decoded by ReClock via LPCM over HDMI and all this simultanously.

I think the author of this project will join soon here to give further explanation but the main thing is explained now, maybe not very technical but I think you will know the problem now and what we (D-Box users) need/want.

[Andy o]

It's ok, I got it. I don't think you could do it with ReClock if you need two audio stream outputs simultaneously.

[rahzel]

ATI is more accurate 'out-of-the-box' than Nv with refresh rates. I can go a whole movie without a single dropped frame without reclock and my refresh rate is 23.9774 (Radeon 5570). I've used Reclock for the past year or two and recently stopped using it because I found it was unnecessary.

If you really don't want to use reclock, you can play around with custom resolutions to alter the timings to get the refresh rate closer to the target 23.976. As you can see, you don't need the refresh rate to be perfect.

Here's some reading for you:
http://www.anandtech.com/show/4380/discrete-htpc-gpus-shootout/5
http://www.avsforum.com/avs-vb/showthread.php?p=20430210&highlight=custom+resolution#post20430210
http://www.avsforum.com/avs-vb/showthread.php?p=20664433&highlight=custom+resolution#post20664433
http://www.avsforum.com/avs-vb/showthread.php?p=21039739&highlight=custom+resolution#post21039739

[THX-UltraII]

ATI is more accurate 'out-of-the-box' than Nv with refresh rates. I can go a whole movie without a single dropped frame without reclock and my refresh rate is 23.9774 (Radeon 5570). I've used Reclock for the past year or two and recently stopped using it because I found it was unnecessary.

If you really don't want to use reclock, you can play around with custom resolutions to alter the timings to get the refresh rate closer to the target 23.976. As you can see, you don't need the refresh rate to be perfect.

Here's some reading for you:
http://www.anandtech.com/show/4380/discrete-htpc-gpus-shootout/5
http://www.avsforum.com/avs-vb/showthread.php?p=20430210&highlight=custom+resolution#post20430210
http://www.avsforum.com/avs-vb/showthread.php?p=20664433&highlight=custom+resolution#post20664433
http://www.avsforum.com/avs-vb/showthread.php?p=21039739&highlight=custom+resolution#post21039739

THis is great and just the solution I was looking for! I ll try this tonight. If this works, I don t need ReClock.

[kennae]

With reclock, should I use 24.000 or 23.976 for monitor when watching typical 23.976 material reclock being set to "AUTO"? I can get close to both Hz's but not sure what to use. Sorry for OT, but you guys were speaking about it anyway. :)
I tested both ways, even without reclock, but I want to be sure.

[SamuelMaki]

With reclock, should I use 24.000 or 23.976 for monitor when watching typical 23.976 material reclock being set to "AUTO"? I can get close to both Hz's but not sure what to use. Sorry for OT, but you guys were speaking about it anyway. :)
I tested both ways, even without reclock, but I want to be sure.

23.976. It is closer (even if its not 23.976) than 24.000... I recommend to use madVR internal frequency- switcher and put there all the max resolution frequencys that your TV/projector supports... Then it chooses the best for each media file...

[kennae]

23.976. It is closer (even if its not 23.976) than 24.000... I recommend to use madVR internal frequency- switcher and put there all the max resolution frequencys that your TV/projector supports... Then it chooses the best for each media file...

Been using it when it came out, AutoFrequency before that. I have 24p/50p/59p/60p available and everything works great.

Thanks for clearing this up.