wst3
Freezing and bouncing certainly free up resources, but I haven't needed to do that, yet. For the most part when I run into problems with playback it is a stutter or a click and bumping up the latency gets me back on track.
As far as workflow goes - I'd give my right... turn signal for an orchestral library that occupied one track per instrument, and included all the articulations in each track, accessible via CCs. That would reduce my template to what, 35-40 MIDI tracks and 35-40 audio tracks for the orchestra. Pretty significant savings!
But library developers don't ask me<G>!
So the choices are:
1) build on the fly and load only those instruments and articulations you need
2) work with a template
As libraries increase is capabilities (and size) and until there is a uniform way to handle multiple articulations per track I think the template wins because loading on the fly is a real concentration breaker. At least for me.
Second (and third, and so on) machine is the easiest way to manage the load today. Not entirely true, I suspect a single machine with 64 GB would do the trick too, but I don't feel like building a new primary DAW right now.
Thanks,
Bill
I am a bit confused about how you are dealing with articulations.
I use EastWest and Kontakt for sample-based instruments, and for an instrument where articulations are needed, I will usually insert one additional midi track for that instrument, but pointing it's midi output assignment to the same synth-rack instance of that instrument, so both midi tracks point to the same loaded instrument.
I then in the 2nd midi track insert individual note-events for the appropriate key-switch for the articulation I want, between one note and the next from the 1st track's midi data.
What I mean is that if I need to change from one vibrato type to another, or to simply add one of the vibrato articulations for a solo violin instrument, I will record the played notes on the original midi track, and then between the last note before the vibrato is to occur, and the note that needs the vibrato, I will insert the needed key-switch note event to the 2nd midi track - at that precise gap between the two notes, so the 2nd midi track contains nothing but articulation key-switch events.
Doing articulations for myself, in the above manner, keeps a single instance of the given instrument, and very little data on a 2nd midi track, and this keeps me from having to use multiple instances of the same instrument, saving resources.
For the EastWest instruments, like Gypsy solo violin, they have multiple instruments, but I use I believe it is the Master instrument, which has all the key-switches set up, and then I have a printed document I keep handy for my usually-used instruments, with the articulation key-switch chart from the EastWest documentation copied/pasted to fit on a single page.
I wasn't quite sure how you approach dealing with articulations, from my read of your quoted post, so I thought I would share what I do.
Bob Bone