IR’s are a must have if you’re using straight up amp sims on your guitar tracks. You load up your IR file into an impulse response loader, which is added to a track that contains a DI guitar and an amp sim of some sort, and the IR mimics the sound of the cab/microphone/room that was recorded. The final recorded file is just a wav or an aif with wav being much more common. Essentially an IR is a recording of a sound (like a guitar) played though a speaker (cabinet) in a environment (ie: studio live room) through a specific microphone. When I first really got started recording instruments, I began hearing about something called IR’s and had to dig to find out what they were. *Updated to include Linux Studio Plugins. I’ve had just as much weird shit happen on Windows and Mac. Whichever happens, at least I can still work on my little projects relatively unhindered.ġ: No, this is NOT because I’m using Linux. So instead of stamping my feet and whinging about it, I’ll just make do 1.Īt some point a fix will appear. However nothing ever works 100% of the time, especially software. So if I do need to change something on, say, G-Heavy02 (tweak a sound, make a cut, etc), I have to freeze G-Clean01 and unfreeze G-Heavy 02. In its current state, if I unfreeze one of those tracks, it will bring back the ToneLib plugin and Reaper will crash. Those locked tracks are, for the most part, completed and I can’t do anything with them in this state past volume, pan, and playback unless I unfreeze them. The other tracks have greyed out media, lock icons, and say “freeze” on them. You can see that the FX toggle on the G-Clean01 track is enabled I have ToneLib loaded on that track and am actively working on the sound. It’s not difficult and it doesn’t add any frustratingly unnecessary time to what I’m doing. In the meantime I can use it on a single track without causing issues so I’ve been freezing tracks as a workaround. I’ve been trying to figure out what’s going on – the best I got was this long thread on the Reaper forums that didn’t amount to much, and that’s it (for now). If I dare add GFX to a second track, Reaper crashes. While I love (love, love!!) ToneLib GFX, for some damn reason Reaper only seems to want to allow it on a single track. That being said, this can also come in handy for working around certain sticky situations. So freezing (or printing or whatever you want to call it) helps out. While there is not a ton of effects being used, each of those guitar tracks is being run through ToneLib GFX which I know from Mixbus can start using a good amount of CPU. Here is a screenshot of the Reaper Performance Meter playing back 18 tracks and 2 groups/buses of a new tune I’m finishing up: In fact, freeze/print any track that has a set and forget plugin.” One of those suggestions was to “Freeze/print tracks that are plugin heavy. A few weeks ago I posted a small bit on Low End Tricks.

Mixbus 32c crashes