I've been trying to get motivated to work on DGAVCDecDI. It's hard because I rarely use it.

DGAVCDec is not licensed for your use. All licenses have been withdrawn and it is not available. You cannot legally use it. I will not respond to any support requests involving it.

Didée as usual has explained things well. The only thing I might add is to point out that if you are choosing encoding parameters and resolution such that your encoding rate is above your GPU decoding rate (e.g., HD->SD transcode), then you likely will be bottlenecked by the decoder. In such a case,...

I don't know anything about that.

Open the stream. Hit Cancel on the resulting Audio Detection Mismatch popup. Now you should have video and be good to go.

The stream on PID 811 is confusing DGIndexNV. I don't know what it is. Do you?

The streams are scrambled so you are hosed.

DGAVCNV? I'm interested in the raw decoding speeds for the two scenarios but not so much transcoding speeds, because so many other variables enter. Please give the raw decoding speed numbers. You use DGIndexNV with the Disable DIsplay option as described in the user manual. Yes, you need 64-bit Avis...

My testing reveals no difference in memory usage between 2038 and 2039. If you want any further followup you will need to provide a test stream and a description of the full and exact process to follow for observing what you say you observe.

That's very interesting. Does that happen only with MPEG2 streams or also for AVC and VC1?

No problem, I have a fast connection.

Thanks for bringing it to my attention.

I asked if you were identifying an issu ewith DGDecNV and you did not affirm that, so I mark this resolved.

I tested your stream with 2038 and 2039. 2038 was broken but 2039 is fine. A fix was added for this specific problem.

I don't know what you are talking about when you talk about x264 stats and "out of sequence" frames. Are you identifying an issue with DGDecNV?

Can you try with 2039 please? Download it fresh to be sure to have all the slipstreams I made.

2039 included a fix for BBC HD streams.

I have your stream now and have duplicated the issue. In fact, this is not an error condition at all and I can't remember why I added that popup. I'll remove it for the next release. For now, just dismiss the popup and continue.

One open instance takes about 128-200MB, which is way more than 3% of 1GB. Use GPU-Z/Sensors/Memory Used. You're right, it seems that GPU Monitor was reporting incorrectly. GPU-Z lists the memory at 758MB when running the 2 instances of 2038. I can't run 2039 right now because I've been encoding a ...

One open instance takes about 128-200MB, which is way more than 3% of 1GB. Use GPU-Z/Sensors/Memory Used.

BTW, do you have D3D mode enabled?

Maybe English isn't your first language?

Looks like you are just running out of graphics memory. Don't do concurrent stuff like that. I don't support it.

Give me a break, I asked twice for a stream.

I don't see any changes in 2039 that could account for this so we are stymied. Does this happen only when you run DGIndexNV on another project while one is being transcoded?

Also, is the error coming from DGIndexNV or DGDecodeNV?

How much memory on your graphics card and did you change it recently?

I don't recommend running DGDecNV concurrently like you are doing. It is not a designed-for condition.

please remember that I am doing this for your benefit Yeah, I really need to spend my time hunting down obscure, rare bugs that nobody cares about without any means to replicate the problem. ;) Is it so hard to give me a link to the entire stream, or a set af RAR files, whatever? I won't ask again.

I need all your system details and a description of a specific scenario that causes it. You haven't even told me if it is DGIndexNV or DGDecodeNV that it happens with, for example.

Did you make the MKV? If so, make a smaller one. Obviously I need a stream sample, so don't make me beg for it.

Can you give me a stream that will allow me to duplicate your issue?