#Reaper automute disable for free
On one track, I'm using SFZ as the VSTi, and on another, I'm using the new and improved SFZ+ (downloaded for free from CakeWalk). Then, I got a brainwave: By using two different soft synths, I am able to bring the buffers all the way down to negligible latency, and I cannot get playback of even the most complex SoundFonts to fail.
#Reaper automute disable full
I pushed the buffers up full and made sure no other CPU-significant software was stealing power, but I couldn't get multiple MIDI tracks to play reliably. Although I played the offending tracks at least fifteen times before making claims of finding a solution, this morning, the same machine playing the same tracks got stuck every second or third time. So, if you're not already using ASIO4All, you might want to start there.
#Reaper automute disable driver
Latency Compensation: 1024 samples (in & out)īTW, using the Focusrite USB 2.0 ASIO Driver supplied with the sound card, I can't get multiple MIDI tracks to play reliably on the laptop AT ALL. Pentium dual-core laptop with Realtek onboard Latency Compensation: 512 samples (in & out) Pentium dual-core laptop with Scarlett 2i2 Latency Compensation: 0 samples (in & out) In case it helps, here are my ASIO4All settings for each configuration. For now, I'm manually programming simple drum tracks. Of course, such a large buffer messes with latency, but I'll worry about that when I connect my MIDI keyboard. Using the onboard Realtek sound card (just as a test), this needs to be pushed all the way up to 2048 samples for reliable playback. On the laptop, I need to increase the ASIO buffer size from the default 512 samples to 1536 samples to make the glitches go away. I'm using a Focusrite Scarlett 2i2 USB sound card with ASIO4All driver v2.11b1 on both machines. The glitches and resulting muted Reaper channels only showed up when I tried to make everything work on an older laptop for portability. I wasn't suffering the problem at all on my Core-i7 with bucket-loads of RAM etc. The user guide doesn't mention automute at all nor does the actions list.Īnd just to clarify, I do not want to disable automute.I'm not sure what hardware you're using, but here's my situation and how I fixed it: So my first question is does this happen to anyone else?īut my more important question is, how do I unmute an automuted channel without saving and reloading the project? Clicking the mute button does not unmute it. It might also be a plugin, and there is a plugin on the guitar bus that's not on any other channel. But I'm not 100% sure on that since it's only happened a few times. So the act of starting back up and reconnecting the interface, if one of the guitar channels is armed for recording might be causing a "pop" and triggering automute. The levels do not clip on that channel.ĭuring my time away, my computer has gone to sleep, and I have to wake it up. I can't seem to do anything to unmute it, except save and reload the project - then it works fine, and the channel does not automute when I play the project. I have an occasional issue where if I leave a project open, but not working on it for a few hours (going about my day), I'll come back to it and my guitar master track/bus has been automuted.
0 kommentar(er)
