GNOME Bugzilla – Bug 644533
Hangs with 100% usage at the end of the rendering process with long vob files
Last modified: 2014-04-22 23:31:05 UTC
Created attachment 183177 [details] debug log with GST_DEBUG=3,gnl*:5,*ERR*:5,python:5 PITIVI_DEBUG=5 From https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/707239 One pattern I have noticed is that vob files that have "hung for a long time at 99% with 100% CPU usage" have all been files with long durations/big filesizes... As such, with some vob files I have here, I can reliably reproduce a "hang" when rendering is nearly complete. Test procedure: 1. import a big vob clip and insert into the timeline 2. trim the clip to a length of ~10 secs (to make rendering/testing faster) 3. render to theora+vorbis Result: the render process hangs at the very end, with pitivi eating 100% CPU (so it's still "working" on something). The render may actually complete, but it can literally take days to do so. Debug log attached.
Note to self: the debug log above was generated by myself, with the Epica vob files as a test case.
I have the same problem with Pitivi 0.15.2 on Ubuntu 12.04 when trying to export to 1280x720 in 30fps. Reducing to 24fps unlocks the rendering (so far)
Created attachment 227012 [details] Log of rendering popup hanged PITIVI_DEBUG=*:5 GST_DEBUG=2 /usr/bin/pitivi > debug.log 2>&1
Update: reducing to 24fps only fixed it for a less-than-one-minute-long video. With 7 minutes, it's impossible to render. I tried a lot of different rendering settings (webm, avi, ogg, mp4, in 29fps, 25fps, 24 fps, in 640x360, in 1280x720). It's upsetting because it makes it completely useless. I can feel it's great and edition is super-easy, and then I can never produce anything with it. I'm attaching a debug log run on a 7 minutes video, where you can clearly see that, after a while, the timelinePositionChanged value doesn't change anymore (there is a single "WARN" a few dozen lines before that). This is where the rendering stops and the window is left at "1 second left". I generated the debug log with: PITIVI_DEBUG=*:5 GST_DEBUG=2 /usr/bin/pitivi > debug.log 2>&1 I'll download the development version now, to check if this has been fixed.
When downloading the dev version and launching autogen.sh (on Ubuntu 12.04), I had autogen fail on the gettext version or something like that: === checking for xgettext... /usr/bin/xgettext ./configure: line 5286: syntax error near unexpected token `0.35.0' ./configure: line 5286: `IT_PROG_INTLTOOL(0.35.0)' === I commented the INTLTOOL line in configure.ac and it let me continue, but then it failed during make: === Making all in po make[1]: entering directory « /tmp/pitivi/po » Makefile:127: *** multiple target schemas. Stop. make[1]: exiting directory « /tmp/pitivi/po » make: *** [all-recursive] Error 1 === After looking around a little, it appears the compilation requires the intltool package to be installed. Would be nice to state it that way in the autogen process. This worked, so I continued and found that launching bin/pitivi didn't work so well, just returning: === GStreamer Editing Services couldn't be found! === Then I tried bin/pitivi-git, which downloaded some gstreamer stuff but then stopped on: === checking for GST... configure: error: Package requirements (gstreamer-0.10 >= 0.10.20) were not met: No package 'gstreamer-0.10' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables GST_CFLAGS and GST_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. === This also moved me (chdir) to ~/pitivi-git, and apparently deleted part of my bash history (too much, actually). Just in case (before starting to install my own version of everything), I tried installing libgstreamer0.10-dev: === sudo apt-get install libgstreamer0.10-dev === But that didn't work out either. Would anybody be so kind as to inspire me a little about what is the "ges" module that bin/pitivi wants to import and how to install it so I can finally test the development version of Pitivi?
So far, I could find that "ges" goes for gst-editing-services. However, I cannot find any reference to "ges" in the gst-python package downloaded by the pitivi-git script, so it remains a complete mistery to me
(In reply to comment #6) > So far, I could find that "ges" goes for gst-editing-services. However, I > cannot find any reference to "ges" in the gst-python package downloaded by the > pitivi-git script, so it remains a complete mistery to me and sudo apt-get install ges0.10-tools libges-0.10-0 libges-0.10-de doesn't help. I'm done spamming now, until someone can spend a few minutes to help me out.
I have a little bit of additional info now (although I'd like to open a new task for this because the way the problem presents itself is a little different now, I still think it's most useful here). I recently upgraded to Ubuntu 12.10 and there has been no change in the behaviour described above. So I decided to follow the instructions on the wiki following the "Manual Way" of the latest git version on the wiki: http://wiki.pitivi.org/wiki/Building_with_GES The installation works well and I can start Pitivi. As far as I can see, there are a few things broken in the timeline view fo now (no pre-rendering of frames) and less rendering options, but that's fine by me. When I try rendering a single video cut in several bits separated by png images and with an MP3 audio track, in HTML5 or in OGV (equally), it gets blocked in the "Rendering in progress" popup at the "Initialization..." step (while in the stable package it used to get blocked at the "1% left" step). I get the following 5 errors (sometimes the URI one if last, sometimes previous-to-last) whatever the format, whatever the size and frames/sec. ERROR 09:55:39 pipeline _busMessageCb: error from <__main__.GstAudioTestSrc object at 0x4315b90 (GstAudioTestSrc at 0x1c259c0)>: Erreur interne de flux de données. (gstbasesrc.c(2791): gst_base_src_loop (): /pitivi+utils+pipeline+Pipeline:pitivi+utils+pipeline+pipeline1/pitivi+project+Timeline:pitivi+project+timeline1/GESTrack:gestrack3/GnlComposition:gnlcomposition3/GnlSource:gnlsource147/GstAudioTestSrc:audiotestsrc52: streaming task paused, reason not-negotiated (-4)) (pitivi/utils/pipeline.py:416) ERROR 09:55:39 pipeline _busMessageCb: error from <__main__.GstVideoTestSrc object at 0x4315b90 (GstVideoTestSrc at 0x36c5800)>: Erreur interne de flux de données. (gstbasesrc.c(2791): gst_base_src_loop (): /pitivi+utils+pipeline+Pipeline:pitivi+utils+pipeline+pipeline1/pitivi+project+Timeline:pitivi+project+timeline1/GESTrack:gestrack2/GnlComposition:gnlcomposition2/GnlSource:gnlsource183/GstVideoTestSrc:videotestsrc122: streaming task paused, reason not-negotiated (-4)) (pitivi/utils/pipeline.py:416) ERROR 09:55:39 pipeline _busMessageCb: error from <__main__.GstAudioTestSrc object at 0x4315b90 (GstAudioTestSrc at 0x1c259c0)>: Erreur interne de flux de données. (gstbasesrc.c(2791): gst_base_src_loop (): /pitivi+utils+pipeline+Pipeline:pitivi+utils+pipeline+pipeline1/pitivi+project+Timeline:pitivi+project+timeline1/GESTrack:gestrack3/GnlComposition:gnlcomposition3/GnlSource:gnlsource147/GstAudioTestSrc:audiotestsrc52: streaming task paused, reason not-negotiated (-4)) (pitivi/utils/pipeline.py:416) ERROR 09:55:39 pipeline _busMessageCb: error from <__main__.GstVideoTestSrc object at 0x4315b90 (GstVideoTestSrc at 0x36c5800)>: Erreur interne de flux de données. (gstbasesrc.c(2791): gst_base_src_loop (): /pitivi+utils+pipeline+Pipeline:pitivi+utils+pipeline+pipeline1/pitivi+project+Timeline:pitivi+project+timeline1/GESTrack:gestrack2/GnlComposition:gnlcomposition2/GnlSource:gnlsource183/GstVideoTestSrc:videotestsrc122: streaming task paused, reason not-negotiated (-4)) (pitivi/utils/pipeline.py:416) ERROR 09:55:39 pipeline _busMessageCb: error from <__main__.GstQTDemux object at 0x4315b90 (GstQTDemux at 0x7f2230012780)>: GStreamer a rencontré une erreur générale de flux. (qtdemux.c(3946): gst_qtdemux_loop (): /pitivi+utils+pipeline+Pipeline:pitivi+utils+pipeline+pipeline1/pitivi+project+Timeline:pitivi+project+timeline1/GESTrack:gestrack3/GnlComposition:gnlcomposition3/GnlURISource:gnlurisource6/GstURIDecodeBin:internal-uridecodebin/GstDecodeBin:decodebin25/GstQTDemux:qtdemux15: streaming stopped, reason error) (pitivi/utils/pipeline.py:416)
For the record: from investigating on IRC, Yannick's problem was not the same thing. When in doubt, bug reports should be filed separately (in his case it turned out to be due to gaps in the timeline).
Hi Yannick, As Pitivi 0.91 has now been released, we would like to encourage you to test it. It is quite possible that this issue is fixed in 0.91, as it is a very significant technical overhaul compared to the 0.15 series. Read more about the 0.91 release here: http://wiki.pitivi.org/wiki/0.91 If you can reproduce this bug against 0.91 or newer (such as the git version), please update this bug report accordingly with detailed instructions to reproduce the bug, updated sample files/projects in xges format, etc. Drop by our IRC channel if you need help getting started or want to help out! Thanks!
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!