Frame properties support for Avisynth+
Frame properties support for Avisynth+
Kiddies would all have heart attacks and drop dead on your porch. Hope you are proud of yourself.
- Bullwinkle
- Posts: 344
- Joined: Thu Sep 05, 2019 6:37 pm
Frame properties support for Avisynth+
Making a neat pile.
Frame properties support for Avisynth+
Can we stay on topic, please?
Frame properties support for Avisynth+
Go work on SQL or something, Mr beancounter.
Frame properties support for Avisynth+
Halloween brings out the best in all of us. Hallelujah!
Frame properties support for Avisynth+
Don't you all think we should remove admin's moderator status? He's such a killjoy. Should I start a poll? I would be an excellent replacement!
Frame properties support for Avisynth+
If I can't get Honoré de Balzac, would you be happy with Baltasar Gracián?
Frame properties support for Avisynth+
Works for me. Get both!
Frame properties support for Avisynth+
Works for me too.
- Bullwinkle
- Posts: 344
- Joined: Thu Sep 05, 2019 6:37 pm
Frame properties support for Avisynth+
Me three.
Frame properties support for Avisynth+
I had to add propSet("_FieldBased", -1) to the following script or the nnedi3resize would give an error about missing properties. Does DGIndexNV pass that parameter?
Code: Select all
SetMemoryMax()
SetFilterMTMode("DEFAULT_MT_MODE", 3)
LoadPlugin("D:\Eseguibili\Media\DGDecNV\DGDecodeNV.dll")
DGSource("N:\In\AnoHana\01.dgi")
propSet("_FieldBased", -1)
ConvertBits(16)
fmtc_resample (1280, 720, kernel="bicubic", a1=1, a2=0, invks=True)
nnedi3resize(1920,qual=2)
fmtc_bitdepth (bits=10,dmode=8)
Prefetch(4)
Frame properties support for Avisynth+
The latest DGDecNV online sets _FieldBased according to the latest semantics. You need a recent Avisynth+. Please advise of any issues you have with it.
Right after DGSource() you can add propShow() to see what it has set.
Note that an intermediate filter, such as fmtc_resample(), may not be passing through the props that DGSource() has set. Use propShow() at various places to test that. The GetFrame() code must be a certain way to pass through the properties.
Right after DGSource() you can add propShow() to see what it has set.
Note that an intermediate filter, such as fmtc_resample(), may not be passing through the props that DGSource() has set. Use propShow() at various places to test that. The GetFrame() code must be a certain way to pass through the properties.
Frame properties support for Avisynth+
Last one from pinterf.
Thank you for the hint. For a progressive stream
Code: Select all
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference fra : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 24 min 29 s
Bit rate mode : Variable
Bit rate : 34.6 Mb/s
Maximum bit rate : 40.0 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.695
Stream size : 5.91 GiB (91%)
Language : English
Default : Yes
Forced : No
Is it correct?
Frame properties support for Avisynth+
Maybe, maybe not. Please provide a sample.
Technical note: Streams are assumed interlaced unless some indication of progressive is seen. These indications are different for the different video types. The code for that is likely incomplete, so your sample will help us to complete things.
Frame properties support for Avisynth+
https://www.upload.ee/files/15323667/AnoHana.7z.html
Don't mind about the other included files, they come from some getnative tests.
Frame properties support for Avisynth+
Thank you. Will check it out. Generally, it is difficult to determine if a stream is "really" interlaced or progressive. For example, a stream may be encoded as interlaced but have progressive content, or vice versa. We can give a best guess based on stream parameters, but it is not foolproof. One case is when the container and ES indications differ. We check only the ES indications.
I don't know MediaInfo's algorithm and I'm not interested in trying to decipher it from the source code.
One thing you can be sure of is that after applying a deinterlacer (using DG), _FieldBased will be set to progressive. For other things, we can surely make tweaks as indicated. I'll check out your stream and report back.
I don't know MediaInfo's algorithm and I'm not interested in trying to decipher it from the source code.
One thing you can be sure of is that after applying a deinterlacer (using DG), _FieldBased will be set to progressive. For other things, we can surely make tweaks as indicated. I'll check out your stream and report back.
Frame properties support for Avisynth+
Happy Russia Day to you all!
Frame properties support for Avisynth+
Thank you, Boris.
@Guest 2
Please test this. If it is OK I'll port the change to the Vapoursynth side and make a slipstream.
https://rationalqm.us/misc/DGDecodeNV_Guest 2.rar
@Guest 2
Please test this. If it is OK I'll port the change to the Vapoursynth side and make a slipstream.
https://rationalqm.us/misc/DGDecodeNV_Guest 2.rar
Frame properties support for Avisynth+
Thank you, I'll make a slipstream.
Frame properties support for Avisynth+
Slipstream with the fix is released.