New York compression

October 19, 2007

In the last few years the technique of parallel compressing drums have become increasingly popular. The idea is to get a “fat & compressed sound”on the drums without suffering the audio degradation that comes with compressing a signal heavily. This technique is also known as New York compression and this is how it set up.

Set up a send on all the drum tracks sending to Buss 1 or any free bus. On the return buss instantiate a compressor, Set a fairly high ratio, 10:1 or higher. A fast attack and a medium slow release are pretty usual but play with it until it sounds good. Now add a EQ after the compressor and boost a couple of db’s of gain around 10K and the same on the low end and blend to taste with the original signal.

Adding the bass on a send to the compressor buss usually work well too.

If you’re on Tools or working on a console then just buss the drums straight without using sends.


Moving projects between platforms

October 19, 2007

Moving song files between platforms is pretty straightforward but it requires a bit of planning (and usually a bit of trial & error).

Moving projects by consolidating files.

Probably the most reliable way of moving songs between platforms is to make sure all tracks have the same starting point ( i/e bar: and then bounce them all to individual audio files . However even if the source app has a “Bounce all tracks” feature, writing down and then setting up all insert and f/x settings again in the new app this can be fairly time consuming.

But with a bit of planning and what’s know as “printing to stems” we can save some time and make sure we’ll get to the pub before last orders.

Let’s say we’re moving a project to another studio in order to record some bass. In the below screenshot the drums have been mixed together to one stereo file (stem) and all the rest of the music to another. The bass have been left on it’s own individual file so we can mute it once the the bass player have learned how to play it. The point of splitting the music and the drums is so we can adjust the level of the drums to suit the bass player preferences.


If we’re recording vocals, guitars etc or programming drums/virtual instruments instead just set up the file accordingly.

Make sure that you note the BPM of the song and that all files are bounced with the same bit and sample rate. Do not use 32 bit files when moving in between platforms as some apps (Pro Tools, Logic) only allows you to import 16 and 24 bit files. The benefit of using 32bit files outside of an app is also highly questionable. When moving between Windows and OSX or vice versa stick to Wav/Broadcast Wav as file format.

Moving projects using OMF .

If your application supports OMF (Open media format) this can be used when moving projects. OMF comes as version 1 or 2 and although most applications understands both always double check that the app your moving to actually do.

The benefit of using OMF is that we don’t have to bounce all the tracks from the same starting point.


Here the the “stem” example file have been exported from Logic as an OMF file and then imported into Cubase. Notice that the individual audio regions have automatically been placed at the correct position on the time line.

Unfortunately OMF can only be used to export audio files it will not work on midi files and plug ins. To move midi files you need to save them separately as .mid files.

Bouncing or glueing?

Bouncing all the instrument and audio tracks in real time can understandably take more time then we are prepared to spend, although bouncing in real time is preferable to “offline” bouncing.

Instead we can opt to glue the audio regions straight in the arrange window. Just place a short snippet of audio/empty region in the beginning ( at bar of the song and then glue it together with the rest of the file. Rinse & repeat for each track.