Remember all settings after exporting

[markba]

Remember all settings of the last export to provide fast and flawless operation. Settings should go in the project file.

[markba (mark-baaijens)]

Openshot 0.9.54
Ubuntu Jaunty 9.04

[Jonathan Thomas (jonoomph)]

Maybe we could store export settings on the project object. So, each .osp file you open would remember the export settings you used. Sounds useful to me. =)

[Thangalin (thangalin-deactivatedaccount)]

This is a good feature request; software should never lose work and changing settings is work.

[Brett Alton (brett-alton-deactivatedaccount)]

What's involved in closing this bug? This is a big workflow problem for me as I customize my export using 'Advanced' settings.

[John Drinkwater (johndrinkwater)]

Please increase the priority of this, its painful to have to pick settings each time; on my 8th export so far today :/

[Andy Finch (fincha)]

I was going to have a look at implementing this, what is the consensus - remember the export settings per project, or globally, so regardless of which project you open you still get the last used settings?

[Bernd Faulstich (bernibaerchen)]

I think per project is better, because you would not override an other project.

[Bernd Faulstich (bernibaerchen)]

sorry, the last exported file.
So if Filename "blabla", Folder "/././.*", Profil eg "web", target eg "VIMEO HD", video profil eg "30p" and quality eg "medium" will be saved, you don't have to klick this settings together.
an other Project has other settings (name,quality,...) so i think global is not good.
Advanced i do not use, but it can be nice for others too.

[markba (mark-baaijens)]

The original bug report (of which I am the poster) indicated that the settings must me stored per project. Rethinking that, I still think it's best, because several projects serves several purposes thus different output parameters.

[Walter Smith (walter-francis-smith)]

I use openshot to export a lot of short films. Having to re-pick all the settings to export a film every time is just a lot of unnecessary work. A feature to save the export settings, in whatever form, would be much appreciated. Thanks.

[Gregory Weber (spottedmetal)]

How about both (1) allowing the user to store global default export settings in "edit preferences", and (2) store individual project settings (which may override the global defaults) in the project file? Wouldn't that make both groups happy? It would make me happy :-)

[battmanux (battmanu)]

I would agree with the following behavior :
 default export settings in edit->preferences => copied in the project file when new projects are created.
Any change made at rendering time are saved in the project file and suggested for next rendering of this project.
Make simple/easy to save settings from one project as a 'profile' so that it is easy to use it/copy it to an other project

[Zoubidoo (zoubidoo)]

Can I suggest we initialise the export settings with the format of the input clip. Then remember new export settings if they are changed.

See feature request #1166169 Export with the same video format as the input clip

[Patrick Rooney (patrick-rooney90)]

I've written a patch that implements this functionality, although there is one issue that definitely needs sorting out: the folder selection widget (fileExportFolder) get its actual value changed to the project's export folder, but it appears blank in the GUI. I've looked at PyGTK's documentation for FileChooserButton and FileChooser and it doesn't look like I'm doing anything wrong, so in case it's a bug in PyGTK, the version I'm using is 2.24.0-5.fc18 (64-bit).

Another thing to note is that because self.project.export_settings is compared to self.render_options to see if the settings were changed, there is some unused data in self.project.export_settings. For example, both the bitrates (in bytes) and the human-readable versions are stored, but only the latter is used. This could create confusion for those who wish to edit the files manually (though it's easier to edit them in Openshot). If the project file has some invalid or missing values, they are skipped and the rest are loaded.

Although I like the idea of default export settings and initializing the project-specific settings with the format of the input clip, I've decided to leave those things for now and just upload what I've already done. Let me know if you have any other issues.

[Andy Finch (fincha)]

Thanks for the patch.

[Patrick Rooney (patrick-rooney90)]

I've discovered a small mistake I made in my first patch: self.txtFileName is only ever set with the project name. This replacement version sets it with the project name at first and then replaces it with whatever file name is saved in the export settings.

[Seán Ó Séaghdha (seanos)]

Rechoosing these settings every time is utterly infuriating. So pointless.