Looking for an organization idea of multi-version multi-DAW project

[middle_color]

What i want to achieve is a folder structure and possible automation support for following single project:
1. compose in Ableton/Bitwig/Reason/Cubase/Studio One
2. mix in Cubase
3. master in Studio One

Looking for ideas of putting it all together under parent folder AND easy process of keep tracking version (i increment version on each SAVE) and situation as such:
While mixing i understand that to continue mixing i need to go to composition project and change particular track and re-render it as a stem for mixing.

What are some suggestions to make it fast, automated and to not mess up versions?

[EdgarRothermich]

Regarding the folder structure, you just organize it the way it makes sense to you. For me, I keep the folders organized by Projects. The files in those folders don't care if they were generated by various apps. You just double-click on them and the corresponding app opens.
Organizing the files by app doesn't seem that practical and you create your project hierarchy for each app again.

Regarding automation, I don't know what you are referring to. I would be suspicious, and I like to open and close projects when I like to and not automatically kick in when an algorithm thinks, "oh, the mix is done, let me bounce it, close Cubase and open Studio One for mastering".
I think the better approach would be creating different templates for the various steps during production.

[middle_color]

Regarding automation, I don't know what you are referring to. I would be suspicious, and I like to open and close projects when I like to and not automatically kick in when an algorithm thinks, "oh, the mix is done, let me bounce it, close Cubase and open Studio One for mastering".
I think the better approach would be creating different templates for the various steps during production.

Thanks for the input.
Regarding automation i wanted something like this:
If i want want to update file from previous stage (ex: Composition -> Mixing), i would like to go to the composition project, then render particular track and it automatically updates inside of a mixing project. Without needing to import updated file manually.

[Tj Shredder]

What is missing in the DAW you want to produce with to make the mix and the master? Or do you want to give those tasks away to someone else?
Mixing and mastering is straight in any DAW if you have the right plugins in your arsenal...
I would not bother with all the hassle to export and import and bouncing and I don‘t know what just to mix or master. Unless you mean mastering a bunch of stereo mixes, but then I would load them into a dedicated editor (like Acoustica or Ozone) and not into a DAW...
If you want someone else to mix, it might be cheaper to buy them the missing DAW... Anyone who can mix, can mix in any DAW...

[middle_color]

What is missing in the DAW you want to produce with to make the mix and the master? Or do you want to give those tasks away to someone else?
Mixing and mastering is straight in any DAW if you have the right plugins in your arsenal...
I would not bother with all the hassle to export and import and bouncing and I don‘t know what just to mix or master. Unless you mean mastering a bunch of stereo mixes, but then I would load them into a dedicated editor (like Acoustica or Ozone) and not into a DAW...
If you want someone else to mix, it might be cheaper to buy them the missing DAW... Anyone who can mix, can mix in any DAW...

Thanks for responding, i somehow missed your message.

I do like to compose in different DAWs (i own a lot of them). Different DAWs has different features: better work with audio, modulation system, session view etc. While working in different DAWs i come up with different workflow that leads me to finished composition.

But mixing and mastering should be streamlined scenario for me, that's why i choose Cubase. Actually since my previous message and switched to master in Cubase also.

What am i missing in different DAWs from Cubase:
- fixed number of insert slots (i use not more than 5 practically). i like that it looks like even spaced grid in mixer
- several mixer views
- q-link (simultaneous parameter tweaks on different channels)
- ability to hide and show tracks freely
- ability to glue tracks to left o right side of a mixer
- control room - super easy track referencing, dim button, quick mono. all from single panel
- disabling and hiding track - to have a track's backup

I actually bounce tracks to wav even if i do whole production in single DAW: this eliminates latency issues. I sometimes alight wave form manually, because timing is not exact after PDC. I also often do momentary silence in the middle of the song to pump listener's cortisol . Automation is not sufficient for this: i do cut audio files with razor to make an effect stronger.

[middle_color]

Follow up to my initial question. I came up with following workflow for now:

Folder structure:

Code: Select all

Project name
    ____stems
        01 - kick.wav
        ...
    ____mixdown
        premaster 01.wav
        ...
    compostion
        Project name (composition).ext
        Project name (composition) ____ 2.ext
        Project name (composition) ____ 3.ext
        ...
    mixing
        Project name (mixing).ext
        Project name (mixing) ____ 2.ext
        ...
    mastering
        Project name (mastering).ext
        ...

I also created super generic Cubase template and track presets, that i can use in all 3 strages hiding or showing different parts of template. Very convenient!

Naming convention allows to differentiate project and its version in a "recent" area in each DAW.

I start in "composition" folder then export stems to "____stems".
Import them in a "mixing" project. Then export mix into "____mixdown" - there are different mixdown versions which are relative to "mixing-project" version.

As for mastering project, i do not save different versions of a project - i create tracks with version convention: "premaster 01", "premaster 02" etc.


__

thanks for inspiration regarding templates!