documentation

Why Ben's Toolbox is different

Ben's Toolbox is not a single shortcut package, but a coherent Logic Pro system: Mac app, own MIDI device, Stream Deck plugin, iPad Remote, UAD Mixer Remote and iPhone Motion access the same database. This allows complex studio workflows to be triggered via buttons, gestures or prepared presets without having to navigate through Logic or UAD console menus each time.

How to start

Language of Logic and Ben's Toolbox

Ben's Toolbox reads many Logic Pro menus, windows, tables, and panels via the visible names in Logic. Therefore, Ben's Toolbox must be set to the same language in which Logic Pro is running. For example, if Logic runs in German, Ben's Toolbox must also be in German; If Logic is in English, Ben's Toolbox must be in English.

Available languages: German, English, French, Spanish, Japanese, Korean and Simplified Chinese.

Setup in Logic

Ben's Toolbox uses its own virtual MIDI device so that actions from the Mac app, Stream Deck, iPad and shortcuts arrive reliably in Logic Pro. When it starts, the Mac app checks whether this device already exists in Logic. If it is missing, it is automatically added to the bottom of the Logic Control Surface list in the background.

Before each automatic change, Ben's Toolbox creates a backup of the Logic Control Surface file. If MIDI devices respond unexpectedly after installation, open in Ben's Toolbox Setup > MIDI Device Manager and use Restore MIDI Device Fileto restore the previous file.

The MIDI Device Manager also contains Re-Install Device for a new automatic setup. The Legacy Installer still uses UI scripting in Logic and is only intended as a fallback. Manual installation also remains available if automatic methods do not work reliably on a system.

After the first launch, three things are particularly important: Ben's Toolbox requires the macOS accessibility features, Logic Pro must be open, and the required data such as plugins, outputs, buses and articulation sets should be scanned in the Mac app. After that, Stream Deck, iPad and Shortcuts can trigger the same prepared actions.

Basic concepts

Action, parameter, trigger

Almost every tool consists of an action and optional parameters. Example: set_output is the action, the desired output is the parameter. The trigger can be a stream deck button, an iPad button, a shortcut, a URL scheme, or a button in the Mac app.

Remote surfaces are control surfaces

Stream Deck and iPad do not run Logic automation themselves. You send an action to the Mac app. This keeps license checking, status, local language, Logic window detection and actual automation in one place.

Dynamic lists

Many options are not hard saved in iPad or Stream Deck. Plugin names, library presets, audio performances, bus performances, I/O names and logic key commands come from the Mac app.

Own MIDI device

Ben's Toolbox sets up its own virtual MIDI device. Logic receives defined MIDI commands, while the Mac app knows which command belongs to which function. This allows iPad, Stream Deck and Shortcut Manager to trigger the same actions without each surface having to maintain its own logic configurations.

The setup usually happens automatically when you start the Mac app. If the device already exists, the existing logic configuration remains unchanged. If it is missing, Ben's Toolbox first creates a backup and then adds the device. You can find restore and re-install in the MIDI Device Manager under Setup.

In practical terms, this means: A button can exist on the iPad, on the Stream Deck or as a shortcut and still trigger the same Ben's Toolbox action with the same parameters. The real intelligence remains in the Mac app.

macOS App

The macOS app provides the actual tools. Use the menu bar symbol to open the windows for scripts, Bouncer Tool, and plugins & Patches, Bus FX, Motion, Shortcut Manager, Articulations, Support, Settings, License and Updates. If Ben's Choir is activated, Voice Central also appears for voice profiles and choir-related workflows.

When launched, the Mac app checks accessibility, license or trial, launches WebSocket/Bonjour for iPad and Stream Deck, loads catalog data, monitors images, and checks the Ben's Toolbox MIDI device in Logic. If the device is missing, it will be installed automatically after a backup; If there are problems, the MIDI Device Manager opens. The app also installs released additional components such as CC Monitor, Ben's Choir and the Stream Deck plugin. The Audio Meter is prepared in the code, but is not automatically delivered in the current release.

Tools: Bounce & export

Bouncer Tool

Opens the full Bouncer Tool window. This tool is intended for complex export tasks and is described in detail below.

Bounce WAV

Exports WAV, AIFF or CAF via Logic Pro. Options include format, bit depth, sample rate, interleaved/split, dithering, normalization, offline/realtime mode, audio tail, tempo information and optional opening of the export folder.

Bounce MP3

Creates MP3 files with fixed mono/stereo bitrate, quality level, stereo mode, normalization, offline/realtime mode, VBR, smart encoding, filter below 10 Hz, audio tail and tempo information.

Bounce WAV + MP3

Combines both deliverables in one pass. Useful if you regularly need to deliver a high-quality master and also a quick listening version.

export

Exports audio based on selected ranges and options. This includes Trim Silence, Cycle Only, Extend to End, Format, Bit Depth, Normalization, Bypass FX, Tail, Volume/Pan and Tempo information.

Tools: Plugins & Presets

AddFX plugin & Quick Insert

Loads a specified audio FX plugin into the next appropriate slot. Optionally, mono-to-stereo may be preferred if Logic offers multiple variants. Opens a search/prompt workflow. You specify the plugin name or choose it via a remote interface. The prompt can appear on Mac, iPad or both.

Open Library Preset

Opens a Logic Library Preset. The selection can be made directly or as a prompt. The list comes from the scan in plugins & Patches and can be grouped by subfolders.

Audio & Bus Performance Picker

Uses saved audio and bus performances on audio or bus tracks. You can trigger a predefined performance directly by pressing a button on iPad, Stream Deck or via a shortcut. Alternatively, the tool opens a prompt in which you can select from the existing performances on the iPad or Mac.

Tools: Mixing & routing

Add Send

Adds an existing send on the current channel. You can define goal, level and prompt behavior. The available send destinations come from the scanned I/O data.

FX Send Preset

Creates or uses a prepared bus FX workflow with send name, plugin, destination output and send level. Ideal for recurring spaces, delays or parallel effects.

Set output

Sets the output of the active channel. The output can be passed directly as a parameter or selected via prompt.

Fade

Changes Fade-In, Fade-Out, Fade-Time, and Fade-Types. Times can be set absolutely or changed relatively. Fade types include, but are not limited to: Out, X, Equal Power and X S.

Set gain

Sets or changes gain in dB. The mode can be absolute or relative, for example +2dB or -2dB.

New Audio (Mono & stereo)

Creates a new mono or stereo audio track with prepared input and optional track name. If the input is not passed hard, Ben's Toolbox opens a prompt where you can select the input and name. This is particularly useful for recurring recording setups such as voiceovers, solo instruments, DI signals, stereo miking, synthesizers, external instruments or submixes.

Hover Actions

Hover Actions are context-dependent actions directly in the logic channel strip. You move the mouse to a marked location and trigger the appropriate Ben's Toolbox action with a Modifier-Klick. This means you don't have to open the Channel Strip manually, search it or select the target slot in a separate window.

The modifier keys for Hover Actions can be used in Shortcut Manager be adjusted. The usual modifier keys are possible; just be careful not to choose a combination that Logic already uses for important actions of its own. Are recommended Control, option and Cmd.

Settings Button on audio and bus tracks

On the Settings button of an audio or bus channel strip, the hover action opens the appropriate performance picker prompt. Audio performances are offered on audio tracks and bus performances on bus tracks. This allows you to apply saved performance setups directly to the current track.

Input, output and send

Hover Actions on Input, Output and Send open the respective routing prompts. The selection lists come from the scanned I/O and bus data of the Mac app. This is particularly useful if you don't want to search for routing destinations via Logic menus, but rather work directly from Ben's Toolbox, iPad, Stream Deck or shortcuts.

Empty instrument and audio FX slots

On empty instrument or audio FX slots, Hover Actions starts the appropriate plugin or quick insert workflow. For instrument tracks, an instrument can be loaded; For audio FX slots, an audio effect is inserted into the empty slot. Alternatively, a prompt can be opened to select from the scanned plugins.

Tools: MIDI & Piano roll

Set velocity

Sets the velocity of selected MIDI events to a target value. This is useful for quick unification or special values ​​like very low trigger velocities.

Next CC

Jumps to the next available CC or automation track in the Piano Roll.

Set CC

Directly selects a piano roll CC lane. Typical controllers such as volume, pan, modulation, Pitch Bend, velocity, balance, breath, foot, portamento, expression, sustain, aftertouch, program change, surround parameters and CC 20 to CC 32 are supported.

Tools: Articulations

Set articulation

Sets an articulation based on a name, for example legato, staccato or pizzicato. The tool looks for a suitable entry in the articulation menu of the current track.

Trigger articulation

Triggers articulations according to slot index 1 to 32. This mode is particularly suitable for Stream Deck and iPad because buttons can be placed directly on slots.

Articulation Menu

Opens the Articulation Picker for quick selection in Logic.

Read Articulations

Reads the current articulation set of the active track and writes it to the shared state for Stream Deck and iPad. This is the most important refresh step if the remote interface does not show the expected playing techniques.

Tools: Utilities

Open Project Folder

Opens the current Logic project's folder in Finder.

SMPTE Reset

Sets the SMPTE position to zero at the current playhead position.

Logic shortcut

Triggers any logic key commands. The key command list is provided from the Logic command data and is searchable on iPad and Stream Deck.

Scan I/O & buses

Rescans I/O and bus names. Use this after template changes, changed output names or audio interface changes.

Set of markers

Creates or names markers based on a passed name.

Paste Colored MIDI Region

Inserts a MIDI region in a selected color. Available colors are red, yellow, green, blue and purple.

Submit Script Request

Opens the way to send new script or workflow requests to support. This tile is not a Logic automation step, but rather a contact and feedback entry point.

Bouncer Tool

The Bouncer Tool is the most important and comprehensive export tool in Ben's Toolbox. It is intended for recurring deliveries: mixes, instrumentals, TV tracks, stems, single tracks, variants and custom deliverables.

Start Bouncer Tool safely

The start deliberately begins before the actual Bouncer window. Save the active Logic project with it Save or Save As; Ben's Toolbox then waits until the project file has been completely written and verified. Only then is the track structure read and the main window opened.

Track reading from project file and autosave

When opening the Bouncer Tool and at Reset & Rescan Ben's Toolbox evaluates the currently active Logic project file. If another arrangement is opened, the previously loaded project-related state is discarded and the new track list is read in. If a newer autosave file exists, it can be considered for version and structure checking; The basis remains the currently verified save status.

The scan reads track IDs, track names, track types, mute states, visible and collapsed tracks, aux/subgroups, and top level and nested levels. When opened, the track list shows whether a track in the arrangement is muted. Mixer and UI Search are not the primary source of the tracklist; they are only used as limited fallbacks when a live state or a collapsed reference path is not directly accessible.

Folder projects, Bouncer scope and root level

The Bouncer Tool also supports Logic projects with multiple nested folder levels. Every bounceable track remains visible and selectable in the track list - regardless of how deep it is in a folder. Folders themselves are not included as an audio source in a round; they serve as orientation and can be used as Bouncer Scope be used.

1. Open the desired folder in the Bouncer track list and check the tracks it contains.
2. Click on the desired folder Root-Symbol at the point where it is on normal tracks S stands.
3. Logic switches to this folder. The Bouncer hides levels above and permanently shows the note Bouncer Scope: [folder name].
4. Within this area, select Tracks, Cycle Reference, Master FX and Bounce-Rounds as usual.

A scope makes sense if a large project involves areas such as: Sketch, arrangement and Mix owns, but only within Mix should be exported. With Show full project you leave the scope again. Start fresh also resets the scope, empties the current Bouncer session and the visible main preset selection - saved Main Presets and audio settings are retained.

Important areas

Recommended workflow

1. Open Bouncer Tool and in the start dialog Save or Save As choose. The tool waits for the fully written and verified project status.
2. Make sure no track is soloed in Logic. For large folder projects, then decide whether the entire project tree or just one folder should be used as the Bouncer scope.
3. Check or select project name and export folder.
4. Define the checkboxes in the header, set the cycle reference and if necessary Master FX Activate or deactivate for the selected channel. To do this, select the corresponding track in the dropdown.
5. Use the Preset Manager to create presets that include or exclude tracks based on names, track types, and properties. Alternatively, you can manually select tracks and add them as Bounce-Round.
6. In the preset you can already prepare Bounce/export type, dictionary, mute rules, Fade and Audio Settings. When adding manually, a prompt asks you to click on Add Tracks the most important round options.
7. Check round names and change them directly in the round if necessary. Only the part is edited # -, so e.g. b. Instrumental. Duplicate Together names are automatically made unique so that exported files do not overwrite each other.
8. If you want to adjust a round later, you can delete individual tracks from the round or drag and drop changed tracks from the track list into an existing round.
9. Select an individual Audio Settings preset for each Bounce-Round if this round requires other Bounce/export settings.
10. If necessary, use the dictionary to specifically rename tracks and achieve consistent naming.
11. If the export includes lyrics, open Lyrics, paste the text, choose the desired formatting and save the text file directly in the Bounce folder.
12. Under Completion If necessary, choose customer email, cloud upload, local ZIP backup and treatment of the finished files. You can save recurring customer settings as your own completion preset.
13. Selection preflight leave activated. This means that every track required in the remaining run, including cycle references, is addressed and validated once before the first export. Pre-flight only only runs this test without bouncing or exporting.
14. If the setup is correct, you can save all the Bounce/export logic as Main Preset and reuse it for another project. This also includes manual rounds, changed round names, Bounce Versions and scheduled mutes.
15. Start complete export.

Selection Preflight and Cycle References

The default active one Selection preflight checks every different track that is needed in the still open run exactly once. These include active round tracks, mute-only destinations and cycle references; Rounds that have already completed a restored session will not be included again. If successful, the actual run will use the validated direct track IDs without having to search and select each track again through the interface before each solo/mute step.

Cycle References are initially addressed directly like all other arrangement tracks. If a reference is in a collapsed stack or is not visible in the direct path, the Bouncer uses limited logic Search and Select Track, displays the path and validates the track found. Because this can cause visible lines to move, the track assignment is then re-bound. UI search remains a fallback and is not used across the board for all subsequent channels.

Resumption after interruption

Ben's Toolbox stores arrangement-related sessions Pre-flight only, start and Cancel. As long as no new Bounce-Round has been created, the empty main field shows available time statuses and Restore session. If a run ends due to a Logic crash, abort or other interruption, the last suitable setup can be restored.

Only fully confirmed rounds are skipped. A round is only considered completed after successful Bounce, final file handling and completion of the associated steps. The round that was just interrupted or failed is therefore re-executed so that no incomplete file is silently treated as finished.

Reset & Rescan is deliberately a complete restart of the track assignment: After confirmation, the currently created Bounce-Rounds are deleted and the tracks are re-read from the saved project. Use instead Restore sessionif you want to resume a previous setup or an interrupted run.

Structured naming

For the sensible use of Bouncer Tool presets, a uniform naming of subgroups, instruments, audio tracks and stem groups is very helpful. Presets, mute rules, track selection and dictionary refer to the names and structure of your Logic project. The more consistent these names are, the more reliably a preset can be applied to different arrangements.

A simple example: If vocal tracks and vocal subgroups in your projects are always named according to the same principle, a Bouncer Tool preset needs significantly fewer special rules to correctly create main mix, instrumental, TV track or vocal stems. Inconsistent names, on the other hand, force more exceptions and increase the likelihood that a trace will be mishandled in a Bounce round.

If there are multiple versions, it is often most efficient to create all versions one after the other in an arrangement. Create a separate reference track for each version and use this track as a cycle reference for the Bounces of this version. If the names of the reference tracks, subgroups and stem groups remain the same across your arrangements, a Main Preset once built can be applied directly to another arrangement. After opening and scanning, the export is then ready to start with practically one click.

Create Bounce-Rounds

A Bounce-Round is a saved export pass within a Bouncer Tool setup. The Bouncer Tool processes the rounds one after the other. Each round can have its own track selection, mute rules, Bounce type, export type, dictionary usage and Fade setting.

1. First read the current Logic project so that the Bouncer Tool knows track names, track types, numbers, mute states and group structure. This happens automatically when you open the window; after structural changes Reset & Rescan necessary.
2. Either select tracks manually in the track list or select a preset in the top right.
3. Click on Add Tracks. For a preset, a round with the preset name is created directly. If selected manually, a manual round is created from the selected tracks.
4. Set in the round whether it should be as Together or Single should run. Together creates a common file from the round, Single processes the included tracks individually.
5. Choose whether the round should run as Logic-Bounce or as an export. With Single rounds this can be done, for example: For example, a track selection can be converted into a single track export.
6. For Single-Rounds, check the names of the files created. These come from track name, Name Preset, project name, optional stem block and dictionary.

For Together and main rounds, the compact round card now deliberately separates two pieces of information: The first line only contains the numbered, editable name of the Bounce-Round. The second line shows the actual resulting export name. This means that directly before preflight or start you can check how the project name, round name, version, prefix, postfix and capitalization are put together using the active Name Preset. Very long names are shortened in the middle of the card; the full name remains available as a clue.

Visible arrangement tracks as individual rounds

Add visible as rounds means the actual visible lines in the Logic arrangement - not the full Bouncer tracklist and not all mixer channels. Visible stack, aux and subgroup tracks are taken into account if they have their own visible arrangement line. Mixer-only channels, pure structure folders and alias lines are excluded. Each track found creates its own Together round; An additional Together/Single selection is therefore not necessary.

The round name can be edited directly in the round settings. What is meant is only the visible part of the name that follows # - stands, not the automatic number in front of it. For Together rounds, this name is used for the common export name. If a Together round with the same name already exists, the Bouncer Tool automatically makes the new name unique so that no output is overwritten.

A round does not only contain the tracks that are to be actively exported. It can also contain mute-only tracks. These tracks are not part of the solo/export selection, but will be temporarily muted before export if a mute rule or manual scheduled mute selection requires it. Mute-only tracks are shown crossed out in the round.

In the tracklist are S and M deliberately separate click targets: S actively includes the track in the round, M plans a Bouncer mute rule. The drag zone lies between these buttons. It is used to drag a changed track into an existing round. After the drop, the temporary selection state of the dragged track is reset.

Tracks can be removed from existing rounds, both in Together rounds and in Single/export rounds. This is important if a preset is fundamentally suitable, but individual tracks should not end up in this round for a specific arrangement.

Mute/Solo state per round

Before each Bounce-Round, the Bouncer Tool compares the scanned original state with the tracks that will be active in this round. An already muted track does not need to be unmuted first for a solo round: Logic gives Solo priority over Mute. Upon completion, the Bouncer removes its temporary solo states and restores the original mutes.

This preserves the musical working state of the Logic project: an originally muted track can still be part of an instrumental, stem or Single export without accidentally remaining muted after the run.

Bounce Versions

Bounce Versions are parent collections of Bounce-Rounds. They are intended for multiple variations of the same arrangement, for example 60sec, 30sec, Underscore or alternative cutdowns. A version can have its own default values ​​for Title Addon, Bounce range, track reference, Audio Settings and master FX behavior.

When creating a new Bounce Version, an existing setup is used as a starting point. You can then change, delete or add rounds per version. A Bounce Version can also be deleted; The associated rounds are removed. At least one version is always retained so that the Bouncer Tool does not end up in an empty state.

Preset logic and track selection

A Bouncer Tool preset does not describe fixed track IDs, but rather rules with which tracks are found in the current project. This allows a preset to be applied to similar projects as long as the naming and structure remains consistent.

The preset mode decides how the main rules are interpreted. In Include mode only tracks that meet one main rule will be included; An optional counter-filter can exclude individual hits again. In Exclude mode In principle, all non-excluded tracks are included; an optional counter-filter can resume certain tracks despite exclusion.

Mute Rules are separate from it. You add tracks to the round as mute-only tracks if these tracks are not already part of the round. So you can e.g. For example, for an instrumental mix, mute all vocal tracks without treating the vocal tracks as separate export tracks.

Create presets

A preset is created in the Preset Manager. It stores the preset name, include/exclude mode, main rules, optional counter rules, mute rules, Bounce type, export/Bounce type, online/offline behavior, stem option, dictionary usage and the Fade option.

1. Open the Preset Manager via the Preset menu in Bouncer Tool.
2. Create a new preset and give it a name that describes the later round, e.g. b. Instrumental, Drums Stem or TV mix.
3. Choose Include or Exclude. Include is useful for stem presets that specifically only collect certain tracks. Exclude is useful for mix versions where almost everything is included and only certain groups are removed.
4. Add search terms. After creating it, you can switch between Contains and Exact per chip using the context menu and optionally set a track type.
5. For Aux/Subgroup or other group tracks, use the appropriate nesting level if only the top group or only a specific nested level is meant.
6. Add Mute Rules if you want tracks to be muted for this round without exporting themselves.
7. Save the preset and apply it in Bouncer Tool. Add Tracks creates a new Bounce-Round from this.

Example: Instrumental preset

An instrumental can be built in Exclude mode: The main rules look for vocal terms like vox, vocal, lead vox or choir. The Bouncer Tool then includes all non-excluded tracks in the round. If you still want certain vocal FX returns to remain in the mix, they can be recorded again using the counter filter. Alternatively, vocal tracks can be muted via Mute Rules if the round is to run as a shared mix.

Example: Stem preset

A drums stem is typically an include preset. The main rules are looking for that's why, kick, snare or a top-level subgroup called Drums. If only the group track is to be exported, the track type should be set appropriately, e.g. B. Subgroup with Nesting Level Top Level. If individual audio tracks are to be exported, the filtering is based on audio or instrument tracks.

Main Preset

A Main Preset is a complete Bouncer Tool setup. It saves not just a single track selection preset, but the entire working configuration: selected Name Preset, click check, low latency check, Bounce master, cycle reference, Master FX, audio settings snapshot, final Fade settings, Bounce Versions and all Bounce-Rounds as templates.

The rounds are not restored as rigid old track objects when loading a Main Presets. The Bouncer Tool reconstructs them using the saved preset names, stable track keys and the current scanned tracks. Manually created rounds retain their selected tracks, changed round names, scheduled mutes, and removed tracks. This allows you to save setups that were not completely created from preset rules.

The Main Preset also includes the active completion configuration. The independent library of your completion presets is retained: loading an older Main Presets selects its saved completion settings, but does not remove customer presets that were created later.

A clean template structure is still important: If track numbers, groups or names change significantly, the tool can only reliably find the tracks that are still recognizable via stable names, numbers and structure.

Open Main Preset via WebSocket or Stream Deck

The tool Bouncer Tool can be opened via WebSocket and therefore also via a stream deck action with an optional Main Preset. Use in the tool parameter for this mainPresetName; the name must be unique. For technical integration mainPresetID the more reliable choice. Without parameters, the Bouncer Tool opens as usual without a forced preset. If several presets with the same name are found, a random preset will not be chosen but the request will be rejected.

Completion Actions: ZIP, cloud and customer email

With Completion you automate the steps after the last Bounce-Round. The Bouncer Tool can collect the files generated in this run, save them as a ZIP, upload them via a connected cloud service and then send a final email. These steps also appear in the progress list on Mac, iPad and iPhone.

If a customer email is activated, the cloud upload as a ZIP is automatically required: The message will only be sent after a successful upload with the checked download link. If a ZIP with the same name already exists in the target folder, the Bouncer Tool creates a unique new name instead of overwriting an existing share unnoticed.

The email to the customer contains the track name, download link and the files actually created. Main rounds are not broken down into a long track list. Before starting, the Bouncer Tool checks the required access for the cloud, keychain and Apple Mail so that system dialogs do not interrupt the ongoing export.

Name Presets

A Name Preset defines how export files are named. It consists of a prefix, separator, optional stem building block, postfix and the option to write the name in capital letters. With Disable title In addition, the Logic project or arrangement name can be completely removed from the export name. Empty name components are skipped so that the file name begins directly with the next existing building block and never accidentally with a separator such as _ starts.

Mark exactly one Name Preset Use as default. This preset is automatically selected every time the Bouncer Tool is started and also saves options such as Disable title and Upper case only. If a Main Preset explicitly loads another Name Preset, the selection stored in the Main Preset takes precedence over the default. This way, a general personal standard is retained without overwriting customer-specific Main Presets.

For Single exports, the file name is built from the optional project or arrangement title, stem component, track name and postfix. Together rounds use the round name accordingly. If multiple tracks had the same name after dictionary mapping, the Bouncer Tool automatically appends a number like -2 so that no files are overwritten.

Dictionary

The Dictionary normalizes names. A dictionary entry consists of a target word and several synonyms. If a track name contains a synonym or exactly matches the target word, the Bouncer Tool uses the target word for the export name. This can result in inconsistent names like Violins 1, See 1 or Violin I become a uniform export name.

Dictionary usage can be saved per preset or round. For Together rounds, the naming is more round-based; the dictionary is particularly important for Single/Stem output, where track names become file names directly.

Lyrics

The Lyrics tool is intended for song lyrics that need to be submitted along with mixes, stems or customer versions. You open it directly in Bouncer Tool, insert the text and immediately get a formatted preview. One is saved .txtfile in the current Bounce folder.

The formatting can be changed live: upper/lower case remains unchanged or is converted to uppercase letters, lowercase letters or the beginning of words; Umlauts like ö, ä and u can too oe, ae and ue become; Individual line breaks and paragraphs can either remain as visible breaks or be replaced by freely selectable characters. The default characters correspond to the previous BMG workflow: / for line jumps and // for paragraphs.

The file name uses the active name manager. Instead of a round name, a fixed Lyrics block is used: lyrics. With a suitable Name Preset, the file ends up in the same naming system as the audio exports, for example as UPM_SONG_LYRICS.txt.

Pre-launch header options

Audio Settings, Bounce/Export and Auto Fade / Final Fade

The Audio Settings of the Bouncer Tool correspond to the relevant audio and export settings from Logic. They are in the Bouncer Tool in areas for Bounce, export and Final Fade divided. Here z. B. Format, sample rate, bit depth, normalize behavior, export range, tail/volume/tempo options and the Fade parameters are prepared.

These Audio Settings can be saved as your own presets. This means you don't have to set the format, sample rate, bit depth, Bounce/export behavior and final Fade options again and again per round. Typical presets are for example Mix WAV 48 kHz, Stems 24 bits, MP3 Preview or a special deliverable setup for a customer.

In the audio settings window you can create, duplicate, rename and delete presets. A preset can then be used by Bounce-Rounds and Main Presets. If an audio settings preset is deleted, affected Main Presets automatically use the preset Default, instead of starting with a missing setting.

A Main Preset can not only restore Bounce-Rounds and track rules, but also load the associated Logic-compatible audio settings for recurring deliverables. This is especially useful if mix, instrumental, stems and preview files require different audio formats or Fade rules.

The Fade checkbox of a round or a preset activates automatic post-processing of the generated audio file. WAV, AIFF/AIF and CAF are supported. After the Bounce, the Bouncer Tool analyzes the end of the file, looks for end silence, and renders a Fade out using the saved final Fade settings.

The threshold, hold time, Fade duration, cut-end and hard-end behavior are stored in the Audio Settings. If real silence is detected at the end, the Fade can be set from this point onwards and the end can optionally be shortened. If there is no end silence, the hard-end Fade can grab and put a short Fade at the end of the file. This option is particularly useful for stems or mix versions where you want to automatically clean up reverb tails, empty ends or hard ends.

iPad integration

The Bouncer Tool can be operated from the iPad. Mac, iPad and iPhone work with the same session state stored on the Mac. When opened, a device adopts the existing status instead of emptying an already prepared session. Changes to Bounce Versions, rounds, order, open details, presets and completion settings are propagated to the connected devices. The Mac app remains the central authority for Logic execution, project scanning and local files.

The secure boot process can also be carried out entirely on the iPad. When you open the Bouncer page, you will be given a choice between Save, Save As and Cancel; The iPad then shows analysis, possible scan hints and the selection preflight. If the start was previously aborted, it also opens Restore session first this save dialog again before the selected session is loaded.

A saved Bouncer session also contains the required expand/collapse state of the logic track stacks. When restoring, the Mac app restores this structure in Logic before Preflight or Bounce begins. This means the saved track targets remain valid and unnecessary search-and-select fallbacks are avoided.

The iPad workflow corresponds to the Mac workflow: Rounds can be opened, renamed, moved, deleted or tracks can be added. Individual tracks can be removed from existing rounds. Bounce Versions can also be deleted on the iPad as long as at least one version remains. Changed tracks from the track list can be dragged and dropped into a round; The temporary selection state is then reset. Completion presets, customer mail, cloud upload, ZIP backup and file handling are also offered in the same order as on the Mac.

During a run, the iPad and iPhone switch to the status view. The active step is automatically scrolled into the visible area. After completion, the prepared Bouncer session remains until you explicitly reset it via Reset or Cancel.

Options in detail

Plugins & patches

This window provides the database for many other tools. It scans and manages plugin names, library presets, I/O elements, buses, outputs, audio performances and bus performances.

AudioFX

instruments

patches

Audio Performances

Bus Performances

I/O

When to rescan?

• After installing or removing plugins.
• After changes to the audio interface, outputs or bus names.
• If iPad or Stream Deck do not display dynamic lists completely.
• If new library presets are not found.
• After major changes to Logic templates.

Bus FX Settings

Bus FX Settings is the administration for fast send workflows. You define a kind of recipe: name, target, plugin, output and send level. A button on the iPad, Stream Deck or in the Shortcut Manager can then execute this workflow.

This management is also present on the iPad. There you can check existing triggers, create new triggers, check plugin, output and send values ​​and rescan I/O and bus data if necessary.

Options

• Trigger name: Name under which the workflow is displayed or found.
• Plugins: Effect to be loaded on the target bus.
• Output: Exit or bus destination.
• Send level: Start value of the send, e.g. B. 0 dB.
• Prompt mode: Selection only when triggered instead of a fixed target.

Routing Map

The Routing Map creates an interactive HTML overview of the routing from the currently open Logic project. The menu item is in the macOS app in the main menu right next to the Bouncer Tool.

When executed, Ben's Toolbox reads the Logic project file, regenerates the HTML, saves it in the project folder and then automatically opens it in the browser. The file is named according to the scheme Project name - Routing Map.html.

What the map shows

• visible tracks and their exits
• Aux, bus and subgroup paths to the output/master
• Sends and sidechain references as far as they can be read from the logic file
• recognized plugins and virtual instruments in the view Used plugins
• Project metadata such as project name, tempo, time signature and sample rate

Service

• Routing Map click in the main menu.
• The HTML is rewritten each time to use the current saved project state.
• The map can be scrolled horizontally and vertically; Zoom works via modifier plus mouse wheel.
• Hovering over a track or aux element highlights the incoming and outgoing connections.

Shortcut Manager

The Shortcut Manager is the bridge between Ben's Toolbox actions and your own keyboard controls. It is also helpful if you want to prepare complex actions without immediately building a Stream Deck layout.

What a shortcut can contain

• An executable Ben's Toolbox action.
• Fixed parameters such as plugin, output, gain value or CC target.
• Prompt options for Mac, iPad or both.
• Shortcut keys and modifiers.
• Action-specific options, for example whether a prompt is opened or a fixed target is used.

Hover Actions are not an optional trigger for a shortcut, but a separate area. You work via the mouse position in the visible Logic Pro Channel Strip and can therefore also reach slots on an inactive track, for example Audio FX in the mixer via hover plus Modifier-Klick.

If a shortcut doesn't respond, first check if the same command from the Scripts window works. If it works there, the problem usually lies in the shortcut, focus or parameter values.

Prepare articulation sets

To optimally use the articulation options of Ben's Toolbox with Logic Pro, an existing articulation set is necessary. Ben's Toolbox does not replace library articulations, but rather prepares existing Logic articulation sets so that they can be used reliably live, during later editing as well as on iPad and Stream Deck.

Basic principle

Ben's Toolbox works with the articulation sets that you already use in Logic Pro. In order to switch live, this must be in these sets Remote switch be active. So that you don't have to enter these values ​​manually, Ben's Toolbox contains a conversion script for existing type sets.

During conversion, the existing articulation set file is overwritten as a working file. Beforehand, Ben's Toolbox automatically creates a backup of the original file. The existing playing techniques will be converted so that Ben's Toolbox can use them for live use, post-editing, iPad and Stream Deck. Remote switch is activated, the required values are entered and Ben's Toolbox uses MIDI channel for this 16. Ben's Toolbox does the rest.

The three tabs in the Articulations window

Convert

The rider Convert prepares existing Logic articulation sets for remote control. Ben's Toolbox activates the remote switch, enters the required switch values and automatically uses the MIDI channel for this workflow 16. The original file is saved beforehand, then the set must be reloaded in Logic on the affected tracks and then read again.

The conversion does not insert a CC monitor plugin into Logic. For live feedback and MIDI recall the CC Monitor are also on the respective track as MIDI FX. The quickest way to do this is to use the combined one CC Monitor / Read-Button on the Stream Deck or above Add MIDI Monitor Plugin or Reconnect in the iPad Remote.

MIDI FX plugins

The rider MIDI FX plugins shows the saved CC monitor instances. Each line represents a specific MIDI-FX plugin on a Logic track and is grouped by arrangement. Online means that the instance is accessible in the currently open project. Saved offline means that Ben's Toolbox knows this instance from a previous project or track state, but it is not actively connected at the moment.

With Show all instances the saved history becomes visible. This is useful for cleaning up old projects, renamed tracks, or CC monitor mappings that are no longer needed. In the normal view, the list remains slimmer and prefers to show the currently accessible instances.

ImageDictionary

The rider ImageDictionary relates exclusively to the representation of the Articulations-Page in the iPad Remote. It does not change any Logic articulation sets, no Stream Deck buttons, and no macOS function. Stream Deck displays articulations over text and statuses, not over these background images.

Keywords are checked against articulation set, track or library names. The most specific match wins: An entry like Contrabassoon can therefore specifically choose the woodwind picture, although in the word too Contrabass occurs. Your own pictures belong in the folder ArticulationBackgrounds; for iPad backgrounds are large images in the format range 2732×2048 px makes sense.

Recommended preparation process

1. Select an instrument track in Logic.
2. Assign the desired articulation set to the track in Logic Pro.
3. Check whether the existing articulation set contains the desired playing techniques.
4. In Ben's Toolbox the window Articulations open and go to tab Convert change.
5. Ben's Toolbox uses the MIDI channel for this 16.
6. Select and convert the individual articulation set or a folder.
7. After conversion, reload the articulation set in Logic on the respective track. For a single set, the reload can be started directly via the results dialog; When converting folders, each affected set must be reloaded individually on its track.
8. Read Articulations to have Ben's Toolbox reread the current set, slots and names.
9. Den CC Monitor Use as MIDI FX on the logic track or Connect Use if live feedback and MIDI recall are to be used.
10. Test on iPad or Stream Deck: Trigger slot, check active state, then check MIDI regions in Logic.

What exactly the conversion does

The conversion edits the existing one .plistfile in the Logic folder ~/Music/Audio Music Apps/Articulation Settings. The file will be overwritten, but the original file will be saved in the subfolder first Bens Toolbox Backup saved. This allows you to return to the original set if necessary.

In the work file, Ben's Toolbox activates Remote Switch, enters the required switch values and converts the existing game techniques so that they can be clearly triggered by Ben's Toolbox and later processed further in Logic. Ben's Toolbox uses MIDI channel for this 16.

CC Monitor

For optimal control of articulations, the CC Monitor as MIDI FX on every Logic track that works with articulations. The plugin helps Ben's Toolbox to report the current articulation state back from Logic and to more reliably align the control via Stream Deck, iPad Remote and Motion with the musical state of the track.

In practical terms, this means: iPad and Stream Deck can not only trigger articulations, but also display the active state better. Motion workflows and remote controls also benefit from this because Ben's Toolbox knows more precisely which gaming technology is active on the track. Therefore, use the plugin on tracks with articulation sets if you want to use live feedback, MIDI recall or the cleanest possible remote control.

Playing live vs. editing playing techniques

What should be checked before converting

• Existing set: The articulation set must already exist in Logic and contain the desired playing techniques.
• Remote switch: Remote switch is required for live switching; the conversion activates and fills these values.
• MIDI-Channel 16: Ben's Toolbox automatically uses this channel for the workflow.
• Backup: The working file will be overwritten, the original file will be in the folder beforehand Bens Toolbox Backup secured.
• CC Monitor: For live feedback, MIDI recall and optimal remote control, use the CC Monitor on the relevant tracks.

MIDI Recall and active state

MIDI Recall is particularly helpful when not only a button is pressed, but the interface should know the current state. The CC Monitor can return articulation information from the Logic context to Ben's Toolbox. This means the iPad or stream deck display can stay closer to what is actually musically active.

Normal: short flashing in Logic

When triggering articulations live via iPad or Stream Deck, if the Piano Roll is not in focus, Logic may flash briefly or visibly change focus. The reason is not a bug in the function, but rather that the wrong window for setting the articulation is active. The articulation is still triggered; flashing does not affect functionality. If it bothers you, click on the piano roll once. As long as the Piano Roll remains the active window, the flashing disappears.

Stream Deck

The Stream Deck is the fastest hardware interface for Ben's Toolbox. It can trigger tools, windows, logic key commands, articulations and prepared workflows.

Installation and updates

When started, Ben's Toolbox checks whether Stream Deck is installed and whether the Ben's Toolbox plugin is present. If the plugin is missing, the app can offer to download it. If an older plugin version is installed, an update window appears and, after downloading, opens the Stream-Deck-Plugin for installation.

Button types

• Tool Actions: direct Ben's Toolbox tools.
• Open Window: Open the Mac app window.
• Logic shortcut: Send logic key commands.
• Articulation buttons: Trigger slots 1 to 32 and display status.

Configure buttons in the Stream Deck app

Many Ben's Toolbox buttons are set up directly in the Property Inspector of the Stream Deck app. There you can specify whether a button immediately works with a fixed parameter or opens a prompt when pressed. The lists come from the Mac app data: plugins, library presets, current Logic project outputs and buses, audio performances, bus performances and bus FX presets.

Complete button list

The following list corresponds to the current Stream-Deck-Plugin. Button actions are intended for normal stream deck buttons; CC Fader and Gain Dial use the knobs of supported stream deck models.

Prompt and picker buttons

At Plugin Picker and Open Library Preset Many buttons can automatically receive the appropriate image. The Stream-Deck-Plugin comes with over 1000 images for plugins and software instruments. You can use this automatic image selection, deactivate it or use your own or manually selected image at any time.

Performances, routing and Bus FX

Audio tracks, gain and Fades

Stream Deck Articulations

Universal articulation buttons

Articulation buttons on the Stream Deck can be created universally. The buttons are not tied to a specific instrument, but rather adapt to the instrument or articulation set of the currently selected Logic track. This allows the same Stream Deck page to be used for different libraries, instruments and articulation sets.

Connect CC Monitor directly in the stream deck button

The CC Monitor can be connected directly from the button configuration. At Automatic articulation The Connect button only appears if no CC Monitor has been detected on the currently selected logic track. Once the track is connected, the Inspector will show the green status. Alternatively, the separate CC Monitor / Readbutton can be placed on a Stream Deck page to quickly check the current track, reconnect, or re-read the articulation set.

The button at the top right of the Stream Deck articulation page is the combined one CC Monitor / Readbutton. If the CC Monitor is not connected, the button tries to connect the current logic track or use the CC monitor plugin. If the CC Monitor is already connected, the same button reads the articulation set of the currently selected track again. When connected, the button shows the name of the articulation set currently being read on a green background, not the currently active playing technique.

Recommended workflow

1. In Logic, select the instrument track whose articulation set you want to control.
2. Press Stream Deck on the CC Monitor / Read. This means that Ben's Toolbox connects the CC Monitor if necessary or rereads slots, names and the active set of the track.
3. Lay Articulation slot-Buttons on the Stream Deck. In Property Inspector you set the desired slot 1 to 32 for each button.
4. Use Property Inspector of an articulation button Connect CC Monitor, if the current track does not yet have a CC monitor MIDI FX plugin. Ben's Toolbox sets or connects the plugin to the active logic track.
5. Then trigger the articulations directly from the Stream Deck. If a MIDI event is selected in the Piano Roll, its articulation is changed. If no MIDI event is selected, the articulation is set live for recording.
6. Check the visual feedback: the button titles come from the Logic articulation set, active articulations are highlighted in color, and the velocity colors help recognize the changes in Logic.

The Connect CC Monitor-Button only appears as a setup or repair step in Property Inspector. If the CC Monitor is already connected on the current track, the Inspector shows the connected status and the button no longer needs to be used. If you switch to another track without CC Monitor, you can continue to use the same articulation button and connect the new track directly from the button configuration.

Alternatively, you can use the separate one CC Monitor / Readbutton on your stream deck page. This button is useful if you want to quickly check or repair whether the currently selected logic track is connected to the CC Monitor while working. It shows directly on the Stream Deck whether the monitor is connected, can re-establish the connection or insert the plugin on the current track and serves as a manual refresh for the articulation set if a connection is established.

Setting up with automatic articulation buttons is particularly quick: If you drag and drop these buttons onto the Stream Deck, each button counts up its slot independently. So you only create the buttons once; They are automatically assigned the correct slot and can then be used by any track with an existing articulation set. The stream deck page is therefore quick to set up and can be used universally for different instruments.

A button press has two tasks: If a MIDI event is selected in the piano roll, its articulation is changed to the playing technique pressed. If no region or MIDI event is selected for editing, the same key press sets the playing technique for live playing. This means you don't have to differentiate between separate editing and live buttons.

MIDI-CC buttons on the Stream Deck

Stream deck buttons can also be used as MIDI-CC or performance parameter buttons. The buttons not only send a value, but can automatically respond to the current Logic state: the active parameter is highlighted on the Stream Deck, while Logic shows the appropriate automation or MIDI lane. This makes it immediately visible whether you are currently controlling modulation, expression, sustain, Pitch Bend, velocity or another controller.

The new one Link CCs-Button holds the currently selected Piano Roll CC lane when changing tracks or regions. When activated, the current CC is adopted as the target. If you then select a different CC via Stream Deck, iPad or shortcut, this new value becomes the link target. The button displays the linked CC, shows the active state in green and the deactivated state in red.

What a button can know

Good first stream deck pages

• Transportation and navigation.
• Bouncer Tool Startup and export folder.
• Plugin Quick Insert and library presets.
• Articulations 1 to 32.
• MIDI CC, Velocity and Piano Roll.
• Window: Bouncer Tool, Motion, Plugins & Patches, Bus FX, scripts, shortcuts.

iPad Remote

Ben's Toolbox Remote is the touch interface for iPad. It connects to the Mac app over the local network. The Mac app provides tool catalog, window list, text, images, presets, articulation status, Bouncer Tool data and UAD console mixer status.

UAD mixer

The iPad Remote can directly display and control selected UAD console mixer functions. The Mac app reads the UAD console state, prepares channel strips, inserts, plugin parameters, preamp controls, sends, cue/aux sends, talkback and session information and synchronizes them with the iPad.

The UAD Mixer is available as its own iPad page and is powered via the Mac app. It is intended for studio situations in which UAD Console runs on the Mac, but levels, sends, inserts or cue mixes should be accessible directly on the iPad.

Tool catalog

The catalog contains Bounce, plugins, performances, mixing, audio, MIDI, articulations and utilities. Many tools have parameters, search lists or status feedback.

Section Presets

Bouncer Tool on the iPad

The iPad can control the complete Bouncer flow: Project via Save or Save As backup, accompany analysis, restore sessions, add visible logic tracks as rounds, load presets, edit rounds, run Preflight Only and start the actual Bounce. When opening the Bouncer page, the iPad Remote requests secure boot from the Mac app. Presets, dictionary, Name Presets, Audio Settings presets, Bounce Versions, track list, round structure and status are then continuously synchronized.

When a Main Preset is loaded, the iPad Remote sees the resulting Bounce Versions, Bounce-Rounds, track selections and audio settings assignments. Rounds can be renamed, tracks can be added or removed from a round using drag-and-drop, and Bounce Versions that are no longer needed can be deleted. The actual Logic execution remains on the Mac so scanning, export path, WebSocket status and automation are controlled in one place.

Since track numbers remain relevant for later mute/solo/select control, the visible track structure should not be changed outside of the Bouncer window while the Bouncer is open. A restored session automatically resets its saved track stack state before preflight. New changes to the structure should only be made via the Bouncer and then reread.

Articulations on the iPad

The iPad app can display active articulations, trigger slots and work with background images. Your own images can be made available via the Mac app; Large, iPad-compatible images are recommended.

In the articulation area there is a toggle in the lower MIDI-CC bar on the right Link CCs. If you activate it, Ben's Toolbox remembers the currently visible piano roll CC lane and tries to restore this lane even after track or region changes. This is helpful if you want to edit the same controller on several orchestral voices one after the other, for example modulation or expression. If no piano roll automation is visible, the CC should first be opened manually in Logic so that the target value is clear.

iPad page for articulations

On the iPad, articulation sets are presented as a separate performance page. At the top you can see the connection to the Mac, the active track and the articulation set read. The large tiles trigger the playing techniques directly; Each generated MIDI event is mapped via the playing technique and velocity. Velocity uses Logic coloring so that recorded articulation changes can be quickly recognized later in Logic. The active articulation can be reported back in color when the CC Monitor is used on the logic track.

Grid, pages and buttons

The iPad grid can be built as a large, template-specific control surface. Pages and sections structure the buttons by work area: prompts, logic tools, helpers, gain/Fade, articulations or your own setups. This means that even a very large button layout can be used without having to put everything on a single layer.

Live articulations with feedback

For sample libraries with many playing techniques, the articulation system is one of the most important workflows. Ben's Toolbox reads the articulation set of the active track, builds a remote representation from it and displays the slots on iPad and Stream Deck. When switching, the active state can be reported back.

If the CC Monitor is on the logic track as MIDI FX, MIDI recall can help to better track the current articulation state. This ties the iPad interface closer to the actual musical state: press button, Logic receives the articulation, feedback goes back to iPad and Stream Deck.

Articulation options

• Trigger slots 1 to 32 directly.
• Read current articulation set.
• Show active playing technique on iPad and Stream Deck.
• Use articulation backgrounds from your own images.
• Use automatic labels from Logic articulation names.
• Assign manual names when Logic names are too long or impractical.
• Use MIDI recall via CC Monitor if the status should be reported back reliably.
• Link CCs Use if you want to keep the same Piano Roll CC lane open when switching between tracks or regions.

iPhone Motion

Ben's Toolbox Motion uses motion and optionally position data from the iPhone to control MIDI CC, Pitch Bend, articulations and performance parameters. The configuration is in the macOS app so that mappings and display can be changed without adjusting the iPhone app.

The iPhone app provides the movement data; the actual configuration is on the Mac. This allows new mappings, presets, CC targets and activation gestures to be changed without customizing the iPhone app itself.

Bouncer control on iPhone

The iPhone Motion app can also operate the Bouncer. Using the Bouncer panel, you select a Main Preset, load the preview with Bounce Versions, Bounce-Rounds, round tracks, cycle/audio/master FX details and start the prepared run directly from the iPhone. The actual Logic execution remains on the Mac.

While a run is in progress, the iPhone app shows status, current round and progress. It can cancel the run and display local iOS notifications for iPhone-started runs, completed rounds, and optionally Mac-started completions. These local notifications work as long as the app can receive status messages; fully reliable background pushes need APNs infrastructure.

Articulations with the volume buttons

An important iPhone motion tool is articulation control via the volume buttons. The existing playing techniques are directly available for selection for the currently recognized articulation set. The assignment is automatically saved for each recognized set; Alternatively, settings can also be saved manually as a preset and reloaded.

Each volume button can hold two articulations: a main slot and a toggle slot. If you press the button while the main slot is active, it will jump to the toggle slot. If the toggle slot is active, it jumps back to the main slot. If neither articulation is currently active, the main slot is set first; with repeated use, the button switches between both slots. This allows a single volume button to be used e.g. B. switch between legato and tremolo or between staccato and pizzicato.

Mapping basics

• Source: Sensor, AR position or other motion data.
• Axis: e.g. B. X, Y, Z or derived directions.
• Direction: only above, only below or bidirectional.
• Goal: MIDI CC, Pitch Bend or internal Ben's Toolbox action.
• Range: minimum and maximum MIDI value.
• Starting value: Value when activated or in neutral state.
• Activation trigger: Movement that first activates a lane.

Pitch Bend and vibrato

Pitch Bend should not constantly react to every small movement. Therefore an activation gesture can be used. When activated, the current iPhone height is set as the zero point. A clean sine wave can be used for vibrato; The movement then determines intensity or activation rather than the actual shape of the curve.

Live preview

The Motion Live Preview shows mappings, values ​​and curves. Sine Vibrato uses a true sine representation to show what is being sent musically.

Typical mappings

Activation triggers

Each lane can optionally only be activated by a different movement. This prevents normal hand movements from immediately sending MIDI. Example: Z axis forward activated Pitch Bend; only then does the height control the vibrato intensity. If the iPhone is withdrawn, Pitch Bend is deactivated again.

Window Catalog

These windows can be opened remotely via iPad or Stream Deck:

• Bouncer Tool
• Plugins & patches
• Bus FX Settings
• Motion
• Scripts
• Shortcuts
• Articulations

System windows such as Settings, License or About are not offered as a remote catalog in the same way.

Tool options at a glance

This table summarizes which parameters the most important tools typically have and why they are relevant in practice. The specific selection may vary depending on the tool catalog, scan status and logic context.

FAQ & Troubleshooting

Which components do I really need?

The macOS app is the center and is always needed. Stream Deck Plugin, iPad Remote and iPhone Motion are additional user interfaces. Without the Mac app running, you cannot control Logic Pro.

What permissions does Ben's Toolbox need?

The app requires macOS operating aids so that Logic Pro can be read and controlled reliably. Network access, MIDI and access to local files may also be relevant for certain functions.

Why does Logic blink when triggering articulations?

When triggering articulations live via iPad or Stream Deck, if the Piano Roll is not in focus, Logic may flash briefly or visibly change focus. The reason is not a bug in the function, but rather that the wrong window for setting the articulation is active. The articulation is still triggered; flashing does not affect functionality. If it bothers you, click on the piano roll once. As long as the Piano Roll remains the active window, the flashing disappears.

Stream Deck Plugin is not recognized

Check whether the Elgato Stream Deck app is installed, the Ben's Toolbox plugin appears in the Stream Deck plugin list and Ben's Toolbox has been restarted after installation. If an old version is installed, the Mac app update window should offer the Stream Deck update.

Logic MIDI Device is missing or MIDI devices respond incorrectly

When starting, Ben's Toolbox checks whether its own Logic MIDI device is present. If it is missing, it will be installed automatically after a backup of the Logic Control Surface file. If the device does not appear or other MIDI devices then react unexpectedly, exit Logic Pro, open in Ben's Toolbox Setup > MIDI Device Manager and use Re-Install Device or Restore MIDI Device File. The legacy installer and manual installation are fallbacks if the automatic file setup does not work on a system.

iPad cannot find the Mac

iPad and Mac must be on the same local network. Also check that Ben's Toolbox is running, the remote connection is active in the Mac app and no firewall is blocking the local WebSocket port.

iPhone Motion feels delayed

If possible, use a stable local WiFi and check in the Motion window whether Live Preview and unnecessary windows are closed. With AR mappings, the position can be smoothed more than pure sensor signals.

Bouncer Tool does not find tracks or does not start

Check that Logic is open, the project is fully loaded, and Ben's Toolbox can read the current Logic project file or autosave file. Save the project manually once if the project path is not yet stable. For large templates, rereading them after they have fully loaded can help.

If track selection, mutes or solos do not fit the visible structure, track stacks outside of the Bouncer have probably been collapsed or expanded. Establish the desired visibility in Logic, reopen the Bouncer or read the tracks again and rebuild the affected round.

Where can I find logs and support information?

Logs are located in the user folder Library/Logs/BensToolbox or in the app support/log area of ​​the installed version. For support, app version, macOS version, Logic version and a short description of the reproducible flow are helpful.

A button doesn't do anything

Check that Ben's Toolbox is running, Logic is open, accessibility features are enabled, and the action works directly in the Mac app.

Lists are empty or incomplete

Scan into plugins & Repatch the affected category. Then reconnect iPad or Stream Deck or reload the catalog.

Articulation status is incorrect

Check active track, save project once or wait for autosave and put CC Monitor on the track as MIDI FX. Ben's Toolbox now prefers to read articulation sets, CC monitor instances and plugin information via the Logic project index; Manual AX reading is usually no longer necessary.

Motion affects incorrect values

Check mapping lane: target, axis, range, direction and activation condition. For Pitch Bend, also check the pitch bend range in the instrument.

Release Notes

Here you will find the most important changes to the current versions of Ben's Toolbox.