madVR - high quality video renderer (GPU assisted)

[xv]

fullrange and height problem is libav/ffmpeg only. The height problem is also only with 4:4:4.
I found the problem for the crashes with "many files" (I tried files from my test dir that contained a lot of 4:4:4 ones): madVR/ffdshow crashes with 4:4:4 files if ffdshow output is RGB, if ffdshow output is YV12 image is a mess (just some colorful changing horizontal lines), older madVR or other renderer works fine.

Found another problem: Intel decoder cannot decode 4:4:4, but madVR accepts connection.

Example files:
4:4:4 YUV: http://www.mediafire.com/?byy5zyv46wrdmru
Internal ffmpeg has chroma plane offset, has ffdshow problem described above, other renderers work.
4:2:0 YCgCo: http://www.mediafire.com/?6mupk5zvxv7og17
Crashes internal ffmpeg (fullrange)
4:4:4 YCgCo: http://www.mediafire.com/?i57edq05b6s6e47
Crashes internal ffmpeg (fullrange), has ffdshow problem described above, other renderer works fine.
RGB: http://www.mediafire.com/?cnhaaej2p11wlub
Crashes internal ffmpeg (fullrange), has ffdshow problem described above, other renderer works fine.

Also found another problem: madVR cannot decode H.264 for some mp4 files (lavsplitter and mpc internal tested) correctly, Intel decoder seems to work (seeking is broken), ffmpeg/libav does not seem to work at all for some files. After remuxing to mkv it works.

[egandt]

Tested with Zoomplayer 8.0RC2 I can use MADVR for decoding (which seems to work fine as all as I select madvr as the render and decoder), but if I do so there are no sub-titles displayed, I noticed in a previous post it was commented upon that you might be adding them in the future, does that mean that as it is configured today, subtitles will not work when using the internal decoders? I ask because I watch a lot of softsubbed movies and Anime, normally in the form ASS, but SRT is also a possibility, I use directvobsub (currently 2.40.3093) to handle these subtitles.


Also, just because it does not get said enough, great job, and thanks for your hard work.
ERIC

[Hypernova]

I'm confused. What's this about MadVR decoding? I tried with latest MPC-HC and do not see any decoding options (x264 in MKV)? All I get is MS DTV decoder if I block all my filters.

It's in madVR option. Folder "Processing"

[pankov]

madshi,
I've managed to do a quick test of the new 0.67 version and I have a bug to report:
when I start the playback directly in fullscreen there is audio and video but ZoomPlayer is not responding and I can't go out of exclusive mode ... or do anything else - windows is not responsive except for Ctrl+Alt+Del. Luckily there is a "Guard dog" in ZoomPlayer MAX and after the configured time it restarts the player. This did not happen with 0.66 and the only thing I did was to copy the new files over and re-register the filter using install.bat.

Now about the new decoders:
They work but I can't see myself using them because of lack of deinterlacing and subtitles support (no way to insert DirectVobSub or FFDShow's subtitles filter which are currently the only two ways to have subs in ZoomPlayer).

[Thunderbolt8]

thanks for the new version.

regarding the "delay playback start until render queue is full", I definately like to have it at the beginning of the movie, but I agree that there should be an option to disable it for seeking if desired. sometimes you just want to seek through the movie, because you are looking for something and then you mostly want to be able to do this as fast as possible.

as for vc-1, I'm for anything which improves it (speedwise), especially anything which improves decoding speed of interlaced vc-1, because that seems to require quite more ressources as the average AVC stuff, and often my system struggles with it (is multic core decoding actually supported here? afaik thats not the case with the other directshow decoders, so there could be some easy performance gain in there).

edit: ok, how can I actually see that these decoders are working right now? Im on windows 7. Is there any additional entry in the mph-hc > filters menu at playback?

btw. do these decoders work together with ffdshow stuff like postprocessing settings or others? so far, Ive always had ffdshow running with e.g. coreavc to accept raw video input and then apply stuff like sharpening. is this still possible? if not, would it be possible to add this then, otherwise, at least for me, I wouldnt be able to use these decoders as long as I dont have a display which can play back the content at an 1:1 pixel ratio.

[oddball]

It's in madVR option. Folder "Processing"


Ah yeah. Found it. It's nice. But I lose ffdshow for processing video in the chain which I use for filters only so back to CUVID for me.

[pankov]

madshi,
I'm sorry but I made a mistake and my report is not entirely true. After a few more tests here are more details:
the problem happens only if I try to go out of fullscreen mode while madVR is in Exclusive mode. If madVR is in Windowed mode there is no problem to "unzoom". The problem is present in v0.66 too.
Here is a log file showing the problem with v0.67
http://www.mediafire.com/?350vxa2lsgu2ib0
I've started a movie, waited a couple of seconds and then double-clicked the video window to go out of fullscreen mode but nothing happened. Since that moment I tried different keyboard shortcuts (Ctrl+Shif+Esc; Windows button; Ctrl+J and others) to make ZoomPlayer/madVR go out of Exclusive mode but nothing helped until just after 20 seconds when ZP's Gurad dog restarted the player.

[cyberbeing]

madshi, can you update madVR [benchmark] to 0.67 so we can get an idea of how the built-in decoders perform on our systems?

Not really a functional limitation, but the Intel decoder shows significantly higher CPU load decoding h264 compared to ffmpeg/libav on an AMD X2.

Edit: madVR obviously no longer works with VSFilter either when the built-in decoders are enabled. Any further thoughts about hacking the VSFilter connection to make it work, or will we just be stuck using ISubRender for subtitles when the built-in decoders are enabled?

Edit2: There is a bug which causes madVR to display a Black Screen indefinitely when first opening a video and the built-in decoders and refresh rate changer are enabled. Re-opening the video after the refresh rate has changed is a workaround. Disabling of the Delay till Render Queue is Full option makes no difference.

Debug Log: http://www.mediafire.com/?wg8ncuhmwdgytic

Edit3: Are you able to max out the merit of the internal decoders? The 0x00800200 merit of CoreAVC (set to preferred) and the crazy 0xff800001 merit of FFDShow cause them to get used instead.

[Hypernova]

Madshi, it seems the subtitle will disappread only if the OSD (Ctrl+J) is on. Otherwise it stays.

[azaze1]

MPC-HC crashes for me now when choosing madVR renderer. If I move to EVR Custom Pres, it's fine. It was hit or miss all day, but towards the end of the day, launch any x264 mkv with madVR as output renderer crashes mpc-hc upon launch.

info: Windows 7 32bit
nvidia: GT 430 (275.33 drivers)
LAV Splitter 0.30
LAV CUVID 0.9 (tried other decoders too, mpc-hc internal, cyberlink's from pdvd 11, etc)
latest nightly MPC-HC x86, actually tried a few thinking it may have been that, no dice.

Sorry if this is not an issue with madVR, but it's brand new behavior after unregistering 0.66 and registering 0.67. I noticed the properties of the renderer options still said 0.66 after I unregistered and registered the 0.67. Only after I unregistered and re-registered for a 2nd time did it say 0.67 in properties. But the crashing occurred ever since the first upgrade attempt.

[ryrynz]

Love the new stats display.

madshi, can you update madVR [benchmark] to 0.67 so we can get an idea of how the built-in decoders perform on our systems?

Seconded.

[Mikey2]

Wow, thanks for this fascinating update! I did about 30 minutes worth of testing, without trying to specifically break things and find boundary conditions, I found that the core functionality seems to work for me! (Relevant info: Intel Q6600 Quad, NVidia 8600 GT, Windows 7 x64, MPC-HC 1.5.2.3329, tried both LAV Splitter and Haali (LAV worked more smoothly, but then it always has on my system,) and ReClock to a Pioneer Kuro 50" Plasma (accepting RGB 0-255 ...primary display.) I focused on ffmpeg on 1080p h.264 movies.

I think I had less problems since because of my good CPU and out-dated GPU I switched to software decoding a while back. However, this brings up a question: I switched to Software Decoding (ffdshow) because from what I understood, as long as one is not doing any post-processing, it does not matter where the decoding is done (neither the filter itself nor its processing location, such as using GPU-located Cuda in CoreAVC.) In other words, I thought "decoding" was a mathematical process that will yield the same results, simply taking a file such as H.264 file and converting to a 4CC code (such as YV12.)

If this is the case, what is the advantage of doing it on your filter rather than on a separate filter where we have the option to do post-processing?

Does this have to do with the 8Bit+ color processing?

If so, can I expect to see any picture-quality improvements right now?

If not, are there any performance enhancements in doing the decoding and rendering within your filter rather than via a separate filter?

Oh, and two more observations:

1) As was mentioned earlier, I was also seeing some issues with ReClock. If the video was not previously played in ReClock (using a different decoder,) ReClock is reporting that it is refreshing based on the default frame-rate (as set in ReClock's settings panel.) However, if it was already played and the frame-rate was already in its database, then it was correctly reporting the correct fps. (Still, it was a little weird, it only reported the fps and not the FOURCC code as it does on other files.) I can show you screenshots if you would like...For now as a workaround I am going to play the file using ffdshow as the decoder first (until the framerate is confirmed by reclock and added to their database. (This is shown when the clock icon switches from blinking red/green to a solid green.) Only then will I block ffdshow and use your decoder...

2) This brings me to an annoyance that has existed for some time: Can you possibly enable the filter to make configuration changes without already playing a video? This is the only DirectShow filter (that I know-of) that does not allow this. I never minded it too much in the past, but with significant functional changes such as using a decoder or not as an option, I would like to make those selections without already playing something. (Heck, it can even be an issue to some people in the future if they only have their systems configured to use madVR as the decoder - one cannot even turn the decoder on before using some other decoder just to play a video and get into the setting screen in the first place!

Anyway, I will echo other comments here: I LOVE this sort of transparent development. As a software engineer myself, I find myself too often stifled from my most creative ideas because of the constraints placed by normal software development. (E.g. this release would never fly in a normal release world, but you have a bunch of super-intelligent nerds here that love this stuff and are happy to play with new functionality, even if it isn't perfect yet. Involving us right from the start (and actually listening to us) is a big part of why I think this is by far the best renderer out there.

Thanks again!
MikeY

[madshi]

You're the man for audio renderer; stop saying you're not interested; think a little bit at others instead of being selfish ! :)
Haha! I simply don't have enough time. If I did start working on audio, madVR would suffer. So no, I have no plans working on the audio side of things.

Madshi, if you can have MadVR decode MPEG2, can you not go all the way and have it work with DVDs?
Because making DVDs work is not as easy as it sounds. It's on my to do list, as are many other things.

Yes. For instance, if I set madVR to present 8 frames in advance, the OSD shows "8-8/8". If I use ffdshow, it fluctuates, but never goes higher than "7-8/8".
Ah ok, well, this difference is really minor. I'd say 7-8 is pretty much the same as 8.

Tried with Haali, LAVSplitter, and MPC-HC's internal splitter with no change.

Well, the only VC-1 files I have are from Blurays, and most are letter-boxed. But I did find four that are not letter-boxed, and they all showed the same corrupted image.
Ah yes, I can reproduce it. It only happens with libav/ffmpeg, but not with Intel, correct?

libav/ffmpeg for h264 works fluid and doesn't drain a lot CPU power but it shows animated subtitles (.ASS files) slightly laggy and also a bit timed off. It gets very confusing on fast scenes, because the subs aren't 100% timed right with libav/ffmpeg.
This is caused by the bad libav decoder timestamps in the current madVR version. This will be fixed in a future version.

2. The combination of Intel decoder+unchecked delay playback will usually crash MPC-HC on my setup after a couple successive seekings.
Ok, will check that.

Also, the a/v unsynced problem on h264 with avi when using multithread is presented with both libav/ffmpeg and Intel decoder. This make me wonder since isn't this supposed to me libav/ffmpeg only bug?
I don't know. Do you have a sample which shows this problem clearly and quickly?

Also the new yCMS seems to be giving better results than in the last version. (not sure if you and yesgrey changed anything around)
yCMS hasn't changed for months. But the way madVR uses yCMS has changed. 2-3 versions ago madVR/yCMS were pretty much broken. Now it should work fine again, so maybe that's the "improvement" you're seeing? Or is it better than e.g. 5 versions ago, too?

@cyberbeing, have you done your yCMS comparison (before/after the changes I introduced)? What did you find?

Well the issue with the ques running out with the one option checked still extists.
There's probably not much I can do about that. Seems to be an issue with the GPU drivers.

fullrange and height problem is libav/ffmpeg only. The height problem is also only with 4:4:4.
I found the problem for the crashes with "many files" (I tried files from my test dir that contained a lot of 4:4:4 ones): madVR/ffdshow crashes with 4:4:4 files if ffdshow output is RGB, if ffdshow output is YV12 image is a mess (just some colorful changing horizontal lines), older madVR or other renderer works fine.

Found another problem: Intel decoder cannot decode 4:4:4, but madVR accepts connection.

Example files:
4:4:4 YUV: http://www.mediafire.com/?byy5zyv46wrdmru
Internal ffmpeg has chroma plane offset, has ffdshow problem described above, other renderers work.
4:2:0 YCgCo: http://www.mediafire.com/?6mupk5zvxv7og17
Crashes internal ffmpeg (fullrange)
4:4:4 YCgCo: http://www.mediafire.com/?i57edq05b6s6e47
Crashes internal ffmpeg (fullrange), has ffdshow problem described above, other renderer works fine.
RGB: http://www.mediafire.com/?cnhaaej2p11wlub
Crashes internal ffmpeg (fullrange), has ffdshow problem described above, other renderer works fine.
Thanks!!

Also found another problem: madVR cannot decode H.264 for some mp4 files (lavsplitter and mpc internal tested) correctly, Intel decoder seems to work (seeking is broken), ffmpeg/libav does not seem to work at all for some files. After remuxing to mkv it works.
Can I have a sample for that, too, please?

Tested with Zoomplayer 8.0RC2 I can use MADVR for decoding (which seems to work fine as all as I select madvr as the render and decoder), but if I do so there are no sub-titles displayed, I noticed in a previous post it was commented upon that you might be adding them in the future, does that mean that as it is configured today, subtitles will not work when using the internal decoders?
When using ZoomPlayer and the internal madVR decoders, subtitles will not work, because ZoomPlayer doesn't have its own subtitle rendering engine. So if you need subtitles and want to use ZP, you should use external decoders for now.

Now about the new decoders:
They work but I can't see myself using them because of lack of deinterlacing and subtitles support (no way to insert DirectVobSub or FFDShow's subtitles filter which are currently the only two ways to have subs in ZoomPlayer).
Yes, in your situation the internal decoders don't make much sense at the moment.

regarding the "delay playback start until render queue is full", I definately like to have it at the beginning of the movie, but I agree that there should be an option to disable it for seeking if desired.
More opinions on that, anybody?

as for vc-1, I'm for anything which improves it (speedwise), especially anything which improves decoding speed of interlaced vc-1, because that seems to require quite more ressources as the average AVC stuff, and often my system struggles with it (is multic core decoding actually supported here? afaik thats not the case with the other directshow decoders, so there could be some easy performance gain in there).
libav/ffmpeg doesn't support interlaced VC-1 decoding at all. You could try whether the Intel decoder decodes interlaced VC-1 faster than the MS VC-1 decoder does. Does it?

edit: ok, how can I actually see that these decoders are working right now? Im on windows 7. Is there any additional entry in the mph-hc > filters menu at playback?
You can see that by the lack of any video decoder in the filters list. If you don't see any external decoder there, then it must be madVR doing the decoding.

btw. do these decoders work together with ffdshow stuff like postprocessing settings or others? so far, Ive always had ffdshow running with e.g. coreavc to accept raw video input and then apply stuff like sharpening. is this still possible? if not, would it be possible to add this then, otherwise, at least for me, I wouldnt be able to use these decoders as long as I dont have a display which can play back the content at an 1:1 pixel ratio.
If you want to use ffdshow processing then the internal decoders don't make much sense for you.

Ah yeah. Found it. It's nice. But I lose ffdshow for processing video in the chain which I use for filters only so back to CUVID for me.
Yes.

the problem happens only if I try to go out of fullscreen mode while madVR is in Exclusive mode. If madVR is in Windowed mode there is no problem to "unzoom". The problem is present in v0.66 too.
It seems that it's ZP which is frozen in this situation? Have you asked Blight for help? It might be more of a ZP problem, but I'm not sure...

madshi, can you update madVR to 0.67 so we can get an idea of how the built-in decoders perform on our systems?
Yeah, will do that with the next build. Will need to double check that the benchmark works correctly with the internal decoders, too.

Not really a functional limitation, but the Intel decoder shows significantly higher CPU load decoding h264 compared to ffmpeg/libav on an AMD X2.
Yeah, that's my impression as well. How about VC-1 and MPEG2 performance of the Intel decoders, compared to other decoders?

Edit: madVR obviously no longer works with VSFilter either when the built-in decoders are enabled. Any further thoughts about hacking the VSFilter connection to make it work, or will we just be stuck using ISubRender for subtitles when the built-in decoders are enabled?
For now, if you want to use the internal decoders, you're stuck with the internal subtitle render engings of MPC-HC, KMPlayer, PotPlayer and J.River MC16. Which I don't consider too much of a problem because these engines produce higher quality subtitle rendering compared to VSFilter, at least for SD content. Or is there any big disadvantage of the internal MPC-HC etc subtitle engines, compared to VSFilter?

Edit2: There is a bug which causes madVR to display a Black Screen indefinitely when first opening a video and the built-in decoders and refresh rate changer are enabled. Re-opening the video after the refresh rate has changed is a workaround. Disabling of the Delay till Render Queue is Full option makes no difference.
Ok, will check if I can reproduce that.

Madshi, it seems the subtitle will disappread only if the OSD (Ctrl+J) is on. Otherwise it stays.
Correct. Basically the subtitles disappear if the same frame is redrawn in paused state. That's not really a bug in madVR, it's a bug in the VSFilter implemention used by MPC-HC. I could avoid it by storing all frames in the decoder queue twice, but that would double the memory usage.

MPC-HC crashes for me now when choosing madVR renderer. If I move to EVR Custom Pres, it's fine. It was hit or miss all day, but towards the end of the day, launch any x264 mkv with madVR as output renderer crashes mpc-hc upon launch.
Can you retry v0.66, just to make sure that it's a new problem introduced by v0.67? Thanks.

However, this brings up a question: I switched to Software Decoding (ffdshow) because from what I understood, as long as one is not doing any post-processing, it does not matter where the decoding is done (neither the filter itself nor its processing location, such as using GPU-located Cuda in CoreAVC.) In other words, I thought "decoding" was a mathematical process that will yield the same results, simply taking a file such as H.264 file and converting to a 4CC code (such as YV12.)

If this is the case, [B]what is the advantage of doing it on your filter rather than on a separate filter where we have the option to do post-processing?

Does this have to do with the 8Bit+ color processing?

If so, can I expect to see any picture-quality improvements right now?
There's no quality difference to be expected with normal 8bit 4:2:0 content. However, right now no external decoder can decode high bitdepth or 4:2:2/4:4:4 content and pass it on to madVR without quality loss. But then, LAV Video Decoder is going to be released soon which will do all that.

If not, are there any performance enhancements in doing the decoding and rendering within your filter rather than via a separate filter?
There might be very small performance improvements, but right now the whole chain is brand new and not very much optimized yet, so you probably won't see better performance at this point in time. Not sure if there will ever be a *measureable* performance advantage in the future.

Still, it was a little weird, it only reported the fps and not the FOURCC code as it does on other files.
The decoded FOURCC is not known to Reclock because the FOURCC conversion stuff is all done internally in madVR.

This brings me to an annoyance that has existed for some time: Can you possibly enable the filter to make configuration changes without already playing a video? This is the only DirectShow filter (that I know-of) that does not allow this.
It annoys me, too, sometimes. It's just a question of where to spend my programming time.

[Hypernova]

About the subtitle: I see. Thank you for clarification

About a sample, I'll quote my post in ffdshow thread:

I don't know if I did any wrong but only the first part seem to playable after splited by DGSplit. Please use the second half where the karaoke appear to see the lag.

http://www.mediafire.com/?9jf19139i6e0uh2

It supposed to be libav/ffmpeg only, so if Intel decoder has the same problem maybe it give some clues for ffmpeg developers?

[ForceX]

thanks for the new version.

regarding the "delay playback start until render queue is full", I definitely like to have it at the beginning of the movie, but I agree that there should be an option to disable it for seeking if desired. sometimes you just want to seek through the movie, because you are looking for something and then you mostly want to be able to do this as fast as possible.

I also agree with this.

So far my only real issue has been with subtitles blinking while using the internal libav decoder, but it's still nice to have a good 10bit decoder. I expect the fansubbers to move to Hi10P. I hope to see a libass-based sub renderer from you in the future. :cool:

[madshi]

It supposed to be libav/ffmpeg only, so if Intel decoder has the same problem maybe it give some clues for ffmpeg developers?
Don't know, I'll see what I'll find out.

So far my only real issue has been with subtitles blinking while using the internal libav decoder
That should be fixed in a future version.

[Hprd]

Yeah, i was thinking of saying it might be my end (as now that i think of it, ever since updating to 275 quadro drivers i've seen this issue, which was about when .63/64 came out), but just kinda wanted a response from you.

Anyhow, keep up the good work then!

[cyberbeing]

Or is there any big disadvantage of the internal MPC-HC etc subtitle engines, compared to VSFilter?

The internal MPC-HC subtitle filter is much slower, which can make using pre-buffering cause lots of flickering with complex subs on slower computers. It seems it can flicker even when pre-buffering is disabled as well. Other than general slowness/flickering, I'm not the best person to ask, but I remember it having issues in the past causing it to produce non-identical output compared to VSFilter with certain subtitles. It could be better now, I don't really know. If you go on IRC #cccp @ irc.rizon.net or #aegisub @ irc.rizon.net someone may be able to give you a better idea of the current issues it has (another option would be making a post on AnimeSuki in the Fansub Groups board).

Bug: Just now I discovered a bug in madVR 0.67 which causes stuttering with moving subtitles which doesn't exist in VMR9. It only happens when the madVR ffmpeg decoder is enabled, so it may have to do with the bad timestamp problem you spoke of?

Another Bug: madVR crashes with the Intel Decoder and 10-bit H264.

[madshi]

The internal MPC-HC subtitle filter is much slower, which make using prebuffering cause lots of flickering with complex subs. It can flicker even when prebuffering is disabled. Other than general slowness/flickering, I'm not the best person to ask, but I remember it having issues in the past causing it to produce non-identical output compared to VSFilter with certain subtitles. It could be better now, I don't really know. If you go on IRC #cccp @ irc.rizon.net or #aegisub @ irc.rizon.net someone may be able to give you a better idea of the current issues it has (another option would be making a post on AnimeSuki in the Fansub Groups board).
Well, I'll keep that in mind for later.

Bug: Just now I discovered a bug in madVR 0.67 which causes stuttering with moving subtitles which doesn't exist in VMR9. It only happens when the madVR ffmpeg decoder is enabled, so it may have to do with bad timestamp problem you spoke of?

Another Bug: madVR crashes with the Intel Decoder and 10-bit H264.
Yes, the stuttering should hopefully be fixed once I implement proper timestamp handling. And the 10bit Intel crash will be fixed in the next build, too.

[cyberbeing]

madshi, would it be possible to make it so madVR configuration can be launched without playing a video?

[madshi]

Possible, yes, but it costs time developing it.

[pankov]

...
It seems that it's ZP which is frozen in this situation? Have you asked Blight for help? It might be more of a ZP problem, but I'm not sure...


Yes, it seems so but then again why doesn't showing the start menu work? I thought madVR had some special code for catching this key and exiting fullscreen exclusive mode on its own. I was just hoping that if you can reproduce it you'll be able to fix it.
Despite this I'll try to contact Blight but I don't have much hope, cause he hasn't been active in the past few weeks/months.

[cyberbeing]

I guess that means it's not as simple as allowing rundll32.exe madvr.ax,configure to launch the settings dialog in the standard way, as other filters do. Indeed, if it takes more then a couple minutes to implement, other more important things should take priority. Maybe something for a madVR 1.0 release.

[madshi]

Despite this I'll try to contact Blight but I don't have much hope, cause he hasn't been active in the past few weeks/months.
Hasn't he recently released ZP 8.0 Beta/RC?

I guess that means it's not as simple as allowing rundll32.exe madvr.ax,configure to launch the settings dialog in the standard way, as other filters do. Indeed, if it takes more then a couple minutes to implement, other more important things should take priority. Maybe something for a madVR 1.0 release.
The problem is not starting the settings editor. The problem is that the settings editor gets the settings from a running madVR instance and not by loading the settings file. So I'd have to modify the settings editor to also be able to load/save the settings file directly. Not a big problem, but it costs time, especially if I want to support all the funny situations, like madVR video playback starting or stopping while the settings dialog is open.

Btw, have you had a chance yet to test the latest madVR/yCMS combination?

[cyberbeing]

Oh, I never realized only madVR.ax itself is able to read/write the registry and settings.dat, which would make what I suggested a bit more work to support.

That makes me wonder, was there a particular reason you separated important madVR functions across multiple files (madHcCtrl.exe, madHcNet.dll, mvrSettings.dll, and madVR.ax)? Easier development, debugging, and version control? Not that it really matters as long as it works. Maybe a better question is, 'Do all the madVR modules have well defined functions and roles they serve?', since I'm sensing there is some overlap.

Btw, have you had a chance yet to test the latest madVR/yCMS combination?

Nothing changed in madVR 0.67 compared to 0.66, correct? I've been using 0.66 with a 6-bit lut since it was released, but I've been afraid to do any measurements to see if colors were accurate. I'll get around to doing that eventually...

I'll need to get back to you on this, but one thing I've been noticing recently are weird maximum rendering time spikes, which cause delayed frames and the render queue to drop to 6-8/8 often. I'll need to do some testing to see if I can track down a cause. I'm almost suspecting it may have to do with a recent NVIDIA driver update, but maybe some other change which happened after madVR 0.61 is to blame. I'll make a post in the coming days with an update on this.

[pankov]

Hasn't he recently released ZP 8.0 Beta/RC?
In fact you are right - the last one was from 29.06.2011 but it had some non important (to me at least) stuff so I felt like a long time since some important changes were made to ZoomPlayer.

btw
I've just found out that starting task manager actually helps but usually I use Process Explorer as a replacement and it doesn't manage to bring ZP out of fullscreen. Is there anything you can do about that?

[madshi]

was there a particular reason you separated important madVR functions across multiple files (madHcCtrl.exe, madHcNet.dll, mvrSettings.dll, and madVR.ax)? Easier development
Yes. Writing GUIs in MSVC++ is like walking through hell. Writing GUIs in Delphi is like a walk in the park. madHcCtrl.exe (which contains the settings editor) in written in Delphi.

Do all the madVR modules have well defined functions and roles they serve?
Yes.

Nothing changed in madVR 0.67 compared to 0.66, correct? I've been using 0.66 with a 6-bit lut since it was released, but I've been afraid to do any measurements to see if colors were accurate. I'll get around to doing that eventually...
Interesting to see would be if measurements pick up any loss of accurateness with 6bit compared to 7bit and 8bit. Also interesting would be the comparison 8bit new version vs. 8bit old madVR/yCMS solution.

I've just found out that starting task manager actually helps but usually I use Process Explorer as a replacement and it doesn't manage to bring ZP out of fullscreen. Is there anything you can do about that?
I'm allowing both "taskmgr.exe" and "procexp.exe" to take madVR out of exclusive mode - but only if they are started in "Always on top" mode. Which is the Task Manager default, but just an option in the Process Explorer.

[pankov]

I'm allowing both "taskmgr.exe" and "procexp.exe" to take madVR out of exclusive mode - but only if they are started in "Always on top" mode. Which is the Task Manager default, but just an option in the Process Explorer.
Well, I tried "Always on top" in Process Explorer but it didn't manage to take madVR out of exclusive while taskmgr.exe does it every time. I also think that it'd be better to not require "always on top" but simply respect the z-order but all this is not important and I'll leave you do better things now.
btw
Just out of curiosity - are you able to reproduce the problem on your PC? If you don't have the time / the will to do it I'll understand. Just to let you know that other ZoomPlayer users are experiencing this problem so it's not only me this time. ... but I guess you already know that if you are following the madVR thread at the ZoomPlayer forum
http://forum.inmatrix.com/index.php?showtopic=10068&st=0

btw
I'm happy to tell you that after I moved to the 64bit version of Windows 7 the strange Access Violation when going to the next file vanished
:D

[cyberbeing]

For the next version of the madVR [benchmark], could you expand it to show minimum and maximum frame-rate in addition to the currently shown average frame-rate?

[Wile-E-Coyote]

Suddenly and for no apparent reason (cause I don't remember changing anything in the setup) I now have a picture filled with green horizontal lines when using madVR. I tried using LAV Cuvid and MPCs internal renderer for two very similar results.

I'm this close to throwing my laptop out the window... Back to EVR Custom until I can get it to work again.

[Carpo]

Having a strange issue here, every .mkv i have encoded with x264 2008, seems to upset madVR 0.67 (all before that rev are fine), but .066 was fine with them, also if i use EVR it plays fine, I am using madvr 0.67 with lav spliter + lav CUVID + Lav audio

http://img59.imageshack.us/img59/8082/madvr.th.jpg (http://imageshack.us/photo/my-images/59/madvr.jpg/)

Before anyone complains about the naming of the file, I have had to name it like that or XBMC wont pick up the information from the tvdb. At first i thought it was something i did (although I'm still open to a configuration error my end), mkvtools or even x264 itself, but after going back to 0.66 it was fine. Also plays fine on Mac and MPlayer.

Anyone else getting this issue or am I just the lucky one :p

edit: Wile-E-Coyote got in there before me as i was typing this, seems I'm not alone :D

edit2: updated x264, same happens, have noticed it is fine before i mux it with latest mkvtools, will drop back to 4.8.0 and try that

edit3: solved it, seems like its an issue with mkvtoolsnix and madVR, in mkvtoolsnix if you select the aspect ratio yourself, under the format specific options, madVR will output the image above, if you leave it as Display width/Height, madVR has no issue with the media

[someone`]

madshi , could you make libav/ffmpeg works with PotPlayer ? madVR libav/ffmpeg settings doesn't effect PotPlayer , PotPlayer uses the decoder configured in its filter setting page .

[ForceX]

madshi , could you make libav/ffmpeg works with PotPlayer ? madVR libav/ffmpeg settings doesn't effect PotPlayer , PotPlayer uses the decoder configured in its filter setting page .

In PotPlayer, go to Preferences> Filter Control> Video decoder> Filter Management> Add Registered Filter. Add madVR from the list, and check the H264 in the Video Decoder list of that page (MPEG2, AVC1 and VC1 should already be checked). Now you can select madVR for the appropriate video format, and it'll work.

[djsolidsnake86]

Having a strange issue here, every .mkv i have encoded with x264 2008, seems to upset madVR 0.67 (all before that rev are fine), but .066 was fine with them, also if i use EVR it plays fine, I am using madvr 0.67 with lav spliter + lav CUVID + Lav audio

http://img59.imageshack.us/img59/8082/madvr.th.jpg (http://imageshack.us/photo/my-images/59/madvr.jpg/)

Before anyone complains about the naming of the file, I have had to name it like that or XBMC wont pick up the information from the tvdb. At first i thought it was something i did (although I'm still open to a configuration error my end), mkvtools or even x264 itself, but after going back to 0.66 it was fine. Also plays fine on Mac and MPlayer.

Anyone else getting this issue or am I just the lucky one :p

edit: Wile-E-Coyote got in there before me as i was typing this, seems I'm not alone :D

edit2: updated x264, same happens, have noticed it is fine before i mux it with latest mkvtools, will drop back to 4.8.0 and try that

edit3: solved it, if you select the aspect ratio yourself, under the format specific options, madVR will output the image above, if you leave it as Display width/Height, madVR has no issue with the media

can't solve this, how solve?

[Carpo]

can't solve this, how solve?

edit2: updated x264, same happens, have noticed it is fine before i mux it with latest mkvtools, will drop back to 4.8.0 and try that

edit3: solved it, seems like its an issue with mkvtoolsnix and madVR, in mkvtoolsnix if you select the aspect ratio yourself, under the format specific options, madVR will output the image above, if you leave it as Display width/Height, madVR has no issue with the mediaa :rolleyes:

Meaning if you remux the files with mkvtoolsnix and select display height/width its will play fine, although i would use EVR and wait for madshi to fix it

[thuan]

edit3: solved it, if you select the aspect ratio yourself, under the format specific options, madVR will output the image above, if you leave it as Display width/Height, madVR has no issue with the media Sorry where is this setting? I am also having this problem with MPC-HC 3423 + LAVCUVID 0.9 + madVR 0.67 and I deleted 0.66 :confused:.

EDIT: NVM, got my answer in the post above.

[Carpo]

The setting is within mkvtoolsnix, it looks as if madVR 0.67 doesnt like the way the files were put together

edit: edited my previous post to make it a bit clearer, hope it helps :)

[madshi]

Suddenly and for no apparent reason (cause I don't remember changing anything in the setup) I now have a picture filled with green horizontal lines when using madVR. I tried using LAV Cuvid and MPCs internal renderer for two very similar results.

I'm this close to throwing my laptop out the window... Back to EVR Custom until I can get it to work again.
Does going back to v0.66 help?

Having a strange issue here, every .mkv i have encoded with x264 2008, seems to upset madVR 0.67 (all before that rev are fine), but .066 was fine with them, also if i use EVR it plays fine, I am using madvr 0.67 with lav spliter + lav CUVID + Lav audio
Can I have a sample, please?

[Carpo]

Can I have a sample, please?

i will remux it selecting the aspect ratio setting and will upload a sample asap

[djsolidsnake86]

it's a bug, need to be fixed

[dansrfe]

"Delay playback start until render queue is full" works very well for me. Seeking is somewhat faster and no dropped frames. I cannot see an appreciable difference in playback start time.

[Vern Dias]

I am having issues with madVR returning to exclusive mode when I return from a context menu on mpc-hc.

MPC-HC version 3329 (also fails on 3403)
madVR version dated 06/27
filter graph:

Default Directshow Device
madVR
Audio Switcher
FFDShow Video Decoder
FFDShow Audio Decoder ( running HDMI passthru audio)
DVD Navigator (Old QDVD.dll from XP)

The issue occurs about 80% of the time when returning from a right click context menu.

I have set up some custom aspect ratios inder the PanandScan context menu, (which doesn't seem to have any provision for short cut keys) so I use the right click context menu at the beginning of each DVD to set the proper dimensions for the aspect ratio.

Upon right clicking, the screen blacks momentarily (as it should) as the renderer switches out of exclusive mode. Then I make my selection of the desired AR and close the context menu. The scrren size alters, but most of the time, the switch back to exclusive mode either displays a black frame or a still of a previous frame with an image of the context menu still superimposed on it.

The audio continues to play during this. A restart of the player is required to recover.

Here is a snippet of the log for both a sucess and a failure of this issue:

***************Successful switch for context menu

00055853 Window CVideoRenderer::NonDelegatingQueryInterface() -> 80004002
00055868 Render Direct3D_CopyToBackbuffer() -> +
00055868 Render copied frame 1182 to back buffer 0 for vsync 1295 in 35 ms, plannedVSync: 1295
00055868 Render NextVSync: 1291, PresentQueueCount: 5, PresentQueuePresentCount: 4, PresentQueue[0].id, vsync, delay, presentId: 1178, 1291, 1, 0, [1].id, vsync, delay, presentId: 1179, 1292, 1, 0, [2].id, vsync, delay, presentId: 1180, 1293, 1, 0, [3].id, vsync, delay, presentId: 1181, 1294, 1, 0, [4].id, vsync, delay, presentId: 1182, 1295, 1, 0, [5].id, vsync, delay, presentId: 0, 0, 0, 0, [6].id, vsync, delay, presentId: 0, 0, 0, 0, [7].id, vsync, delay, presentId: 0, 0, 0, 0, [8].id, vsync, delay, presentId: 0, 0, 0, 0
00055868 Render Queue_UnlockItem();
00055868 Render Queue_RefreshEvents -> ItemCanBeAdded: -, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00055868 Render Queue.decoded: 8, uploaded: 8, rendered: 6, backbuffered: 1, presented: 4, PresentQueueCount: 5, PresentQueuePresentCount: 4
00055868 Render ids: 1177 1178 1179 1180 1181 1182 1183 1184, valid: ++++++++, marked: --------, locked: --------, uploaded: ++++++++, rendered: ++++++--, buffered: ++++++--, presented: +++++---, onScreen: +-------
00055868 Render Queue_UnlockItem() -> +
00055868 Render Direct3D_ResetDevice(width = 1920, height = 1080, modified = +, oldExclusive = +, newExclusive = -);
00055868 Render Osd_DisplayMessage(windowed, 2000)
00055868 Render Osd_DisplayMessage() -> +
00055868 Render Queue_LockAll();
00055868 Render Queue_RefreshEvents -> ItemCanBeAdded: -, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00055868 Render Queue.decoded: 8, uploaded: 8, rendered: 6, backbuffered: 1, presented: 4, PresentQueueCount: 5, PresentQueuePresentCount: 4
00055868 Render ids: 1177 1178 1179 1180 1181 1182 1183 1184, valid: ++++++++, marked: --------, locked: --------, uploaded: ++++++++, rendered: ++++++--, buffered: ++++++--, presented: +++++---, onScreen: +-------
00055868 Render Queue_LockAll() -> +
00055868 Render PresParams.BackBufferWidth: 1920, Height: 1080, Format: 22, Count: 3, MultiST: 0, Quality: 0, SwapEffect: 1, hDeviceWindow: 0004041C, Windowed: +, EnableADS: -, ADSFormat: 0, Flags: 0, RefreshRate: 0, PresentInterval: 1
00055868 Render display mode: 1920x1080, 23 Hz, progressive, 16

***************Failed switch back to exclusive mode

00063953 Render Queue_UnlockItem();
00063953 Render Queue_RefreshEvents -> ItemCanBeAdded: +, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00063953 Render Queue.decoded: 5, uploaded: 5, rendered: 0, backbuffered: 0, presented: 0, PresentQueueCount: 5, PresentQueuePresentCount: 4
00063953 Render ids: 1369 1370 1371 1372 1373 1367 1366 1365, valid: +++++---, marked: --------, locked: --------, uploaded: +++++---, rendered: --------, buffered: --------, presented: --------, onScreen: --------
00063953 Render Queue_UnlockItem() -> +
00063953 Render Queue_RefreshEvents -> ItemCanBeAdded: +, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00063953 Render Queue.decoded: 5, uploaded: 5, rendered: 0, backbuffered: 0, presented: 0, PresentQueueCount: 5, PresentQueuePresentCount: 4
00063953 Render ids: 1369 1370 1371 1372 1373 1367 1366 1365, valid: +++++---, marked: --------, locked: --------, uploaded: +++++---, rendered: --------, buffered: --------, presented: --------, onScreen: --------
00063954 Render Queue_LockItem(id: 1369);
00063954 Render Queue_LockItem() -> +
00063954 Render rendering frame 1369
00063954 Render Rendering_Render(step: 0, format: YV12, uploadedY: 0EAF1600, uploadedCbCr: 0EAF1720, uploadedYCbCr: 00000000, uploadedRGB: 00000000, target: 0EAF1860, start: 625904996);
00063954 Render Queue_UnlockItem();
00063954 Render Queue_RefreshEvents -> ItemCanBeAdded: +, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00063954 Render Queue.decoded: 5, uploaded: 5, rendered: 0, backbuffered: 0, presented: 0, PresentQueueCount: 5, PresentQueuePresentCount: 4
00063954 Render ids: 1369 1370 1371 1372 1373 1367 1366 1365, valid: +++++---, marked: --------, locked: --------, uploaded: +++++---, rendered: --------, buffered: --------, presented: --------, onScreen: --------
00063954 Render Queue_UnlockItem() -> +
00063954 Render Queue_RefreshEvents -> ItemCanBeAdded: +, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00063954 Render Queue.decoded: 5, uploaded: 5, rendered: 0, backbuffered: 0, presented: 0, PresentQueueCount: 5, PresentQueuePresentCount: 4
00063954 Render ids: 1369 1370 1371 1372 1373 1367 1366 1365, valid: +++++---, marked: --------, locked: --------, uploaded: +++++---, rendered: --------, buffered: --------, presented: --------, onScreen: --------
00063954 Decoder CCustomMemAllocator::GetBuffer();
00063954 Decoder CCustomMemAllocator::GetBuffer() -> +
00063954 Render Direct3D_ResetDevice(width = 1920, height = 1080, modified = +, oldExclusive = -, newExclusive = +);
00063954 Render Osd_DisplayMessage(exclusive, 2000)
00063954 Render Osd_DisplayMessage() -> +
00063955 Render Queue_LockAll();
00063955 Render Queue_RefreshEvents -> ItemCanBeAdded: +, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00063955 Render Queue.decoded: 5, uploaded: 5, rendered: 0, backbuffered: 0, presented: 0, PresentQueueCount: 5, PresentQueuePresentCount: 4
00063955 Render ids: 1369 1370 1371 1372 1373 1367 1366 1365, valid: +++++---, marked: --------, locked: --------, uploaded: +++++---, rendered: --------, buffered: --------, presented: --------, onScreen: --------
00063955 Render Queue_LockAll() -> +
00063955 Render PresParams.BackBufferWidth: 1920, Height: 1080, Format: 22, Count: 4, MultiST: 0, Quality: 0, SwapEffect: 1, hDeviceWindow: 0009039E, Windowed: -, EnableADS: -, ADSFormat: 0, Flags: 0, RefreshRate: 23, PresentInterval: 1
00063955 Render display mode: 1920x1080, 23 Hz, progressive, 16
00063956 Decoder CVideoRenderer::PrepareRender();
00063956 Decoder CVideoRenderer::PrepareRender() -> +
00063956 Decoder CVideoRenderer::DoRenderSample(ActualDataLength: 2949120);
00063956 Decoder CVideoRenderer::DoRenderSample(step 1);
00063956 Decoder CVideoRenderer::DoRenderSample(step 2);
00063956 Decoder CVideoRenderer::DoRenderSample(step 3);
00063956 Decoder CVideoRenderer::DoRenderSample(step 4);
00063956 Decoder Queue_AddFrame();
00063956 Decoder GetVih2 original media type:
00063956 Decoder AM_MEDIA_TYPE:
majortype: {73646976-0000-0010-8000-00AA00389B71}
subtype: {32315659-0000-0010-8000-00AA00389B71}
formattype: {05589f80-c356-11ce-BF01-00AA0055595A}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 2949120
cbFormat: 88
00063956 Decoder VIDEOINFOHEADER:
rcSource: (0,0)-(1440,960)
rcTarget: (0,0)-(1440,960)
AvgTimePerFrame: 400000
BITMAPINFOHEADER:
biSize: 40
biWidth: 2048
biHeight: 960
biPlanes: 1
biBitCount: 12
biCompression: YV12
biSizeImage: 2949120
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00063956 Decoder GetVih2 final output:
00063956 Decoder VIDEOINFOHEADER:
rcSource: (0,0)-(1440,960)
rcTarget: (0,0)-(1440,960)
AvgTimePerFrame: 400000
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 1440
dwPictAspectRatioY: 960
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 2048
biHeight: 960
biPlanes: 1
biBitCount: 12
biCompression: YV12
biSizeImage: 2949120
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00063956 Decoder Queue_AddFrame(vih2.width: 2048, height: 960) -> id: 1374, index: 5
00063956 Decoder Queue_PlanPresentation();
00063956 Decoder StartTime: 11318710000, RefClock->GetTime: 11946085208, QueryPerformanceCounter: 17108597175, PerfFreq: 14318180, frameDuration: 597179, nextTick: 17108616538
00063956 Decoder VSync_TimeLeft();
00063956 Decoder VSync_TimeLeft() -> + (-140552 microseconds)
00063956 Decoder step 1, nextVSync 1485, timeLeft -140552, frame vsyncs 1369: (1482.44-1482.44 1482 625904996), 1370: (1483.44-1483.44 1483 626322078), 1371: (1484.44-1484.44 1484 626739160), 1372: (1485.44-1485.44 1485 627156242), 1373: (1486.44-1486.44 1486 627573326), 1374: (1487.44-1487.44 1487 627990408)
00063956 Decoder VSync_TimeLeft();
00063956 Decoder VSync_TimeLeft() -> + (-140581 microseconds)
00063956 Decoder final, nextVSync 1485, timeLeft -140581, frame vsyncs 1369: (1482.44-1482.44 1482 625904996), 1370: (1483.44-1483.44 1483 626322078), 1371: (1484.44-1484.44 1484 626739160), 1372: (1485.44-1485.44 1485 627156242), 1373: (1486.44-1486.44 1486 627573326), 1374: (1487.44-1487.44 1487 627990408)
00063956 Decoder Queue_PlanPresentation() -> +
00063956 Decoder Queue_RefreshEvents -> ItemCanBeAdded: +, NoItemLocked: +, ItemCanBeUploaded: +, ItemCanBeRendered: +
00063956 Decoder Queue.decoded: 6, uploaded: 5, rendered: 0, backbuffered: 0, presented: 0, PresentQueueCount: 5, PresentQueuePresentCount: 4
00063956 Decoder ids: 1369 1370 1371 1372 1373 1374 1366 1365, valid: ++++++--, marked: --------, locked: --------, uploaded: +++++---, rendered: --------, buffered: --------, presented: --------, onScreen: --------
00063956 Decoder CVideoRenderer::DoRenderSample(step 5);
00063956 Decoder CVideoRenderer::DoRenderSample() -> +


If I go to windowed mode, eventually the player will crash with the following event log entry:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-07-17T14:36:43.000Z" />
<EventRecordID>7397</EventRecordID>
<Channel>Application</Channel>
<Computer>HTPC-2</Computer>
<Security />
</System>
- <EventData>
<Data>mpc-hc.exe</Data>
<Data>1.5.2.3329</Data>
<Data>4e13f53f</Data>
<Data>madVR.ax</Data>
<Data>0.66.0.0</Data>
<Data>4e088161</Data>
<Data>c000000d</Data>
<Data>0003488b</Data>
<Data>cac</Data>
<Data>01cc448ebc7a97d3</Data>
</EventData>
</Event>


I have a log of this as well, but it's almost a gig, so I obviously can't post it here.

I just love the video quality of madVR, so I hope this one issue can be resolved.....

Thanks, Vern

[madshi]

@Vern, can you try to create a smaller log with this problem in it, then zip it and upload it somewhere?

[Vern Dias]

I wish I could, but it takes a series of attempts to recreate it as the crash is quite intermittent.

Since this only occurs after the failure of the reset to exclusive mode, when I go to windowed mode by accident (double click on fullscreen), I suspect that the crash issue will go away if the switch to exclusive mode problem is fixed.... BTW, running in debug mode reduces the frequency of the reset to exclusive mode failure, so it could be a timing issue.

Here is the end of the log just before the crash:

****************** Stuff Deleted - crash upcoming


00247998 Render Osd_SetBitmap(name: madVR.internal.DebugOSD, leftEye: 00000000, posX: 0, posY: 0
00247998 Render Osd_SetBitmap(name: madVR.internal.SeekBar, leftEye: 00000000, posX: 0, posY: 0
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (66884 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (108587 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (150290 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (191992 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (233696 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (275399 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (317102 microseconds)
00247998 Render Queue_LockItem(id: 5565);
00247998 Render Queue_LockItem() -> +
00247998 Render copy frame 5565 to back buffer 0
00247998 Render Direct3D_CopyToBackbuffer(backbuffer: 0);
00247998 Render copying back buffer failed (exclusive mode)
00247998 Creator CVideoText::OnReceiveMessage(msg: f, wParam: 0, lParam: 0);
00247998 Creator CVideoText::OnReceiveMessage(WM_PAINT) -> +
00247998 Render Queue_UnlockItem();
00247998 Render Queue_RefreshEvents -> ItemCanBeAdded: -, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00247998 Render Queue.decoded: 8, uploaded: 8, rendered: 1, backbuffered: 0, presented: 0, PresentQueueCount: 0, PresentQueuePresentCount: 0
00247998 Render ids: 5565 5568 5569 5570 5571 5572 5573 5574, valid: ++++++++, marked: --------, locked: --------, uploaded: ++++++++, rendered: +-------, buffered: --------, presented: --------, onScreen: --------
00247998 Render Queue_UnlockItem() -> +
00247998 Render Queue_RefreshEvents -> ItemCanBeAdded: -, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00247998 Render Queue.decoded: 8, uploaded: 8, rendered: 1, backbuffered: 0, presented: 0, PresentQueueCount: 0, PresentQueuePresentCount: 0
00247998 Render ids: 5565 5568 5569 5570 5571 5572 5573 5574, valid: ++++++++, marked: --------, locked: --------, uploaded: ++++++++, rendered: +-------, buffered: --------, presented: --------, onScreen: --------
00247998 Render Osd_SetBitmap(name: madVR.internal.DebugOSD, leftEye: 00000000, posX: 0, posY: 0
00247998 Render Osd_SetBitmap(name: madVR.internal.SeekBar, leftEye: 00000000, posX: 0, posY: 0
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (66675 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (108377 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (150080 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (191783 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (233486 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (275189 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (316892 microseconds)
00247998 Render Queue_LockItem(id: 5565);
00247998 Render Queue_LockItem() -> +
00247998 Render copy frame 5565 to back buffer 0
00247998 Render Direct3D_CopyToBackbuffer(backbuffer: 0);
00247998 Render copying back buffer failed (exclusive mode)
00247998 Creator CVideoText::OnReceiveMessage(msg: f, wParam: 0, lParam: 0);
00247998 Creator CVideoText::OnReceiveMessage(WM_PAINT) -> +
00247998 Render Queue_UnlockItem();
00247998 Render Queue_RefreshEvents -> ItemCanBeAdded: -, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00247998 Render Queue.decoded: 8, uploaded: 8, rendered: 1, backbuffered: 0, presented: 0, PresentQueueCount: 0, PresentQueuePresentCount: 0
00247998 Render ids: 5565 5568 5569 5570 5571 5572 5573 5574, valid: ++++++++, marked: --------, locked: --------, uploaded: ++++++++, rendered: +-------, buffered: --------, presented: --------, onScreen: --------
00247998 Render Queue_UnlockItem() -> +
00247998 Render Queue_RefreshEvents -> ItemCanBeAdded: -, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00247998 Render Queue.decoded: 8, uploaded: 8, rendered: 1, backbuffered: 0, presented: 0, PresentQueueCount: 0, PresentQueuePresentCount: 0
00247998 Render ids: 5565 5568 5569 5570 5571 5572 5573 5574, valid: ++++++++, marked: --------, locked: --------, uploaded: ++++++++, rendered: +-------, buffered: --------, presented: --------, onScreen: --------
00247998 Render Osd_SetBitmap(name: madVR.internal.DebugOSD, leftEye: 00000000, posX: 0, posY: 0
00247998 Render Osd_SetBitmap(name: madVR.internal.SeekBar, leftEye: 00000000, posX: 0, posY: 0
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (66504 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (108207 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (149911 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (191614 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (233317 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (275021 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (316724 microseconds)
00247998 Render Queue_LockItem(id: 5565);
00247998 Render Queue_LockItem() -> +
00247998 Render copy frame 5565 to back buffer 0
00247998 Render Direct3D_CopyToBackbuffer(backbuffer: 0);
00247998 Render copying back buffer failed (exclusive mode)
00247998 Creator CVideoText::OnReceiveMessage(msg: f, wParam: 0, lParam: 0);
00247998 Creator CVideoText::OnReceiveMessage(WM_PAINT) -> +
00247998 Render Queue_UnlockItem();
00247998 Render Queue_RefreshEvents -> ItemCanBeAdded: -, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00247998 Render Queue.decoded: 8, uploaded: 8, rendered: 1, backbuffered: 0, presented: 0, PresentQueueCount: 0, PresentQueuePresentCount: 0
00247998 Render ids: 5565 5568 5569 5570 5571 5572 5573 5574, valid: ++++++++, marked: --------, locked: --------, uploaded: ++++++++, rendered: +-------, buffered: --------, presented: --------, onScreen: --------
00247998 Render Queue_UnlockItem() -> +
00247998 Render Queue_RefreshEvents -> ItemCanBeAdded: -, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00247998 Render Queue.decoded: 8, uploaded: 8, rendered: 1, backbuffered: 0, presented: 0, PresentQueueCount: 0, PresentQueuePresentCount: 0
00247998 Render ids: 5565 5568 5569 5570 5571 5572 5573 5574, valid: ++++++++, marked: --------, locked: --------, uploaded: ++++++++, rendered: +-------, buffered: --------, presented: --------, onScreen: --------
00247998 Render Osd_SetBitmap(name: madVR.internal.DebugOSD, leftEye: 00000000, posX: 0, posY: 0
00247998 Render Osd_SetBitmap(name: madVR.internal.SeekBar, leftEye: 00000000, posX: 0, posY: 0
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (66341 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (108044 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (149748 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (191451 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (233154 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (274858 microseconds)
00247998 Render VSync_TimeLeft();
00247998 Render VSync_TimeLeft() -> + (316561 microseconds)
00247998 Render Queue_LockItem(id: 5565);
00247998 Render Queue_LockItem() -> +
00247998 Render copy frame 5565 to back buffer 0
00247998 Render Direct3D_CopyToBackbuffer(backbuffer: 0);
00247998 Render copying back buffer failed (exclusive mode)
00248001 Decoder CCustomMemAllocator::GetBuffer();
00248001 Decoder CCustomMemAllocator::GetBuffer() -> +
00248002 Decoder CVideoRenderer::PrepareRender();
00248002 Decoder CVideoRenderer::PrepareRender() -> +
00248002 Decoder CVideoRenderer::DoRenderSample(ActualDataLength: 2949120);
00248002 Decoder CVideoRenderer::DoRenderSample(step 1);
00248002 Decoder CVideoRenderer::DoRenderSample(step 2);
00248002 Decoder CVideoRenderer::DoRenderSample(step 3);
00248002 Decoder CVideoRenderer::DoRenderSample(step 4);
00248002 Decoder Queue_AddFrame();
00248002 Decoder Queue_WaitReady(00000378, +);
00248101 Decoder Queue_WaitReady() -> +
00248101 Decoder VSync_TimeLeft();
00248101 Decoder VSync_TimeLeft() -> + (-36939 microseconds)
00248101 Decoder Queue_WaitReady(00000378, +);
00252407 Creator CVideoText::OnReceiveMessage(msg: f, wParam: 0, lParam: 0);
00252407 Creator CVideoText::OnReceiveMessage(WM_PAINT) -> +
00252407 Creator CVideoText::OnReceiveMessage(msg: 7e, wParam: 32, lParam: 70780800);
00252407 Decoder Queue_WaitReady() -> +
00252407 Decoder VSync_TimeLeft();
00252407 Decoder VSync_TimeLeft() -> + (-4342203 microseconds)
00252407 Decoder Queue_Delete(id: 5565);
00252407 Decoder Queue_RefreshEvents -> ItemCanBeAdded: -, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00252407 Decoder Queue.decoded: 7, uploaded: 7, rendered: 0, backbuffered: 0, presented: 0, PresentQueueCount: 0, PresentQueuePresentCount: 0
00252407 Decoder ids: 5568 5569 5570 5571 5572 5573 5574 5565, valid: ++++++++, marked: -------+, locked: -------+, uploaded: ++++++++, rendered: -------+, buffered: --------, presented: --------, onScreen: --------
00252407 Decoder Queue_Delete() -> +
00252407 Decoder VSync_TimeLeft();
00252407 Decoder VSync_TimeLeft() -> + (-4300524 microseconds)
00252407 Decoder Queue_Delete(id: 5568);
00252407 Decoder Queue_RefreshEvents -> ItemCanBeAdded: +, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +
00252407 Decoder Queue.decoded: 6, uploaded: 6, rendered: 0, backbuffered: 0, presented: 0, PresentQueueCount: 0, PresentQueuePresentCount: 0
00252407 Decoder ids: 5569 5570 5571 5572 5573 5574 5565 5568, valid: +++++++-, marked: ------+-, locked: ------+-, uploaded: +++++++-, rendered: ------+-, buffered: --------, presented: --------, onScreen: --------
00252407 Decoder Queue_Delete() -> +
00252407 Decoder VSync_TimeLeft();
00252407 Decoder VSync_TimeLeft() -> + (-4258842 microseconds)
00252407 Decoder Queue_Delete(id: 5569);
00252407 Decoder Queue_RefreshEvents -> ItemCanBeAdded: +, NoItemLocked: +, ItemCanBeUploaded: -, ItemCanBeRendered: +

Vern

[6233638]

Bug: with the "Delay playback start until render queue is full" enabled, DVD playback never starts. (is indefinitely paused)

Blu-ray playback is completely broken, using LAV filters/decoders. (have not tried new internal ones yet)

http://i.imgur.com/mL32wl.jpg

Log: http://www.mediafire.com/?wfhsc8w7etxd829
Madshi, if you can have MadVR decode MPEG2, can you not go all the way and have it work with DVDs?DVDs have been working in MadVR for some time now if you use LAV Splitters/Decoders instead of ffdshow and start the disc via the "open DVD" command in MPC-HC.

Unfortunately, I have yet to figure out how to get DVD subtitles working with this setup; as soon as you add ffdshow back into the chain, you get macrovision errors again.

Update: Enabling MPC-HC's internal "MPEG-2 Video" transform filter fixes subtitles.

[SamuriHL]

People really need to learn to use pastebin....good Lord.

[robpdotcom]

Yes. For instance, if I set madVR to present 8 frames in advance, the OSD shows "8-8/8". If I use ffdshow, it fluctuates, but never goes higher than "7-8/8".

Ah ok, well, this difference is really minor. I'd say 7-8 is pretty much the same as 8.

Just to better understand, and I believe you explained this before, but what would be the advantages/disadvantages of setting the present queue to a high number? Higher could reduce dropped frames, but slow down seeking, correct?

Well, the only VC-1 files I have are from Blurays, and most are letter-boxed. But I did find four that are not letter-boxed, and they all showed the same corrupted image.


Ah yes, I can reproduce it. It only happens with libav/ffmpeg, but not with Intel, correct?

Correct.

I also noticed with the "delay playback start until render queue is full" option checked: Toggling the remaining time in MPC-HC (Ctrl-I is the default shortcut, I believe) causes a brief "stuttering" glitch.

One other change since v0.66:

I've created some mkv's using segment linking. They will play clips from various files, and play them as though they were one file. Some of the files have different resolutions. Before v0.67, madVR played them just fine, but now I get a distorted image with green lines. Turning the "delay playback start until render queue is full" on or off makes no difference. I know it isn't normal to create files like this, so I'm not bothered by it, but I thought you might want to know. I've uploaded a sample: http://www.megaupload.com/?d=4AZ65FD0

Lastly, a while back you asked me for a sample of telecined material which I said was handled better by the ffdshow "pulldown removal" mod than it is by Dscaler. After I separated a small clip of the file, I'm not so sure I can still tell a difference. Anyway, the sample is also included in the link above.

[Wile-E-Coyote]

Does going back to v0.66 help?
Can't find the install files for0.66 on my hdd anymore... This really isn't my day :(

[leeperry]

Can't find the install files for 0.66http://www.videohelp.com/tools/madVR/old-versions#download

[Fer]

Hi madshi,

Please can you locate the new OSD within the area of a 21/9 aspect ratio screen like in previous versions. With the last versión the OSD is located in left up corner of a 16/9 screen and several lines are not easily seen.

Thank you so much.