trim and mainconcept standalone.

[45tripp]

Using something like:

LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\dgdecode.dll")
mpeg2Source("goods-prog.d2v")
trim(5500,7000)

with mainconcept sometimes returns video 1 frame short.
I've tried with 2 diff sources and tried diff ranges but can't find a pattern to it.

Does anybody know about this?

I can't find the missing frame.
How would I find it?
What would be the best way to re-insert it, or the best/fastest/easiest way to faux fix it?

I want the exact range I've selected with the exact no of frames.

[manono]

That script of yours returns 1501 frames. Are you saying that MainConcept sometimes returns 1500 frames? I don't use it, so I don't know. Maybe it's related somehow to the fact that AviSynth begins with frame number 0. I don't know how you'd find it, except to suspect it's at the very beginning or very end. To add another frame to get the number you like, you can repeat one of the frames using the Loop command:

http://avisynth.org/index.php?page=Loop

[45tripp]

That script of yours returns 1501 frames. Are you saying that MainConcept sometimes returns 1500 frames?

Exactly

I don't know how you'd find it, except to suspect it's at the very beginning or very end. To add another frame to get the number you like, you can repeat one of the frames using the Loop command:

I think it drops either the last or 3rd from last frame. I have no idea when it chooses one over the other.

I've tried

LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\dgdecode.dll")
mpeg2Source("goods-prog.d2v")
trim(500,3800)+trim(5500,7000)
loop(2,7000,7000)

Which gives 4803 frames

and

LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\dgdecode.dll")
mpeg2Source("goods-prog.d2v")
trim(500,3800)+trim(5500,7001)
deleteframe(7001)

which again gives 4801

I just can't seem to get 4802...
[/quote]

[manono]

Hi-

According to File-File Information of VDubMod, the first script gives 4803 frames, and without the Loop Command, it gives 4802. I don't know what MainConcept gives.

The second script gives 4802 frames, and without the DeleteFrame command, 4803. Again, I don't know what MainConcept gives.

Which gives 4803 frames
which again gives 4801

Those are the framecounts from your MainConcept encode? So it gives you the right count for the first script, and is one short for the 2nd script? Strange, eh? How are you getting the encoded frame count? Have you made a D2V from the encoded MPV or M2V, and an AviSynth script using the new D2V to then open in VDubMod to get the framecount? I'm not sure I'd trust any framecount that wasn't from a script.

[45tripp]

hi

Which gives 4803 frames
which again gives 4801
Those are the framecounts from your MainConcept encode?
So it gives you the right count for the first script, and is one short for the 2nd script?

Yes.
The thought was to up to 4803 and hope it cuts a frame, which it doesn't, or try
a diff script that outputs 4802, and hope mainconcept likes it.

Strange, eh?

Annoying too.

How are you getting the encoded frame count? Have you made a D2V from the encoded MPV or M2V, and an AviSynth script using the new D2V to then open in VDubMod to get the framecount? I'm not sure I'd trust any framecount that wasn't from a script.

Yes.
The first time at least.
Then I'd just input the mpv into vdub-mpeg2 to get framecount.
The problem is at the origin where mainconcept interprets the avs script to contain 4801 frames instead of 4802. And what it interprets it outputs. It's not faulty encoding, mainconcept is not handling the avs script correctly in the first place.
Maybe it just doesn't like trim.
Not encouraging at all.