Rework Export window

Bug #1046889 reported by Andy Finch
76
This bug affects 13 people
Affects Status Importance Assigned to Milestone
OpenShot Video Editor
Confirmed
Wishlist
Unassigned

Bug Description

Some enhancements to the export window are needed. This bug report consolidates a number of others into one.

1. Don't allow invalid format/codec combinations. In the advanced tab, users can select any format/codec combination. If they are an invalid combination, it results in a crash in ffmpeg. Hanspb has created a sheet of valid combinations. See http://openshotusers.com/forum/viewtopic.php?f=27&t=1150#p5870

2. Ensure formats get exported with the commonly used extensions, i.e.mkv instead of matroska. See the sheet above for format/extension details.

3. Provide a way to export only part of the timeline, whether it is by markers on the timeline or a position counter on the export window.

4. Include the ability to save custom export settings as a new preset.

5. For advanced users, allow the use of ffmpeg encoding options directly.

6. Show encoding time estimation.

There is a thread in the forum including some good mockups.

http://openshotusers.com/forum/viewtopic.php?f=27&t=1150

Andy Finch (fincha)
Changed in openshot:
importance: Undecided → Wishlist
status: New → Confirmed
description: updated
Revision history for this message
Rick Gabriel (klaxian1) wrote :

I really like the mockups in the referenced thread and I hope these settings changes can be implemented relatively quickly. I would prefer a "Constant Quality" or similar option in the "compression method" pulldown instead of requiring users to know advanced ffmpeg encoding options. A constant quality setting is already available in Pitivi, Avidemux, Handbrake, and others for examples. There's not much left in my wishlist, but "Constant Quality" encoding is at the top. Thanks for the great work on a top notch video editor!

Revision history for this message
Kris Thomsen (lakristho) wrote :

Wouldn't it be easier to keep track of these bugs, if each bug/enhancement has their own bug id?

Revision history for this message
Dan Dascalescu (ddascalescu+launchpad) wrote :

Yes, this bug should be split into multiple tickets. One issue per bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.