In part II, I\u2019d like to go through a case study from when I recreated the ‘Star Wars’ theme of Rey by composers John Williams. Included is the blog post is the Logic Pro X project file itself, giving you a place to experiment and see how I used automation, reverb, and the other steps mentioned in part 1. Download the Logic Pro session file here<\/a>. If you happen to use Cubase, Pro Tools, or something other than Logic, KEEP READING! These tips will apply to most all audio workstations.<\/span><\/p>\n As you can see in this above example, I have multiple sections of instruments, all with automation in slightly different places. You usually wouldn\u2019t want the automation to be exactly the same as each other unless it\u2019s a section such as the example below (instruments in the same section playing the same melody) And even then, giving each individual instrument slightly different automation will help realism. Generally, each instrument will have its own specific automation based on what notes it\u2019s playing and the type of expression you\u2019re going for.<\/span><\/p>\n Pro Tip:\u00a0<\/b><\/span>A popular technique is to automate the actual \u201cexpression\u201d versus the \u201cvolume\u201d. So what I\u2019ve always done is actually just automate the volume to great results, but if you want to take some extra time and try it out for yourself, go into the detailed settings of your instrument and find where you can automate \u201cMIDI expression\u201d. Modifying\u00a0this won\u2019t turn down the volume, but rather work within the parameters of expression, which you can control from your MIDI controller. You can also program this by hand. Both ways work, just give it a go and see which method you prefer!<\/span><\/p>\n You\u2019ll also see many professional\u00a0composers automate with hundreds of dots, so in other words, a much more detailed curve formed between the line and the dots. I generally do a\u00a0 2:1 ratio of dots to lines, but a lot of producers and composers will have something like a 25:1 ratio of dots to lines, which means LOTS of time spent on automation. I\u2019ve discovered that other parts of the production process are more important to giving ultra detailed attention than others, and I usually automate more if I have less instruments, but when I\u2019m hovering 100 tracks, a more simple automation technique will suffice.<\/span><\/p>\n I also automate in SOLO for the most part, but always check it right afterwards with SOLO turned off. Many times, solo-ing too much without checking the big picture will lead to an off-balance mix, so make sure to balance when you use SOLO during mixing.<\/span><\/p>\n Another element to consider is panning and\/or binaural spacing. In this case study, I used a basic panning, which means if I stereo pan to the right by +15 dB, I\u2019m really turning down the left side by 15 dB. There are however, ways to place instruments in a surround sound space, which is when you pan using the \u201cbinaural\u201d setting. The basic way to pan is the former technique, but the latter technique will give you a much more detailed and realistic placement of the instruments within the space. So look at an orchestra chart and place them where they belong, like a fun kids game!<\/span><\/p>\n Creating orchestral music can be tough, especially when you add the challenge of trying to recreate that realistic sound in a DAW (digital audio workstation). Using the three steps addressed in <\/span>part I<\/a> of this series, along with some of the advanced techniques of this case study in part II will provide you with some useful nuggets for composing orchestral\u00a0music in the box.\u00a0<\/span><\/p>\n![\"Logic](\"https:\/\/compozly.com\/blog\/wp-content\/uploads\/2019\/09\/unnamed-1024x780.png\")
<\/p>\n![\"Logic](\"https:\/\/compozly.com\/blog\/wp-content\/uploads\/2019\/09\/unnamed-1-1024x495.png\")
<\/p>\nFinal Thoughts<\/span><\/strong><\/h2>\n