Skip to content
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

Target track number not saved with preset #7

Closed
DLongoni opened this issue Jul 22, 2020 · 10 comments
Closed

Target track number not saved with preset #7

DLongoni opened this issue Jul 22, 2020 · 10 comments
Labels
enhancement New feature or request
Milestone

Comments

@DLongoni
Copy link

If I save a preset with reaper "save preset" function and then I reload it on another project the track numbers are replaced sometimes with and sometimes with seemingly random numbers. The same is true for "Send effect" number with target set to "Track send volume".

Am i doing something wrong?

@helgoboss
Copy link
Owner

@helgoboss helgoboss added the enhancement New feature or request label Jul 22, 2020
@helgoboss
Copy link
Owner

@DLongoni
Copy link
Author

I see, sorry, I didn't look for it on bitbucket. I really think this could be very useful!

@helgoboss
Copy link
Owner

Combinations that make sense in my opinion:

Id, name, pos ×
Id, pos, name ×
Name, id, pos ×
Name, pos, id ×
Pos, name, id ×
Pos, id, name ×

Id, name × CURRENT (keep for compatibility)
Id, pos ×
Name, id ×
Name, pos ×
Pos, name ×
Pos, id ×

Id ✓
Name ✓
Pos ✓

... fallback combinations are not really useful. So a single dropdown for saying what anchor to use to lookup the track should be sufficient.

@DLongoni
Copy link
Author

Totally agreed. Personally, this is the most useful feature I am currently missing, thank you so much for looking into it.

@DLongoni
Copy link
Author

Hello, sorry to annoy you again on this. Been using relearn for quite some time, the lack of this feature is becoming more and more of a limit for me, I just wonted to know if you had any plan of looking into this sooner or later, cause otherwise I have to look for another solution. Just for info, not to pressure. Thanks a lot.

@helgoboss
Copy link
Owner

I will look into this in the next days. Probably simple for me to fix, difficult for you to migrate to something else.

@helgoboss helgoboss added this to the 1.12.0 milestone Nov 29, 2020
@DLongoni
Copy link
Author

True that for me it would be a mess. Don't know about how easy it could be for you, but that would be awesome, thanks a lot.

helgoboss added a commit that referenced this issue Dec 8, 2020
@helgoboss
Copy link
Owner

Implemented in upcoming v1.12.0-pre6 including a better handling of non-present tracks

@DLongoni
Copy link
Author

DLongoni commented Dec 8, 2020

Looking forward to this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants