I do understand you very well Phil! And there has to be no debate. but you might let me post something as it would not be that good to leave that subject until you got time.
But if someone else does underline your point he can also act for you. As I do not say "Its like I do say" but Im following a logic and an experience of mine, ... thats all
DVD sources are ...based on mpeg2 yv12 streams ... therefore also based on DCT based compression like mpeg4! I think we agree in this point.
IF you got a veery good high quality backup in mpeg4 of your DVD (and we are talking here about exact that rare case)... means a quality like the orig. Also here MA (IMHO) can be used as it also bases on yv12 input.
Good or Bad??? Do you think I would use a such high filtering Optimalscript on a very exact clean mega detailed mpeg4 incl. not one "blocky" part etc?
And thats why I recommended to the starter of this thread to just "try" the MA on his source as optimal script (as he told) was filtering to heavy on his mega good source. I m not in doubt of your way (btw. you didnt understand it like this but just saying that in case of other participants of this thread)
So how do we have to "see" his problem in case of this "blinking".
So an answer cant be generally "leave MA" on mpeg4 (although in regular that would be right).
So I want to know the EXACT parameters of that Avisource:
- Content seems to be a movie
- is it still in a telecined state? means 29.97 (sorry if you already pointed that out but im here in that many threads so I do not remember)
- how do you encode later?? Means which encoder is used AND which settings are used!
still interlacing was set in encoding options (Tmpgenc i.e.)... and so on!
The best would be to provide some seconds of that "credits" part of the ready encoded avi in here where these issues do occur ... then I can tell you what happens and if the probem could come from the Avisynth script OR from the later encoding process.