![]() ![]() If you’re getting the error message “Computer too slow to play song!” odds are that it doesn’t mean anything good, so let’s look at an easy fix for this. Suggestion #8 - Remove the CPU Usage Limiter However, your routings will not be saved if you save an instrument patch (as it’s an external device).Īlso, you’ll no longer have control over the automation as you would in the sequencer, so if you can, avoid using this one unless you have to. This way, instead of recording an automation lane in the sequencer, you can just use a device to do it. Use the Curve CV OUT from the Matrix Pattern Sequencer to “automate” the Pan CV IN of a mixer. This is somewhat difficult to explain without giving an entire lecture on CV, but I’ll give you an example. So you’re really stressed over CPU usage? You can use CV routing instead of automation on devices. Suggestion #7 - Use CV instead of Automation Of course, if you’re looking to improve sound quality rather than performance, set a higher sample rate and turn on high-end sound features (covered later). For example, on a Thor synthesizer, get rid of all the LFOs and Filters that you aren’t using. Lastly, deactivate filters and effects on devices. However, this tends to kill quality faster than any other performance booster. Now, there is an obvious thing you can do, which is decrease the sample rate in Preferences. For any instruments, you can play them in mono (obviously you will lose quality again here). Next up, for any devices that play in polyphony, lower the number of voices. Next, if you’re playing back samples at higher than recorded frequencies, consider using a program such as Recycle to pitch shift it. Get rid of all the stuff you’re not using (which you probably should have already done already). Warning: this will affect the quality of your sounds. Suggestion #6 - Optimize Your Instruments and Samples If you’re using the right driver, most people report that this actually decreases performance. This is contrary to Reason 4’s manual, which advises raising the buffer setting to reduce computer overhead. If you are using the best sound driver you have available, it is advised not to use the Buffer Size slider, as this will cause issues. Many users have experienced it, where you hit a key, and what seems like ages later, the sound is actually triggered. If you don’t have that, try using the DirectX driver, or whichever driver has the lowest latency, which is shown right below the “Buffer Size” slider.ĭoing this will also solve a very common problem in Reason: slow MIDI playback response. If you can, use the ASIO (Audio Stream Input/Output) driver, as it usually has the lowest latency and best interface with the sound card. What you want to do is use the driver with the lowest possible latency. ![]() If you’re having issues with your sound in Reason, or if you just think things should be sounding a little bit better than they are, go to Preferences > Audio. However, as smart as programs try to be, they can’t quite measure up to human intelligence. When you first install Reason, it tends to do a lot of work and configuration for you, by detecting your various audio devices and MIDI controllers. Suggestion #1 - Set Up Your Sound Card Properly We’ll also solve a few commonly encountered problems, so let’s get to it. For example, if the suggestion is to turn off High Quality Interpolation, turn High Quality Interpolation on. ![]() If you’re looking to improve the quality of your sound, steer clear of suggestions that include a warning about effects on quality. Keep in mind that, while most of these suggestions are aimed at decreasing the CPU power that Reason requires, some of them result in a lower quality sound (however noticeable it may be). So let’s take a look at ten simple things you can do to increase the performance of Reason, so that you can use Reason and your favorite DAW at the same time. If you’re like me and you don’t work with just one program at a time, you need them to be able to interact with each other without negative performance side effects. This brought the issue of performance back to the forefront for many users, particularly those who wished to run Reason alongside an intensive program such as Pro Tools or Logic. People then began discovering the power of ReWire, using Reason as an instrument or effect in other DAWs. As technology evolved, however, most users began to acquire computers that were more than capable of running Reason without issues. In this article, we’re going to look at ten things you can do to help maximize the performance of Reason, fix various annoying issues, and avoid CPU strain during heaving automation and interaction with other DAWs.īack when Reason was first introduced to the digital audio community, many users had difficulties running the program because of the performance requirements. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |