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 720349 - Rendering only audio or video without sound doesn't work
Rendering only audio or video without sound doesn't work
Status: RESOLVED OBSOLETE
Product: pitivi
Classification: Other
Component: Rendering
0.92
Other Linux
: Normal normal
: 1.0
Assigned To: Pitivi maintainers
Pitivi maintainers
: 748861 (view as bug list)
Depends on: 749056
Blocks:
 
 
Reported: 2013-12-12 20:21 UTC by Jean-François Fortin Tam
Modified: 2015-10-20 13:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jean-François Fortin Tam 2013-12-12 20:21:42 UTC
As part of bug #590639, a feature was added to allow rendering audio-only or video-only by simply using the relevant checkboxes in the rendering dialog.

With Pitivi 0.91+, this feature doesn't do anything, you always end up with video + audio.

(See also bug #673699 for some historical problems we encountered back then)
Comment 1 Jean-François Fortin Tam 2014-03-15 18:36:07 UTC
AFAICS this is another regression from commit 267dd141, which completely removed checks such as

   if self.video_output_checkbutton.get_active():

and

   if self.audio_output_checkbutton.get_active():

in render.py.
Comment 2 Thibault Saunier 2015-05-04 09:23:56 UTC
*** Bug 748861 has been marked as a duplicate of this bug. ***
Comment 3 j1234d2003 2015-05-05 01:08:58 UTC
Seems like a fairly old issue. Any chance of this being given a priority in near future? 

Another related aspect is related to project settings. From a usability perspective, many of my usecases require editing/fixing things in an existing video. These could be as trivial as chopping out a portion of video or inserting another video clip (same settings as input) into an existing video. Working with timeline makes it much easier than command-line tools.

For such usecases, it would be desirable to have a way to create a project based on an input video's settings, do work in pitivi to update the input video and produce a video that uses same settings as input. This helps preserve original video settings which is extremely useful for these usecases. Current method of creating a project with specific video settings and rendering requires too much work and hence limits pitivi's usability for these usecases.
Comment 4 Thibault Saunier 2015-05-05 07:40:04 UTC
That issue is not a high priority but can be fixed pretty easily.

Concerning using a clip as project settings you can already do it, from http://www.pitivi.org/manual/medialibrary.html:

'Clip properties... opens a new window with information on video size, frame rate and aspect ratio. Clicking the Apply to project button adjusts the project settings to the clip properties. You can select which properties to apply by leaving them ticked/unticked.'
Comment 5 j1234d2003 2015-05-07 01:43:37 UTC
That is great. I was able to apply video settings to project settings from existing clip's clip properties. However, it does not work for audio. My video file (ogv) has no audio and the project settings shows stereo 14.4kbps Vorbis. Rendering still renders video with audio channel. I am guessing this is result of same bug that is represented here.

If this issue is fixed, I can really use Pitivi very effectively for many of my usecases. Is there anything else I can do to make this fix probable in near future?
Comment 6 Thibault Saunier 2015-10-20 13:26:59 UTC
This bug has been migrated to https://phabricator.freedesktop.org/T3113.

Please use the Phabricator interface to report further bugs by creating a task and associating it with Project: Pitivi.

See http://wiki.pitivi.org/wiki/Bug_reporting for details.