Another round of frequently asked questions, random findings and other lore from the realms of Bitwig Studio! :-)
Not totally obvious: CTRL clicking a Track Fader or Pan/Send Knob shows the numeric value ready for entering a new one:
Also not really obvious: If you select a Clip in the Clip-Launcher and then hit CTRL-A, the Row is selected, but hit it again and the Scene is selected:
When editing Automation: ALT-dragging on a connection line bends it up or down, CTRL-dragging moves the line segment up or down and ALT-dragging on a Point creates a S-Curve around it:
To move automation points only in one axis, select them and use the arrow keys to move them up and down. Press SHIFT at the same time for smaller increments.
Press ALT + arrow keys to move the selected points to the left and right, again, holding SHIFT will give you smaller increments.
The left and right arrows without a modifier select the automation points on the left or right, holding down SHIFT allows to select several points with the keyboard.
As of Bitwig Studio 1.1, we can now completely deactivate tracks, device layers and devices so they no longer use CPU. The global shortcut for this is ALT-A.
Renaming of things was very inconsistent before 1.1 and has now been streamlined in most areas to ALT-clicking for instance a track title or a device-panel-mapping name.
A persistent Application Shortcut:
On Windows, if you drag the application shortcut from the start menu to the desktop and later on update Bitwig Studio, the link no longer works since it is somehow version specific. But if you go to the Bitwig Studio installation folder instead and drag “Bitwig Studio.exe” to the desktop while holding the ALT-key to create a shortcut, this shortcut will from then on work independent of the Bitwig Studio version you have installed.
As of Version 1.1.3, Bitwig Studio finally has Input-Quantize.
I didn’t find it at first so if you are in the same boat, here it is, in the recording dropdown of the transport panel:
The Project- and I/O-Panels:
Many people miss the additional panels in the browser pane, so let’s have a look:
Down at the bottom right of the window, you have 3 icons for Browser, Project Panel and I/O Panel:
Since the browser is obvious, let’s look at the other two panels: The Project Panel holds first an „Info“ tab where you can enter a project title, author, description and all kinds of notes you may want to keep for the current project:
But maybe the most important tab is: Used Files, here you see a searchable list of all files used in the project. You have options to show all, show only external files (that is, files not in the project folder) and missing files (files that belong in the project and are used but that can’t be found):
In addition to the tools for the individual files, at the bottom you have buttons for „Find all“, which brings up a folder selector you can use to show Bitwig Studio where it should look for the files. „Collect and Save“, which allows you to copy all external files into the project and finally „Delete unused“ to remove unused files (for instance if you recorded many takes and on finishing the project you want to delete all that didn’t make it into the final version to clean up.
Be very careful with this last function, it may delete files you use elsewhere or that you inserted manually in some subfolder of the project!
At the bottom you have the pre-listen facilities you are familiar with from the main browser.
The Used Plugins tab works pretty much the same, it shows all plugins you use in your project, shows missing plugins and if there is a version conflict (project uses a newer version than the one installed).
Finally there is the Studio I/O panel:
At the top you select your monitor output and what should be used for cueing.
Below that you can see all the controllers you have active in preferences and all the User Mappings you assigned with midi-learn. From here, you can delete those assignments globally.
As of Bitwig Studio 1.1, there is an additional use for this panel:
The latest API version allows controller script authors to define settings for the script in preferences (global settings) as well as in the studio I/O panel (project specific settings). It’s totally up to the scripter what is shown here, but as an example it would be possible to have a dropdown with all possible scales for a grid controller here and each project would then be able to save the scale and restore it on reload.
In the screenshot above it shows the controls of my Generic Midi-Learn script.
Speaking of the new settings for controller scripts (Options -> Preferences -> Controllers):
Since Bitwig Studio 1.1, each controller script has four new icons below it’s title:
The Gear-icon opens and closes the settings for the controller (if there are any).
The Bubble-icon enables and disables visual on-screen feedback from the controller.
The Circular-Arrow-icon reloads the script. Some settings need this to be activated.
The Questionmark-icon opens the help file for the controller (if any).
Everything else on above screenshot is controls that I implemented for the before-mentioned Generic Midi-Learn script.
Oh, and you can now double-click on the white part of the controller name and change it, so that even generic scripts show up in the input list with a distinctive name. :-)
That’s it for now,