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 640245 - DV Rendering fails to output a file
DV Rendering fails to output a file
Status: RESOLVED INCOMPLETE
Product: pitivi
Classification: Other
Component: Rendering
Git
Other Linux
: Normal major
: 0.91
Assigned To: Pitivi maintainers
Pitivi maintainers
: 655637 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-01-22 09:38 UTC by the_monkey_man_72
Modified: 2014-11-06 20:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description the_monkey_man_72 2011-01-22 09:38:06 UTC
On selecting the default profile for DV rendering in PiTiVi, and then pressing the render button once, nothing happens. 

If the button is pressed a second time, the project will apparently start to render, the video pane will proceed to play the clip, and the pop-out box will give me an ETA for completion. However, there is no file being generated in the target directory during render, and there is no file created after the render. 

If run from the terminal, after clicking render, the terminal will generate this report:


Traceback (most recent call last):
  • File "/usr/lib/pitivi/python/pitivi/ui/encodingdialog.py", line 147 in _recordButtonClickedCb
    self.addRecordAction()
  • File "/usr/lib/pitivi/python/pitivi/ui/encodingdialog.py", line 219 in addRecordAction
    self.renderaction.activate()
  • File "/usr/lib/pitivi/python/pitivi/action.py", line 119 in activate
    self._ensurePipelineObjects()
  • File "/usr/lib/pitivi/python/pitivi/action.py", line 567 in _ensurePipelineObjects
    self.pipeline.getBinForFactoryStream(producer, automake=True)
  • File "/usr/lib/pitivi/python/pitivi/pipeline.py", line 532 in getBinForFactoryStream
    bin = stream_entry.bin = factory.makeBin(stream)
  • File "/usr/lib/pitivi/python/pitivi/factories/base.py", line 564 in makeBin
    bin = self._makeBin(input_stream)
  • File "/usr/lib/pitivi/python/pitivi/encode.py", line 185 in _makeBin
    rb = self.renderfactory.makeBin()
  • File "/usr/lib/pitivi/python/pitivi/factories/base.py", line 655 in makeBin
    bin = self._makeBin(input_stream)
  • File "/usr/lib/pitivi/python/pitivi/encode.py", line 126 in _makeBin
    b2 = EncoderFactory(setting).makeBin()
  • File "/usr/lib/pitivi/python/pitivi/factories/base.py", line 655 in makeBin
    bin = self._makeBin(input_stream)
  • File "/usr/lib/pitivi/python/pitivi/encode.py", line 62 in _makeBin
    mod.link(enc)
gst.LinkError: failed to link bin16 with ffenc_dvvideo0

My suspicion is that this bug is related to the codec rather that PiTiVi itself, but I have no idea how to troubleshoot from this point.

This problem is not present on using any other codec.

No errors are given through the graphical interface for PiTiVi at any point.
Comment 1 Jean-François Fortin Tam 2011-01-23 21:34:11 UTC
I can indeed reproduce this with pitivi git (select an AVI container and ffenc_dvvideo for the video codec).

I'm wondering if it's a pitivi bug or rather a gstreamer bug, but I suspect the latter. Also happens with gst-jhbuild.
Comment 2 David Schleef 2011-04-24 23:19:46 UTC
Not a GStreamer bug, as it is possible to create DV files using this pipeline (and similar for DV in AVI).

gst-launch videotestsrc -v num-buffers=300 ! ffenc_dvvideo ! ffmux_dv ! filesink location=out.dv audiotestsrc num-buffers=100 samplesperbuffer=4800 ! audioconvert ! audio/x-raw-int,channels=2,rate=48000 ! ffmux_dv0.

It may be a problem that ffenc_video (and ffmux_dv) have strict requirements on input formats which may conflict with other parts of the encoding pipeline.
Comment 3 Jean-François Fortin Tam 2011-08-01 16:29:58 UTC
*** Bug 655637 has been marked as a duplicate of this bug. ***
Comment 4 Jean-François Fortin Tam 2011-09-23 19:37:15 UTC
To investigate this, we would need to check the caps of "bin16" etc. and see if they are actually compatible.

But maybe this will be magically solved by the switch to GES, so it will have to be reevaluated then.
Comment 5 Jean-François Fortin Tam 2013-09-30 15:12:07 UTC
Hi there,

As Pitivi 0.91 has now been released, we would like to encourage you to test it.

It is quite possible that your issue is fixed in this version,
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!
Comment 6 Jean-François Fortin Tam 2014-11-06 20:36:30 UTC
Closing this bug report as no further information has been provided.
Please feel free to reopen if the issue persists with 0.94 or newer
and if you can provide the information asked for. Thanks!