madVR - high quality video renderer (GPU assisted)

[madshi]

With 0.33 I'm getting only one EC_VIDEO_SIZE_CHANGED message, but the application freezes after that message exactly at the same line as before. Now I can't even see the initial channel and the screen remains black so no frame has been processed.
IIRC, with the old version you could see the 1st TV station, but madVR stopped working when you switched to another station, is that right? And now with v0.33/0.34, you don't even see the 1st TV station, anymore? Do I understand that right? So it's worse than before? :(

[XPC]

IIRC, with the old version you could see the 1st TV station, but madVR stopped working when you switched to another station, is that right? And now with v0.33/0.34, you don't even see the 1st TV station, anymore? Do I understand that right? So it's worse than before? :(

Yes, that's right with v0.33. I'll try 0.34 now 0.34 and report the results.

[madshi]

HDMI 1.3 supports 120Hz refresh rates AFAIK, and I know someone who owns that cheapo Acer pj, he said that in 120Hz the Reclock tearing test was dead smooth.

It's not HDready, nor has an HDMI input, but the manual says that it does support 120Hz in 640*480/800*600/1024*800 over VGA
Who cares about 640*480 or 1024*800? We're in the age of Blu-Ray, which is 1920x1080. I'll not implement black frame insertion if it doesn't work for 1080p.

[XPC]

With 0.34 I got the same problem as 0.33

[madshi]

With 0.34 I got the same problem as 0.33
That's bad. Maybe instead of reducing the number of EC_VIDEOSIZE_CHANGED messages I should increase it? :D

But maybe this is good, after all? Maybe you can now reproduce it with a recorded movie file, too? Or does it still only happen with live TV?

[leeperry]

Who cares about 640*480 or 1024*800? We're in the age of Blu-Ray, which is 1920x1080. I'll not implement black frame insertion if it doesn't work for 1080p.
soon enough it will, it's only a matter of time...HDMI 1.3 and dual-link DVI support 120Hz and the manufacturers are running out of ideas to sell us new stuff, give it a bit and they'll all do 120Hz over HDMI 1.3. Acer/Viewsonic and Samsung already support it in XGA over VGA on many of their entry level DLP pj's.

AFAIK all the 3D-ready displays are forced to accept 120Hz input, like this 22" 1680x1050 LCD over dual-link DVI: http://www.hk.viewsonic.com/en/products/productspecs.php?id=349

http://www.pixelz.fr/f/1/2/6ea3ea7891f2ebb0fbaa648c8be07tt.jpg (http://www.pixelz.fr/f/1/2/6ea3ea7891f2ebb0fbaa648c8be07.png)

maybe they have the same in 1080p already, but if they don't...it's only a matter of time.

it'd be nice to have this feature after 1.0 is out IMHO.

[madshi]

soon enough it will, it's only a matter of time...
Probably. But now JVC also added black frame insertion to their projectors. So the question is: When the time has come that displays support 1080p120, won't they all do black frame insertion, too? If so, there's little reason to do it in madVR.

HDMI 1.3 and dual-link DVI support 120Hz
You're not making sense, leeperry. As I told you before, current HDMI chips are not fast enough for 1080p120. They might do 120Hz in some low resolutions, but not with 1080p.

AFAIK all the 3D-ready displays are forced to accept 120Hz input
Sorry, but that's total bull. How often do I have to repeat myself before you believe me? Maybe you should read the HDMI 1.4a 3D update PDF which is publically available. This is my last post on this topic. I have better things to do than repeating myself.

[leeperry]

JVC also added black frame insertion to their projectors. So the question is: When the time has come that displays support 1080p120, won't they all do black frame insertion, too? [..]
current HDMI chips are not fast enough for 1080p120.
goodie! but believe or not, there was a life before 1080p(and many BD's don't even use the full 1080p resolution). I'm sure the ppl who grab those cheap Acer pj's wouldn't mind getting black frame insertion, or the ppl using 1680x1050 LCD monitors in 120Hz dual-link DVI. TMDS doesn't require HDMI, and 120Hz is very real. Now if you only care for 1080p HDMI, fair enough. That was merely a suggestion, I don't see why 1080p/120 wouldn't be possible over dual-link DVI...but who cares.

[XPC]

That's bad. Maybe instead of reducing the number of EC_VIDEOSIZE_CHANGED messages I should increase it? :D

But maybe this is good, after all? Maybe you can now reproduce it with a recorded movie file, too? Or does it still only happen with live TV?

I still can't reproduce it with a recorded file. :(
When I maximize the window before opening the device it is still working OK. The only thing new I noticed then is some new messages:

MAD channels 2 1 samplerate 48000 8000
MAD channels 2 2 samplerate 48000 24000
MAD channels 2 2 samplerate 48000 22050
MAD channels 2 2 samplerate 48000 22050
MAD channels 2 2 samplerate 48000 24000
MAD channels 2 2 samplerate 48000 12000
MAD channels 2 2 samplerate 48000 11025
MAD channels 2 2 samplerate 48000 12000
MAD channels 2 2 samplerate 48000 16000
MAD channels 2 2 samplerate 48000 22050
MAD channels 2 1 samplerate 48000 24000
MAD channels 2 2 samplerate 48000 44100
MAD channels 2 1 samplerate 48000 44100
MAD MAD_ERROR_BADDATAPTRMAD channels 2 2 samplerate 48000 12000
MAD channels 2 2 samplerate 48000 44100
MAD channels 2 1 samplerate 48000 22050
MAD channels 2 1 samplerate 48000 32000
MAD channels 2 2 samplerate 48000 32000
MAD channels 2 2 samplerate 48000 11025
MAD channels 2 2 samplerate 48000 8000
MAD channels 2 2 samplerate 48000 22050
MAD channels 2 2 samplerate 48000 24000
MAD channels 2 2 samplerate 48000 22050
MAD channels 2 1 samplerate 48000 32000
MAD channels 2 2 samplerate 48000 24000
MAD MAD_ERROR_BADDATAPTRMAD channels 2 1 samplerate 48000 22050

(see below my old post with the results testing v0.32 and the exact line where the application freezes).


First test: Switching from 1440x1080 to 720x576 (SW_SHOWMAXIMIZED)
ResetMpeg2Decoder()
--> CMainFrame::OnGraphNotify on thread: 2732; event: 0x0000000a (EC_VIDEO_SIZE_CHANGED)
720x576
--> CMainFrame::OnGraphNotify on thread: 2732; event: 0x0000000a (EC_VIDEO_SIZE_CHANGED)
720x576
--> CMainFrame::OnGraphNotify on thread: 2732; event: 0x0000000e (EC_PAUSED)
ResetMpeg2Decoder()
The thread 'Win32 Thread' (0xfe8) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x10d0) has exited with code 1 (0x1).

CBaseVideoFilter::ReconnectOutput; wout = 720, hout = 576, current = 5x4, set = 16x9
--> CMainFrame::OnGraphNotify on thread: 2732; event: 0x0000000a (EC_VIDEO_SIZE_CHANGED)
720x576
--> CMainFrame::OnGraphNotify on thread: 2732; event: 0x0000000a (EC_VIDEO_SIZE_CHANGED)
720x576
--> CMainFrame::OnGraphNotify on thread: 2732; event: 0x0000000a (EC_VIDEO_SIZE_CHANGED)


Second test: Switching from 1440x1080 to 720x576 (fails here!)

ResetMpeg2Decoder()
--> CMainFrame::OnGraphNotify on thread: 2732; event: 0x0000000a (EC_VIDEO_SIZE_CHANGED)
720x576
--> CMainFrame::OnGraphNotify on thread: 2732; event: 0x0000000a (EC_VIDEO_SIZE_CHANGED)
720x576
--> CMainFrame::OnGraphNotify on thread: 2732; event: 0x0000000e (EC_PAUSED)
ResetMpeg2Decoder()
The thread 'Win32 Thread' (0x1694) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x8fc) has exited with code 1 (0x1).

CBaseVideoFilter::ReconnectOutput; wout = 720, hout = 576, current = 5x4, set = 16x9
--> CMainFrame::OnGraphNotify on thread: 2732; event: 0x0000000a (EC_VIDEO_SIZE_CHANGED)
720x576



I found the exact point where the application hangs in the second test: madVRAllocatorPresenter (Ln 233): pBV->GetVideoSize(&size.cx, &size.cy);

TDMETHODIMP_(SIZE) CmadVRAllocatorPresenter::GetVideoSize(bool fCorrectAR)
{
SIZE size = {0, 0};

if(!fCorrectAR)
{
if(CComQIPtr<IBasicVideo> pBV = m_pDXR)
pBV->GetVideoSize(&size.cx, &size.cy);
}
else
{
if(CComQIPtr<IBasicVideo2> pBV2 = m_pDXR)
pBV2->GetPreferredAspectRatio(&size.cx, &size.cy);
}

return size;
}

[Mangix]

madVR's downscaling algorithms should be superior to Haali + anisotropic. Actually I don't really see how anisotropic filtering would affect downscaling, anyway. But then I don't really know how Haali's scaling solution is implemented technically in detail.

no idea either. when downsizing i do notice that the text is very sharp and aliased with madvr's stock settings. softcubic on the other hand looks good but the text is more grayish than white(white text on black background). haali's renderer has the best of both worlds.

[JarrettH]

lol 1.0

there's really no significance to the version numbers in madvr :p

[Snowknight26]

There's a typo in net-protocol.txt. 'enpty' instead of 'empty.'

[fairchild]

Thanks for the awesome rendrer Madshi. I have a possible bug report for you. I love the implementation of separate devices with different settings, but I can't get this to work properly for me. I have 2 devices connected to my PC, an Acer AL2216W monitor connected through DVI which I want to have MadVR send it PC levels (0-255) and then I have a Sony KDL-32EX400 TV connected through DVI-HDMI cable that I want MadVR to send it TV levels (16-235).

Now what happens is, whenever I first setup a device (regardless of which it is, the initial setting which I set for the levels, are the ones that are loaded everytime. Even if switch the levels for my TV and set them to TV levels (16-235), and even though MadVR show's it's set to TV levels, it actually is rendering for me at PC levels (0-255) which were the ones I initially set.

I know because when watching an MP4 video clip with a brightness test pattern, the levels are always incorrectly set. I can click on PC levels, then hit apply, and nothing changes. Then I click back on TV levels and click apply and then it finally sets the right level.

I'm using the latest PotPlayer 32bit v1.5 (build 24796) and MadVR v0.34 my videocard which is feeding both my PC monitor and my HDTV is an ATI XFX HD 4890. Both devices are setup properly as Digital Monitor / TV

The only workaround I've found to do is just set both the devices to use TV levels. Then when I want to watch a movie on my PC monitor (which is the Acer), I just use a different media player and don't use MadVR (i use the 64-bit Potplayer with EVRCP renderer and have it do 0-255)

Let me know if you need anything else from me or any more info.

[madshi]

I don't see why 1080p/120 wouldn't be possible over dual-link DVI...but who cares.
Bandwidth. The current HDMI chips aren't fast enough. They can't do the full theoretical bandwidth set as "max bandwidth" in the HDMI specs.

I still can't reproduce it with a recorded file. :(
When I maximize the window before opening the device it is still working OK. The only thing new I noticed then is some new messages
Funny. "MAD" messages, but not coming from madVR/madFlac.

Hmmmm... Is the DirectShow filter chain (source, splitter, decoder) the same when watching live TV and when watching a recorded file? Or are there any differences?

no idea either. when downsizing i do notice that the text is very sharp and aliased with madvr's stock settings. softcubic on the other hand looks good but the text is more grayish than white(white text on black background). haali's renderer has the best of both worlds.
Can you post screenshots with Haali with and without anisotropic filtering vs. madVR? You know, madVR has more downsizing methods than just the default settings and SoftCubic. Have you tried the other settings, too?

P.S: Please don't attach the screenshots to the forum post, instead upload them to some external image host. Thanks.

lol 1.0

there's really no significance to the version numbers in madvr :p
What do you mean?

There's a typo in net-protocol.txt. 'enpty' instead of 'empty.'
Ah, thanks, will correct that.

Thanks for the awesome rendrer Madshi. I have a possible bug report for you. I love the implementation of separate devices with different settings, but I can't get this to work properly for me. I have 2 devices connected to my PC, an Acer AL2216W monitor connected through DVI which I want to have MadVR send it PC levels (0-255) and then I have a Sony KDL-32EX400 TV connected through DVI-HDMI cable that I want MadVR to send it TV levels (16-235).

Now what happens is, whenever I first setup a device (regardless of which it is, the initial setting which I set for the levels, are the ones that are loaded everytime. Even if switch the levels for my TV and set them to TV levels (16-235), and even though MadVR show's it's set to TV levels, it actually is rendering for me at PC levels (0-255) which were the ones I initially set.

I know because when watching an MP4 video clip with a brightness test pattern, the levels are always incorrectly set. I can click on PC levels, then hit apply, and nothing changes. Then I click back on TV levels and click apply and then it finally sets the right level.

I'm using the latest PotPlayer 32bit v1.5 (build 24796) and MadVR v0.34 my videocard which is feeding both my PC monitor and my HDTV is an ATI XFX HD 4890. Both devices are setup properly as Digital Monitor / TV

The only workaround I've found to do is just set both the devices to use TV levels. Then when I want to watch a movie on my PC monitor (which is the Acer), I just use a different media player and don't use MadVR (i use the 64-bit Potplayer with EVRCP renderer and have it do 0-255)

Let me know if you need anything else from me or any more info.
Hmmmmm... A few questions:

(1) How are your monitors set up? As "clone" or as "extended desktop"?
(2) Did madVR automatically detect both of your displays?
(3) When you disconnect the secondary display, does it go "gray" in the madVR settings dialog? (You need to close and reopen the settings dialog, after having disconnected.)
(4) When you want to playback on the secondary monitor, do you move the media player to the secondary monitor *before* loading the video file or after? With the current madVR version you need to move the media player window to the target monitor *before* loading the video file.

[fairchild]

Hmmmmm... A few questions:

(1) How are your monitors set up? As "clone" or as "extended desktop"?
(2) Did madVR automatically detect both of your displays?
(3) When you disconnect the secondary display, does it go "gray" in the madVR settings dialog? (You need to close and reopen the settings dialog, after having disconnected.)
(4) When you want to playback on the secondary monitor, do you move the media player to the secondary monitor *before* loading the video file or after? With the current madVR version you need to move the media player window to the target monitor *before* loading the video file.

1. Well through the ATI CCC, I just go to Desktops and Displays, then I have 3 options for the monitor/TV that I am going to switch to: Duplicate, Extend, or Replace. I just choose Replace. I have profiles setup for doing this quickly. Replace function basically disables the signal being sent to the other device. (the device that is not being used anymore loses it's signal and it goes into the powered down state) So the device that I hit Replace on, becomes the device where my videocard sends the signal to. (the desktop and everything)

2. When I first install MadVR and then first run it, MadVR will see whichever device I'm on first and only that device. So when I install MadVR for the first time on say the Acer monitor, it is the only device that MadVR sees. I then tell MadVR this device is a Monitor/TV and set the range I want on that device. Then when I switch to the second device (through the replace command in CCC) and run MadVR, it sees the new device and I do the same thing (specify it's a Monitor/TV and set the range). Once both devices have been recognized and setup, MadVR correctly knows which device it's on, and it grays out the other one. (but it still lets you change the levels or the 3dlut on the grayed out device, not that I have tried doing that)

3. Yes it's grayed out, but all settings are still there. This is what it looks like, I took a screenshot:

http://img816.imageshack.us/img816/3458/madvr1.jpg

4. Yeah I don't think this applies to me. Since the method which I use (replace the monitor and desktop), the graphics card just sends the image to the current monitor/TV and sends no image to the other device (which causes my Acer monitor to go into sleep mode and the Sony TV says it finds no signal)

[madshi]

I just choose Replace.
Ok, I've never used or tested that option yet. Didn't even know it exists!! I thought there were only "Clone" and "Extend"...

4. Yeah I don't think this applies to me. Since the method which I use (replace the monitor and desktop), the graphics card just sends the image to the current monitor/TV and sends no image to the other device (which causes my Acer monitor to go into sleep mode and the Sony TV says it finds no signal)
Do you hit "Replace" first and then load the video file? Or the other way round? I think you must first hit "Replace" to make the target monitor active you want to play the video file on, then in the next step start your media player and load the video file.

Does that work around the problem?

[fairchild]

Do you hit "Replace" first and then load the video file? Or the other way round? I think you must first hit "Replace" to make the target monitor active you want to play the video file on, then in the next step start your media player and load the video file.

Does that work around the problem?

Yes, this is currently how I do it, and No, it doesn't fix the issue.

This is what I do every time: I've been working on my Acer 22" monitor (usually gaming) and I finished what I was doing and I'm ready to watch a media file (be it AVI, MKV, WMV etc) on my bigger 32" Sony 1080p HDTV. So I hit my profile (which I had set up previously) which the function that it performs is to right click on the device that is not being used and hit replace on it. This causes my Acer monitor which I was working on to go into standby mode, and makes my Sony TV into the main and only display device which is receiving a signal at the time. I could play games or do anything else on my now active Sony TV (which I was doing on my Acer monitor if I wanted) then I open up PotPlayer and start to watch the media file.

So yes, I always make sure to be on the device I'm going to use BEFORE I go ahead and open the media file and thus open MadVR. :)

[madshi]

Ok, I'll see if I can reproduce and fix the problem. If the problem still occurs with the next madVR version (probably out next weekend or the week after that), please complain.

[fairchild]

Ok, I'll see if I can reproduce and fix the problem. If the problem still occurs with the next madVR version (probably out next weekend or the week after that), please complain.

Cool beans! Thanks a bunch! :thanks:

Edit: I got a little bit more information for you that might help you narrow down the problem. It seems that when you first run MadVR for the first time after a fresh install (by fresh install this is what I do: I go to the directory where all the MadVR files are at and where you executed the install.bat file to register it with the system, then execute uninstall.bat then delete all files. Then I of course re-extract the latest madvr.zip file and then execute install.bat)

The first device that is identified by MadVR after a fresh install (whether I'm on the Acer monitor at the time or the Sony HDTV) this is the device that seems to have total control as to which levels MadVR uses when it is executed regardless if you want different levels on the second device. Yes, you can change the levels on the second device, but MadVR doesn't seem to care if you have different levels setup on the second device, it will only start up with the levels which are currently set on the first device. I've tested this by installing MadVR on both devices after a fresh install. Each time, the device which was first recognized, MadVR would always use those levels even if the levels were set different on the other device.

[Razoola]

There does seem to be alot of confusion over 3D displays. Alot of it comes from nvidia and their 3D vision. They said you needed a 120hz display for 3D but you have to remember they are more coming from a gaming prospective. When you set up 3D vision it looks for a 120hz refresh rate, if the monitor does not have it at higher resolutions (800x600 is not enough) its impossible to set it up... The thing is... Once you have set it up you can test 3D vision at refresh rates right down to 60hz (and 800x600)... Its a real scam to be honest to get you to buy a new display for 3D.... The reality is you 100% don't really need one if you have a crt or a panel with fast pixel responce times (1ms). To be honest CRT presently is going to give you the best 3D image, followed by plasma and LCD.

All this said 120hz is the holy grail of refresh rates given you can get multiples of 24hz and 30hz into it. These panels that say they do 240hz is a scam because they cannot, the manufacturers are trying to con you into thinking a 120hz refresh rate with a 120hz backlight equals a 240hz refresh rate.... Reailty is it's still only 120hz with the other 120 being faked, its still only putting five 24p frames into that so called 240hz and not 10 which would be a true 240hz refresh rate.

Madshi, I still feel you should consider adding this blank frame creation if its doable and you have some spare time plus not more important things to do, even if its only in a few builds for testing to see how it goes.

[dansrfe]

I just detected a bug. When playing a DVD from the VIDEO_TS.ifo file, it shows 25.000 fps for the beginning disclaimer and ads which I really don't care about anyways, but when I skip to the title of the actual movie, it still detects it at 25.000 fps and consequently playback is shaky. When I play directly from the movie vob file, it shows 29.976 which I guess is ok but considering that the source is progressive, ntsc film @ 23.976 fps that kind of worries me. Haali used to pickup 23.976 and 25 fps depending on what "core" fps ffdshow was actually sending even for dvd sources with soft pulldown from pal film or ntsc film rates. I think this is just a detection bug of some sort but I'm not sure.

[XPC]

Hmmmm... Is the DirectShow filter chain (source, splitter, decoder) the same when watching live TV and when watching a recorded file? Or are there any differences?


For life TV the source and splitter are different. The filter chain would be something similar to:

Network provider -> Tuner -> Capture -> MPEG-2 Demux ->Video decoder -> Video renderer

The Demux has several output pins depending to the type of stream (MPEG2 Video, H.264 video, Audio, AC3, MPEG2 Sections and tables, ...). One instance of each decoder is always connected to the MPEG2 Demux. Only one video decoder is connected to the video renderer and only one audio decoder is connected to the audio renderer. When switching channels, in case of switching between video MPEG2 and H.264 channels, the video renderer is disconnected and then connected with the right video decoder.

Another important particularity is that the source here is working in push mode, while when whatching a recorded file it is done in pull mode. This might be the source of the problem.

The following link includes a Graphedit view of the directshow filter chain:

http://www.mediafire.com/imageview.php?quickkey=33ivd03v80zc02p&thumb=4

Please let me know if you need more information or more debugging.

[madshi]

if [...] you have some spare time plus not more important things to do
Spare time? What is that? I could easily fill 48 hours a day.

I just detected a bug. When playing a DVD from the VIDEO_TS.ifo file, it shows 25.000 fps for the beginning disclaimer and ads which I really don't care about anyways, but when I skip to the title of the actual movie, it still detects it at 25.000 fps and consequently playback is shaky. When I play directly from the movie vob file, it shows 29.976 which I guess is ok but considering that the source is progressive, ntsc film @ 23.976 fps that kind of worries me. Haali used to pickup 23.976 and 25 fps depending on what "core" fps ffdshow was actually sending even for dvd sources with soft pulldown from pal film or ntsc film rates. I think this is just a detection bug of some sort but I'm not sure.
madVR simply shows the pin connection media type information. This framerate is not even used by madVR right now, except for the OSD information.

For life TV the source and splitter are different. The filter chain would be something similar to:

Network provider -> Tuner -> Capture -> MPEG-2 Demux ->Video decoder -> Video renderer

The Demux has several output pins depending to the type of stream (MPEG2 Video, H.264 video, Audio, AC3, MPEG2 Sections and tables, ...). One instance of each decoder is always connected to the MPEG2 Demux. Only one video decoder is connected to the video renderer and only one audio decoder is connected to the audio renderer. When switching channels, in case of switching between video MPEG2 and H.264 channels, the video renderer is disconnected and then connected with the right video decoder.

Another important particularity is that the source here is working in push mode, while when whatching a recorded file it is done in pull mode. This might be the source of the problem.
Is there any way to watch live TV with "normal" DirectShow filters? Or is there any way to watch a recorded file with the "live" DirectShow filters?

[XPC]

Is there any way to watch live TV with "normal" DirectShow filters? Or is there any way to watch a recorded file with the "live" DirectShow filters?

Not as far as I know, but you might try with a digital camera as a life source.

[ryrynz]

(1) Your MPC folder including exe file and ini file, so that I use the same MPC version and same settings.
(2) Which filters are you using (splitter, decoder)?
(3) Video samples with which the problem occurs. You can cut them down to as small a size as you like, as long as they allow me to reproduce the problem.


Screen shot again.

http://www.fileden.com/files/2006/10/26/319696//Image3.jpg

Below are my MPC folder with ini and a sample clip which reproduces the problem for me (I add it twice into the playlist) I took a screenshot of the filters menu in MPC while I was playing the clip, I hope that's sufficient. I did a fresh extract of madVR and set that up with MPC and it didn't change anything so I didn't include it in the files uploaded.


http://www.fileden.com/files/2006/10/26/319696//MPC.rar

http://www.fileden.com/files/2006/10/26/319696//Hot Metal.avi

http://www.fileden.com/files/2006/10/26/319696//Image1.jpg

[madvr]

ryrynz - you are not using FFDshow for video decoding. That is why it says MPC decoder... the inbuilt DXVA decoder. Just set FFDshow video decoder to preferred in MPC, and disable DXVA.

[ryrynz]

It also happens when FFDshow is enabled, I enabled the internal decoder to troubleshoot, thought it would help narrow down the problem.

Here's another pic showing the filters used when FFDshow is enabled.

http://www.fileden.com/files/2006/10/26/319696/Image.jpg

[Razoola]

I had an issue today with 034 and the render queues not filling up fully. Im not sure what the cause was but I would have to pause and unpause playback to get them to fill. I tried to make a log but as soon as I switched to the debug version the problem stopped and I have not been able to reproduce it since (even with non debug build). Though I would just mention it though, I'll post a log if it happens again and I can get one.

[*Touche*]

Screen shot again.

http://www.fileden.com/files/2006/10/26/319696//Image3.jpg

I can confirm this. Using MPC-HC 1.3.2444.0 and madVR 0.30.

When you go windowed->full screen exclusive, it "remembers" the frame during which the switch occurred. If you then go to the next video file (while in full screen) it looks just like the picture above for a brief moment before playing the next video. That is the "remembered" frame. This can be either the next video in playlist or when you advance through folder manually.

But, it happens only on the first transition. It doesn't happen during further advancement through files. Unless you do the windowed->full screen switch again. And if you do the switch multiple times, the remembered frame will be from the last switch.

I hope this makes sense :)

Win7 x64, Aero ON, ATI 4670 CAT10.6

[Thunderbolt8]

confirm it with 0.34

[ryrynz]

confirm it with 0.34

I already have. Madshi hasn't been able to duplicate it so far and thus hasn't been able to find the cause.

[nevcairiel]

I've seen a similar thing when switching from exclusive mode back to windowed, it shows the frame that was active when i switched to exclusive for a very brief time. Nothing i actually worry about, you should not expect perfect playback when switching between windowed and full screen all the time.

For the "next file" issue, well, most players will destroy the renderer and create a new instance, which causes this issue. On subsequent switches you won't see anything, because most files start with a black frame. You would notice it again if you switch between windowed/exclusive during playback and then go to the next file.

[Thunderbolt8]

I already have. Madshi hasn't been able to duplicate it so far and thus hasn't been able to find the cause.yes, now I remember that post -.-

[Razoola]

I have had to go back to version 032, there is something in 034 that seems to not play nice with reclock and for the life of me I cannot create a log because I cannot get the problem to happen in the debug build.

[ryrynz]

Nothing i actually worry about, you should not expect perfect playback when switching between windowed and full screen all the time.



Anyway, I can not reproduce the problem on my PC. I'd like to reproduce it


I'm merely stating my observations, as you can see Madshi is interested in reproducing it. I don't expect perfection, it is natural however to strive for it.

[pankov]

madshi,
I have a major problem with the latest versions of madVR (> 0.31) and the latest builds of MPC Matroska splitter.

If I try to play a second file using a shortcut or the "next" button on my remote control while being in FSE mode I get the following error:
---------------------------
Zoom Player
---------------------------
Access violation at address 4A402E1A in module 'madVR.ax'. Read of address 00000018.
---------------------------
OK
---------------------------
I get the same error if Zoom Player automatically advances to the next video file in the playlist.
If I'm in windowed or fullscreen windowed mode everything is fine.

I've tested MatroskaSplitter.ax 1.4.2505 and 1.4.2667 and both versions work fine with madVR 0.31. Also Halli's Media splitter works fine with both madVR 0.31 and madVR 0.34 so I suppose there is something wrong with the way madVR reads the streams from the splitter.

here is a .log file that I'm hoping is showing the error.
http://www.mediafire.com/file/t9f05kpx5dz141d/madVR%20-%20log%20-%20access%20violation.rar

I'm not uploading a sample because this happens with all .mkv files I have.

Edit:
I just got the error with Haali's splitter too so I guess it's not a splitter issue even though with this splitter I don't get the error every time I jump to the next file.

[*Touche*]

Hmm, MPC-HC freezes on me sometimes if I do the same thing - press next on my remote. madVR 0.30. It happens rarely and I've only tried avi xvid files. No error pops up though, I just have to kill MPC-HC in Task Manager. I should try 0.34, I know... :)

[LordX2]

This whole 120hz issue is concerning. I posted a message a few days back in regards to a good video card that would be capable of handling MadVR.

Should I make sure this video card has 2 DVI ports for dual link DVI so that in the future when projectors can do true 1080p @ 120hz I will be ready?

Pretty much the question is: Which video card will not only work well with MadVR - but also be ready for true 1080p 120hz for the future?

[Owyn]

btw, there are two bugs i found found while using madVR in KMPlayer

1. in fullscreen mode when you press esc and it supposted to minimize it stucks on screen and you can't really do anything further - need reset or other blind actions to turn off video

2. esc again, when you open subtitles menu (alt + q) the esc which is supposted to close it just doesn't do it but does thing to video (minimize or corrupts it(see 1st))

all other video renderers have no such bugs

[dansrfe]

need subtitle and screenshot taking support. I know it's the same thing everyone else has been saying but how much longer.

[Mark_A_W]

?

Press Printscreen.

[dansrfe]

^ yea but I don't know about the quality/accuracy of doing that vs having madVR do that internally. Printscreen does work though.

[Hypernova]

^ yea but I don't know about the quality/accuracy of doing that vs having madVR do that internally. Printscreen does work though.

I think madshi said in the early part of this thread that it's low priority since printscreen is good enough.

[Mark_A_W]

If you are running a 1:1 resolution compared to the source, then it should be identical to madVR. (?)

[pankov]

guys,
does printscreen work in exclusive mode?
Last time I tried it didn't work for me. Can I've done something wrong or something changed since v0.31?

[Hypernova]

guys,
does printscreen work in exclusive mode?
Last time I tried it didn't work for me. Can I've done something wrong or something changed since v0.31?

Mine does.

[Boogerlad]

Can you delete the madvr folder after installation?

[leeperry]

does printscreen work in exclusive mode?
yay

Can you delete the madvr folder after installation?
nay

[ExtraEye]

hi,
i installed the latest version and when i choose madvr in mpc hc the video doesn't start. it just keeps "loading".
tried using the debug version and it worked once then stopped. anyway i found the log file on the desktop - 30mb 0_O - and thought i'd share some of it:

00000000 Creator Thread "Creator" = ThreadID 0000076c
00000000 Creator madVR v0.34
00000000 Creator CVideoRenderer::CreateInstance();
00000000 Creator CVideoInputPin constructor;
00000000 Creator CVideoInputPin constructor -> +
00000000 Creator CVideoText constructor;
00000000 Creator CVideoText::GetClassWindowStyles();
00000000 Creator CVideoText::GetClassWindowStyles() -> +
00000000 Creator CVideoText::OnReceiveMessage(msg: 81, wParam: 0, lParam: 81246500);
00000000 Creator CVideoText::OnReceiveMessage() -> +
00000001 Creator CVideoText::OnReceiveMessage(msg: 83, wParam: 0, lParam: 81246480);
00000001 Creator CVideoText::OnReceiveMessage() -> +
00000001 Creator CVideoText::OnReceiveMessage(msg: 1, wParam: 0, lParam: 81246500);
00000001 Creator CVideoText::OnReceiveMessage() -> +
00000001 Creator CVideoText::OnReceiveMessage(msg: c, wParam: 0, lParam: 1245989792);
00000001 Creator CVideoText::OnReceiveMessage() -> +
00000001 Creator CVideoText constructor -> +
00000001 Creator CVideoRenderer constructor;
00000001 Creator Settings_Init();
00000003 Creator Settings_Init() -> +
00000003 Creator Queue_Init();
00000003 Creator Osd_InitKeyHook();
00000003 Creator Osd_InitKeyHook() -> +
00000003 Creator CVideoRenderer constructor -> +
00000003 Creator CVideoRenderer::CreateInstance() -> +
00000003 Creator CVideoRenderer::NonDelegatingQueryInterface(IUnknown{00000000-0000-0000-C000-000000000046});
00000003 Creator CVideoRenderer::NonDelegatingQueryInterface() -> 0
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface(IUnknown{00000000-0000-0000-C000-000000000046});
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface() -> 0
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface({9cc7f9f7-3ed1-493c-AF65-527EA1D9947F});
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface() -> ISubRender
00000004 Creator CVideoRenderer::SetCallback();
00000004 Creator CVideoRenderer::SetCallback() -> +
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface({56a86895-0ad4-11ce-B03A-0020AF0BA770});
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface() -> 0
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface({8e1c39a1-de53-11cf-AA63-0080C744528D});
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface() -> 80004002
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface({f90a6130-b658-11d2-AE49-0000F8754B99});
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface() -> 80004002
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface({56a86895-0ad4-11ce-B03A-0020AF0BA770});
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface() -> 0
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface({cedb2890-53ae-4231-91A3-B0AAFCD1DBDE});
00000004 Creator CVideoRenderer::NonDelegatingQueryInterface() -> 80004002
00000004 Creator CVideoRenderer::GetPin(0);
00000004 Creator CVideoRenderer::GetPin() -> +
00000004 Creator CVideoRenderer::GetPin(0);
00000004 Creator CVideoRenderer::GetPin() -> +
00000004 Creator CVideoInputPin::ReceiveConnection();
00000004 Creator CVideoInputPin::CheckMediaType();
00000004 Creator CVideoRenderer::CheckMediaType({32315659-0000-0010-8000-00AA00389B71});
00000004 Creator GetVih2 original media type:
00000005 Creator AM_MEDIA_TYPE:
majortype: {73646976-0000-0010-8000-00AA00389B71}
subtype: {32315659-0000-0010-8000-00AA00389B71}
formattype: {f72a76a0-eb0a-11d0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 1
cbFormat: 112
00000005 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(0,0)
rcTarget: (0,0)-(0,0)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000005 Creator GetVih2 final output:
00000005 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(528,352)
rcTarget: (0,0)-(528,352)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000005 Creator CVideoRenderer::CheckMediaType(MEDIASUBTYPE_YV12, width: 528, height: 352, bitcount: 12, aspectX: 3, aspectY: 2) -> +
00000005 Creator CVideoInputPin::CheckMediaType() -> 0
00000005 Creator CVideoInputPin::SetMediaType();
00000005 Creator CVideoRenderer::SetMediaType();
00000005 Creator GetVih2 original media type:
00000005 Creator AM_MEDIA_TYPE:
majortype: {73646976-0000-0010-8000-00AA00389B71}
subtype: {32315659-0000-0010-8000-00AA00389B71}
formattype: {f72a76a0-eb0a-11d0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 1
cbFormat: 112
00000005 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(0,0)
rcTarget: (0,0)-(0,0)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000005 Creator GetVih2 final output:
00000005 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(528,352)
rcTarget: (0,0)-(528,352)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000005 Creator CVideoText::HandleNewMediaType();
00000005 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(528,352)
rcTarget: (0,0)-(528,352)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000005 Creator CVideoText::IsDefaultTargetRect();
00000005 Creator CVideoRenderer::GetTargetRect();
00000005 Creator CVideoRenderer::GetTargetRect() -> 0, 0, 0, 0
00000005 Creator CVideoText::IsDefaultTargetRect() -> +
00000005 Creator CVideoText::HandleNewMediaType(size: 528 352; aspect: 3 2; sum: 528 352)
00000005 Creator CVideoRenderer::SetSourceRect(newRect: 0, 0, 528, 352);
00000005 Creator CVideoRenderer::SetSourceRect() -> +
00000005 Creator CVideoRenderer::GetTargetRect();
00000005 Creator CVideoRenderer::GetTargetRect() -> 0, 0, 0, 0
00000005 Creator CVideoText::HandleNewMediaType() -> +
00000005 Creator CVideoRenderer::SetMediaType() -> +
00000005 Creator CVideoInputPin::SetMediaType() -> 0
00000005 Creator CVideoRenderer::CompleteConnect();
00000005 Creator GetVih2 original media type:
00000005 Creator AM_MEDIA_TYPE:
majortype: {73646976-0000-0010-8000-00AA00389B71}
subtype: {32315659-0000-0010-8000-00AA00389B71}
formattype: {f72a76a0-eb0a-11d0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 1
cbFormat: 112
00000005 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(528,352)
rcTarget: (0,0)-(528,352)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000005 Creator GetVih2 final output:
00000005 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(528,352)
rcTarget: (0,0)-(528,352)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000005 Creator CVideoText::HandleNewMediaType();
00000005 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(528,352)
rcTarget: (0,0)-(528,352)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000005 Creator CVideoText::IsDefaultTargetRect();
00000005 Creator CVideoRenderer::GetTargetRect();
00000005 Creator CVideoRenderer::GetTargetRect() -> 0, 0, 0, 0
00000005 Creator CVideoText::IsDefaultTargetRect() -> -
00000005 Creator CVideoText::HandleNewMediaType(size: 528 352; aspect: 3 2; sum: 528 352)
00000005 Creator CVideoRenderer::SetSourceRect(newRect: 0, 0, 528, 352);
00000005 Creator CVideoRenderer::SetSourceRect() -> +
00000005 Creator CVideoText::HandleNewMediaType() -> +
00000652 Creator CVideoRenderer::ReportChapters();
00000653 Creator CVideoRenderer::ReportChapters() -> +
00000653 Creator CVideoRenderer::ReportTracks();
00000653 Creator CVideoRenderer::ReportTracks() -> +
00000653 Creator CVideoRenderer::CompleteConnect() -> +
00000653 Creator CVideoInputPin::ReceiveConnection() -> 0
00000654 Creator CVideoInputPin::GetAllocator();
00000654 Creator CCustomMemAllocator constructor (attachNewMediaType: -);
00000654 Creator CCustomMemAllocator constructor -> +
00000654 Creator CVideoInputPin::GetAllocator() -> +
00000654 Creator CCustomMemAllocator::SetProperties(bufCount: 1, bufSize: 278784, align: 1, prefix: 0);
00000654 Creator GetVih2 original media type:
00000654 Creator AM_MEDIA_TYPE:
majortype: {73646976-0000-0010-8000-00AA00389B71}
subtype: {32315659-0000-0010-8000-00AA00389B71}
formattype: {f72a76a0-eb0a-11d0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 1
cbFormat: 112
00000654 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(528,352)
rcTarget: (0,0)-(528,352)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000654 Creator GetVih2 final output:
00000654 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(528,352)
rcTarget: (0,0)-(528,352)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000654 Creator enumerated media type:
00000654 Creator AM_MEDIA_TYPE:
majortype: {73646976-0000-0010-8000-00AA00389B71}
subtype: {32315659-0000-0010-8000-00AA00389B71}
formattype: {f72a76a0-eb0a-11d0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 1
cbFormat: 112
00000654 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(0,0)
rcTarget: (0,0)-(0,0)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000654 Creator GetVih2 original media type:
00000655 Creator AM_MEDIA_TYPE:
majortype: {73646976-0000-0010-8000-00AA00389B71}
subtype: {32315659-0000-0010-8000-00AA00389B71}
formattype: {f72a76a0-eb0a-11d0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 1
cbFormat: 112
00000655 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(0,0)
rcTarget: (0,0)-(0,0)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000655 Creator GetVih2 final output:
00000655 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(528,352)
rcTarget: (0,0)-(528,352)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000655 Creator GetVih2 original media type:
00000655 Creator AM_MEDIA_TYPE:
majortype: {73646976-0000-0010-8000-00AA00389B71}
subtype: {32315659-0000-0010-8000-00AA00389B71}
formattype: {f72a76a0-eb0a-11d0-ACE4-0000C0CC16BA}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 1
cbFormat: 112
00000655 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(0,0)
rcTarget: (0,0)-(0,0)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000655 Creator GetVih2 final output:
00000655 Creator VIDEOINFOHEADER:
rcSource: (0,0)-(528,352)
rcTarget: (0,0)-(528,352)
AvgTimePerFrame: 417080
VIDEOINFOHEADER2:
dwInterlaceFlags: 00000000
dwCopyProtectFlags: 00000000
dwPictAspectRatioX: 3
dwPictAspectRatioY: 2
dwControlFlags: 00000000
BITMAPINFOHEADER:
biSize: 40
biWidth: 528
biHeight: 352
biPlanes: 3
biBitCount: 12
biCompression: YV12
biSizeImage: 278784
biXPelsPerMeter: 0
biYPelsPerMeter: 0
00000655 Creator CCustomMemAllocator::SetMediaType();
00000655 Creator CCustomMemAllocator::SetMediaType() -> +
00000655 Creator GetVih2 original media type:
00000655 Creator AM_MEDIA_TYPE:
majortype: {73646976-0000-0010-8000-00AA00389B71}
subtype: {32315659-0000-0010-8000-00AA00389B71}
formattype: {f72a76a0-eb0a-11d0-ACE4-0000C0CC16BA}

does it help?

[leeperry]

does it help?
it'd be more helpful to ZIP/RAR up the complete logfile and put it on mediafire.com ;)

you may also want to specify your OS/graphic card/drivers version/etc, and how to reproduce it.