Help with developing a similar workflow for S1 (coming from MOTU DP)...

[Sayat Nova]

I am trying to set-up a best-practices work flow process in S1 (coming from MOTU DP). I mostly always record live acustic sources with microphone in a room and go from there. My usually process is to record all of my tracks, then prep each one for mixing (correct any timing, pitch, volume levelling, etc), then finally start to mix them.

In DP, there is a system of having multiple "sequences" within an open project. So, I create a project, then use the first sequence for the recording session tracking only- so all of my raw audio files are here. I then create a second sequence (still within the same project) and do all of my basic edits and comping here to have all the tracks prepped, cleaned-up and ready for mixing. I then create a third sequence (still within the same project) and copy these mix-ready tracks over and get to mixing.

I think the way to do this is by creating a new Song in S1 (This seems to be the S1 equivalent to the Project), then record into this. Then, I guess you would create a second Song for edits and keep open both Songs open to be able to edit and work (copy/paste files) between them, as needed? Finally, I would create a new third Song, and then copy the mix-ready tracks and then mix into the third Song window? Is there a way to group all of these 3 Song windows for one project so that they are in a clearly contained folder in S1? What would be the best way to achieve what I am looking for, within S1s' framework/ecosystem?

Finally, when you use "transform to audio" to bake-in all of your edits (to prep the "ready-for mixing" files), does this also include Melodyne ARA instances on those tracks-are these just seem as an insert, as well? I hope so!

Thank you for the help and time.

 

[ozinga]

I think Scratch Pad might be the closest thing to what you need. Yes ARA is included as well.

 

[Sayat Nova]

Thank you for the reply. Good to know about the ARA.

My only concern with using Scratch Pad is that I am trying to limit my CPU usage as much as possible. I am assuming Scratch Pads will also put a load on the CPU if in the same Song?

 

[ozinga]

Thank you for the reply. Good to know about the ARA.

My only concern with using Scratch Pad is that I am trying to limit my CPU usage as much as possible. I am assuming Scratch Pads will also put a load on the CPU if in the same Song?

No problem,
No, all scratch pad versions and main project use the same mixer tracks inserts sends. So no processing is doubled or tripled.
Another way you can achive this is by using disable and hide tracks if you do not want to use scratch pads.
You can duplicate your raw tracks and disable originals put in a folder and hide, then do your edits on the duplicate. When you are done export and import mix files to the same session and disable and hide the edit tracks. So all versions of your files are on the same project but only mix tracks are visible and using CPU.

 

[Gary Shepherd]

I too came from DP many years ago (I still own it and keep it updated). I still use DP sometimes for more complex MIDI editing as it is much easier than S1 which seems more event based and still trips me up when trying to merge midi takes etc.

Scratch Pad - hmmm.....I too thought it might be the answer to having a sequence based composition rather than S1's linear approach. I was wrong - it really is a hindrance and screwed up one song for me, causing crashing and confusion. I don't even have the button for it on my toolbar anymore. I find it easier to go to the end of a song and setup a new Arranger Block for variations - and then you can copy and move the new block into the existing arrangement via the Inspector of the Arrange window.

I have for many years suggested that Scratch Pads may have some use for some people, but for me it is a good idea but done in a half baked way with the split screen. It is not a solution to replace having more sequence or Chunks based composition. I still prefer to compose and record in separate sequences (like Verse and Chorus etc.) rather than the Studio One linear method of having the whole song on the one screen.

However, moving Arranger Blocks on the Inspector window can help you move stuff around and experiment - and using a new Arranger Block at the end of the song (as it stands) means you can loop it and work on it discretely before copying it back into the main arrangement. I learned Daw recording on Opcode Vision and DP, and on hardware sequencers such as the Roland MSQ-700 and the Alesis MMT8 which are sequence (or Chunk or Block) based. It tends also to be the natural way for me to compose on guitar or keyboard - in sections.

I worked in a commercial studio in the 70's with 16 track and of course in those days you had to record the whole song - it was rarer to record in sections and either cut and paste (literally) on the 2 inch 16 track master, or 1/4 inch master ( but we did do it and there are famous tracks such as Strawberry Fields where the tape was cut and spliced).

 

[Sayat Nova]

No problem,
No, all scratch pad versions and main project use the same mixer tracks inserts sends. So no processing is doubled or tripled.
Another way you can achive this is by using disable and hide tracks if you do not want to use scratch pads.
You can duplicate your raw tracks and disable originals put in a folder and hide, then do your edits on the duplicate. When you are done export and import mix files to the same session and disable and hide the edit tracks. So all versions of your files are on the same project but only mix tracks are visible and using CPU.

Thank you for follow-up. This is all helpful information.

 

[Sayat Nova]

I too came from DP many years ago (I still own it and keep it updated). I still use DP sometimes for more complex MIDI editing as it is much easier than S1 which seems more event based and still trips me up when trying to merge midi takes etc.

Scratch Pad - hmmm.....I too thought it might be the answer to having a sequence based composition rather than S1's linear approach. I was wrong - it really is a hindrance and screwed up one song for me, causing crashing and confusion. I don't even have the button for it on my toolbar anymore. I find it easier to go to the end of a song and setup a new Arranger Block for variations - and then you can copy and move the new block into the existing arrangement via the Inspector of the Arrange window.

I have for many years suggested that Scratch Pads may have some use for some people, but for me it is a good idea but done in a half baked way with the split screen. It is not a solution to replace having more sequence or Chunks based composition. I still prefer to compose and record in separate sequences (like Verse and Chorus etc.) rather than the Studio One linear method of having the whole song on the one screen.

However, moving Arranger Blocks on the Inspector window can help you move stuff around and experiment - and using a new Arranger Block at the end of the song (as it stands) means you can loop it and work on it discretely before copying it back into the main arrangement. I learned Daw recording on Opcode Vision and DP, and on hardware sequencers such as the Roland MSQ-700 and the Alesis MMT8 which are sequence (or Chunk or Block) based. It tends also to be the natural way for me to compose on guitar or keyboard - in sections.

I worked in a commercial studio in the 70's with 16 track and of course in those days you had to record the whole song - it was rarer to record in sections and either cut and paste (literally) on the 2 inch 16 track master, or 1/4 inch master ( but we did do it and there are famous tracks such as Strawberry Fields where the tape was cut and spliced).

Ha! I, too, came to DP when Gibson killed Opcode.... I also have DP installed and keep it updated. I am very used to the Chunk and sequence workflow and think it is very well done, as is the excellent MIDI implementation. However, DP is rather clunky to use after working in S1, and I got fed-up with the Hardware Insert not working correctly and the limited Console One MK3 integration...These same issues are completely solved in S1. I, also, mostly use basic MIDI capabilities, and will just go to DP when I need more than is there in S1.

I think given all of the information here, I will probably just do as I stated in my original post; create individual Songs in a collected "Project" folder for tracking, prep for mixing, and mixing. From a DP point of view, I will use the "Home" button in S1 as the "Sequence select" function in DP, and the Song files in S1 will be my Sequences in DP. The keeps things clean and lean.

Obviously subject to revision, but it is a start.

Thanks, Everyone for the help and info.

 

[Gary Shepherd]

However, DP is rather clunky to use after working in S1, and I got fed-up with the Hardware Insert not working correctly and the limited Console One MK3 integration..

Clunky is always the way I have described DP too.