![]() ![]() This does not impair functionality, but it can lead to needless confusion while editing actions if you don't keep it in mind.īy default, the Action List can be brought up with the '?' key, both in the Main window and in the MIDI Editor window. Therefore, an action that is mapped in the Main action list will not work in the MIDI editor action list, and vice versa. The main REAPER window and the MIDI Editor window have separate action lists as REAPER treats them as separate areas of focus. ![]() It's primarily through use of this feature that we'll make the MIDI Editor do what we want. Using this feature, just about every REAPER command can be re-mapped to keyboard/mouse/MIDI controller shortcuts, assigned to custom toolbars, chained together in macros (Custom Actions), and more. REAPER's core usage revolves around a central feature: the Actions List.Second - a few basic concepts need to be understood: Many of the tips and tricks I'll be going into further into this guide will not be possible without them. Regardless of how much you use the MIDI Editor, they dramatically extend REAPER's capabilities and functionality. There is nothing to lose and everything to be gained by installing these two add-ons. For the sake of brevity, I'll assume very basic knowledge of how the software works.įirst - If you haven't done so already - install the following: Please note: this guide is written for those who are relatively new to REAPER. However, if you're in a hurry or want to get a basic overview before delving into the details, I've prepared this "quick start" guide to help you on your way. The best way to learn how to do this - as with anything in software as flexible and comprehensive as REAPER - is to read the manual. However, with a bit of customization, the MIDI Editor can easily be turned into a very powerful and flexible tool for large, MIDI-centric projects. This is completely understandable, as REAPER's MIDI Editor is - upon initial installation - quite a mess. I had hoped it was a Windows issue, but a recent trial with W7 confirms that it is a Cubase issue.At first glance, REAPER's MIDI Editing capabilities may seem cumbersome or bare-bones compared to other DAWs. It is the same issue with Windows 7, 8 and 8.1. Before then, it was C5 32bit which I used it on. When I moved to Cubase 64bit, it was with my move to C6.5 and I did not need the Liquid Mix that much. I can’t pinpoint when I started getting the issue. What could be going on in Cubase 64bit that would make the unit fail? Is there anything under the hood which I can try and change in the settings? I have found that Reaper 64bit exports mixdowns with the Liquid Mix perfectly. I had thought that because it was a relatively old piece of tech that it was just a reality of technology but since the general silly issues brought in by Cubase 8, I have looked into Reaper more and more. Any tracks with the Liquid Mix on it just seem jumbled up, random snare hits out of time. It works perfectly for everything else, but when I have to mix down, I need to switch to the 32bit version of Cubase, and it works fine there. For the past few years, I have noticed that it does not work during the exporting of mixdowns with the 64bit version of Cubase 6.5 and Cubase 8. I have been a long time user of the Focusrite Liquid Mix. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |