Harrison Labs V2.0.2 manual Jack I/O, About Jack, Track I/O Selections, Track I/O Editor

Page 10

5.0 JACK I/O

About JACK

Mixbus uses an internal audio routing system called "JACK" to make audio connections between Mixbus, your sound I/O, other programs, and even between parts of Mixbus. In many cases, you can use Mixbus without ever being aware of JACK connections. By default, Mixbus makes these routes:

The master bus is connected to the first two physical output ports.

Track/Bus inputs are assigned sequentially from the physical inputs whenever a new track/bus is created.

The Auditioner and the Click are connected to the first two physical output ports.

However it is possible to change any or all of these routes using the tools provided in Mixbus, or a third-party routing app such as JackPilot (OS X), Patchage (Linux), or qjackctrl (Linux). Other things that can be routed via JACK include Track Sends, Track Inserts, and Mixbus sidechain inputs.

%Note: JACK connections use a floating-point 32-bit format, which means that headroom is essentially unlimit- ed. You don't have to worry about "clipping" the sound when routing from one application to another. You may

route a single JACK output port to several inputs, and an input port can be routed from several different outputs (the summing of these signals is done automatically).

Track I/O Selections

Track inputs can be assigned directly from the mixer strip, by clicking on the "input" button.

The menu provides these selections:

Edit: launch the Track Input dialog for this track (see below)

Disconnect: remove all JACK connections from this track's input

"in 1" ... "in N": These are shortcuts to the physical soundcard inputs on your system

Similarly, the Master Bus has an "output" button which can be used to select the ports that the master bus output will feed.

%Note: The "shortcuts" won't display a connection to the inputs until you choose it this way from the menu. So don't be surprised if there's

nothing checked in the menu but you are still connected to a JACK port when you view JACK connections in another way.

Track I/O Editor

The track input editor window allows you to connect any

Jack output port to the track/bus input:

Add/Remove: Add/Remove an additional JACK port to this track. (this is normally disabled in Mixbus, where tracks are either mono or stereo, but it is kept for com- patibility with Ardour.

Disconnect All: Removes all Jack connections to this track's inputs

in: displays the Jack ports that are connected to this track's input(s). Click on a port name to disconnect it.

Available connections: There are tabs for your sound

￿Tip: Each track/bus also provides a direct JACK output port. This can

be useful if you want to use Mixbus as a multitrack record/playback machine. Every track output can be directly patched to a physical soundcard input or output. To access this feature, click on the track's "name" button and then choose "Direct out". Mixbuses also have this feature which is a good way to cre- ate a cue feed to the headphones of the artist.

Section 5.0 - Jack I/O

10

Mixbus User Guide

Image 10
Contents Harrison Mixbus OS X & Linux Table of Contents Introduction Editor/DAW Features Features & SpecificationsMixer Features System RequirementsInstalling Jack InstallationInstallation OSX Installing MixbusDownloading and Installing Mixbus Installation LinuxSoundcard I/O support Installation All Platforms Download and Install the License fileGetting Started How does audio I/O work in Mixbus, and what is JACK?Getting Started Creating Tracks for recordingNeed Help? Track I/O Selections Jack I/OAbout Jack Track I/O EditorTrack/Bus Inspector Jack MenuOverview Mixbus Editor and Mixer WindowsInput Strips Mix Buses Master Bus Mixer WindowSignal Flow Input Channels Track Name Click to rename and other utility functionsMix Bus Channels Master Channel Right-click here to add or remove redirectsMixer Conventions & Tips Mixbus Knobs and FadersPlug-in Control Sliders Redirects Plug-ins, Sends & InsertsRedirects Redirect MenuPlug-ins Summary of plug-in support in MixbusLatency Compensation Plug-in ManagerSends Outputs InsertsInputs Creating Tracks Edit Window OverviewBasic Editing Concepts Track ManagementTrack and Bus Management in the Editor Track and Bus Management in the MixerGroups Using TracksRecording, Loops and Punch Ranges Navigating in the Editor window Zooming and Panning Transport Menu and ToolbarMixbus Automation Region Gain and AutomationGraphical Automation Editing Automation tracks Edit Modes Editing Tools & ModesEditing Tools Gain Tool Smart EditingEdit Menu TimeFX ToolBehaviors with Join Playhead on Join Playhead ModeOperation Priority Behaviors with Join Playhead offEdit Point = Playhead Edit PointImplicit Edit Range Edit Point = MouseObject Region Editing Object Region EditingRegion Context Menu Region LayersRegion level Importing Files to Mixbus Importing FilesAdd Files Insert MappingExporting to a File Exporting FilesAudio Consolidation and Export Initiating an ExportFormat Clocks Clocks & SynchronizationSynchronization Tempo, Click, & Grid Using the ClickUsing the Grid Defining a Songs Tempo and MeterGrid Modes Monitoring MonitoringMode Locations Window Rhythm Ferret Window Keybindings Paths/Files PreferencesSync Kbd/MouseMisc AuditionMidi Ports Preferences Mixbus Options Menu OptionsAutoConnect Control Surfaces MackieControl Surfaces Generic Midi MonitoringMisc. Options Primary/Secondary Clock Delta to Edit Cursor Stop Transport at Session End12dB gain reduce during ffwd/rewd Always Copy Imported FilesGeneric Midi Control Surfaces Logic Control Protocol Session and File Handling Keyboard & Mouse Shortcuts LinuxTransport and Recording Control Standard Mixbus Layout Cubasish Layout ProToolish LayoutChanging What’s Visible Window Visibility Editing With Edit PointEdit Point Playback Aligning With The Edit PointMoving The Playhead Edit Range Region OperationsEdit Point Active Mark? Edit Range Selecting Markers and LocationsDefining Loop, Punch Range, and Tempo Changes Mouse ModesMouse Ops on Solo/Mute/Rec-enable Mouse Object ModeMouse Zoom Mode Mixbus Function Mouse CommandMouse Ops on Solo Buttons Only Mouse Ops on Faders & Plug-in ControlsKeyboard & Mouse Shortcuts Mac Standard Mixbus Layout Cubasish Layout ProToolsish LayoutKeyboard 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 What is the difference between Snapshot and Save As? Why is there no Save As?How do I route audio from another application into Mixbus? What audio file formats are supported? How do I use Midi transport controls MTC/MMC with Mixbus?For generic Midi CC What Hardware controllers are supported?Debugging Midi CC All Platforms Mixbus just bounces in the dock when I try to launch it OSXLinux Appendix B Release Notes MixbusAppendix B Release Notes Mixbus 1.4.1 Known Issues All platformsMixbus 1.5.1 Mixbus 1.4Mixbus 1.3 Features Mixbus v1.2Appendix B Release Notes Mixbus Appendix B Release Notes Contact Information Http//mixbus.harrisonconsoles.com