Harrison Labs V2.0.2 manual Region Context Menu, Region Layers

Page 35

16.0 Object Region Editing

Region Layers

￿

Tip: By default, regions are

Regions may be stacked on the same location in the timeline. This is called

 

opaque. Opaque regions are visi-

"layering". Normally only the top region is heard; it covers the audio regions

bly and audibly opaque, meaning you

below it. However there are cases where the region below can be heard.

can't see of hear the region underneath

One example is the top region's fade-in or fade-out. Region fades operate

(except during the crossfade area). The

as crossfades. If a region is stacked on top of another region, then the

right-click menu allows you to disable the

opaque flag, and make the region(s)

region underneath will audibly "fade out", while the topmost region "fades in"

"transparent". Transparent regions are

across the length of the crossfade. The second way to hear a region below

visibly transparent, allowing you to see

the topmost region is if the topmost region is not opaque. (the Opaque flag

any waveforms beneath the region.

can be turned off in the Region menu and/or the right-click Region context

They are also audibly transparent,

menu).

meaning that their sound is mixed with

 

the regions underneath, instead of

Region layering can be changed on-the-fly by the user. Try right-clicking on

replacing it. This is an excellent way to

a region to change its layering. Layering is one way to manage multiple

work when you are assembling sound

"takes" of a performance. Each time a track is recorded, a new region is

effects that may overlap but do not need

to occlude each other or create cross-

written onto the topmost layer. But the layers underneath still exist.

fades.

 

There are global options that define the default behavior of crossfades and

 

 

 

 

 

 

layers. While the defaults are suitable for most users, understanding these options can be very important for

advanced users. (see Crossfade and Layer Modes in Section 26.0 Mixbus Options)

 

Region Context Menu

The region context menu (launched by right-clicking a region) has many of the same operations as the main Region menu. The Region context menu always operates on the single region that was right-clicked on, while the Region menu operates on all selected tracks. Many items in the Region Menu are self-explanitory. For details about a spe- cific function, click Help->Reference.

Section 16.0 - Object Region Editing

35

Mixbus User Guide

Image 35
Contents Harrison Mixbus OS X & Linux Table of Contents Introduction System Requirements Features & SpecificationsMixer Features Editor/DAW FeaturesInstalling Mixbus InstallationInstallation OSX Installing JackSoundcard I/O support Installation LinuxDownloading and Installing Mixbus Download and Install the License file Installation All PlatformsCreating Tracks for recording How does audio I/O work in Mixbus, and what is JACK?Getting Started Getting StartedNeed Help? Track I/O Editor Jack I/OAbout Jack Track I/O SelectionsJack Menu Track/Bus InspectorMixbus Editor and Mixer Windows OverviewMixer Window Input Strips Mix Buses Master BusSignal Flow Track Name Click to rename and other utility functions Input ChannelsMix Bus Channels Right-click here to add or remove redirects Master ChannelMixbus Knobs and Faders Mixer Conventions & TipsRedirect Menu Redirects Plug-ins, Sends & InsertsRedirects Plug-in Control SlidersSummary of plug-in support in Mixbus Plug-insPlug-in Manager Latency CompensationSends Inputs InsertsOutputs Track Management Edit Window OverviewBasic Editing Concepts Creating TracksTrack and Bus Management in the Mixer Track and Bus Management in the EditorRecording, Loops and Punch Ranges Using TracksGroups Transport Menu and Toolbar Navigating in the Editor window Zooming and PanningRegion Gain and Automation Mixbus AutomationGraphical Automation Editing Automation tracks Editing Tools Editing Tools & ModesEdit Modes TimeFX Tool Smart EditingEdit Menu Gain ToolBehaviors with Join Playhead off Join Playhead ModeOperation Priority Behaviors with Join Playhead onEdit Point = Mouse Edit PointImplicit Edit Range Edit Point = PlayheadObject Region Editing Object Region EditingRegion Layers Region Context MenuRegion level Add Files Importing FilesImporting Files to Mixbus Mapping InsertInitiating an Export Exporting FilesAudio Consolidation and Export Exporting to a FileFormat Synchronization Clocks & SynchronizationClocks Defining a Songs Tempo and Meter Using the ClickUsing the Grid Tempo, Click, & GridGrid Modes Monitoring MonitoringMode Locations Window Rhythm Ferret Window Keybindings Kbd/Mouse PreferencesSync Paths/FilesMidi Ports AuditionMisc Preferences Menu Options Mixbus OptionsMonitoring Control Surfaces MackieControl Surfaces Generic Midi AutoConnectMisc. Options Always Copy Imported Files Stop Transport at Session End12dB gain reduce during ffwd/rewd Primary/Secondary Clock Delta to Edit CursorGeneric Midi Control Surfaces Logic Control Protocol Standard Mixbus Layout Cubasish Layout ProToolish Layout Keyboard & Mouse Shortcuts LinuxTransport and Recording Control Session and File HandlingChanging What’s Visible Editing With Edit Point Window VisibilityMoving The Playhead Aligning With The Edit PointEdit Point Playback Edit Point Active Mark? Edit Range Region OperationsEdit Range Markers and Locations SelectingMouse Modes Defining Loop, Punch Range, and Tempo ChangesMixbus Function Mouse Command Mouse Object ModeMouse Zoom Mode Mouse Ops on Solo/Mute/Rec-enableMouse Ops on Faders & Plug-in Controls Mouse Ops on Solo Buttons OnlyStandard Mixbus Layout Cubasish Layout ProToolsish Layout Keyboard & Mouse Shortcuts MacKeyboard Shortcuts Macintosh Window Visibility Aligning With The Edit Point Command+e Copy Command+c Cut Command+x Delete Delete alternate Defining Loop, Punch Range, and Tempo Changes Mouse Object Mode Mouse Ops on Solo Buttons Only Appendix a FAQ How do I route audio from another application into Mixbus? Why is there no Save As?What is the difference between Snapshot and Save As? How do I use Midi transport controls MTC/MMC with Mixbus? What audio file formats are supported?Debugging Midi CC What Hardware controllers are supported?For generic Midi CC Linux Mixbus just bounces in the dock when I try to launch it OSXAll Platforms Mixbus Appendix B Release NotesAppendix B Release Notes Mixbus 1.4 Known Issues All platformsMixbus 1.5.1 Mixbus 1.4.1Mixbus 1.3 Mixbus v1.2 FeaturesAppendix B Release Notes Mixbus Appendix B Release Notes Http//mixbus.harrisonconsoles.com Contact Information