GNOME Bugzilla – Bug 579666
[LGM2009] saved timeline renders incorrectly
Last modified: 2009-05-01 16:53:26 UTC
I spent some time making an actual video editing project with pitivi today and was hit by a bug. The timeline was rendering fine, until past some point when the project was pretty much complete. I don't know what was the turning point, but probably that the project file got messed up somehow. The result is that if I try to render the timeline, after half of the first clip, it starts lagging, skipping frames, freezing frames, etc. All with the latest gnonlin git. No changes were pulled from pitivi/gnonlin between the moment I started editing and the moment I experienced this bug. This used to render fine before the timeline was complete, so I'm just throwing the wild hypothesis that the xptv file may be borked. I can provide the sample files if needed, they're ~230 Mib.
Created attachment 132997 [details] xptv file and debug log
http://jeff.ecchi.ca/public/bug-pitivi-579666.mov is a demonstration of the problem
Ok, this happens no matter what project I do (made a new timeline today), so I won't be able to render anything until then.
Created attachment 133276 [details] debug log GST_DEBUG=3,gnl*:5,python:5 PITIVI_DEBUG=5 of a different timeline rendering.
Marking as "LGM blocker" because it prevents me from showing a rendered output/production.
Created attachment 133735 [details] debug log GST_DEBUG=3,gnl*:5,python:5 PITIVI_DEBUG=5 killed pitivi brutally during the rendering as requested
Fixed by this commit, confirmed by Jeff. commit 930bb1019ba6dbdbb1805614029a0e7b9f49bd65 Author: Edward Hervey <bilboed@bilboed.com> Date: Fri May 1 18:27:19 2009 +0200 action/sinks: When disabling Sync, also disable QoS. This should fix the 'stuttering' issue when rendering on computers which are too slow to do (faster than) real-time rendering.