Leaderboard

You really have a whole host of FPS-related problems in that video 0:09 Here you have 2 problems. The most obvious one is the constant flickering from one frame to the next. This is caused by a combination of the camera motion and a lack of motion blur. Motion blur would largely fix this, but then of course youll have a much softer animation. The real answer here is that this simply isn't a shot you should do on low fps projects (24, 25 30fps) The second problem here is that you have a 24/25 fps mismatch. Once per second the camera skips an entire frame, this usually means you have rendered at 24fps, but your editing app is trying to stretch this to 25 fps. 0:22 Here you have a different fps mismatch. You can see the image jumping 4-5 times per second, this tells us that there is a 24/25 to 30 fps conversion problem.

I've had a similar problem once, and it was fps-related. My C4D-scene was setup with 24 fps. I rendered it as an image sequence and imported that to Premiere. The Premiere project setting was also 24 fps. BUT! When I imported my rendered image sequence, Premiere decided to interpret it as 25 fps -- introducing a very similar amount of jitter as shown in your video. The solution: After importing the image sequence into premiere, go to your project bin, select the clip, rightclick and search for "interpret footage as" (or something similar). In the dialogue, select your correct fps. Only after doing this, use the clip in the timeline. Now everything should be smooth as butter. I guess, the same solution applies to other apps than Premiere as well.

I'm not sure, what count of segments means? If it is the number of selected polygons, then the "Selection to Indices" node comes to the rescue. On it's output you get an array with indices (with default settings) of selected entities (points, polygons,...). "Get Count" node can then deliver the size of the array and thus the number of selected entities.

Been busy, but still alive.