Remove timestamp

[Rockel83]

I've configured all the video's now so far and I'm doing a final check to see if all the video's are included, are in the right order and if the transitions are good. For this I've commented delogo out temporarily, so I can take advantage of the timestamp here for easier coordination.

The things so far:
- I've opened the script in the first tab. And opened the corresponding video's in the right order in extra tabs, calling them v1, v2, v3 etc.
- I've looked for places where to take the transitions and put that info in the script in the first tab in the corresponding output. So v1 to o1, v2 to o2 etc.
- And looked if and where there were glitches of the loop recording cuts. If they were, they always occured at frame 10801 (easy!). So I believe I've replaced glitching frame 10801 with frame 10802 all the time.

(I'm on my way to work now, so I quickly made some foto's)


[Attachment 65350 - Click to enlarge]


[Attachment 65353 - Click to enlarge]

But now on my final check (on the playback screen in the script tab) before "exporting" it seems that the transitions look fine and exactly how and where I've put them. But the replaced frames where the glitches were seem to be still there and visible in playback in the script screen.
Only the first clip where a replacement frame is set, seems to be correct and duplicated. Then I see 1 duplicated frame. But in the following positions I still notice glitches.


[Attachment 65351 - Click to enlarge]

[Selur]

seems to me like
".Trim(10856,999999).FreezeFrame(10801, 10801, 10802)" (and similar)
is wrong, it should be
".FreezeFrame(10801, 10801, 10802).Trim(10856,999999)"
like VoodooFX wrote a few times,....

[VoodooFX]

For some reason he refuses to listen to our advises.

PS
jagabo wrote that you should use "0" instead of "999999" [I didn't knew about "0" option, because I'm too lazy read AvS docs].
And he gave you example of "OpenAV" to simplify your tasks...

[Rockel83]

Oh, excuse me. Thought it didn't made anny difference as long it's on the same line.

It was working in the first 2 clips, so I thought it should be fine.

So I need to change everything to the following setup: .freezeframe -> .trim?

I'm going to make these changes tonight after work then!

Edit:
But isn't this the same setup then?
First the trim function is mentioned, seccond the freeze function.

Line 10 in your script does nothing, since it's overwritten in line 11.
You probably wanted:

o1 = AudioDub(v1,a1).Trim(0,10856)
o1 = o1.FreezeFrame(10801,10801,10802)

[VoodooFX]

Oh, excuse me. Thought it didn't made anny difference as long it's on the same line.

It doesn't make difference as long as you understand what you are doing.
Trim() changes timeline, if you take frame numbers from original timeline then they may not fit a changed timeline.

Let's say if you cut off first 100 frames [Trim(100, 0)], so 150th frame from original timeline is 50th after your trim is done, you've to take that into account when using filters after Trim.

[Selur]

Oh, excuse me. Thought it didn't made anny difference as long it's on the same line.

That is why folks should not start with doing multiple statements in a line, it takes them to wrong assumtions,...

[VoodooFX]

I doubt that multiple lines help newbies to understand changed timeline.

EDIT:
Look at his edit, confirms my assumption.

[Rockel83]

Oh, excuse me. Thought it didn't made anny difference as long it's on the same line.

It doesn't make difference as long as you understand what you are doing.
Trim() changes timeline, if you take frame numbers from original timeline then they may not fit a changed timeline.

Let's say if you cut off first 100 frames [Trim(100, 0)], so 150th frame from original timeline is 50th after your trim is done, you've to take that into account when using filters after Trim.

Oh, so if I'm understanding this correctly it's following the sequence in order it's written?
So when I take Trim before freeze. Then it's first cutting (let's say) 10 frames off. And freeze 10801 occurs actually on frame 10811then?

So this explains why it's looks normall on the first 2 clips, because the first clip is not trimmed and is starting at the actual first frame, and because of this frame 10801 is still on the 10801 position?

[VoodooFX]

Yes.
No idea what you meant there. [10801 frame from original timeline would be in 10801-10 position after trim in a changed timeline]
Yes.

PS:
If you still want to use FreezeFrame after Trim, then you can apply same Trim in other tab to get fitting frame numbers, or just use math.

[Rockel83]

Oh excuse me, then I will go to try to put freeze before trim. It will be easier and quicker then the seccond method. Freeze is replacing the glitched frame with the following frame. So it will not change the timeline length and interfere with with the trim function then?

But what is the difference with every edit on a different line? Then I also need to place freeze before trim. So freeze in the first line and trim in the second?

[Selur]

So it will not change the timeline length and interfere with with the trim function the

no, since it does not change the frame count.

But what is the difference with every edit on a different line?

Might be easier to understand what is happening. you clearly did not with multiple calls in one line.

So freeze in the first line and trim in the second?

Yes, one would do speparate lines with the FreezeFrame before the Trim call.

[Rockel83]

Ok, clear!
So freeze should come before trim because trim is changing the timeline length. No matter when using a single line or multiple lines

I will going to look into it after work tonight.

[VoodooFX]

Here is InpaintDelogo with perfected mask for your videos to achieve higher quality de-timestamp:

InpaintDelogo(Loc="4,990,-1380,-4", DynMask=3, DynTune="140 - 200", DynColor=$FFB900, DynColorTol=65, DynInflate=2, Dyn3Seq=52)

It needs latest InpaintDelogo v2.17, where I added option for a ranged luma mask.

Previous mask vs New mask [at bottom] comparison:

[Rockel83]

Here is InpaintDelogo with perfected mask for your videos to achieve higher quality de-timestamp:

InpaintDelogo(Loc="4,990,-1380,-4", DynMask=3, DynTune="140 - 200", DynColor=$FFB900, DynColorTol=65, DynInflate=2, Dyn3Seq=52)

It needs latest InpaintDelogo v2.17, where I added option for a ranged luma mask.

Manny thanks! Awsome!

I've just updated the plugin to the newest InpaintDelogo 2.17.
But when I'm trying to use your new part of the script I get the following error:


[Attachment 65369 - Click to enlarge]

[VoodooFX]

I've just updated the plugin to the newest InpaintDelogo 2.17.
But when I'm trying to use your new part of the script I get the following error:

That error means that you didn't updated.

[Rockel83]

I've just updated the plugin to the newest InpaintDelogo 2.17.
But when I'm trying to use your new part of the script I get the following error:

That error means that you didn't updated.

Oh, but I took the file from Github, saved the RAW file as *.avsi and placed it in the pluginfolder with the other plugins.

Edit:
Ok, I think I know what I did wrong here...
I commented the 2.14 file out with an "_". But it was still in the plugin dir.
Completely removed it, and it works now

[VoodooFX]

Maybe again it was saved with ".txt" extension like before.

[Rockel83]

No, it had the right extension.

But I thought I could comment it out with an "_". But seems I needed to colmpletely remove it from the plugin folder.

[VoodooFX]

If you want to "comment out" plugin then you need to change an extension name, not a filename. Like this: ".dll_".

[Rockel83]

Oh I see yes, I was thinking that Avisynth is just reading all the files in the plugin folder, despite the filename.
Normally I comment out files like this "_filename.file" when I need to test something and to keep something as backup to go back to the previous settings. But commenting out the extension is also a good option btw! Just deletede the old IndePaintlogo file for now. But it works.

btw, I think the old mask gives me a slightly better coverup in some video's. Especially when there's a lot of detail in the background like, leaves in the jungle.

There the new mask seems to have some problems with the dashes there, while the old mask covers everything op besides a single small point of a ":".




[Attachment 65370 - Click to enlarge]

[VoodooFX]

There the new mask seems to have some problems with the dashes there, while the old mask covers everything op besides a single small point of a ":".

Could be, I tested only on your videos you've shared, bump DynInflate to 3 then, mask will be a lil bigger to cover everything but still should be better than old one:

InpaintDelogo(Loc="4,990,-1380,-4", DynMask=3, DynTune="140 - 200", DynColor=$FFB900, DynColorTol=65, DynInflate=3, Dyn3Seq=52

[Rockel83]

There the new mask seems to have some problems with the dashes there, while the old mask covers everything op besides a single small point of a ":".

Could be, I tested only on your videos you've shared, bump DynInflate to 3 then, mask will be a lil bigger to cover everything but still better than old one:

InpaintDelogo(Loc="4,990,-1380,-4", DynMask=3, DynTune="140 - 200", DynColor=$FFB900, DynColorTol=65, DynInflate=3, Dyn3Seq=52

Cool, going to try that!

The new old one is more obvious yes.

Edit:
Can't remove it, even not with DynInflate to the max. of 4


[Attachment 65371 - Click to enlarge]

[VoodooFX]

[Attachment 65370 - Click to enlarge]

Hmm, that's strange. Can you share this part of video?

[Rockel83]

Hmm, that's strange. Can you share this part of video?

Yes, I'm going to look how to extract this part.

I've added a printscreen of DynInflate to the max in my last comment.

[jagabo]

The worst part of using such close masking is that you can still read the timestamp (or logo or subtitle or whatever it is you're trying to hide).

[Rockel83]

I'm getting this error when I try to export it:


[Attachment 65373 - Click to enlarge]

[jagabo]

You need to provide an extension for the output filename.

[Rockel83]

You need to provide an extension for the output filename.

Oops...

[VoodooFX]

Yes, I'm going to look how to extract this part.

Same as before, with MKVToolNix.

The worst part of using such close masking is that you can still read the timestamp.

You can't, closer the mask less things to "read" there.

[Rockel83]

Yes, I'm going to look how to extract this part.

Same as before, with MKVToolNix.

Yes, I'm exporting only the first segment for you already now, i'ts only 3 min, so it shouldn't be a lot much bigger than 350MB I guess

Edit:
This is the sample
https://we.tl/t-XqIitSFCPE

with DynInflate to the max. of 4