Bug 603102 – cannot render until the timeline has been seeked, and traceback if trying to seek after trying to render directly

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 603102 - cannot render until the timeline has been seeked, and traceback if trying to seek after trying to render directly


Summary:	cannot render until the timeline has been seeked, and traceback if trying to ...


Status:	RESOLVED FIXED

Product:	pitivi
Classification:	Other
Component:	General
Version:	Git
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	0.13.4
Assigned To:	Pitivi maintainers
QA Contact:	Pitivi maintainers

URL:
Whiteboard:

Duplicates:	593452 (view as bug list)
Depends on:
Blocks:

Reported:	2009-11-27 01:58 UTC by Jean-François Fortin Tam
Modified:	2010-04-20 01:50 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Jean-François Fortin Tam 2009-11-27 01:58:57 UTC

1. import MVI_0436.MOV (from http://www.osnews.com/img/22106/sx200is.zip)
2. drag it into a blank timeline
3. do not seek the timeline yet
4. try rendering, the render will hang there indefinitely. Click Cancel.
3. try seeking.

Comment 1 Jean-François Fortin Tam 2009-11-27 02:00:50 UTC

Argh, bugzilla scrubbed the rest of my message.

This traceback will happen at step 5 (sorry, misnubered it as step 3 #2):

Traceback (most recent call last):

+ Trace 219314

File "pitivi/ui/mainwindow.py", line 1056 in _timelineRulerSeekCb
```
self.viewer.setPipeline(self.project.pipeline)
```
File "pitivi/ui/viewer.py", line 105 in setPipeline
```
self._connectToPipeline(pipeline)
```
File "pitivi/ui/viewer.py", line 147 in _connectToPipeline
```
self.action.activate()
```
File "pitivi/action.py", line 119 in activate
```
self._ensurePipelineObjects()
```
File "pitivi/action.py", line 563 in _ensurePipelineObjects
```
self.pipeline.getBinForFactoryStream(producer, automake=True)
```
File "pitivi/pipeline.py", line 510 in getBinForFactoryStream
```
stream, automake)
```
File "pitivi/pipeline.py", line 451 in _getStreamEntryForFactoryStream
```
factory_entry = self._getFactoryEntryForStream(factory, stream, create)
```
File "pitivi/pipeline.py", line 440 in _getFactoryEntryForStream
```
raise PipelineError("Pipeline not in NULL/READY,"
```

pitivi.pipeline.PipelineError: Pipeline not in NULL/READY, can not create source bin




Now, take note that this problem does not occur if you seeked the clip in the timeline *before* rendering (everything will work correctly).

Comment 2 Edward Hervey 2009-11-27 11:40:52 UTC

I think this is somewhat related to bug #603045

Comment 3 Jean-François Fortin Tam 2009-11-27 14:34:14 UTC

Well, one interesting thing to note is that it also impairs the use case "open a project and hit the render button directly" (the render will never happen and appear to "hang". This could explain so many bugs...). I just had to seek a timeline after opening before I could actually render a newly opened project.

Comment 4 Brandon Lewis 2009-12-10 19:26:45 UTC

commit 837f0d73b7d510b695ee1c9a1cb961c779ad6534
Author: Brandon Lewis <brandon_lewis@alum.berkeley.edu>
Date:   Wed Dec 9 15:10:10 2009 -0800

    mainwindow.py,test_integration.py: issue preliminary seek on timeline
    closes bugs 603045, 603424, 603102

Comment 5 Jean-François Fortin Tam 2010-04-20 01:50:04 UTC

*** Bug 593452 has been marked as a duplicate of this bug. ***