I've slipstreamed a fix. Please re-download 2037 and test it. Thank you.

OK, I have found the problem with MKV files. I'll release a fix tonight.

It's a .mkv file but I muxed it to .ts and used DGSplit. Confirmed to still only index the first 120 frames. PM'd link. What you gave me was an MKV file renamed as .ts. You cannot split that with DGSplit. I will compare against 2036 behavior, but I'd really appreciate receiving proper files. Please...

What kind of file is it? I ask in order to tell you the right way to cut it. I am not going to download a 1GB file from a torrent tracker! I don't even have a torrent client installed and don't intend to install one. You need to cut the file down and then upload it to mediafire.com. If it is TS or M...

Thanks for that information, madshi. It is very useful to a DirectShow noob like me.

I can do this: In the filter constructor try to open up CUDA and create a video decoder. If it fails, then throw you an exception. So you'll at least get an indication at filter startup that things are amiss. Can you catch an Avisynth exception and respond appropriately?

Hi madshi, Thanks for dropping in. It's an honor to see you here. And thanks for the information on DirectShow and madVR. I'm just getting my feet wet now with DirectShow. I hope it is not as painful as you say! I'll probably be in touch with you as I make progress and have questions. Ciao! BTW, fra...

I've repaired what I could here. There is a mix of audio types at the start. You have to start your project in far enough to get beyond that. After doing that, the delay seems fine to me in build 2037.

Build 2037 ---------- * Fixed use of an uninitialized variable that could cause crashes and/or bad hinting for MPEG2 and VC1 files. * Added a string to the first line of the DGI file that identifies the version of DGIndexNV used to generate the index. * Fixed counting of leading B frames for AVC str...

Some more questions... Are you thinking of this primarily for playback purposes, rather than filtering, transcoding, etc? The answer determines how frame accurate it has to be. Are you wanting an ES decoder with an input pin for compressed video and an output pin for decompressed video? I.e., a deco...

That DGAVCDecNV you are running. Is that a pirated version? I can't find any registration for the machine code you gave. I don't care since you donated, but you have to get rid of that thing; I won't be responsible if you have that on your system.

I think you must have created DLL hell. Search your hard disk for old copies of my DLLs. Remove them and DGAVCDecNV completely. Reinstall the Nvidia drivers. Run DGIndexNV. Does it still show dots?

Also, do the dots show in DGIndexNV, the served video, or both?

And you claim that your video shows no dots with that (right now, not in the past) but does show dots with DGIndexNV 2036?

If that is true then the only thing I can think of is that the NV12 --> RGB24 CUDA kernel is failing on your specific hardware/driver combination.

UncleBob wrote:DGAVCIndexNV still displays no dots...

Please post a screenshot of the About box from this program.

Please post a link to an unprocessed source sample. There are various reasons that may cause the problem. One is that you are goofing up. Another is that the material may not be amenable to the filter because it does not have full frame flicker but rather "rolling shutter" flicker. So to help you pr...

Sorry to hear that.

I have done this: 1) At first start you get two error popups that timeout after 5 seconds each. 2) After that green frames are returned with the text "CUDA Error!" written on them with no further popups. This way the encode will finish but with bad video. I don't know how to signal you that things w...

I can't throw exceptions outside my filter constructor.

I can make the message boxes timeout (say 5-10 seconds) and I can just return garbage frames instead of committing hari kari.

Would that work for you?

It has nothing to do with licensing. Your video driver must be hosed.

Post a link to an unprocessed source sample.

It's an interesting idea.

Regarding the existing filters you mentioned, why don't they work with MadVR?

Everything looks fine with force film, which is what you should be using. The anomaly with T/D and MEGUI can be due to jumping around on the timeline, maybe MEGUI is doing some silliness with previews or something that causes Telecide() or Decimate() to see a frame history that is different from jus...

I don't like to speculate on things without the sample clip, so I will wait for that.

1. If it's 99% film, you should use Force Film mode rather than Telecide/Decimate. Assuming the flagging is accurate, that will not only solve your problem completely, but it will also be much faster. 2. I already use a windowed algorithm. Such small changes have always been a challenge for adaptive...

Something does seem to be amiss. Investigating...