Skip to main content

Multiple Global Racks

Posted

What would you expect how should Synfire behave when saving the global rack:

  1. Save to "CurrentRack.cogsetup", not touching "WhateverRackWasLastLoaded.cogsetup"
  2. Save to (and overwrite) "WhateverRackWasLastLoaded.cogsetup"

Currently it does (1).

The advantage of (1) is that racks, once they have been saved to a different file, can not be modified by accident anymore. The disadvantage is, when you finised a project, you may forget to "Save As..." the current global rack to whatever file you want to keep it permanently.

Since the global rack is saved quite frequently, keeping a history of, say, 5 backups will not provide much protection against accidental mistakes. That's another argument for (1).

Any thoughts I may have missed?


Sun, 2013-09-08 - 21:58 Permalink

Ah... now the things become clear to me. I already was wondering. I already lost setups, obviously because the setup files are not stored as I have expected.

What happened to me (if I recall correctly) was this: I created a setup file and saved it (with the Save As command) under the name xy.cogsetup. Then during the project I made changes at the setup and saved it regularly (normal Save command). When I was finished with the project, I moved the file xy.cogsetup together with the .cognac files to an archive folder. Then, at a later point in time I wanted to reopen this old project. Therefore I loaded the archived xy.cogsetup and xy.cognac files. Et voilà...wrong sounds. Now it is clear to me: When I thought I save the updated xy.cogsetup file with the Save command, it wasn't saved at all. It was saved at the CurrentRack.cogsetup file instead. And I archived the wrong setup file.

Since then I always use the Save As.. command and double check if the setup file is saved correctly.

(1) is confusing, IMHO. (2) is more intuitive. 

 

Mon, 2013-09-09 - 00:37 Permalink

The advantage of (1) is that racks, once they have been saved to a different file, can not be modified by accident anymore. The disadvantage is, when you finised a project, you may forget to "Save As..." the current global rack to whatever file you want to keep it permanently.

Since the global rack is saved quite frequently, keeping a history of, say, 5 backups will not provide much protection against accidental mistakes. That's another argument for (1).

Any thoughts I may have missed?

 

I would like to see a window with more options when closing a project:

1. "Save" the current Global Rack - OR

2. "Save as..."  - OR

3. Both - ie "Save" - and then "Save as..."

When the User clicks on the 2nd or 3rd choice, they would be prompted for the "Save as..." info and the program would do the rest.

 

 

Mon, 2013-09-09 - 03:02 Permalink

Off topic i know, but woud help jurgen and prbably many others.....

How about an option simliar to ableton's collect all and save. Ths then gives the option of what to save, arrangement, library, racks, etc. it ten saves everything selected into whatever folder and name selected,

 

as to the original question I prefer option 2 but maybe with a change so that a special backup is taken when the users saves the rack and ths is only overwritten by other super save backups.

Mon, 2013-09-09 - 11:37 Permalink

I'd prefer the first (currently used) behaviour. Or even better a configuration option for whether to save the default rack or the last used.

Tue, 2013-09-10 - 05:02 Permalink

What would you expect how should Synfire behave when saving the global rack:

  1. Save to "CurrentRack.cogsetup", not touching "WhateverRackWasLastLoaded.cogsetup"
  2. Save to (and overwrite) "WhateverRackWasLastLoaded.cogsetup"

 

 

If this is a important distinction and both #1 and #2 have pros and cons, why cannot there be a dialog box asking you which operation you prefer when saving the global rack?

Tue, 2013-09-10 - 17:53 Permalink

Thanks for your input everyone.

Adding more dialog boxes or another option to the preferences is something I would really like to avoid. If there is a standard way that matches the expectations of most users, that's the way to go (Keep It Simple). Others will get used to it, or find their own way to handle things using a different workflow.

Juergen quite convinced me that (2) would be more intuitive - the good old "Save As..." logic (saves the current file under a new name while keeping it open for further editing). If one needs a backup, one can save a copy of the rack to a safe location (or just copy the file).

:D