Quote:
|
I'll take a look and see if I can spot an error in source.
|
Just to be clear, I have this issue with Morph, not FrameSurgeon. I created a new thread which details this particular issue (among other things perhaps too many things at once !...). I verified, the code is strictly identical to what I copied from this thread in January, and it worked flawlessly then :
https://forum.doom9.org/showthread.php?t=161154
As I said in that thread I created today, StaxRip apparently changed something in the Avisynth+ directory, but I can't figure out what exactly, or determine if it's indeed related with that issue.
I also get this message when opening AVSPMod :
Error parsing plugin string at position 0:
And nothing else, so I don't know what the exact problem is...
Quote:
|
Best source to use is always gonna be from lossless (ideally AVI, reliable frame exact)
|
Well, as far as I understand it, loading any source in Avisynth produces the equivalent of a lossless video stream for all the processing filters which are applied in the script... Or did you mean something else ?
Quote:
|
also note, FrameSurgeon switches OFF scene change detection [thSCD1 & thSCD2] in MvTools, (as Sawbones/FrameSurgeon is user driven, and user presumably thought result was good).
|
I'm not sure I understand that part... What does switching off scene change detection entail in this case ?
Quote:
|
Where bad result, dont mark for use in Framesurgeon, must process later (perhaps with some mvtools solution and with thSCD1 & thSCD2 not switch off, where will probably result in blend / or frame copy depending upon mvtools blend arg).
|
Not sure I understand this either !
I've read threads where it was reported that MVTools would produce that kind of artifacts with sources in resolutions higher than 1280x720 :
https://letransfert.soforums.com/t61...S-MVTOOLS2.htm
https://forum.doom9.org/showthread.php?t=165075
Those threads are several years old, do you know if there has been any progress since then ?
Thanks for your quick feedback !