Flow 2 Installation guide

2.1. Windows users

LoopMidi is a simple free application that allows you to create midi ports.

You can download LoopMidi from this page 1

2.2. Mac users

Mac users can use the native MIDI solution to create the necessary midi ports.

To do this go in Window > Show MidiStudio Click ‘choose midi configuration’ and then ‘new configuration’ (or click on the red square image).

Finally add the new ports as listed in the previous page while keeping blank the name of the configuration and ensuring to click on the activate checkbox.

Please make sure to leave empty the name of the device which by default is IAC, if the ports do not have the same name the communication between Flow+ and Cubase will not work

4.1. Project logical presets

The first step to configure Cubase is to import the logical presets which are used by Flow application to control Cubase.

To do that you need to import the content of the folder Setup/Project Logical Editor into your Cubase folder Presets/Project Logical Editor (copying whole Flow2 folder).

Mac location:
User/Library/Preferences/Cubase/Presets/Project Logical Editor

Win location:
C:/Users/[your user]/AppData/Roaming/Steinberg/Cubase/Presets/Project Logical Editor

Win location for Cubase 12:

C:/Users/<user name>/Documents/Steinberg/Cubase/User Presets.

Copy the entire Flow folder with all its content into the Cubase Project Logical Editor folder.

4.2. Generic remotes

To setup Cubase you need to create one generic remote for each generic remote file located in the generic remote folder.

A generic remote can be added from Cubase in the menu Studio → Studio Setup → + Add device → Generic Remote, after creation import the generic remotes that are part of the Flow2 files you have downloaded. You also need to import the quick controls one in the standard “Track quick control” generic remote of Cubase.

After importing a generic remote set the midi input and output as specified in the name of the file (the in port in the out field)

NB if there are more than one file for one port (for example you have Flow_actions_flow1(1).xml and Flow_actions_flow1(2).xml) you just need to create another generic remote with the same port setting and import that second file into it

Flow_selection_flow-main.xml

Flow_actions_flow1(1).xml

Flow_actions_flow1(2).xml

Both must be imported in two different generic remotes mapped to flow-1-out

Flow_actions_flow3(1).xml

Flow_quick controls_flow-main.xml

4.3. Setup expression map remote mode

You need to change the way Cubase receives trigger to change articulations from a remote. The default setup is with a MIDI CC, you will need to switch to program change since this is the way Lemur communicate with Cubase to ask for an articulation switch.

Cubase will later transform this Program Change message into a MIDI CC and sent it through to Vienna which will then apply the change.

To change this parameter open the Flow2 Cubase project, select any instrument track, go to expression map, click setup Expression Maps (bottom of the long list) and in the dialog window set to Program change the parameter as shown in the picture on the left.

A restart of Cubase is required to make the copied presets available in the Project logical editor window

4.4. Project preferences settings

Open the Preferences settings located in the Edit menu and make sure the option “Enable Record on Selected Midi Track” is checked otherwise Cubase will not be able to send info on the selected track to Flow+

5.1. Import data from Flow template

Flow+ needs json data to visualize its content, when you purchase Flow+ it comes with no data. The data is purchased separately within template products and needs to be imported in the app folder.

To do so click on the import function (third button from right) in the top menu of Flow+

Finally select the folder from the template where the json data is located e.g. c:\Flow. cv Professional\03 Flow+

And decide to

• Erase all content clicking on the reset button
• Import all data
• Import just a set of the available libraries

Please note that you will need to restart Flow+ after changing the data content to see it applied

5.2. Installation

Starting from version 1.7 of Open Stage Control the installation is pretty simple, all required libraries are bundled in the downloaded package so all you need to do is download the latest version from this page 2 and run it.

5.3. Configuration

When launching for the first time you need to do the following settings:

• port: 5000 (or the one you prefer)
• midi: copy and paste this value flow:flow-main-in,flow-main-out flow1:flow-1-in,flow-1-out flow2:flow-2-in,flow-2-out flow3:flow-3-in,flow-3-out
• theme: select the flow.css file located in the css folder of Flow+ source
• instance-name: flow+ or as you like
• load: select the artificialharmonics.com_flow+_osc-data.json file located inside flow+ sources folder
• custom-module: select the artificialharmonics.com_flow+_custom-module.js file located inside flow+ sources folder

5.4. Important for Mac users, launch the server with root rights

Fixed with the new version 1.0.1! Download the new version and just run the server normally

5.5. Authenticate the machine

With the order you have received a license key which allows you to use the application in one server at the time (but all the clients you need).

At the first launch you will need to validate the license and authorize the machine. You can do so clicking on the key button located in the top menu.

Insert the email address used to purchase Flow+ and the license you have received with your order, then click activate (or reset if you want to use Flow+ on a different machine)

Please note that Flow+ requires an internet connection to check the license, if this is not possible for more than 10 days the password will be reset and a new activation will need to be performed.

It is necessary to restart the application after the activation is fully validated