After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 669869 - pitivi won't create project - internal GStreamer error
pitivi won't create project - internal GStreamer error
Status: RESOLVED INCOMPLETE
Product: pitivi
Classification: Other
Component: General
0.10.x
Other Linux
: Normal normal
: 0.15
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2012-02-11 12:35 UTC by Matthias
Modified: 2013-09-21 19:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias 2012-02-11 12:35:04 UTC
Hi,

trying to make a slideshow of jpegs with an audio-ogg-file. On clicking "create" ("Erzeugen") pitivi does nothing and gives this error message in the console:

$ pitivi
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
ERROR [14760] [0x7ffe9dc85700] "<Pipeline at 0x3abc790>"        pipeline          Feb 11 13:10:29      _errorObject: error from /GstPipeline:pipeline1/GstBin:bin57/GstAutoVideoSink:autovideosink2/GstXvImageSink:autovideosink2-actual-sink-xvimage (__main__.GstXvImageSink): Internal GStreamer error: negotiation problem.  Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer. (xvimagesink.c(2251): gst_xvimagesink_setcaps (): /GstPipeline:pipeline1/GstBin:bin57/GstAutoVideoSink:autovideosink2/GstXvImageSink:autovideosink2-actual-sink-xvimage:
Error calculating the output display ratio of the video.) (/usr/lib/pitivi/python/pitivi/log/loggable.py:30)
ERROR [14760] [0x7ffe9dc85700] "<Pipeline at 0x3abc790>"        pipeline          Feb 11 13:10:29      _errorObject: error from /GstPipeline:pipeline1/GstBin:bin1/GnlComposition:gnlcomposition2/GnlSource:gnlsource: VideoTestSourceFactory46/GstBin:bin48/GstVideoTestSrc:videotestsrc8 (__main__.GstVideoTestSrc): GStreamer hat einen allgemeinen Datenstromfehler festgestellt. (gstbasesrc.c(2550): gst_base_src_loop (): /GstPipeline:pipeline1/GstBin:bin1/GnlComposition:gnlcomposition2/GnlSource:gnlsource: VideoTestSourceFactory46/GstBin:bin48/GstVideoTestSrc:videotestsrc8:
streaming task paused, reason not-negotiated (-4)) (/usr/lib/pitivi/python/pitivi/log/loggable.py:30)

pitivi doesn't freeze, though. I can stop the process ("Abbrechen") and continue to work with pitivi. But I can't create any video.

This happens only with this "special" selection of jpegs & ogg-file (I don't know what makes it special). Other jpegs & audio work fine (even within the same session).

strange, but true...

btw, great tool! Continue the good work!
Comment 1 Vincent Penquerc'h 2012-02-12 12:46:25 UTC
Can you run pitivi like this:

GST_DEBUG=5 pitivi >& /tmp/pitivi.log

Then reproduce the issue, trying to do as few things as needed to reproduce it.
Once reproduce, just ^C, compress the log, and attach it.

If possible and not too large, the particular input files would be good also.

I assume those input files can be played fine with, eg:

gst-launch-0.10 plabvin2 uri=file:///path/to/the/file

If not, then please attach a GST_DEBUG=5 log of this gst-launch-0.10 command instead of the pitivi one.
Comment 2 Matthias 2012-02-13 21:13:50 UTC
Hi! 

Sorry for the delayed reply. After posting the bug I started that particular slideshow from scratch and didn't run into the bug again. So at first, I couldn't reproduce it. But, while working on another selection of jpeg/ogg/avi-files I got it again!

First, I tried to play selected (not all) input files the way you asked to and they worked - I don't think the input-files cause any trouble: They are just your usual run-of-the-mill digital camera jpegs & ogg-files created with ubuntu from CDs. 
I then ran pitivi in the debug-mode as you requested but even though I reduced the number of steps to a minimum the log-file was bigger than 1GB before the bug occured! (Probably due to my vast number of pics) I played around with it for a bit and finally found, that I got some very tiny spaces between successive jpegs on the dashboard. When I removed those spaces (by moving/stretching the duration of the jpegs) everything was fine again & I could create a project.

Those spaces seem to be a bother for pitivi: Sometimes I just throw all the jpegs on the dashboard/timeline to play around with them. This frequently leads to pitivi freezing up & I need to kill & restart. This happens especially when I work with a large number of jpegs (typically 100+). It seems that the more and the bigger the spaces are the more it troubles pitivi...

Well, I hope that helps you to look for ways to increase stability.

My immediate problem is solved, although by a work-around.

Let me know if I can give you any more usefull information.

Cheers,

Matthias
Comment 3 Vincent Penquerc'h 2012-03-29 17:22:46 UTC
Thanks, that's a good lead. Occasional repro when having gaps between jpegs in the project. Never used Pitivi so I'm not sure how straightforward this is to make a simple debug case, but it sounds like a good repro, so marking as NEW, thanks.
Comment 4 Tim-Philipp Müller 2012-09-28 09:26:09 UTC
not-negotiated errors are usually a bug in the application (despite the unhelpful error message asking you to file a bug against GStreamer), so moving to pitivi.
Comment 5 Jean-François Fortin Tam 2012-10-13 14:23:50 UTC
Hi Matthias, it would be good to specify the exact pitivi version. If it's anything other than 0.15.2 it's probably obsolete. The problem with hundreds of files in the timeline might be bug #593377
Comment 6 Matthias 2012-10-13 18:36:14 UTC
Hi! Just installed a new system and am now on 0.15.2. Don't know what version it was before, and haven't tried the new version yet. I guess - on your word, that it is now fixed - we can set this bug on "solved" and I might open a new one if the same bug comes up with 0.15.2.

Cheers & thx
Comment 7 Jean-François Fortin Tam 2013-09-21 19:31:00 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can reproduce the problem with the current development version.
Thanks!