How to mix when using Songs

[mgraham]

I've gone down the road of creating a project with multiple sections (intro, verse, chorus, etc.) - each in its own sequence. All sequences share VIs and effects, using a shared v-rack.

Then I've lined these up in the Song window so they play back in order.

So far so good.

When I want to listen to my piece as a whole, I use the "merge chunks to sequence" feature and make a mixdown from that.

However, now I want to start making mix changes to each sequence separately. For instance, the drums might be a little too loud in the verse, and the piano might be a little too quiet in the chorus.

What some strategies to approach this?

I tried using the VCA system to create groups and VCA faders in a sequence. This works when the sequence is active, but all of the groups get lost when I "merge chunks to sequence".

Another approach is to have all virtual instruments routed to busses, and have these busses routed to Aux Tracks within the original sequence. But the problem with this approach is that when I "merge chunks to sequence", all the aux tracks from all the sequences are included in the resulting sequence resulting in the level changes from different sequences overwriting each other.

I have a feeling that I'm "doing it wrong". Are there any other approaches I can take? Or have I hit the limits of what the chunk/song system can do?


Michael

[mgraham]

I've also noticed that dragging a sequence into the Tracks Overview of an empty sequence also does not include its VCA faders or groups

[MIDI Life Crisis]

The strategy, IMO, is to not use the song window. If you do, don't flatten (merge to sequence) until you're happy with the mix. Once you merge them, it's one hot mess to deal with. If it still works the way it used to, if you don't merge, you can double click on the item (sequence) in the song window and the original sequence should open for editing.

Frankly, I see no reason to use the song window for any serious work. It's great if you're creating a repetitious series of sequences (verse, chorus, verse, chorus, yadda yadda yadda...) and I'm not saying there's anything wrong with that if you like that M.O., but the song window, while "precise," is also only accessing the individual sequences until you merge them, at which point it becomes the one sequence editing nightmare you are experiencing.

You may be able to UNDO until just before the merge and continue working on individual sequences, but if that's not an option, all I can say is good luck and don't do it again...

[mgraham]

Thanks for your feedback. So - to be clear, are you recommending using a single sequence for each musical piece?

The reason I've been using Chunks/Songs is not because my work is repetitive or formulaic, it's because I'm testing out song structures and arrangements. The song I'm working on has gone from a 4 minute pop song to a prog rock epic and back again more than once as I've added and removed and reordered sections, experimenting with what works and what doesn't.

Being able to work this way has been fantastic so far - I've tried out new ideas by starting a new sequence and then inserting it into the song structure. Most of my sections have different tempi and time signatures as well.

[MIDI Life Crisis]

Yes, a single sequence (AKA chunk) for each piece. In my case, each cue is a separate chunk. In my film work, I generally will have multiple chunks. When I'm ready to start putting that together into a complete score I'll bounce each sequence into the project format (bwave 48k/24 in my case) and create a master sequence/chunk where I can place the individual sequences - all in the same DP project.

Some folks like to use one project for each cue, which makes no sense at all to me, but whatever. If i was doing an album, I'd probably do each song in a separate project. Based on your progress (from song to a larger form) one project for all is probably the best way to work. The only exception would be if one section is really massive in terms of plugs, routing, etc., and also uses big VIs.

If you're using large VIs, there are strategies to lessen CPU hits, but that's another discussion...