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 658307 - Rendering does not work when using a render preset
Rendering does not work when using a render preset
Status: RESOLVED DUPLICATE of bug 658303
Product: pitivi
Classification: Other
Component: Rendering
Git
Other Linux
: Normal blocker
: 0.15
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2011-09-06 00:18 UTC by Alex Băluț
Modified: 2011-09-07 15:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alex Băluț 2011-09-06 00:18:25 UTC 
Steps to reproduce:
1. Click the render button to render a project,
2. Click the "HTC Desire" render preset (I also noticed it happens with the iPhone one),
3. Click the Render button, notice the "Rendering" dialog appears and shows "Estimating", but it does nothing. If I click the Render button without selecting a preset, it renders fine. The following stacktrace appears in the console:

$ bin/pitivi ../tmp/Untitled2.xptv 
Traceback (most recent call last):

+ Trace 228345

  • File "pitivi/ui/encodingdialog.py", line 696 in _renderButtonClickedCb 
    self.startAction()
  • File "pitivi/actioner.py", line 151 in startAction 
    self.addAction()
  • File "pitivi/actioner.py", line 102 in addAction 
    self.action = self._createAction(sources)
  • File "pitivi/actioner.py", line 230 in _createAction 
    self.have_video, self.have_audio)
  • File "pitivi/settings.py", line 605 in export_settings_to_render_settings 
    astream = get_stream_for_caps(export.getAudioCaps())
  • File "pitivi/stream.py", line 345 in get_stream_for_caps 
    log.debug("stream", "caps:%s, pad:%r" % (caps.to_string(), pad))
AttributeError: 'NoneType' object has no attribute 'to_string' 






Comment 1


Alex Băluț





          2011-09-07 15:04:02 UTC
        



This is probably related to bug 658303 which is caused by unavailable codecs which are used by the render presets. So we need to figure out what to do when a render preset is selected by the user and the video or audio codecs specified by the preset are not available.

*** This bug has been marked as a duplicate of bug 658303 ***