Appended clip speeds up

[Squeeto]

test.avs:

Source = DirectShowsource("00008.mts")
Source.trim(0,100)
Left=last
Source.trim(200,300)
Right=last
#Dissolve(Left, Right, 30)
#FadeOut(Left,30)++FadeIn(Right,30)
#FadeOut(Left,10)+FadeIn(Right,10)
#Left+Right
Left++Right


source is AVCHD
MPEG4 H264 1920x1080 29.97fps (interlaced)
Dolby AC3 48000Hz stereo

laptop
i7-3610QM 2.3GHz
Windows 7 64bit
AMD Radeon HD 7670M

Haali Media Splitter vers 1.11.96.14
ffdshow ver 1.1.3326 (by clsid)

The resulting video from the above .avs shows the first clip fine but the appended clip speeds up for a half second then settles down.

The same happens for FadeIn. Dissolve looks like a dog's breakfast.

Thank you.

[Squeeto]

LoadPlugin("c:\Program Files (x86)\Avisynth 2.5\plugins\ffms2.dll")
Source = FFMpegSource2("00008.mts",atrack=-1)

Source.trim(0,100)
Left=last
Source.trim(200,300)
Right=last

Left+Right


Is actually worse. It freezes then catches up to a later frame.
FFmpegSource2 2.17

:thanks:

[Didée]

Not a problem of Avisynth (core), it's merely a problem with the source filter.

DirectShowSource: Not frame accurate. Seeking (i.e. trim() ) will cause problems.

ffmpegsource: regularly makes problems with interlaced AVC. (May range from smaller problems, up to "plain unusable")

For fms2: 1st of all, remux the mts to MKV. Then try on the MKV with "threads=1", and if still no joy, additionally with "seekmode=-1" (very slow).
Also, try DSS2 (DirectShowSource2, part of the Haali MediaSplitter package)

BTW, no such problems with DGDecodeNV. It just works. If the system has an Nvidia graphics - weigh up what is worse: one time a few bucks, or thousands-of-times problems, swearing and crying, and all the time that gets lost in fighting windmills.

[Squeeto]

Thanks Didée


LoadPlugin("C:\Program Files (x86)\Haali\MatroskaSplitter\avss.dll")

Source = DSS2("00008.mts")

Source.trim(0,100)
Left=last

Source.trim(200,300)
Right=last

Left++Right


Nope. Better than ffmpeg, worse than direct.

remux the mts to MKV
I hope to not have to convert my clips before editing. Can this be done in memory on the fly?

DGDecodeNV. It just works.
Is this for NV only? I have the AMD Radeon above.

[Asmodian]

I hope to not have to convert my clips before editing. Can this be done in memory on the fly?

Sorry, no.

Is this for NV only? I have the AMD Radeon above.

Sorry, yes, NV only.

[Squeeto]

Good news, DGAVCDecode actually works for me.
There is no way I can see a dissolve transition in real time with the avs but the encoded mkv plays just fine.

[Taurus]

@Squeeto
So you are lucky.
Didée was talking about DGDecodeNV, not DGAVCDecode.
DGAVCDecode is not maintained by its developer anymore and sure has some bugs.
If it works for you, call yourself a lucky guy.
But dont rely on it for future projects.

[Squeeto]

Didée was talking about DGDecodeNV, not DGAVCDecode.


I found DGAVCDecode by looking for a non-NVidia version of DGDecodeNV.


DGAVCDecode is not maintained by its developer anymore.


Afaics, DGDecodeNV, DGAVCDecode and DGDecode (updates) are all Donald Graft (Neuron2). Just wanted to mention this since a lot of thanks go out to him right now.

[poisondeathray]

You'd better examine the footage more closely - the problem you're going to have is macroblocking and pixellation, decoding errors - there is a known issue with AVCHD PAFF (interlaced) streams and DGAVCIndex

[Squeeto]

I am quickly being educated. Thank you.
I will continue to document my progression, in this thread, so it may assist the next person.


there is a known issue with AVCHD PAFF (interlaced) streams and DGAVCIndex


What about using an updated libavcodec.dll?
Or is there a better way to go?

[Guest]

What about using an updated libavcodec.dll? Or is there a better way to go? Nope, DGAVCDec checks the DLL version number and insists upon the one it was shipped with.

The better way to go is get a cheap VP5 nVidia card and use DGDecNV.

[Squeeto]

get a cheap VP5 nVidia card and use DGDecNV


Good thing I have a dedicated graphics card on my laptop.

DGDecNV is designed to work with the NVidia chipset, is DGAVCDecDI the same as DGDecNV only it can work for any video card?

[Guest]

It's closer to DGAVCDec but with functioning PAFF support.

[Squeeto]

Okay, I found a 2nd way that works. You have to keep dissolves at around 10 frames though.

Substitute avisynth.dll with the 2.6 MT version from SEt and use the DSS2 pluggin.

The wife and I watched a frame by frame clip of gymnasium badminton and didn't see any decoding errors through 3 transitions with either DGAVCDecode or DSS2 (with avisynth alpha4 MT). But we are no pros.

The DGAVCDecode video seems to be slightly better but that is probably because the encoding produced an overall bit rate of 15.8 Mbps as opposed to the DSS2 video at 15.5.

I haven't optimized (research/tested) the encoding process, I just used:
x264.exe --preset veryslow --crf 18 -o output.mkv test.avs


My journey ends here. The wife says good enough. :cool: