It's just another day at the office for Logic. So whenever you add or delete audio channels, instruments, or a MIDI processor such as a chord memorizer, you're changing the project's environment. See, the environment is where all of your channel strips, auxes, instruments, arpeggiators, and various other virtual studio devices actually live. In fact, the state of the environment in any project – especially at the beginning stages of a production – is constantly in flux and that's perfectly normal. Rather, each project has its own environment, and altering Project A's environment will have no effect on Project B. Well, that's not the case!Īnd it's not Logic that has an environment, per se. But this implies that the environment is somehow global to Logic's overall operation, and tinkering with it could somehow break Logic in general. When discussing what the environment is and the functions it serves, people usually refer to it quite innocently as “Logic's environment”. Then, in subsequent articles, we'll examine the function of various specialized environment devices, and delve into some advanced environmental exploits that have very practical musical uses. In this, my first article in a series on this fascinating aspect of Logic, we'll start by learning some basic concepts. However, if you're reading this article, it's probably because you want to learn more about the environment and discover if there are ways it can facilitate and enhance your creativity. And much of what goes on in there is transparent to the user, as it should be. And more than a few people have paid tribute to the environment by visiting internet forums and expressing their heart's desire that in future versions of Logic, we will no longer find an environment.īut there's no requirement for any Logic user to ever pay the environment a visit.
Feeding the fear are long-standing misconceptions about what the environment is and how (supposedly) complicated it is. Many Logic users fear to tread in the environment.
0 kommentar(er)
