I'm a little confused on the best ways to use sub-mixes in PARIS.Is this mainly to get more virtual tracks once the first 16 are full?Please give me a step by step example... thanks, tonehouse
That is correct. Since each submix retains all settings, automation, etc, it is much more useful, and faster than traditional bouncing and resetting the mixer for more tracks (the actual update process does happen in realtime though - it plays through the song to update each submix).
Let's say you have only one EDS card, and Submix 1 is assigned to that card (A). Once you fill those 16 tracks, and need more you would assign the card to a new submix (Submix 2 for ex.), which will then change Submix 1 to "Virtual". Now hit "update" on Submix 1, and that submix would create a virtual, or bounced submix of those 16 tracks with all EDS, VST, DX, effects, Auxes, EQs, automation, etc. Then you can work on the next submix (2) with full access to all tracks. Switch back and forth at will, add more submixes, whatever you heed. If you have v3.0, you also have "Native" submixes that can use the cpu for all EQs, etc. I find these take way more processing than any other host-based DAW, and don't sound as good as card based submixes. They can be useful for a handful of backing tracks (synths, effects, loops, etc) that don't require as much hi-fi as critical tracks.
Tonehouse, That is correct. Since each submix retains all se
Tonehouse,
That is correct. Since each submix retains all settings, automation, etc, it is much more useful, and faster than traditional bouncing and resetting the mixer for more tracks (the actual update process does happen in realtime though - it plays through the song to update each submix).
Let's say you have only one EDS card, and Submix 1 is assigned to that card (A). Once you fill those 16 tracks, and need more you would assign the card to a new submix (Submix 2 for ex.), which will then change Submix 1 to "Virtual". Now hit "update" on Submix 1, and that submix would create a virtual, or bounced submix of those 16 tracks with all EDS, VST, DX, effects, Auxes, EQs, automation, etc. Then you can work on the next submix (2) with full access to all tracks. Switch back and forth at will, add more submixes, whatever you heed. If you have v3.0, you also have "Native" submixes that can use the cpu for all EQs, etc. I find these take way more processing than any other host-based DAW, and don't sound as good as card based submixes. They can be useful for a handful of backing tracks (synths, effects, loops, etc) that don't require as much hi-fi as critical tracks.
Dedric