If you want to redownload 2039, I have slipstreamed a change that adds an error popup for attempting to open an MP4 container.

OK, you are good to go. Redownload 2039 and update DGIndexNV and DGDecodeNV.

Oops, yet another slipstream fix for a bug in the MPEG2 workaround. I also added three more changes so refer to the change listing above.

Update both DGIndexNV and DGDecodeNV.

I have it fixed and will slipstream it later tonight. Watch the News thread for 2039 to see when that happens.

Thanks for pointing this out.

Even in English it can be useful to dispel the belief in some quarters that GPU decoding can magically accelerate transcoding rates by large amounts.

Of course faster *encoding* is possible. Use a faster CPU, use faster settings for your encoder, reduce the resolution, preprocess to reduce detail, etc. The primary advantages of DGDecNV, as I have said several times, are correct decoding of AVC/MPEG/VC1 in different flavors (such as interlaced VC1...

VP is the video processor pipeline, otherwise known in marketing speak as PureVideo. Video decoding is accelerated by means of functionality of the VP engine.

What part do you not understand?

Is there something about my reply that you do not understand?

The VP engine clock speed is probably the same and that is the clock that primarily determines decoding performance.

Your file is an MP4 container, which is not yet supported by DGDecNV. It is on my to-do list.

I would add that it's possible to buy overclocked versions of Nvidia cards. They can give a useful boost to the VP engine performance. Also, get a card with as wide a memory interface as possible.

Quadro and Tesla have Windows Server support and are CUDA enabled.

You'll have to ask Nvidia about this. I don't know anything about drivers for Windows Server 2008 R2.

I have slipstreamed the fix into 2039, so redownload it and update DGIndexNV.

Thank you for pointing this out, SpasV.

I had to slipstream an important fix into 2039: Fix 'Output Trimmed TS' for large trims.

Re-download and update DGIndexNV.

OK, I have easily duplicated that. Investigating...

I have slipstreamed 2039 again so please re-download. I have restored the IDR check and fixed Vippe's BBC-HD trimming problem.

Update both DGIndexNV and DGDecodeNV.

Nvidia has sent me a fix. Man, I love Nvidia! I think I'll slipstream it into 2039 and upload it later tonight after some regression testing. So I'll mark this resolved. Thank you, Vippe, for bringing it to my attention and for your clear and complete problem data. Analysis from Nvidia: This is inde...

I had to temporarily back out the IDR check added in 2039 as it was being triggered by legal IDRs with multiple slices (oops). I'll fix that and restore the check ASAP. Re-download and replace DGIndexNV.exe.

Build 2039 ------------ * The info overlay DGSource(debug=true) was modified so that IDR and I frames are now properly distinguished. * The DGI file format was modified to add a frame number indication to the FRM lines. The file format version number was not bumped because 2039 is backward compatibl...

It's a bug in decoding of MPEG2 dual prime prediction (which is rare) in the VP3+ engines.

Nvidia has given me a workaround for this. It will be included in build 2039 which is about to pop out. So I mark this resolved.

Thank you for bringing this to light.

If it works, then fine, but as that is not designed behavior I can't vouch for it.

Sent to Nvidia for analysis.