c_major

Stopwatch is a video clip and has its own frame rate although it's generated programmatically.

Hi Pete,

That's because on sequence preview next frame will stop at the closest frame on any track. Say if you have two clips with different speed on two tracks, you are getting some thing like this:

Track A:  1     2     3     4     ...

Track B:  1    2    3    4    ...

Since the frames are not aligned on the timeline, the next frame start from the beginning in the mixed sequence is something like this:

A(1)+B(1) A(1)+B(2) A(2)+B(2)  A(2)+B(3) A(3)+B(3) ....

So that's why the number is not jumping every time you click 'Next Frame'.

This is not an issue since VideoPad will insert and delete frames at the right position depend on user settings when export.

Hope that make sense.

16 hours ago, Pete31684 said:

Download the H.264 file from here...

https://archive.org/details/VideoTestFiles/1024X76830FpsPhotoJpeg75.mov

Single frame step through that, you'll see the bug in all its glory.

I see now. Will get this fixed. Thanks.

On 5/20/2023 at 6:24 PM, Pete31684 said:

Single stepping through the frames (on 30 fps) now correctly shows the relevant frame, forwards and backwards so that's an improvement. However, on any frame that ends in 33ms the "next" frame is always wrong. It shows the current frame and the next frame as being the same frame.

To clarify that, set it to "show previous and next frames", the "next" frame is always wrong on a 33ms interval. It shows the current frame as also being the next frame. The other two (at 00ms and 067ms) are correct (this bug existed previously).

I have tried a few different files and found that it's actually the video themselves have duplicated frames. I.e. frame 33 and frame 67 are the same. This could happen if the video is re-encoded by a video editor by forcing a constant frame rate.

I tried some original videos directly from cameras or computer rendered, they don't have this issue.

BTW: The stopping bug will be fixed for next release.

Confirmed that it will be fixed in the next release.

Hi Denty,

Sorry to hear about your problem. I couldn't reproduce this on my end so I'm unable to identify the issue.

What about turn off looping for space key? If that's a problem for everyone we will change it without an option.

Maybe an option to lock the cursor at center of the screen?

@Pete31684

It looks like a bug when seeking backward. Thanks for reporting the issue.

I see your point. I'll find a solution to this. I think this behavior should be turned off for paid users.

I have filed the bug. Thanks for reporting.

Sorry for the confusion here. We randomly turn new features off until it accepted by majority of the users. If a new feature is causing a disaster we will remove it permanently and it won't cause full damage. This is some kind of risk control strategy. We will turn the feature permanently on once it pass the testing period.

Sorry guys. Super resolution is still under development and it isn't ready yet. The check box was visible because of a mistake. We've removed it from the recent release builds.

We apologies for the confusion. I will get back here as soon as we finish this feature.

Thanks for brought up the issue. I've filed a suggestion for adding force keyframe options.

Yes, that make sense.

@Isildor121

Sorry to hear about your bad experience with VideoPad and thanks for trying out the latest version.

If you could tell us the particular issues we will look into them.

You can always export to 4k resolution. But only vector graphics, e.g. text or effects are scale with output quality.

BTW: We are adding Super Resolution feature in the next release, which will try to add detail to the original low resolution video clip through machine learning algorithm.

Hi Bart,

I've tried your test project. It looks fine here and doesn't seem to related to Lame at all.

If you can reproduce the issue constantly, would you mind if I send you a debug build so we can have a look what's in the trace log?

Thanks.

11 hours ago, BartNZ said:

Is something like that not possible in VideoPad?

VideoPad produce trace log from the debug build but not the release build.

Thanks Bart. This could be real problem for other users.

We will look into this issue and try to get it fixed.

Hi Bart,

Would you mind share the file to us so we can track down the issue?

@Lancelot Chan

Is it always happen at the same position or every time different when you reopen or export again?

Thanks for sharing the files.

The maximum memory address VideoPad 32 bit build can access is 4G.

PAE works for the OS but can't extent the address space for individual applications.

Hi Chan,

Sorry for the inconvenience. 

Do you mind share your project files with us?

You can also try unlink the video and audio clip.

There is an "Unlink" button on the sound clip on timeline. Video clip can be selected and deleted separately.