@JWL said:
You must tell us how you accomplished this-- seems to have involved some extremely sophisticated balancing-- and one one computer? There's a great lesson in this for rest of us.
JWL, and others: Wow. Thanks for saying such nice things about my work. I hadn't expected that, and I'm gratified to hear your comments.
The following is for those who have asked about how I did this with a single 1.8 Ghz Mac G5:
To accomplish this on one computer, first of all, you have to be poor. I suppose any of us who actually have the VI cube would qualify. This removes the possibility of being able to throw more money at the problem, forcing you to think.
Digression: I was watching Apollo 13 (The Ron Howard movie) and thought, if NASA could do such an amazing thing with the computing power of a Mac Plus (I'm guessing), then there simply must be a way to get my rinky-dink Mac to get me the performance I wanted for David Heuser's piece. Well, NASA had a huge team of very smart people, too. Smart enough to realize that relying on computers to solve their problem would have been foolish. And, more importantly, smart enough to actually solve the problems they faced with their own brains. The point is, the most important part of this is to know very clearly what the end result should be and be very facile with the available tools.
So here is how I did itI made simple MIDI version in Logic with no VI plugins and got the tempo and spacing between phrases/sections roughly in place. Then I peeled off one instrument group at a time (via "Save As ...") to its own Logic song file.
Then, for example, I opened the Violins file, put in the VI tracks with no reverb or anything else, not even any panning. I then worked on just those instruments until they were right (to me) in this totally dry setting. I kept those god-awful QuickTime MIDI tracks muted. I instead tried to imagine the violins' relative loudness with respect to the other, muted instruments. I then bouned the Violins to a WAV file.
I repeated this procedure with all the rest of the instruments, too, ending up with about twenty separate Logic files, each with no more than four or five VI tracks. Working this way, it was a pleasure to just be able to add a track when I needed, say, polyphonic legato, and not be concerned about whether my Mac would balk. However, this also served to give me a taste of what it would be like to just work and not have to worry about computing resources. [:)]
Next I took the original MIDI Logic file that had the tempo/time signature and saved a copy ... and deleted all the tracks. I then made an audio track for each of the twenty-odd WAV files I now had and just imported all those audio files to the appropriate track.
Dealing with the audio files in Logic was very easy. It was in this final version that I used space designer and the direction mixer to get the space/reverb work done (which I'm really not that satisfied with, still. But that's not a technical limitation, just a limit of my own experience).
I also used hyperdraw on some, but not all, tracks to adjust some balances here and there. I also added a "sub-bass" enhancement to the bass drum part and bit of eq on the horn, violins, basses and piano.
(BTW, I forgot until just now that the piano was not a VI instrument. I used Post's Steinway "Old Lady" and eq'ed it to be brighter. Also, the police whistle I could not find in the VI percussion instruments. So I bought a sound effect from SoundRangers.com for that.)
I did also use an AdLimiter plugin on the Output 1-2 fader, but only a smidgen because some of the stuff was just too quiet.
The main problem I anticipated before I started turned out not to be so bad after all. Namely, that it would be crushingly slow to have to move back and forth between different Logic files to tweak things. It turns out that opening a Logic file with only a handful of VI tracks (that all were optimized, too ... that made a big difference), really didn't take that much time. And so "workflow" pacing was really not bad.
For example, if I need to change something in the Bass section after having already incorporated the audio into the final Logic file, I just closed the final file, opened the Bass file, made the tweak, bounced to WAV (using the same target filename as before), closeed the Bass file and opened the final file. Logic automatically updates the file if any of the component audio files have changed. That sometimes would take twenty seconds. This could become very annoying if you have to go back and forth like that to refine something. But I only had to redo a particular spot maybe about five times at the most. Again, the key is to get it right the first time so you can avoid this rather more tedious method of making changes.
So, I would sum up by saying, if real time, simultaneous processing of all VI tracks is not required, you can work in this manner, provided you have a very clear idea of how all the pieces should be put together in the end.
I readily admit that this is not the ideal way to do it, but the additional time and frustration I anticipated that I might have had to pay for working this way turned out to have been negligible. ... It took me three solid weeks to make the performance, working about 8 hours a day, not including weekends (when I spend time with my kids [:P] )
- Paul
