View Issue Details

IDProjectCategoryView StatusLast Update
0003641ardourfeaturespublic2020-04-19 20:15
Reporterdanboid Assigned Tocth103  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
Target Version3.0-beta2 
Summary0003641: Save Configuration
DescriptionAt present there is no mechanism for the saving and restoring of Ardour editor config settings. It should be both available as an option to 'Save Configuration' under the session menu as well as being optionally auto-activated when quitting a session.

These are the things I routinely alter hence what I would like to see saved and restored by such a feature:

Editor window size and position
Status of the primary, secondary and nudge clock
Timeline settings
Size of summary view
Size and visibility of editor mixer
Grid mode, Grid unit and edit point settings

As it stands I'm having to alter every one of the above every time I create a new session
TagsNo tags attached.

Activities

paul

2011-02-08 02:45

administrator   ~0010052

many of these variables ARE saved at present, but not per-session.

clock settings are main exception.

danboid

2011-02-14 22:53

reporter   ~0010088

Last edited: 2011-02-14 22:54

Saving of clock visibility setting is key to A3 fitting horizontally onto my laptop display without having to disable the 2nd clock then awkwardly resize the main window every time I start up.

cth103

2011-02-16 17:08

administrator   ~0010119

AFACIS clock visibility is saved per-session (ie whether the primary and secondary clocks are off, BBT, frames etc.). danboid, are you not seeing this?

danboid

2011-02-16 20:01

reporter   ~0010123

Fixing 3778 (session templates) may provide the saving and restoring of all the settings I usually have to configure upon starting a new session hence could solve this maybe?

danboid

2011-02-18 01:59

reporter   ~0010160

Now that creating a new session from an existing one works I can properly comment on this. The clock status and timeline settings DO get saved in the session, but the editor window size (please fix this one if nothing else here!), visibility of the editor mixer and the status of pretty much all the mode buttons - grid mode, edit point etc. - do not get saved or restored under 8887.

danboid

2011-02-20 14:55

reporter   ~0010168

The size and status (visibility) of the summary view should also get saved and restored per session.

danboid

2011-02-27 15:43

reporter   ~0010193

I realise this is already down as a b1 issue but I'd very much like to see as much of this issue get resolved as possible in time for the alpha as it affects all users and I firmly believe A3 will be a much more pleasant user experience once this is resolved. I'm spending waaay too much time configuring and resizing the interface as it is.

danboid

2011-03-03 21:00

reporter   ~0010269

As for saving/loading of settings when loading a session- that mostly seems to work now under 9059 - all apart from the window size which is sometimes restored correctly, other times its a bit small and I have to maximise it but either way A3s usability is greatly improved now - I'm running XFCE under squeeze.

The problem with this now comes when restoring settings via 'Use an existing session as a template' as not all settings get transferred to the new session such as window size, visibility/size of the editor mixer and the state of the various tool bar icons and options.

paul

2011-11-15 15:31

administrator   ~0012036

things like window size and so forth are not considered part of a session's state. they are considered properties of the Ardour GUI for a given user. to think about why this is, consider sending an ardour session to a user who has (a) a different screen setup (b) different work habits. they don't want your settings, and you don't want theirs.

the idea is that these things are more consistent across user-on-a-given-machine than across all instances of a session.

cth103

2011-11-15 17:49

administrator   ~0012054

Looks like this might be resolve-able: are there still problems?

danboid

2011-11-15 22:56

reporter   ~0012071

I'd say this is safe to resolve now yes thanks

system

2020-04-19 20:15

developer   ~0022332

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2010-12-30 20:03 danboid New Issue
2010-12-30 22:54 cth103 cost => 0.00
2010-12-30 22:54 cth103 Target Version => 3.0-beta1
2011-02-08 02:45 paul Note Added: 0010052
2011-02-14 22:53 danboid Note Added: 0010088
2011-02-14 22:54 danboid Note Edited: 0010088
2011-02-16 17:08 cth103 Note Added: 0010119
2011-02-16 20:01 danboid Note Added: 0010123
2011-02-18 01:59 danboid Note Added: 0010160
2011-02-20 14:55 danboid Note Added: 0010168
2011-02-27 15:43 danboid Note Added: 0010193
2011-03-03 21:00 danboid Note Added: 0010269
2011-11-15 15:26 cth103 Target Version 3.0-beta1 => 3.0-beta2
2011-11-15 15:31 paul Note Added: 0012036
2011-11-15 17:49 cth103 Note Added: 0012054
2011-11-15 17:49 cth103 Status new => feedback
2011-11-15 22:56 danboid Note Added: 0012071
2011-11-15 23:04 cth103 Status feedback => resolved
2011-11-15 23:04 cth103 Resolution open => fixed
2011-11-15 23:04 cth103 Assigned To => cth103
2020-04-19 20:15 system Note Added: 0022332
2020-04-19 20:15 system Status resolved => closed