Rocky is busy coding some new doodad he fantasized (good luck with that -- NV is more tightly coupled than you hope) Don't be so negative Bullwinkle! I already have DGDemux disconnected from NV and I have just now performed my first full demux from Cars 2 using DGDemux. Just have to clean up a lot ...

gonca wrote: ↑

Sat Nov 02, 2019 11:45 am

No, but if I want an 8 bit file preprocessed and encoded in 10 bit (DVD and some BD, imported) right now the preprocessing must be done in 8 bit and then converted to 10 bit for encoding

And that's a problem because...?

gonca wrote: ↑

Sat Nov 02, 2019 11:06 am

DGTelecide and DGDecimate working with 16 bit depth would help with the 10 bit encode chain

Have you ever seen a high-bit-depth video that is 3:2 telecined?

It is pointless to multithread DGSource() because there is only one decoder on the GPU. All it will do is consume extra memory and add CUDA context switching overhead. Avisynth+ has the ability to specify multithreading per filter. DGSource() would be serialized while the others can be multithreaded...

Script multi-threading and multi-filter-instance are not the same thing! I regret that I do not have time to educate you on basic stuff. I told you how to get your Avisynth version. You want to know why it doesn't fail on the Xeon? I have no idea because I don't know what GPU it has or how much memo...

Your last post is totally unresponsive to my last post. You still haven't even told me what version of Avisynth you run. You are all confused about what you call "cudas". We'll get much further if you listen to me and follow my instructions. I'll close the thread if you keep ignoring my questions an...

SetMTMode() is not an Avisynth+ thing, so it looks like some holdover from 2.6MT. Are you sure you are running Avisynth+? Make a script with just Version() and that will tell you. You cannot multithread DGSource(). That may be why you run out of memory. Refer to the Avisynth+ documentation for multi...

Shockingly, this works: LoadPlugin("C:/Program Files (x86)/AviSynth+/plugins/DGDecodeNV.dll") DGSource("2019-10-16.1800.wv.IN-v-MD.gl4-2-6.720p60.btn.c2-tv.ed-14m.dgi") But if I leave off the loadplugin line, it fails as before. Something wrong with my plugins access? It's not shocking at all! You ...

Your experiences of the past are not helpful. We are trying to solve your current situation. Please try with a basic script loaded into VirtualDub2 and report your result: LoadPlugin(".../DGDecodeNV.dll") DGSource("your DGI file") If you think the card is bad, then try the other one! Another questio...

If you do not answer my questions I can't help you. You did not give the script, only an excuse. Look, make a basic script with just DGSource() and try that. You did not answer me about the memory on your card, nor did you do any of the memory monitoring I suggested. You did not tell the resolution ...

Is it possible for the cuda cores part of a card to go bad but the normal video function of the card (seeing the desktop on my computer monitor) still works? No, the same CUVID/CUDA calls are used in both DGIndexNV and DGDecodeNV, and you say it works in DGIndexNV. Can I see your script? Maybe you ...

I asked if the video shows fine in DGIndexNV. Please answer that directly. You only said indexing works. Also it's not clear from what you say if you a full power cycle after the problem started. Please do so. I would try the other card before anything else. What is that card? I also ask you to try ...

Please give your OS and OS build details, your nVidia card details, your nVidia driver version, and DGDecNV version. It is nonsensical that you refuse to upgrade. Be aware that I am not going to support an almost 4-year-old version of DGDec, so if general considerations do not suffice, you will be s...

Thank you for the status update, Sharc!

Time to mark this resolved.

OK, no problem, thank you.

DGDecNV slipstream 191: * Fixed handling of streams with profile_idc = 244. [Sharc] * Fixed formatting of the Info dialogs. [Bullwinkle] * Fixed incorrect frame rate used for demuxing of PGS subtitles. [Xunkar] * Updated the DGIndexNV and DGDecodeNV user manuals. To get this slipstream, simply re-do...

Should be fixed in slipstream 191.

Great report. I'm pretty sure I know what the problem is. Will report back when I have a slipstream for you to test.

OK, but was profile 244 explicitly requested on the command line?

Netflix Meridian. Sneaker converted a sample to 1920x1080 8bit 4:2:0 from the 300GB file for testing https://mega.nz/#F!BlNDGIgJ!7lBUBs61l1oiIIBScrMyYg Do we know what sneaker used to convert to HD and what was the command line? I am trying to determine how profile 244 came about. Also, the file in ...

Thank you!

You are most welcome, Vraelon!

I should make this explanation a part of every slipstream notification post. I will try to remember to do so.

When a slipstream is released, I simply replace dgdecnv2053.zip in the binaries area with the updated one. So all you need to do is re-download dgdecnv2053.zip. The slipstream number can be seen in DGIndexNV's Help/About dialog. It is also in the file properties for both DGIndexNV.exe and DGDecodeNV...

DGIndexNV was not accepting profile_idc = 244 as valid. I have fixed that and everything works fine after that. Fix will be in the next slipstream. Thank you for pointing this out, Sharc . Probably the other apps that fail with this stream also do not handle profile_idc = 244. 244 stands for High 4:...