terrible jittering or flickering of some parts of the tree

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Normal use? I'll include the command line below.

What is the expected output? What do you see instead?
Smooth flowing. Instead I see parts of the tree that flicker back and forth 
badly... like some of the nodes can't decide between two points where they 
should be... say 20px apart from each other at 1280x720

What version of the product are you using? On what operating system?
0.34 and 0.37 on Linux Mint 12 64bit

Please provide any additional information below.
The command line params are:
gource --hide filenames -c 4 --load-config gource2.cfg --max-user-speed 100 -r 
25

With the config file:
[display]
viewport=1280x720

[gource]
auto-skip-seconds=0.01
camera-mode=overview
default-user-image=person5.png
font-colour=f3f516
hide=progress
highlight-colour=f3f615
highlight-dirs=true
highlight-users=true
key=true
logo=HAIKU logo - white on transparent - small.png
seconds-per-day=0.01
stop-at-end=true
time-scale=1.2
user-image-dir=/home/justin/haiku/.git/avatar/
user-scale=8

and a long list of user names to highlight such as
highlight-user=DarkWyrm

Original issue reported on code.google.com by jstress...@gmail.com on 4 Mar 2012 at 3:29

[GoogleCodeExporter]

I've uploaded a video of it... a perfect example of this problem is found at 
the time stamp: http://www.youtube.com/watch?v=MDd5rdNPCg0#t=168s

I'd really like to figure out what's causing this so that I can do a proper 
version without the glitches. Thanks!

Original comment by jstress...@gmail.com on 4 Mar 2012 at 4:37

[GoogleCodeExporter]

It appears that -c 4 (time-scale 4) is causing the jerky animation. I would 
suggest trying smaller values until it goes away. time-scale is kind of a hack 
which alters the size of the time delta used by the simulation, and large time 
deltas cause the physics simulation to produce bad results in complex 
situations.

The best approach if you want the video to appear sped up is to tell ffmpeg to 
treat the incoming frame rate as a multiple of the framerate being used by 
gource (eg gource -r 30, ffmpeg -r 60).

Original comment by acaudw...@gmail.com on 13 Mar 2012 at 9:26

[GoogleCodeExporter]

Thanks for the feedback. :) I'll give that a try next time.

Original comment by jstress...@gmail.com on 13 Mar 2012 at 9:34

[GoogleCodeExporter]

Original comment by acaudw...@gmail.com on 4 Apr 2012 at 9:28

• Changed state: Done