Jeremy Scott
Omaha, NE - Recording Connection Student
This week it was lesson XII, synchronization Console Automation. Of course, the understanding of automation is a necessity if you want to make your job easier as an audio engineer. We first went over SMPTE time code (which is what my mentor uses): My mentor explained bits, sync data, time code frames, LTC and VITC time code, jam sync, synchronization using SMPTE time code (he showed me his master, or synchronizer, and explained all of its duties), SMPTE offset times, loops, and distribution of SMPTE signals. My mentor explained SMPTE, he showed me how everything is connected, and he explained to me his whole synchronized system, with emphasis on his master device. Secondly, we covered MIDI-basd synchronization; Tim doesn't have any MIDI devices, he used to have a MIDI-based system, but he believes SMPTE is a more reliable way. We went through MIDI real-time messages, MIDI time code, MIDI time code messages (quarter-frame, full, and MIDI cueing messages), and then he quickly explained how it's possible to convert SMPTE time code into MIDI time code and vice versa. My mentor finished explaining synchronization by talking about master/slave relationship, modular digital multitrack machines, and DAWs.
For the next part of class we went over console automation. He really stressed how much console automation can aid a mix. My mentor first explained the functions of automation, switching and dynamics. Next, he went over each system of console automation (vca, dca, moving fader, midi-based) and explained the difference between each; by the way, he has a moving fader system. My mentor then opened up a song and show me automation in action. He soloed the vocals and explained, while applying, the three operating modes of console automation. As usual he graded my assignment. This was a good lesson to acquaint me with the use of digital application of audio.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment