The Official KSAND Kent Sandvik Web Site

Producer, guitar player, composer and maker of noise.

Massive Rediscovered, Bouncing

Posted on | December 29, 2008 | 2 Comments

Native Instruments MassiveAs I switched over to a MacPro as my main studio computer I didn’t immediately install all the earlier plug-ins. Rather I put them in on demand, such as the mastering tools. The rest I kind of kept in the attic, and installing them with a fresh mind. It’s like picking up a guitar from storage and falling in love with the guitar again. Attics are nice, software attics, too.

This time I installed Massive as I’m looking at more electronic-centric film music as a project. It was indeed fun rediscovering this one. Here’s a quick sample I did as one of the first sounds: [audio:massive_pad.mp3]

Still with plenty of RAM and an Intel MacPro, Massive is still a massive CPU-eater, that’s for sure.

However, in most cases either freezing or bouncing is quite fine to do. I use bouncing quite a lot nowadays to render down material that could be played back later with less manipulations. It forces me to make production decisions on the fly so that I don’t get stuck in endless tinkering. I even re-configured the default key bindings so that Command-E in Logic is now exporting regions, not exporting whole tracks, as that’s the more common operations.

Another option is to save it as an AppleLoop and drag the green AppleLoop into an audio track. This way the saved 24-bit audio file is used rather than the midi file with the plug-in. And if you ever want to change the MIDI you could drag it into an instrument track and re-tweak. So there’s plenty of flexibility in the Logic environment. I tend to avoid freezing tracks as it takes a while to freeze a whole song track, but that’s always an option, too.

Comments

2 Responses to “Massive Rediscovered, Bouncing”

  1. Xichael
    January 14th, 2009 @ 10:18 PM

    You could also just lower the CPU mode a couple notches. “Eco” mode can halve the CPU load on some patches, with surprisingly little consequence.

  2. Kent Sandvik
    January 15th, 2009 @ 12:20 PM

    That’s a good point. Many SW synths have a way to disable the number of polyphonic tones present, helping out with the overall CPU load. Vanguard has something similar. The curse is that the vendors have it on max setting by default to show all the features while we end users would prefer to start from a smaller value by default and increase if needed…

Leave a Reply

You must be logged in to post a comment.

About

This is an area on your website where you can add text. This will serve as an informative location on your website, where you can talk about your site.

Subscribe to our feed

Search

Admin