Pete31684

Shouldn't that read "how the animation module doesn't work"? But if broken is the best it's going to get, then I guess I can't say anything else.

Start with a 30fps clip. Add it to the timeline. Add a stopwatch, I tried milliseconds. Single frame stepping "sort of" works in that it will step, but you get four frames per hundred milliseconds instead of the 3 it should be. Enable "Show Previous and Next Frames". Now it just locks up when trying to frame step forwards.

I've done some more checking and installed it on Win 10, it's still buggy, but in a slightly different way. You can see it in your last video. Look at the VP cursor position. It displays 00, 33, 66, 67, 00, etc. That's obviously wrong in that the 66 shouldn't exist. The result is four steps every 100ms instead of three. On Win 8.1 (two different machines) it just locks up going forwards, and displays the wrong numbers going backwards.

Are we at cross purposes here? One can add a stopwatch, that's it, done. Takes about 3 seconds. It will count for hours and display the elapsed time on the screen. But it doesn't work for single stepping. It just locks up going forwards, and displays the wrong numbers going backwards. I don't see any other way to duplicate this other than manually creating 54,000 frames. Are you saying the stopwatch works for you? EDIT: Ah, you're suggesting creating a stopwatch, exporting that as a video, then using that as a clip and overlaying it? I think. It's just that you said "typewriter effect" so I assumed you meant "typewriter effect."

Exporting the overlays isn't the problem. It's creating 54,000 of them, by hand, that is the problem. It would be far more sensible for NCH to simply fix the bug in the stopwatch.

A half hour clip would need 54,000 hand made things .

Ok, so it's a programmatically generated video clip. I suppose we can call it whatever we want, but it still doesn't work. It locks up when you try to single frame step forwards. It displays the wrong time when single stepping backwards. Please try it instead of denying there is an issue.

It would be nice if that was the problem. And it would indeed make perfect sense (for anyone mad enough to try to use variable frame rate). But it isn't the actual issue. I am using a single track, just one. 30 fps. It is the only clip in the media bin, and appears once in the timeline. When adding a (for example) stopwatch, it will single step forwards one or two frames, then locks up. It simply won't move any further. When moving backwards, it doesn't lock up, but it does display the wrong numbers on every third frame.

As previouisly reported, when using 30 fps files, VP seems to have nothing but trouble. It took a few hundred versions (that really isn't an exaggeration) for single frame stepping to finally work properly. But adding things like timers, stopwatches etc never works. They always lock up when frame stepping forwards, and usually show the wrong figure when stepping backwards. How difficult is it to make a processor count properly?

If you try to download the beta version under this... VideoPad Video Editor v 13.68 for Windows You get a zip file, which in itself is a new thing, but it contains an Android installation package instead of Windows. Some of the other zip links seem to be screwed up too.

My experience of reporting bugs via the official channels is that it has zero effect.

Yes, sorry, the effects. Perhaps I should have been more specific... 1. Place a 30 fps clip on the timeline. 2. Add a millisecond stopwatch. 3. Try to step through the "Sequence Preview" (not the "Clip Preview") frame by frame during the stopwatch section. It sticks on two stopwatch values (x66ms) which it shouldn't even have (they should be x67ms). 4. Enable "Show Previous and Next Frames". Now it simply jams up and won't move forwards. Backwards it misses values. All of the timer effects have some sort of problem, but this one is very clear. -0-0- I've installed VideoPad on a different PC. Version 13.49 - Exactly the same results. VideoPad can't count.

Now the frame by frame timing seems to have been fixed, there's a new bug. At least I think it's new. With a 30 fps clip, the timers and counters no longer work. They stop frame forwards working, the clip just jams up. Play works, frame back works, but frame forwards doesn't work. And it's always on the 33ms frame, like the other issue.

This is an absolutely massive improvement. Genuinely huge. It's not quite perfect, but after a 10 minute test drive it appears to be good enough that the few minor remaining issues are trivial enough to be ignored or worked around... So far. Yay. VideoPad has learnt how to count to 30 without tripping itself up!

That simply doesn't explain what is seen. If it was the video itself that had duplicated frames, they would also show as duplicated in the "previous" and "current" frame. They do not. Only the "next" frame is wrong. They would also show duplicated frames in other software packages. They do not. Only VideoPad "next" frame gets them wrong. Nothing else. The file I am using was manually generated (in Express Animate as it happens). It consists of individual frames that simply contain the time and frame number. It was created at 30fps. No re-encloding, no frame rate conversion. The results are as follows (you'll have to put it into a text file to get the columns right):- Time previous current next 167 04 05 06 200 05 06 07 233 06 07 07 <- this is wrong 267 07 08 09 <- where has frame 08 gone? 300 08 09 10 333 09 10 10 <- this is wrong 367 10 11 12 <- where has frame 11 gone? It is definitely a bug in VideoPad, not a currupt video file. -0- 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.