macmuse Posted May 31, 2015 Share Posted May 31, 2015 Hi, Most of my work originates as MIDI, so I've had the habit of keeping two separate projects: MIDI for the writing stage, and a new project with rendered audio tracks for mixing. Mostly this old habit was carried over from a time back when computers were slow, and also to have the audio tracks in case a plugin became obsolete in the future. One downside to this is that when I wanted to change something in the mix, I'd do so in the audio version instead of the original MIDI, which then made for sloppy file keeping. However now I'm rethinking this strategy, and wondering if maybe the results are better, etc. to stay in MIDI for the mix? How many of you mix with the MIDI tracks or do you still render the tracks first? If you render, are you bouncing in place or exporting the tracks to audio in Logic? Thanks. Link to comment Share on other sites More sharing options...
Eriksimon Posted May 31, 2015 Share Posted May 31, 2015 You just keep it MIDI untill you notice your Mac starts to "buckle", then you can Freeze (=render to (uneditable) audio) tracks with the heaviest CPU-using plugins. Freezing renders a track to audio, automatically bypassing the software instrument, thus freeing up CPU taken by the instrument. The frozen file has to be read from disk though, so be sure that your disk can handle that. The advantage over "oldskool" bouncing a track to audio is that freezing doesn't need the creation of an extra track. Also, unfreezing and refreezing (to re-edit some MIDI) is fairly easy. The "bouncing-to-keep-an-effect-that-may-not-be-compatible-or available-in-the-future" action still makes sense though. http://help.apple.com/logicpro/mac/10.1/#/lgcpf1cbfd51 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.