Yes, or almost. Lets say that in my largest projects the amount of tracks approach about 100. Of those maybe 70% are VST instruments and of those maybe 70% are CPU/RAM heavy VST instruments. When the project reaches its end the amount of tracks is reduced significantly, usually to abt. 40-50 tracks or so.Pitch Black wrote:This is a real-world scenario for you?golemus wrote:I did some initial tests... I have an 80 track project (each track has Massive, Pro-Q, Volcano, Timeless and Zebrify)
I explain a bit of my workflow. I do a lot of melodies. I make a melody, choose a patch, then put a few plugs. After this I duplicate the track, and browse through patches until I find next one I like. Then I do this again, sometimes about 10 times if it is important melody. So I have 10 duplicates of the same melody with different patches, some of them even with different VST instrument. Then I play it above bassline and percussions.
Then I make another melody. I repeat this process and get another 5-10 tracks.
Then I do the same for drumloops, I get maybe 5-8 drumloops.
After I have these I experiment by muting/unmuting different channels that which VST-instrument/patch fits the best to the mood I am trying to create. Then again I do this with the loops.
Only when the song is in quite final phases I feel that I can with confidence decide patches and then start deleting all duplicate melodies. Sometimes after that creating extra layers with new patches (chosen with the same approach.
So even that there is this large amount of tracks, most of the time most of them are muted, and in the end deleted