save as

[rosea.grammostola]

Hey,

Ok you've your non-session, synth -> non-mix. Then you get creative and
add all kinds of ladspa plugins to non-mix and add even some synths. Now
you want to have your existent session (which you had at start of the
creative process) and the new one with the added stuff.

Afaik, duplicate session is for situations where you *plan* to being
creative or productive. But it's nice to be free to get into an 'flow'
too and keep all your data (past, present).

\r

[J. Liles]

On Fri, Jan 11, 2013 at 4:05 PM, rosea.grammostola <

Post by rosea.grammostola
Hey,
Ok you've your non-session, synth -> non-mix. Then you get creative and
add all kinds of ladspa plugins to non-mix and add even some synths. Now
you want to have your existent session (which you had at start of the
creative process) and the new one with the added stuff.
Afaik, duplicate session is for situations where you *plan* to being
creative or productive. But it's nice to be free to get into an 'flow' too
and keep all your data (past, present).
\r

I have no idea what you're asking.

[rosea.grammostola]

Post by J. Liles
On Fri, Jan 11, 2013 at 4:05 PM, rosea.grammostola
Hey,
Ok you've your non-session, synth -> non-mix. Then you get creative
and add all kinds of ladspa plugins to non-mix and add even some
synths. Now you want to have your existent session (which you had at
start of the creative process) and the new one with the added stuff.
Afaik, duplicate session is for situations where you *plan* to being
creative or productive. But it's nice to be free to get into an
'flow' too and keep all your data (past, present).
\r
I have no idea what you're asking.

Save the session with a different name, e.g. 'save as'.

[rosea.grammostola]

Post by rosea.grammostola

Post by J. Liles
On Fri, Jan 11, 2013 at 4:05 PM, rosea.grammostola
Hey,
Ok you've your non-session, synth -> non-mix. Then you get creative
and add all kinds of ladspa plugins to non-mix and add even some
synths. Now you want to have your existent session (which you had at
start of the creative process) and the new one with the added stuff.
Afaik, duplicate session is for situations where you *plan* to being
creative or productive. But it's nice to be free to get into an
'flow' too and keep all your data (past, present).
\r
I have no idea what you're asking.

Save the session with a different name, e.g. 'save as'.

an NSM session that is

[J. Liles]

On Sat, Jan 12, 2013 at 2:11 AM, rosea.grammostola <

Post by rosea.grammostola

Post by J. Liles
On Fri, Jan 11, 2013 at 4:05 PM, rosea.grammostola
Hey,
Ok you've your non-session, synth -> non-mix. Then you get creative
and add all kinds of ladspa plugins to non-mix and add even some
synths. Now you want to have your existent session (which you had at
start of the creative process) and the new one with the added stuff.
Afaik, duplicate session is for situations where you *plan* to being
creative or productive. But it's nice to be free to get into an
'flow' too and keep all your data (past, present).
\r
I have no idea what you're asking.

Save the session with a different name, e.g. 'save as'.

How is this different from the existing duplicate function?

[rosea.grammostola]

Post by rosea.grammostola
Save the session with a different name, e.g. 'save as'.
How is this different from the existing duplicate function?

I tried to explain it. If I launch a session, then edit it and then hit
duplicate, I've two sessions, one changed session (so I lost the
original) and a new session. With 'save as' I still have the original
session and a new session (the changed session).

You could argue that you need to run duplicate first and then edit the
session, but on a computer it's nice to freely experiment and then
decide whether you wish to save the changes or not.

\r

[J. Liles]

On Sat, Jan 12, 2013 at 2:25 PM, rosea.grammostola <

Post by rosea.grammostola

Post by rosea.grammostola
Save the session with a different name, e.g. 'save as'.
How is this different from the existing duplicate function?

I tried to explain it. If I launch a session, then edit it and then hit
duplicate, I've two sessions, one changed session (so I lost the original)
and a new session. With 'save as' I still have the original session and a
new session (the changed session).
You could argue that you need to run duplicate first and then edit the
session, but on a computer it's nice to freely experiment and then decide
whether you wish to save the changes or not.
\r

Due to the differences in the way client programs manage their state,
having a 'save as' function is not possible. There's no rule stating that a
client can't save its state before a 'save' message comes along (and in the
case of a DAW-like program, waiting until 'save' is not at all practical
[because the recorded audio has to go somewhere]).