Has anything been resolved with this issue? It’s kind of astonishing that this has remained a problem for so long. I use six different DAWs for various reasons and Cubase is the only one where importing tracks is problematic. Sure, there are workarounds, but that’s not the point. It’s a basic, no-brainer task. I import and export tracks constantly to manage very large templates as projects change and also to keep sessions updated as they evolve. I’ve been able to whittle my master template down to around 3200 tracks and I import pre-built sample library templates when I need to change out string or brass sections or bring in more orchestral fx or a completely different synth palette. Everything is pre-formatted to match the master template. It’s “modular,” I guess, and the only way I can keep the template size manageable. But I still have to re-route every one of these auxiliary sessions when I import them. Track archives have not been reliable. It’s nuts.
I don’t know why Import Tracks From Project does not retain the input routing for Audio Tracks. It seems like an oversight to me.
To anyone wondering, Import Track Archive does retain input routing for Audio Tracks. This makes it even more puzzling given how similar these two operations are.
In what way? I use Import Track Archive on a regular basis and have not come across any issues.
Even more astonishing than Cubase - Nuendo being the Premium recording studio product to rival ProTools - also this is still not working in 14.0.32.
When using Track Archives, I’ve encountered routing anomalies, missing track pictures, missing inserts, re-ordered tracks, and colorization being defaulted. Other nitpicky things show up randomly. What I’m saying is that it’s inconsistent. It doesn’t happen all the time, but it happens enough that I don’t see using them as a go-to alternative to import. I’ve thought that maybe it has to do with the size and complexity of what I’m moving around, but that’s not a consideration in every other DAW I use. Don’t get me wrong, I LOVE Cubase for composing, that’s why I stay with it. But it has a number of idiosyncrasies that are unique to it (I’ve actually kept a list!) that leave me baffled on a regular basis.
As I said, I use Track Archives routinely and have not experienced any of the anomalies you describe. There are a few things I’ve learned along the way though.
Source and destination buses must be available in both the project you’re exporting from as well as in the project you’re importing into. It’s not sufficient that these buses share the same name. My guess is that this might be the main source of your issues.
I can’t speak to missing track picture as I don’t use them.
Track colors will differ if Project Colors do not match between the project used when exporting tracks and the one used when importing.
I’m aware of all this. But that’s not the point. Import and Export abilities are core functionalities of pretty much any app that allows you to create or modify data, not just DAWs. These functions are almost always in a main menu, right out front. Having to match things between projects to get a clean import is ridiculous. Can you imagine importing a huge Excel spreadsheet into another one and all the formatting is gone? Imported tracks are not “children” of the session you’re importing into. They’re autonomous and the DAW should adapt them to the current session, regardless if you’ve changed something in it. In Cubase, I use sub-templates that are directly derived from my master template. The Audio Connections and Studio Setup are identical, but every import still needs re-assigning. That makes absolutely no sense. In every other DAW I’ve used, if you import a track that doesn’t have a matching output or bus, that track is left de-activated, but fully intact. A quick modification to the I/O setup/matrix brings it online. If something is say, assigned to output 5-6, it imports and plays to output 5-6, even if what’s going to output 5-6 in the current session is different. Just yesterday, I built a master template and six sub-templates in Pro Tools that utilized 240 audio tracks, 11 instrument tracks, 26 5.1 busses, 26 stereo busses, 13 Atmos busses, 12 FX sends, 3 Main outputs for three different formats, the foldown matrix for everything, and various monitoring options for playback. It was a complicated setup. In doing this, I moved around thousands of tracks in those setups by the time I was done. Number of times anything imported incorrectly: 0.
I’m sorry, but there’s no reason or excuse Cubase shouldn’t be rock-solid dependable when exporting or importing anything, especially for a AAA player in its market segment. It’s inexcusable.