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 722929 - No rendering: GStreamer flow error
No rendering: GStreamer flow error
Status: RESOLVED DUPLICATE of bug 720699
Product: pitivi
Classification: Other
Component: Rendering
0.92
Other Linux
: Normal blocker
: Git
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2014-01-24 19:55 UTC by Mathieu
Modified: 2014-02-02 01:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mathieu 2014-01-24 19:55:39 UTC
Using Pitivi 0.92-1 from Debian experimental, I'm not able to render videos any more (as far as I can tell, I did not have too much problems with 0.92). For instance, on a multi-video project, I get the following error:

  Sorry, something didn’t work right.

  Erreur interne de flux de données. [~ Internal error of data flow]

  gstbasesrc.c(2865): gst_base_src_loop (): /pitivi+utils+pipeline+Pipeline:pitivi+utils+pipeline+pipeline0/GESTimeline:gestimeline0/GESAudioTrack:gesaudiotrack0/GnlComposition:gnlcomposition1/GnlSource:gnlsource53/GstAudioTestSrc:audiotestsrc1:
  streaming task paused, reason not-negotiated (-4)

The project looks fine to me, and the rendering options (e.g. resolution, frame rate) are the same as the input videos. I tried several codecs (webm with VP8, avi with x264enc), to no avail.

On the simplest project (just dropped a video, used the video properties as project properties, etc.), I get a fairly similar error:

 Sorry, something didn’t work right.

  GStreamer a rencontré une erreur générale de flux. [~ GStreamer encountered a general flow error]

  qtdemux.c(4402): gst_qtdemux_loop (): /pitivi+utils+pipeline+Pipeline:pitivi+utils+pipeline+pipeline1/GESTimeline:gestimeline1/GESAudioTrack:gesaudiotrack1/GnlComposition:gnlcomposition3/GnlSource:gnlsource1/GstBin:audiosrcbin/GstURIDecodeBin:uridecodebin4/GstDecodeBin:decodebin10/GstQTDemux:qtdemux8:
  streaming stopped, reason not-negotiated

In both cases, the error is blocking: no video is produced.

Not sure where to start with this one, the message is not really explicit to me... I'd be happy to provide more information, or to try other approaches/settings.
Mathieu.
Comment 1 Mathieu Duponchelle 2014-01-24 20:12:42 UTC
Can you upload the project somewhere ? You can use Project -> Export as archive to do so.

Thanks for your feedback !
Comment 2 Mathieu 2014-01-25 00:25:07 UTC
Sure thing. I made a very simple project: one low-resolution video, simply added to the timeline, no effects, etc. and properties of the project taken from the video.

Rendering throws the same error as above on my machine:

  GStreamer a rencontré une erreur générale de flux. [~ GStreamer encountered a
general flow error]

  qtdemux.c(4402): gst_qtdemux_loop (): /pitivi+utils+pipeline+Pipeline:pitivi+utils+pipeline+pipeline1/GESTimeline:gestimeline1/GESAudioTrack:gesaudiotrack1/GnlComposition:gnlcomposition3/GnlSource:gnlsource1/GstBin:audiosrcbin/GstURIDecodeBin:uridecodebin4/GstDecodeBin:decodebin12/GstQTDemux:qtdemux10:
  streaming stopped, reason not-negotiated

Here is the archive (1.5 Mo):

http://mathieu.basille.net/tmp/Test2.xges_tar

Hope this helps!
Comment 3 Mathieu 2014-01-28 03:36:42 UTC
Is there anything I can do to try to debug this problem? I'm not even sure where to start:

- Is this a problem with Pitivi? With this version only?
- Does it affect only the Debian (experimental) package?
- Could it be a problem from GStreamer, or other (potentially missing) dependencies?
- Does it affect only me?

Right now, I'm completely blocked: Debian only ships Pitivi 0.15.2-0.2 and 0.92-1, and I think Pitivi 0.15 can not handle .xges project files...

Any pointer would be much appreciated!
Mathieu.
Comment 4 Jean-François Fortin Tam 2014-01-29 14:39:04 UTC
I can reproduce with that project file. Could it be that you used the clip properties' "Apply to project" feature to set the project settings? If so that's bug 720699.
Comment 5 Jean-François Fortin Tam 2014-01-29 14:40:33 UTC
Oh wait, re-reading your initial problem description, that's it :)

*** This bug has been marked as a duplicate of bug 720699 ***
Comment 6 Mathieu 2014-01-29 15:22:37 UTC
Oh, good to know that it's an already identified bug! This explains why I was able to render some earlier videos, but I couldn't understand the difference and why it was happening (I was assuming some issue with a Pitivi update here).

Now, I see this particular bug is not fixed. Is there any solution for me to use those projects already saved with the 'Apply to project...' approach? I have a couple of pretty advanced projects, which I would really not want to start over, is there a way to render them anyway with this bug?
Comment 7 Jean-François Fortin Tam 2014-01-30 16:00:29 UTC
As a workaround, I would suggest doing a diff between the two files and looking at the <stream-profile parent='pitivi-profile' id='1' type='audio'   line.

For a working project it has   rate=(int)44100'
For a broken project it has    rate=(glong)44100'

So using a text editor to replace the glong by int should make it work.
Comment 8 Mathieu 2014-02-02 01:17:34 UTC
The workaround seems to work for me, thanks a lot!

However, I ran into a new sort of problem: while it works perfectly for low quality video, Pitivi is rendering without the video part for HD videos! I explain this in more details in bug 723447 here: https://bugzilla.gnome.org/show_bug.cgi?id=723447

Many thanks for the workaround!
Mathieu