Support forum for DG Tools

Hello,I am a DGNV user.Your tools are very great! I always use DGSource() in VapourSynth.
Now,I have a suggestion.When I use DGSource() to open a video,the messages from Clipinfo() are too less.This means that there are less info in the clip which opened by DGSource().

Just like this...
My vpy file：
"
import vapoursynth as vs
import sys
import havsfunc as haf

core = vs.get_core(accept_lowercase=True,threads=8)

core.max_cache_size = 12000

core.avs.LoadPlugin("C:/Program Files/dgdecnv/x64 Binaries/DGDecodeNV.dll")
src = core.avs.DGSource("G:/DGNVindex/XXX/XXX.dgi",fieldop=2,deinterlace=0)
#src = core.lsmas.LWLibavSource(source="G:/DGNVindex/XXX/XXX.m2ts")

src = core.text.ClipInfo(src)

src.set_output()
"

I hope that the clip opened by DGSource() have more info in the future.

Thank you！

Welcome to the forum and thanks for your kind words.

I would have to fill out Vapoursynth per-frame properties, but I cannot do that in an Avisynth filter. I am working on a dual native VS/AVS version that would be able to do that. I'll fill out what I can in the VS properties. Leaving this thread open to remind me.

I look forward to your VS version！！！

+1

Slipstream 144 populates all properties except ChromaLocation, which I find to be useless and not worth the trouble.

Of course, you will have to use the Vapoursynth native invocation of DGSource(), i.e., core.dgdecodenv.DGSource(). If you use the Avisynth native version, the extra properties are not populated.

Thank you, Morpheus, for suggesting this enhancement.

admin wrote: ↑

Mon Apr 16, 2018 8:22 am

Slipstream 144 populates all properties except ChromaLocation, which I find to be useless and not worth the trouble.

Of course, you will have to use the Vapoursynth native invocation of DGSource(), i.e., core.dgdecodenv.DGSource(). If you use the Avisynth native version, the extra properties are not populated.

Thank you, Morpheus, for suggesting this enhancement.

Nice！