|
|
|
|
Tech Tips: Project5 Basics, Part 1 of 2
PART 1: BASICS Signal flow is the most important aspect to get. It ties together MIDI filtering, audio mixing, effects, and the views. Because Project5 is strictly a soft synth environment, all sound generation originates within the application. MIDI goes in, audio comes out. The audio path originates with a DXi or VSTi, which is controlled by a rather sophisticated MIDI input filtering scheme. After that, the sound is channeled through a local effects chain and gain stage (mix level), possibly sent to an effects bus, and terminates at the master gain stage where the bits are then pumped to your hardware mixer. Signal flow is managed in the Track Pane and Syn.Ops (for Synth Operations). Syn.Ops provides an exploded view of the currently selected track, most importantly displaying the synth's property page and the patch point for MIDI and audio effects.
Synths are initially patched into the track pane, which abuts the track view (aka Tracker). The track pane also serves as the mixing console and provides several unique features designed to accommodate an unfettered workflow: A one-to-one correspondence exists between soft synth and track, because
it is assumed that one track will usually be used for a single voice.
Arranging becomes a lighter task since all patterns in a given track will
go directly to that synth. However, accommodations are made for those
wishing to use multi-timbral instruments, such as being able to assign
track patterns to any MIDI channel (more on that later). You can specify the MIDI port and channel through which and instrument receives event notifications. In this there are two powerful implications:
Audio Output Selectorhe output selector appears on the track strip when you insert an instrument that has more than one output. As you scroll to select an output, the mix controls update to show the settings for the currently selected output. In the spirit of keeping a clean workspace, only one track strip is consumed for all the instrument's possible outputs. This has implications in Syn.Ops too, as the patch bay for effects updates to show you what's patched in at a specified output.
In contrast to SONAR or other audio/MIDI sequencers, the track view is comprised of patterns, not clips. Patterns are the atoms of your song arrangement. In P5, even audio lives inside a pattern. All patterns roll out and repeat at their specified loop points, like Groove Clips in SONAR. This makes song development a breeze of course. Inside the Track View, patterns appear as three different types:
Patterns are edited in P-SEQ (the Pattern Sequencer) and typically consist of MIDI events and automation for your synths and effects. Sometimes you may want to have a pattern that is nothing but filter sweep automation, and place it strategically throughout the arrangement. When you make changes to a specific pattern, other instances of that pattern are also affected, a terrific time saver. In cases where you'd like a pattern to break off its family ties, you can simply "dupe" it from P-SEQ.There are, however, a couple attributes which will not affect other instances of the same pattern. These "instance attributes" include MIDI channel and Pitch Transpose. Transpose works on audio and MIDI clips.
|
||||||
|
|
|||
|
Copyright © 2008 by Cakewalk, Inc. All rights
reserved. View complete copyright notice. |
|||