That's traditionally the function of a template, to start a song with everything setup just how you like it.

I haven't used import song data yet, still trying to wrap my head around how I would use it.

I mainly spend a lot of time setting up synths to create a section of a song, I can't change it all for another section so maybe just import mixdowns of the sections or something, still working on where to put the modules and how to access them.

Maybe there is a problem with the template, which I am assuming was created in V3? To rule that out, can you recreate your song template from scratch in V4, and then try the same steps?

No this problem does not relate to templates in the traditional Studio one sense nor anything to do with v3.
This all relates to the "import Song data"

Seems like it would get confusing if you're bringing in the audio routing with the data, especially if it conflicted with what's in the song already.

I just tried this out with a US-16x08 with a folder of Guitar tracks with 4 different inputs assigned.

The folder imported fine with the inputs correctly assigned.

Sorry - I don't have the same interface

Thanks bobf for trying this and replying.

I retested mine again today but simplified it.

In my original test I too had folders but the latest test was without.

Did you do this.
I created a blank song then cleared all my audio inputs in the audio setup for the song. Then created two new mono audio Inputs labelled input1 and input 2 (the default). Then in the arrange window I created two new audio mono tracks and i assigned these two tracks to inputs 1&2 . Saved the song as "test audio.song"

Then created another blank song and set the audio up as above but without the two audio tracks. Went to song import song data and imported the two tracks from "test audio song". They both came in as "none" for their inputs.
So if you did the same and you get inputs assigned then why doesn't mine?

Thanks for your time.

Can you attach that test song to his thread please?

peterbirch wroteThanks bobf for trying this and replying.

I retested mine again today but simplified it.

In my original test I too had folders but the latest test was without.

Did you do this.
I created a blank song then cleared all my audio inputs in the audio setup for the song. Then created two new mono audio Inputs labelled input1 and input 2 (the default). Then in the arrange window I created two new audio mono tracks and i assigned these two tracks to inputs 1&2 . Saved the song as "test audio.song"

Then created another blank song and set the audio up as above but without the two audio tracks. Went to song import song data and imported the two tracks from "test audio song". They both came in as "none" for their inputs.
So if you did the same and you get inputs assigned then why doesn't mine?

Thanks for your time.

My scenario wasn't exactly the same.

I create new songs from a user template that has the audio I/O config set the way I want for 99% of the cases. This template contains no tracks.

I created song (1) from this template, with the Guitar tracks mentioned above and some instrument tracks.

I then created song (2) from the same template. I then used ISD to import the tracks from song (1) into song (2).

Try this:

Create a new empty song and set up the I/O the way you want.
Save this as a song template and close it.

Create a new song(1) based on this new template. Add the track config you want to reuse.
Save.

Create a new song(2) based on the same template, then use ISD to bring in the tracks from song(1).

If nothing else, this might tell us whether or not there is something different between manually setting I/O identically in two songs, or using a template to accomplish the same.

I can see why yours worked BobF but what a long winded way. I thought that Importing song data would accomplish that in one import. Well it does actually structure and all, except for the assignments.

I just tried this on my other play machine which has a Balance audio box that has 1 stereo and 2 mono inputs L&R. Cannot get simpler than that.

Created two tracks mono L&R named Audio in L and Audio In R

When imported into a blank song the two tracks showed Audio in L on both tracks.

There was no point uploading a song as this problem has shown on both my machines (win8.1)
and more importantly it is so simple to test for anyone running S1v4
Thanks to jpettit and Bobf for taking an interest.

Now that you know more can you better articulate the issues?

Is is that the import does not bring on the original I/O settings or the opposite the settings are not mapped to the new I/O?

peterbirch wroteI can see why yours worked BobF but what a long winded way. I thought that Importing song data would accomplish that in one import. Well it does actually structure and all, except for the assignments.

I just tried this on my other play machine which has a Balance audio box that has 1 stereo and 2 mono inputs L&R. Cannot get simpler than that.

Created two tracks mono L&R named Audio in L and Audio In R

When imported into a blank song the two tracks showed Audio in L on both tracks.

There was no point uploading a song as this problem has shown on both my machines (win8.1)
and more importantly it is so simple to test for anyone running S1v4
Thanks to jpettit and Bobf for taking an interest.

Your steps are simple to follow but I can't duplicate your results at least not on S1 v4.0.0. Mac OS X 10.12.6. That's why a song file might help. For the record, I simply opened the old song from the Browser and dragged and dropped the tracks into the new song. Input L, R, etc showed up as they were.

When you say you create "an empty song", are you creating it with a new song or a new song from a template? I understand that you are using Import Song Data but S1 treats songs created from templates differently, even if it's an empty template, so we're trying to rule that out.

peterbirch wroteI can see why yours worked BobF but what a long winded way.

Yeah, that does seem like the Longest Path. When you do it all at once anyway.

Keep in mind that these aren't steps I follow every time I want to use ISD. The template I use to create songs has been gradually tweaked so that using it actually eliminates a ton of click-this/click-that when starting a song.

So the actual use case goes like this:

I start a new song from my template and decide I want the same drum config I had in Old Song 27 and the same guitars as Old Song 14. The I/O and the source tracks were already created, so the steps are much fewer.

I've seen some discussion (Idon't remember where) about including I/O settings as part of ISD. In my thinking that could cut both ways, and could be problematic when trying to share "Track Template" songs with other users that will likely have a different interface.

Please do take the time write up exactly how you think ISD would work best in this regard. ISD is new and will likely see some tweaks along the way.

viewtopic.php?p=176255#p176255
Yes I have now idea what the issue is.

BobF wrote

peterbirch wroteI can see why yours worked BobF but what a long winded way.

I've seen some discussion (Idon't remember where) about including I/O settings as part of ISD. In my thinking that could cut both ways, and could be problematic when trying to share "Track Template" songs with other users that will likely have a different interface.

Please do take the time write up exactly how you think ISD would work best in this regard. ISD is new and will likely see some tweaks along the way.

Sharing is always going to be a compromise as most setups differ from small to large ways.
Audio can be shared either as a song going to MAIN or as stems. MIDI is problematic if the external or internal instruments are different.

OK on the second point. Templates, were to me, a kind of one stop shop. You prepared a template based on what you think you will need. Sometimes I created a template with ALL bells and whistles, in case, then deleted what I didn't need bit like the cart before the horse. Never got to terms with this. E.g. you could have a template for recording Acc Guitars and Vox, simple and small but then if it is decided to bring in a small string ensemble, you could not "tack-on" another string template. You can make work arounds but it seems a clunky first step in Studio One evolution. In similar fashion track templates useful but...time wasted looking for them and then importing, if it was good enough to save then it should be part of the track ready for ISD.

ISD seems to be a grown up solution where you can mix and match. Now I am convinced that the vast majority of users and studios have a stable environment. In that, the audio hardware doesn't change that much. Original templates can be saved as a song, so the Symphony Orchestra Template can be saved as a blank event song. Then in the above scenario, a new song is created from a blank. ISD tracks/busses from a known acc+vox song then to add more tracks, ISD the bass, drums from o song you liked and the string ensemble tracks from the orchestra song. All this would be quick and efficient. I think Presonus have done a good job with what can be imported. Just needs the I/O of the stable environment.

If there is a shared song from someone then obviously one would have to change I/O assignments that's a gimme because of hardware.

Well Bobf you did ask me to take the time to write it up - be-careful what you wish for...

peterbirch wrote

BobF wrote

peterbirch wroteI can see why yours worked BobF but what a long winded way.

I've seen some discussion (Idon't remember where) about including I/O settings as part of ISD. In my thinking that could cut both ways, and could be problematic when trying to share "Track Template" songs with other users that will likely have a different interface.

Please do take the time write up exactly how you think ISD would work best in this regard. ISD is new and will likely see some tweaks along the way.

Sharing is always going to be a compromise as most setups differ from small to large ways.
Audio can be shared either as a song going to MAIN or as stems. MIDI is problematic if the external or internal instruments are different.

OK on the second point. Templates, were to me, a kind of one stop shop. You prepared a template based on what you think you will need. Sometimes I created a template with ALL bells and whistles, in case, then deleted what I didn't need bit like the cart before the horse. Never got to terms with this. E.g. you could have a template for recording Acc Guitars and Vox, simple and small but then if it is decided to bring in a small string ensemble, you could not "tack-on" another string template. You can make work arounds but it seems a clunky first step in Studio One evolution. In similar fashion track templates useful but...time wasted looking for them and then importing, if it was good enough to save then it should be part of the track ready for ISD.

ISD seems to be a grown up solution where you can mix and match. Now I am convinced that the vast majority of users and studios have a stable environment. In that, the audio hardware doesn't change that much. Original templates can be saved as a song, so the Symphony Orchestra Template can be saved as a blank event song. Then in the above scenario, a new song is created from a blank. ISD tracks/busses from a known acc+vox song then to add more tracks, ISD the bass, drums from o song you liked and the string ensemble tracks from the orchestra song. All this would be quick and efficient. I think Presonus have done a good job with what can be imported. Just needs the I/O of the stable environment.

If there is a shared song from someone then obviously one would have to change I/O assignments that's a gimme because of hardware.

Well Bobf you did ask me to take the time to write it up - be-careful what you wish for...

Peter - thanks for taking the time. I want to play back my understanding to make I got the meat:

You're basically happy with the current state of ISD, the exception being I/O assignments?

Bobf absolutely. This was worth the upgrade cost and will greatly change and ease my workload. Hope the I/O gets some thought.

peterbirch wrote Hope the I/O gets some thought.

What is missing?
In one sentence please so this could be expressed as an FR.

It sounds like I/O assignments aren’t being properly transferred when you’re using ISD. The “write up” was thoughtful, we just need some clear and concise info that specifically relates to reproducing your issue.

The reason is that I tried reproducing the steps that you alluded to but couldn’t duplicate your issue.

1. Were any of the songs in your tests created using a template?

2. Can you please attach a simple test song to this thread? Preferably a test song that doesn’t properly transfer IO data when you use Import Song Data on it.