I know, it's just that you can drag so many other things, and when the one project is on the left and the other on the right it feels a little senseless to have to export, then import a track template. Like I said, you can move plugins and clips, so why not tracks? Also seems weird that you can drag regular vsts (including the ones inside a PC chain) but not the ProChannel modules. Not that I use those, just something I noticed when I was trying it just now.

Sanderxpander
I know, it's just that you can drag so many other things, and when the one project is on the left and the other on the right it feels a little senseless to have to export, then import a track template. Like I said, you can move plugins and clips, so why not tracks? Also seems weird that you can drag regular vsts (including the ones inside a PC chain) but not the ProChannel modules. Not that I use those, just something I noticed when i was trying it just now.

Yea, I hear you.  One thing they should work on is having the ability to move anything anywhere.  

Coincidentally, I'm kind of surprised that this seems an uncommon workflow? This is how I practically always move audio between projects. Perhaps this is why people keep insisting on the "apply mix preset" thing in that other thread? It's pretty easy to do it this way around.

It does mean reloading each plugin when you "activate" a project but on a modern system, assuming the project isn't super heavy, it's quite quick.

Sanderxpander
Coincidentally, I'm kind of surprised that this seems an uncommon workflow? This is how I practically always move audio between projects. Perhaps this is why people keep insisting on the "apply mix preset" thing in that other thread? It's pretty easy to do it this way around.

It does mean reloading each plugin when you "activate" a project but on a modern system, assuming the project isn't super heavy, it's quite quick.

What would be the typical use-case for what I am doing though? I never had to do this, this is just a one time thing b/c I want to use a new template but have these old songs i want to transfer over to my new workflow.
 
Also, what is this "apply mix preset" thing you are talking about?

While you can only open one instance of the actual version of the software, you can have dozens of "work" spaces opened within the software. Duh, they are windows! All Windows software uses this since 1995? So they (the projects) can all be re-sized to fit any amount of screen space. 
 
I often open 2 projects side by side to transfer tracks. Even though I have 2 monitors, I do this on my main screen. I only need to see the track name in the inspector and a tiny bit of the actual track. 
 
When I record a live session I open 24 or so blank template projects and minimize them. They line up neatly along the bottom. This requires Sonar to be in "floating mode" so you can see the desktop at the bottom. A second monitor would also work. This way I have a fresh project ready to go in less than 10 seconds. 
 
PS: I'm pretty sure you can have two complete Sonar's open side by side too. They would just have to be different versions. Not sure if they would both play at same time?? OOk. 
 

alewgro

Sanderxpander
Coincidentally, I'm kind of surprised that this seems an uncommon workflow? This is how I practically always move audio between projects. Perhaps this is why people keep insisting on the "apply mix preset" thing in that other thread? It's pretty easy to do it this way around.

It does mean reloading each plugin when you "activate" a project but on a modern system, assuming the project isn't super heavy, it's quite quick.

What would be the typical use-case for what I am doing though? I never had to do this, this is just a one time thing b/c I want to use a new template but have these old songs i want to transfer over to my new workflow.
 
Also, what is this "apply mix preset" thing you are talking about?

Well for me it's relatively common to move audio between projects, and sometimes midi parts too. Rather than using the relatively opaque "import" dialogs I like to drag stuff and drop it where I can see it. I've also used it to copy fx, in which case I keep a "related" project open and try out copying fx or chains. For me it's quicker than opening the project, creating a track template, then putting that into the new project and moving the audio. Additionally, I like keeping my track templates folder neat and filled with actual templates that I might use to set up a project. Not a whole bunch of presets I only needed once or only wanted to try.

In response to Sock Monkey, I think it would depend on the sound card. Mine only supports one ASIO client at a time, although I could run a second version in WDM mode.

Sanderxpander

alewgro

Sanderxpander
Coincidentally, I'm kind of surprised that this seems an uncommon workflow? This is how I practically always move audio between projects. Perhaps this is why people keep insisting on the "apply mix preset" thing in that other thread? It's pretty easy to do it this way around.

It does mean reloading each plugin when you "activate" a project but on a modern system, assuming the project isn't super heavy, it's quite quick.

What would be the typical use-case for what I am doing though? I never had to do this, this is just a one time thing b/c I want to use a new template but have these old songs i want to transfer over to my new workflow.
 
Also, what is this "apply mix preset" thing you are talking about?

Well for me it's relatively common to move audio between projects, and sometimes midi parts too. Rather than using the relatively opaque "import" dialogs I like to drag stuff and drop it where I can see it. I've also used it to copy fx, in which case I keep a "related" project open and try out copying fx or chains. For me it's quicker than opening the project, creating a track template, then putting that into the new project and moving the audio. Additionally, I like keeping my track templates folder neat and filled with actual templates that I might use to set up a project. Not a whole bunch of presets I only needed once or only wanted to try.

In response to Sock Monkey, I think it would depend on the sound card. Mine only supports one ASIO client at a time, although I could run a second version in WDM mode.

just out of curiosity, what is your use-case for moving tracks between different projects?  for me its a one-time thing as I have a bunch of songs I built without a track template.  Now that I have a pretty sophisticated one setup, I want to copy my old songs into them.

Well for instance if I've made a mix or edit decision that I end up not liking, I can import the original from an older version. Or if I'm mixing a thing and I remember having a nice vocal chain during a certain project and I want to see how it works on this one. I could use a track template I suppose but it seems roughly the same amount of work (having to open the old project, export the template, etc.) and this way I can see what I'm doing a little better. It's also useful to compare mixes, especially when working with the same people.
 
In Ableton I do more dance-oriented projects and it can be really useful to import an entire track with a good groove or sweep and all fx and everything already on it.

Sanderxpander
Well for instance if I've made a mix or edit decision that I end up not liking, I can import the original from an older version. Or if I'm mixing a thing and I remember having a nice vocal chain during a certain project and I want to see how it works on this one. I could use a track template I suppose but it seems roughly the same amount of work (having to open the old project, export the template, etc.) and this way I can see what I'm doing a little better. It's also useful to compare mixes, especially when working with the same people.
 
In Ableton I do more dance-oriented projects and it can be really useful to import an entire track with a good groove or sweep and all fx and everything already on it.

ahh ok.  that makes sense!  :)

alewgro

Sanderxpander
Glad to hear it! Can I get "best answer" now? :p

Technically, your idea works, so you now have the answer. :)  I hope I dont piss of John.
 
-alewgro

No! In fact I prefer being proved wrong when it proves useful! In this case I couldn't be happier.