Harrison Labs V2.0.2 manual Plug-ins, Summary of plug-in support in Mixbus

Page 20

12.0 Redirects: Plug-ins, Sends & Inserts

Plug-ins

Mixbus can load plug-ins in several formats. Mixbus can only use plug-ins that meet these criteria:

The plug-in must be a supported format on your platform (see below)

The plug-in must be installed in the standard folder for your platform.

The plug-in must be compiled for your platform. (Intel/PPC, OSX/Linux, 32-bit/64-bit)

• The plug-in must support either 1>1 I/O (for mono channels) or 2>2 I/O (for stereo channels)

%Note: Instrument plug-ins (plug-ins that take MIDI input and convert them it into audio) are currently not sup- ported.

A summary of plug-in support in Mixbus:

Apple AU plug-ins (supported on OSX only)

AU (Audio Unit) is the native plug-in format for OSX. AU plug-ins may be free or commercial in nature. AU plug-ins nearly always provide a customized GUI. AU plug-ins may require authorization from the developer to use in your system. AU plug-ins are only available for OSX.

LADSPA plug-ins (supported on OSX and Linux)

LADSPA is the "Linux Audio Developers Simple Plug-in Architecture". Simple to develop and usually free, there are nevertheless many LADSPA plug-ins that are quite good. LADSPA plug-ins do not support customized GUIs, they will simply be shown as sliders on a simple window. Being very portable, most LADSPAs are available for all plat- forms (OSX, Linux and Windows).

LV2 plug-ins (supported on Linux only)

The "next generation" LADSPA plug-ins, LV2 plug-ins will usually have a customized GUI. LV2 plug-ins may be free or commercial. LV2 plug-ins may require authorization from the developer to use in your system. LV2 is portable and plug-ins will likely become available for all platforms in the future. You must use LV2 plug-ins that are compiled for your platform, but there is a method of packaging LV2 plug-ins which bundles one or more platforms into a single plug-in object. This will make LV2 a very popular format in the future.

Steinberg VST plug-ins (no support currently)

VST (Virtual Studio Technology) plug-ins were developed by SteinbergTM and are the most common plug-in format on Windows. VST plug-ins can be developed for Windows, OSX, and Linux. Mixbus does NOT support VST plug-ins in any current release, but this is under development.

Digidesign TDM/RTAS plug-ins (no support currently)

RTAS and TDM plug-ins are proprietary formats for ProToolsTM. Mixbus does NOT support RTAS or TDM plug-ins. It is unlikely that Mixbus will ever support RTAS or TDM plug-ins.

Windows DirectX plug-ins (no support currently)

%Note: While we have taken care to follow the specifications for each plug-in format, plug-ins are developed by third-party vendors. This means that Harrison cannot take responsibility for plug-ins that don't work as

expected. Please use caution when trying a plug-in for the first time. Verify that all the functions work as expected before committing to using a particular plug-in in a session.

The DirectX plug-in API was developed by Microsoft and is the native plug-in format for Windows. Mixbus does NOT support DirectX plug-ins in any current release.

Section 12.0 - Redirects: Plug-ins, Sends & Inserts

20

Mixbus User Guide

Image 20
Contents Harrison Mixbus OS X & Linux Table of Contents Introduction Features & Specifications Mixer FeaturesEditor/DAW Features System RequirementsInstallation Installation OSXInstalling Jack Installing MixbusSoundcard I/O support Installation LinuxDownloading and Installing Mixbus Installation All Platforms Download and Install the License fileHow does audio I/O work in Mixbus, and what is JACK? Getting StartedGetting Started Creating Tracks for recordingNeed Help? Jack I/O About JackTrack I/O Selections 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 FadersRedirects Plug-ins, Sends & Inserts RedirectsPlug-in Control Sliders Redirect MenuPlug-ins Summary of plug-in support in MixbusLatency Compensation Plug-in ManagerSends Inputs InsertsOutputs Edit Window Overview Basic Editing ConceptsCreating Tracks Track ManagementTrack and Bus Management in the Editor Track and Bus Management in the MixerRecording, Loops and Punch Ranges Using TracksGroups Navigating in the Editor window Zooming and Panning Transport Menu and ToolbarMixbus Automation Region Gain and AutomationGraphical Automation Editing Automation tracks Editing Tools Editing Tools & ModesEdit Modes Smart Editing Edit MenuGain Tool TimeFX ToolJoin Playhead Mode Operation PriorityBehaviors with Join Playhead on Behaviors with Join Playhead offEdit Point Implicit Edit RangeEdit Point = Playhead Edit Point = MouseObject Region Editing Object Region EditingRegion Context Menu Region LayersRegion level Add Files Importing FilesImporting Files to Mixbus Insert MappingExporting Files Audio Consolidation and ExportExporting to a File Initiating an ExportFormat Synchronization Clocks & SynchronizationClocks Using the Click Using the GridTempo, Click, & Grid Defining a Songs Tempo and MeterGrid Modes Monitoring MonitoringMode Locations Window Rhythm Ferret Window Keybindings Preferences SyncPaths/Files Kbd/MouseMidi Ports AuditionMisc Preferences Mixbus Options Menu OptionsControl Surfaces Mackie Control Surfaces Generic MidiAutoConnect MonitoringMisc. Options Stop Transport at Session End 12dB gain reduce during ffwd/rewdPrimary/Secondary Clock Delta to Edit Cursor Always Copy Imported FilesGeneric Midi Control Surfaces Logic Control Protocol Keyboard & Mouse Shortcuts Linux Transport and Recording ControlSession and File Handling Standard Mixbus Layout Cubasish Layout ProToolish LayoutChanging What’s Visible Window Visibility Editing With Edit PointMoving The Playhead Aligning With The Edit PointEdit Point Playback Edit Point Active Mark? Edit Range Region OperationsEdit Range Selecting Markers and LocationsDefining Loop, Punch Range, and Tempo Changes Mouse ModesMouse Object Mode Mouse Zoom ModeMouse Ops on Solo/Mute/Rec-enable 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 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? What audio file formats are supported? How do I use Midi transport controls MTC/MMC with Mixbus?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 Appendix B Release Notes MixbusAppendix B Release Notes Known Issues All platforms Mixbus 1.5.1Mixbus 1.4.1 Mixbus 1.4Mixbus 1.3 Features Mixbus v1.2Appendix B Release Notes Mixbus Appendix B Release Notes Contact Information Http//mixbus.harrisonconsoles.com