Open each one with a DGSource() instance and then combine the decoded streams as desired using Avisynth.

You're welcome but I merely channeled AntrimMan, so thanks to him too.

I think it is included in this update:

http://support.microsoft.com/kb/973923

Correct me if I am wrong, AntrimMan. I searched at the VirtualDub forum but didn't find your thread.

Hi Floren,

You have mail!

Don

Thanks and sorry for the inconvenience. I do plan to merge the apps at some point so that issue will not arise.

Looks like you are actually invoking DGSource() from the DGDecodeNV.dll and not from DGAVCDecodeDI.dll. The reason I know that is because the error message "DGMultiSource: ..." exists only in DGDecNV. In DGAVCDecDI, it is just "DGSource: ...". Add a loadplugin() line at the start to explicitly load ...

Please post the first 20 lines of the DGI file.

Can you tell us what the improvements were? Is it actually adaptive now? Thank you.

Got the stream and duplicated the issue. In the GUI, doing Save Project results in Progressive while Preview does not, so something is indeed amiss. Investigating...

mediafire keeps erroring out and not starting my download. Can you try a different site?

Meanwhile I will check the code.

Does this happen if you do not use CLI but just open DGIndexNV in GUI mode?

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 ...