New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

save tracks as track template, slot x #591

Closed
Jeff0S opened this Issue Jul 8, 2014 · 6 comments

Comments

Projects
None yet
1 participant
@Jeff0S
Member

Jeff0S commented Jul 8, 2014

From eure.ja...@gmail.com on August 08, 2013 08:54:00

Would love to be able to save directly in to a specific slot, mostly just to avoid the confirmation window. :)

or, if it's easier, change how the Auto-save action works. There are actions available to clear slot(x) if you edit the S&M ini. If Auto-save track template slots saved to the first empty slot, instead of adding a slot, a macro could be made to save to slot(x).

Original issue: http://code.google.com/p/sws-extension/issues/detail?id=591

@Jeff0S

This comment has been minimized.

Show comment
Hide comment
@Jeff0S

Jeff0S Jul 8, 2014

Member

From eure.ja...@gmail.com on August 07, 2013 23:55:22

the other resources (Fx chains, etc) could work the same way as well. :)

Member

Jeff0S commented Jul 8, 2014

From eure.ja...@gmail.com on August 07, 2013 23:55:22

the other resources (Fx chains, etc) could work the same way as well. :)

@Jeff0S

This comment has been minimized.

Show comment
Hide comment
@Jeff0S

Jeff0S Jul 8, 2014

Member

From jeffos...@gmail.com on September 16, 2013 11:40:28

"just to avoid the confirmation window"

oops, this one is a bug in fact:

  • the auto-save button is supposed to prompt (overwrite selected files/slots -or- add brand new slots)
  • BUT auto-save actions were supposed to be more macro-friendly and so not supposed to prompt for anything (they must always add a new slot/file)

=> thanks for the report, fix coming soon!


About the FR:

"If Auto-save track template slots saved to the first empty slot, instead of adding a
slot, a macro could be made to save to slot(x)."

I see the (nice!) idea, James: doing everything from macros!

As you probably already know what you propose has some drawbacks though...
What I'd propose instead is to add a "last slot" flavor for all existing slots actions.
This means adding a bunch of new Resources actions (but not much work required given the way things are current designed), for example:

  • SWS/S&M: Resources - Apply track template to selected tracks, last slot
  • SWS/S&M: Resources - Apply track template (+envelopes/items) to selected tracks, last slot
  • SWS/S&M: Resources - Import tracks from track template, last slot
  • etc..

That way you could handle everything from macros, w/o worrying about slot numbers, corner-cases (the "first empty slot" you were talking about), w/o tweaking S&M.ini, etc..
I can also add actions like "SWS/S&M: Resources - Delete last track template slot/file" so that you can cleanup things at the end of macros.

Waiting for some feedback before implementing this => let me know what you think (or if something is not clear)!

Member

Jeff0S commented Jul 8, 2014

From jeffos...@gmail.com on September 16, 2013 11:40:28

"just to avoid the confirmation window"

oops, this one is a bug in fact:

  • the auto-save button is supposed to prompt (overwrite selected files/slots -or- add brand new slots)
  • BUT auto-save actions were supposed to be more macro-friendly and so not supposed to prompt for anything (they must always add a new slot/file)

=> thanks for the report, fix coming soon!


About the FR:

"If Auto-save track template slots saved to the first empty slot, instead of adding a
slot, a macro could be made to save to slot(x)."

I see the (nice!) idea, James: doing everything from macros!

As you probably already know what you propose has some drawbacks though...
What I'd propose instead is to add a "last slot" flavor for all existing slots actions.
This means adding a bunch of new Resources actions (but not much work required given the way things are current designed), for example:

  • SWS/S&M: Resources - Apply track template to selected tracks, last slot
  • SWS/S&M: Resources - Apply track template (+envelopes/items) to selected tracks, last slot
  • SWS/S&M: Resources - Import tracks from track template, last slot
  • etc..

That way you could handle everything from macros, w/o worrying about slot numbers, corner-cases (the "first empty slot" you were talking about), w/o tweaking S&M.ini, etc..
I can also add actions like "SWS/S&M: Resources - Delete last track template slot/file" so that you can cleanup things at the end of macros.

Waiting for some feedback before implementing this => let me know what you think (or if something is not clear)!

@Jeff0S

This comment has been minimized.

Show comment
Hide comment
@Jeff0S

Jeff0S Jul 8, 2014

Member

From eure.ja...@gmail.com on October 02, 2013 04:52:00

I think this would work, with enough associated actions for this "last slot".

would the last slot be just a temporary slot? i.e, would it be remembered after closing and re-opening reaper?

Member

Jeff0S commented Jul 8, 2014

From eure.ja...@gmail.com on October 02, 2013 04:52:00

I think this would work, with enough associated actions for this "last slot".

would the last slot be just a temporary slot? i.e, would it be remembered after closing and re-opening reaper?

@Jeff0S

This comment has been minimized.

Show comment
Hide comment
@Jeff0S

Jeff0S Jul 8, 2014

Member

From jeffos...@gmail.com on October 02, 2013 05:41:26

Thanks for the feedback, let's do it then!

First, I forgot to clarify that this "last slot" idea makes sense assuming the "prompt bug" above is fixed. I mean, if auto-save actions never prompt for anything and always add a new slot/file, i.e. the last slot we're talking about.

I think this would work, with enough associated actions for this "last slot".

Yes, in fact there would be a "last slot" flavor for all existing slot actions - i.e. many new actions but not much work as I said.

would the last slot be just a temporary slot? i.e, would it be remembered after closing and re-opening reaper?

It would be a normal slot (not "temporary" one) that is persisted when re-launching REAPER, etc.. But that's actually why I also proposed to add actions like "SWS/S&M: Resources - Delete last track template slot/file" so that you can cleanup things when you are done with your macros.

Status: Started
Owner: jeffos...@gmail.com

Member

Jeff0S commented Jul 8, 2014

From jeffos...@gmail.com on October 02, 2013 05:41:26

Thanks for the feedback, let's do it then!

First, I forgot to clarify that this "last slot" idea makes sense assuming the "prompt bug" above is fixed. I mean, if auto-save actions never prompt for anything and always add a new slot/file, i.e. the last slot we're talking about.

I think this would work, with enough associated actions for this "last slot".

Yes, in fact there would be a "last slot" flavor for all existing slot actions - i.e. many new actions but not much work as I said.

would the last slot be just a temporary slot? i.e, would it be remembered after closing and re-opening reaper?

It would be a normal slot (not "temporary" one) that is persisted when re-launching REAPER, etc.. But that's actually why I also proposed to add actions like "SWS/S&M: Resources - Delete last track template slot/file" so that you can cleanup things when you are done with your macros.

Status: Started
Owner: jeffos...@gmail.com

@Jeff0S

This comment has been minimized.

Show comment
Hide comment
@Jeff0S

Jeff0S Jul 8, 2014

Member

From eure.ja...@gmail.com on October 02, 2013 06:24:42

sounds good. Thanks!

Member

Jeff0S commented Jul 8, 2014

From eure.ja...@gmail.com on October 02, 2013 06:24:42

sounds good. Thanks!

@Jeff0S

This comment has been minimized.

Show comment
Hide comment
@Jeff0S

Jeff0S Jul 8, 2014

Member

From jeffos...@gmail.com on October 09, 2013 11:52:00

coming soon ( r1142 )

Status: Done

Member

Jeff0S commented Jul 8, 2014

From jeffos...@gmail.com on October 09, 2013 11:52:00

coming soon ( r1142 )

Status: Done

@Jeff0S Jeff0S closed this Jul 8, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment