Animations start on the wrong frame about mb3d

[bezo97]

I'm pretty sure this bug was present in a lot earlier versions too, way before the 1.9x releases.

[thargor6]

I'm also pretty sure that I did not change there anything during the last years.
Unfortunately, I could not even duplicate the problem. Added two keyframes and it worked as expected. What else is requiered?

[WAUthethird]

That's it, really. I changed nothing from the default aside from the image type.
You're sure it worked as expected? As in, you rendered the first frame both as a standalone render and as an animation to compare?

[WAUthethird]

Here's a test .m3a that exhibits the problem.
test.zip

[thargor6]

I rendered the whole animation as single frames (which btw. did never stop, might this be a bug, too?) Which setting exactly would be "as animation"?
Thanks for the file, will check that later.

[WAUthethird]

Yeah, I rendered as single frames as well. What I'm referring to is a render in the main program (i.e. sending the first position to the main program) versus an animation via the animations window. The never stopping issue is another problem; it does eventually stop but only after quite a few extra frames past the supposed stop number.

[bezo97]

I was able to replicate it, it's easier to see on a formula that's supposed to be symmetrical in the very first frame, such as Menger3:

[WAUthethird]

@thargor6 No pressure, but do you have any updates regarding this? I have a slightly time-sensitive project I'd really like to get going on.

[thargor6]

I'm currenty very busy with other projects and hoping for a free time-slot soon...

[thargor6]

could be then combined with the feature request regarding animation frames

[WAUthethird]

Hi again. I really don't want to come off as rude (I know you're doing this for free) but I'm just wondering if you have any updates on this?

[thargor6]

So I had a look at your example file.
The reason seems to be Bezier interpolation (a Bezier curve does not exactly hit the interpolation points).
There seem at least three workarounds:
a) use linear interpolation
b) insert a keyframe with the same position before the first keyframe
c) start with the camera a little bit more at the left
Does this make sense to you?

[WAUthethird]

Yes, that makes sense.
I tested linear interpolation and inserting a keyframe with the same position before the first keyframe.
Linear interpolation exhibits none of the problems that Bezier interpolation does, however this comes at the cost of clean movement, so for me at least, it is not an option.
Inserting a keyframe with the same position data as the first before the first keyframe does work provided I set the number of frames calculated to 1 (don't want it to render the same frame 50 times) but it does work.

However, there is another issue with the program that suggests this is a bug. On every animation render I do, the program usually keeps going past the set framelimit for a while before stopping. This means that camera movement is slower than accounted for, which makes syncing to music very difficult.
I have a suspicion that these two are connected, as the fact that the counter keeps going up (i.e. it'll say "584 out of 500 done") tells me there's something going wrong.

Perhaps this is related?

mb3d/Interpolation.pas

Line 638 in c87fcf0

//new: step midpos back to camera! ... direct header H1..H3 manipulation is not allowed!

[thargor6]

I see, and also faced this problem a long time ago. But looking at this code, I have to conclude that it would be easier to rewrite it than to understand it with all its hard coded values and many commented out parts. It seems that the original author also tried many things and then stopped somewhere.
Maybe you could switch to Mandelbulber?

[WAUthethird]

Yeah. That definitely makes sense.
Okay, I'll probably try to use your workarounds for a while before trying to get myself to finally learn Mandelbulber haha

Thanks for the help!