I too would like to understand better the vagaries of track archives. And indeed a proper grown up way to port channel strips, INCLUDING instrument channels, is really needed…
In the meantime, the track archive “workaround” needs further clarification.
I have also seen the cannot make master track error. It is undoubtedly due to a difference in the projects start start of the destination project, and that of the project from which the tracks were exported…
If the the progenitor project starts earlier than the destination project, nuendo will insert time. If that time is not divisible by a beat, the master track error occurs. That’s my basic understanding. I think!
If the the progenitor project starts after the destination project, similar issues occur.
I wonder, if one always archived out from a project that was at a TC that one was unlikely to hit (eg 22:00:00:00) then perhaps this would minimize the collateral damage to the timeline at least. I need to try this out back at the studio.
But please, Steinberg, we need some sensible thought on this. A similar malaise occurs when trying to duplication vst instrument rack and midi track setups, along with the outputs. If we could have a track preset that included:
A the instantiation of a vst instrument into the vst rack
B the creation of several tracks pointing at that instantiation
C the activation of audio outputs from that instantiation
D the effects, sends and routings of those outputs
In effect, a loadable template of instrument tracks and midi tracks.
So for example, supposing I have, after some creative work, arrived at:
A- an instance of VE Pro pointing at a preserved slave (or maybe a stylus RMX instance for arguments sake)
B- say 5 midi tracks pointing at specific ports and channels of that above instance
C- say 4 stereo returns from that instance activated
D- a send from each of those instrument tracks, some eq here and there, and NAMES, very important, NAMES.
E- oh and I might have the midi tracks in a folder.
Now, if I solo any one of those midi tracks, nuendo certainly has the intelligence to know which instruments tracks they are ultimately going to come from. Nuendo knows to solo the vst tracks from the instance that the midi track points to. Can that intelligence not be applied to a track preset?
In my proposal, I would select the four midi tracks, and "save aggregate preset’ or whatever we want to class it as.
Open a new or existing project. Load that aggregate preset and have nuendo create:
A - the correct instance of the vsti, with the correct set loaded in it (or in the ca of VE pro, pointing to the right slave) in an available slot in the vst rack.
B- the 5 midi tracks (in their folder track) pointing at said instance
C- the four stereo returns activated, named and coloured as saved
D- ideally any inserts, Eq and sends, together with routing all setup as saved
The last part would of course be dependant on the destination project having the routings and fx tracks extant in the project. No big deal if not though - unassigned or main mix output being the default in this case.
Please? Pretty please?