In short, when it comes to saving projects with non-last take lanes soloed, there are issues when the project is reloaded. Also there are issues with displaying non-last takes in staff mode.
On 6/12/2022 at 1:37 PM, David Baay said:
I use lane-soloing frequently to 'promote' the best take (or bounced mix) which is often not the last take/bounce. I have not seen any issues with this. This should probably be a new thread, but I'm curious what you're seeing.
On 6/12/2022 at 1:44 PM, User 905133 said:
Thanks for for interest. I will . . . start a new thread.
Background (edited from original post from 5/27/2022):
Quote
I just did a basic test of take lanes:
Track 1: Created a bass line (1 measure + 4 measures looped).
Track 2: Played successive test fillers over measures 2 -> 5.
I haven't used this work flow in several years [and discovered two possible issues]:
Last take priority issue:
When the basic test project was saved and reloaded,
the solo state of the takes was ignored, unless the last take was soloed
the soloed take did not play the soft synth (except if it was the last take, in which case the last take played)
If the last take is muted, all other takes are muted.
Staff View issue:
I was unable to see a staff of just the selected take lane.
I have concluded: (1) because I haven't used take lanes in a long while, the results I got might be due to user error or (2) the results might be either (a) expected behavior or (b) quirks. Since no one seems to have noticed either of these issues, if I explore them further, it will likely be for the sake of my own curiosity.
Are these issues the result of user error and if so, what might I be doing wrong? Or, are these issues expected results based on how Take Lanes/Comping works?
Update:
Issues are still in the original basic test project. I will have to start fresh and try to replicate it keeping meticulous track of the steps.
I forgot to mention explicitly, I am using 100% (with VSTs); no audio.
New test variation tried: Split Instrument Track and watched as I soloed different take lanes.
The MIDI data changes from the take lane soloed [selected?] gets placed in the Instrument Track's now separated MIDI Track.
Not sure that is related to what I have described as "Last Take Priority." I need to do more testing.
Edited by User 905133 to prune the post; to add a Preliminary Update
Question
User 905133
Background (from another thread):
Background (edited from original post from 5/27/2022):
Are these issues the result of user error and if so, what might I be doing wrong? Or, are these issues expected results based on how Take Lanes/Comping works?
Update:
-
Issues are still in the original basic test project. I will have to start fresh and try to replicate it keeping meticulous track of the steps.
-
I forgot to mention explicitly, I am using 100% (with VSTs); no audio.
-
New test variation tried: Split Instrument Track and watched as I soloed different take lanes.
-
The MIDI data changes from the take lane soloed [selected?] gets placed in the Instrument Track's now separated MIDI Track.
-
Not sure that is related to what I have described as "Last Take Priority." I need to do more testing.
Edited by User 905133to prune the post; to add a Preliminary Update
Link to comment
Share on other sites
9 answers to this question
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now