jmh wrote:Is this something you can do en-masse while track-selecting?

yes

jmh wrote:If say you like to copy to layer 1, and
output 1 is on layer 4, output 2, is on layer 2 and output 3 is on layer 3?

"Like to copy to Layer 1"? Um, no, that would be a bad idea, contrary to what users should do.
Copy from layer 1 to back up a alternative automation.

Those scenarios you listed would have to be done one at a time;
same for any track type I, R or O

again, those higher number layers will always revert to Layer 1 once the edl is re-opened

so if user has 20 output tracks with automation, it might be wise to have layer 1 be the final automation.

how else would users know? in some kind of a log? text doc; paper?

Todd R wrote:Yeah, I can't be doing that! I've nearly maxed out the output matrix...it's easy enough to copy the automation to another layer and leave Layer 1 as the final edit :-)

Thanks for validating what I'm seeing, greatly appreciated

Is this something you can do en-masse while track-selecting?


If say you like to copy to layer 1, and
output 1 is on layer 4, output 2, is on layer 2 and output 3 is on layer 3?

UpTilDawn wrote:I also "discovered" this behavior during the last project and had to quickly learn to check the main output layer each time I opened the session. I'd never noticed in the past, because I generally didn't write automation to the main output track, let alone to layers other than one. It seemed odd to me, but no time to worry beyond just being alert, so I didn't render the wrong mix file.

Yeah, I can't be doing that! I've nearly maxed out the output matrix...it's easy enough to copy the automation to another layer and leave Layer 1 as the final edit :-)

Thanks for validating what I'm seeing, greatly appreciated

I also "discovered" this behavior during the last project and had to quickly learn to check the main output layer each time I opened the session. I'd never noticed in the past, because I generally didn't write automation to the main output track, let alone to layers other than one. It seemed odd to me, but no time to worry beyond just being alert, so I didn't render the wrong mix file.

Maybe this scenario hasn't been covered before?

for SawStudio64:
I have found that if save edl with Output Track active layer other than Layer 1;
then next time that edl is launched, the Output Tracks active layers have reverted to Layer 1.

I don't find any info on this in the User Manual. This reversion to layer 1 being the active layer for output tracks on re-launch of edl happens on both Direct Audio Device Outputs and Sub-Group Outputs.

I do have a workaround for my purposes (saving previously written automation), yet, if more than two automation layers are needed, it might get very difficult to track changes.
Clearly that workaround is to copy the wanted previous automation to a layer other than layer 1 :-)

many thanks