Are you able to set it up just like you want it?

You could start your song with that setup using a template.

Please up-vote the feature request I made here....

https://answers.presonus.com/37488/add- ... -song-data

Two other glaring omissions (IMHO) to Import Song Data functionality as well for your consideration to up-vote...

Mix View Scenes not available via ISD...
https://answers.presonus.com/37489/add- ... -song-data

...aaaannndddd.... no VCA's in ISD either....
https://answers.presonus.com/37487/add- ... -song-data

Thanks!

powerkor wroteSo, at the core of my issue is that 'Import Song Data' doesn't import busses that are on instrument output auxs. For example, I use SSD5 (steven slate drums 5) and I have all the outs separated so I can add plugins on specific drum pieces (like the snare for example)... the issue is that when I do import song data, it will import the midi file and all the outputs for SSD5 but if I have the toms going to a TOM buss, it doesnt do the buss.

Is there anyway to get the busses to come over that are associated with the instrument outs ??? Or is there a way to make all the instrument outs show up as a 'track'??

I solved this issue like this(in my case Superior Drummer 2). in doing in source projects.

I have seven separate stereo out for, kick, snare, toms, hihat, overhead, and two I call room and character that are combination of room mikes and close up mikes. And these outs are routed into a bus.

So always doing like this, anything will be accessible in import song data.
Here it goes
a) In arrange view create a track folder
b) put instrument track in folder
c) put the bus in the folder
c) assign the folder out to where bus go

And this create an entity that is visible for import song data.

I usually do this to project that I use as track templates, but if sticking to this principle - busses in folder for the purpose, and folder to where busses go - this seem to work nicely.

This works for any busses - put in folder and folder to where bus go.

I don't think it's necessary to put everything routed to a bus in folder as well, but often that is practical in that they belong together.

Can't wait to try this...

Right click Edit Automation for Busses and VCA's which will make arrange automation tracks for them and they'll list in the ISD dialog track list for import. Technically speaking, Busses and VCA's aren't tracks, they're channels, so they don't show up in the ISD track list in the dialog.

Or, check Options > Advanced > Automation > Automatically create automation tracks for channels and it will always happen by default.

That's good to know it can be done, but they are technically "song data" that we should be able to "import" without going through workarounds and adding stuff that we may not need.

The distinction track or channel - I wonder how many feel there is a difference other than that busses don't hold clips.

The mystery is why devs made a distinction between these when doing Import Song Data?
Just one and not the other.

The need for track template idea is ancient, kind of. All major daws have it.

Thanks to lawrence that extended understanding a bit.

darrenporter1 wrote..., but they are technically "song data" that we should be able to "import" without going through workarounds and adding stuff that we may not need.

If you look at the ISD dialog it quite literally says "Tracks" there in the list, Arrange tracks are tracks, and mixer channels are channels. Of course, audio tracks are both at same time. It's just the "1.0 iteration" of that new feature where they didn't yet include mixer bus channels.

Nothing to disagree about or debate really, that's just how it currently works and the FR for the other stuff has been on Answers since the feature first released in May in 4.0 so vote it up ...

https://answers.presonus.com/28860/s1v4 ... 860#q28860

https://answers.presonus.com/29216/more ... 216#q29216