![]() Setting up your Focusrite Audio interface in Studio One is very similar to older versions of the software, however it is important to keep in mind that some of the MENU titles have changed in addition to where they are located. This process differs slightly between Windows and Mac. In this tutorial we are using the Scarlett 18i8 2nd Generation on a Windows PC (Windows 10 to be exact) in Studio one 3. For all versions of Studio One, input and output configuration will be necessary to ensure an efficient signal path from your Focusrite interface is established. This will open Studio One's main OPTIONS MENU where most of the Global Settings for your audio inputs, outputs, MIDI instruments and others settings are modified. In the following screenshot you will see Studio One's AUDIO SETUP menu. Here is where our Scarlett 18i8 will show up but will be not be listed as a Scarlett 18i8. As you see, selecting Focusrite USB corresponds to the 18i8. Under the PROCESSING tab in the same menu is where we modify other settings. "Process Block Size" pertains to the BUFFER settings for your recording sessions and this will vary from one system to the next and may have to be modified to compensate for higher CPU levels when projects themselves become more abundant with tracks, VSTs, plugins, group tracks, sends & returns, macros and other extensions. ![]() is a MIDI Logging Script with logical switches for Orba 1/2 eventsīut also useful as a generic MIDI logger.The Focusrite ASIO Control Panel must also match up to these settings as well to ensure that no clocking or other sync errors occur which may severely cripple any recording session. I will use the 4 Knobs in the next version to change specific CC’s from the Orba 2, 74, 112 and 113 so it’s not an Orba Exclusive script. This script can isolate specific CC numbers and only log those event. Better for my needs than MIDI Spy or other since they present too much data. A Musical Instrument Digital Interface (MIDI) is a protocol that facilitates communication between external musical instruments and your computer. It does not need to be driven my an Orba: it’s a MIDI Monitoring (using Mozaic Logging) and Filtering app. This is the current version of the script which for a Mozaic hacker is good enough to install and test the script. Otherwise, it’s best to just use them as triggers for specific events like loop launching or Muting. ![]() Ideally a CC controller is smooth and predictable when in use. I’m still wondering what to do with “Shake, Radiate, Spin, Move” but Monitoring them in isolation is the key to seeing what they send and what kind of range they have. The Spire Vision 7025 RGB is a midi monitor with a surprising design. The Orba folks set up pitch bend as a semitone deviation form mid-centerline pad touches but fingers are fat can cover 25% of a pad’s width so it’s only useful for a mild vibrato and NOT the Note Glide/Silde we can get from a Roli MPE controller so it’s NOT that type of experience. Spire Vision 7025 RGB glass design midi tower with RGB lighting - This PC case is. Orba doesn’t really have a gesture that fits that model. The script has helped me understand the MPE features of the Orba and why PitchBend and Mod wheel really need to be a spring loaded wheel or joy stick that goes home to a center position to get you back in tune or stop that unwanted tremolo. That counter is buggy as hell so at times I down load dozens of my scripts to assuage my ego. Using the AUM Project and hitting save in Mozaic will also get you the file and cheat me of a Download count in PatchStorage. It’s a work in progress and I’ll put it up on Patchstorage soon in an AUM Project which loads Mozaic with it ready to go and as a Mozaic script for anyone to download and add to their Mozaic files. I created a Mozaic script to Monitor and Filter Orba MIDI Output so I can use it with MIDI Learn features in AUM and synths. 4 Knobs are exposed to allow for custom CC Monitoring and Forwarding. It’s set up by default for 4 specific MIDI CC’s (Shake, Radiate, Spin, Move). It can also pass the selected MIDI types which is useful for targeting specific MIDI types when Using MIDI Learn and the controller is outputting a simplex stream that needs filtering to choose the right MIDI event for mapping. Touching a PAD and turning it RED enables Logging of that MIDI Type or CC. This Script Monitors incoming MIDI and has PAD switches to enable/disable MIDI Types and Selectable CC’s. The Mozaic script “MIDI-Monitor-Filter-Logger” is also ready for downloads and use: ![]() The AUM Project to load the Mozaic “MIDI-Monitor-Filter-Logger” script is ready for downloads and user input: ![]()
0 Comments
Leave a Reply. |