Steinberg Cubase 5 Operation Manual
Have a look at the manual Steinberg Cubase 5 Operation Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 523 Steinberg manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
392 The Project Logical Editor Introduction On the Edit menu you will find the function “Project Logical Editor…”. This opens a Project Logical Editor for the entire project. It works similar to the Logical Editor on the MIDI menu, see the chapter “The Logical Editor, Transformer and Input Transformer” on page 380. The most important difference is that the Logical Editor for MIDI works at the event level, whereas the Project Logical Editor works at the project level and is therefore a very powerful tool for “search and replace” functions in your entire project. ÖThe MIDI events in the MIDI parts will not be affected by the Project Logical Editor operations. If you want to change MIDI notes or controller data, you have to use the Logical Editor. With the Project Logical Editor, you can combine filter conditions with actions to create complex procedures, e.g. for special track type operations on tracks that are named identically. You can use its functions to delete all muted MIDI parts or to toggle the open state of all folder tracks in your project, etc. Included with the Project Logical Editor are a number of presets that give you an impression of the great possibili- ties that this feature offers, see “Working with presets” on page 399. Many of them can also be used as starting points when you set up your own editing operations. The principle for the Project Logical Editor is this: You set up filter conditions to find certain elements. This could be elements of a certain type, with certain attributes or values or on certain positions, in any combination. You can combine any number of filter conditions and make composite conditions using AND/OR operators. You select the basic function to be performed. The options are Transform (changing properties of the found elements), Delete (removing the elements) and Select (selecting the found elements). You set up a list of actions, which specify exactly what should be done. This is not necessary for all functions. For example, the Delete function does not require any additional action specifications – it simply removes all found elements. In the Macro pop-up menu you can choose an additional macro that will be executed after the actions you defined. Use this to extend the possibilities offered by combining the filter condi- tions and actions specified in the Project Logical Editor even further. By combining filter conditions, functions, the specific ac- tions, and additional macros, you can perform very power- ful processing. Opening the Project Logical Editor 1.Open the desired project. All elements in the project will be affected, you do not have to make any selection. 2.Select “Project Logical Editor…” from the Edit menu. Window overview To understand the Project Logical Editor, it might be a good idea to start by exploring the included presets. These are found on the Presets pop-up menu at the top of the window. For information on how to create and handle your own presets, see “Working with presets” on page 399. !The Project Logical Editor allows all kinds of settings that may not always make sense. Experiment a bit be- fore applying your edits to important projects. You can undo the operations by using the Undo command on the Edit menu. Function and Macro pop-up menus Presets pop-up menu List of filter conditionsAction ListApply button
393 The Project Logical Editor Setting up filter conditions General procedure The upper list is where you set up the filter conditions, de- termining which elements to find. The list contains one or several conditions, each on a separate line. To add a new condition, click the Add button (+) below the list. The new line is added at the bottom of the list. If there are many lines, you may need to use the scrollbar to the right to view them. To remove a condition, select it and click the Delete button (-) below the list. ÖIf you have already defined filter conditions and/or ap- plied a preset, but want to start again from scratch, you can initialize the settings by selecting the Init option from the Presets pop-up menu. You set up a filter condition line by clicking in the columns and selecting options from the pop-up menus that appear. Here is a brief description of the columns:Below, the different Filter Targets (and their corresponding Condition and Parameter options) are described in more detail. Searching for Media types 1.Select “Media Type” in the Filter Target pop-up menu. This allows you to find elements of certain types of media only. 2.Open the pop-up menu in the Parameter 1 column and select the desired option. When the Filter Target is set to Media Type, the pop-up menu lists the available media types. The following table lists what will be found: Column Description Left bracket This is used for “bracketing” several lines together when creating conditions with multiple lines and the boolean operators And/Or. See “Combining multiple condition li- nes” on page 396. Filter Target Here you select which property to look for when finding elements. Your choice here affects the available options in the other columns as well, see below! Condition This determines how the Project Logical Editor should compare the property in the Filter Target column to the values in the Parameter columns (see below). The avail- able options depend on the Filter Target setting. Parameter 1 Here you set which value the element properties should be compared to (depending on the Filter Target). For example, if the Filter Target is “Position” and Condi- tion is “Equal”, the Project Logical Editor will look for all elements starting at the position you specify in the Pa- rameter 1 column. Parameter 2 This column is only used if you have selected one of the “Range” options in the Condition column. Typically, this allows you to find all elements with values inside (or out- side) the range between Parameter 1 and Parameter 2. Bar Range/ Time BaseThis column is only used if the Filter Target is set to “Po- sition”. If one of the “Bar Range” options is selected in the Condition column, you use the Bar Range/Time Base column to specify “zones” within each bar (allowing you to find e.g. all elements on or around the first beat of ev- ery bar). If any of the other Condition options is selected, you can use the Bar Range/Time Base column to specify the time base (PPQ, Seconds, etc.). See “Searching for elements at certain positions” on page 395. Right bracket This is used for “bracketing” several lines together. See “Combining multiple condition lines” on page 396. bool This allows you to insert the boolean operators And/Or, when creating conditions with multiple lines. See “Com- bining multiple condition lines” on page 396. Media Type Description Audio If no container type is specified, this finds audio events, audio parts and audio tracks. MIDI If no container type is specified, this finds MIDI parts and MIDI tracks. Automation If no container type is specified, this finds automation events and automation tracks. Marker If no container type is specified, this finds marker events and marker tracks. Transpose If no container type is specified, this finds transpose events and transpose tracks. Arranger If no container type is specified, this finds Arranger events and Arranger tracks. Tempo If no container type is specified, this finds tempo events and tempo tracks. Signature If no container type is specified, this finds signature events and signature tracks. Column Description
394 The Project Logical Editor 3.Open the pop-up menu in the Condition column and select the desired condition. For media types, the following options are available: For example, if you have set up the Project Logical Editor like this… …it will find all Marker events and tracks in the project. Searching for Container types 1.Select Container Type in the Filter Target pop-up menu. This allows you to find parts, events or tracks. 2.Open the pop-up menu in the Parameter 1 column and select the desired option. When the Filter Target is set to Container Type, the pop-up menu lists the available container types. The following table lists what will be found: 3.Open the pop-up menu in the Condition column and select the desired condition. For container types, the following options are available: For example, if you have set up the Project Logical Editor like this… …it will find all Folder tracks in the project. Combining Media Type and Container Type The combination of the filter targets Media Type and Con- tainer Type represents a versatile tool for logical operations: Here, the Project Logical Editor will find all MIDI and instrument parts in the project. Here, the Project Logical Editor will find all automation tracks (not events) in the project whose name contains vol. Here, the Project Logical Editor will find all MIDI and instrument parts (not tracks) in the project that are muted. Here, the Project Logical Editor will find all MIDI and instrument parts (not tracks) or all audio events (not parts or tracks) in the project that are muted. Searching for Names 1.Select Name on the Filter Target pop-up menu. 2.Enter the desired name, or a part of a name in the Pa- rameter 1 column. 3.Open the pop-up menu in the Condition column and select the desired condition. For names, the following options are available: Condition Description Equal This finds the Media Type set up in the Parameter 1 column. All Types This finds all Media Types. Container Type Description Folder Track This finds all folder tracks, included FX Channel and Group Channel folders. Track This finds all track types. Part This finds audio, MIDI and Instrument parts. Folder parts will not be found. Event This finds automation points, markers, as well as au- dio, arranger, transpose, tempo and time signature events. Condition Description Equal This finds the Container Type set up in the Parameter 1 column. All Types This finds all Container Types. Condition Description Equal This is the exact same text string as set up in the Parameter 1 column. Contains This contains the text specified in the Parameter 1 column.
395 The Project Logical Editor For example, if you have set up the Project Logical Editor like this… …it will find all tracks in the project whose name contains “voc”. ÖTo take maximum advantage of this feature, we recom- mend using a standard nomenclature in your projects (Drums, Perc, Voc, etc.). Searching for elements at certain positions 1.Select “Position” in the Filter Target pop-up menu. This allows you to find elements starting at certain positions, either rela- tive to the start of the project or within each bar. 2.Open the pop-up menu in the Condition column and select the desired condition. For positions, the following options are available: If you select any condition other than the Range, Bar Range, Cursor, Loop or Cycle options, you set up a spe- cific position (in PPQ, seconds, samples, or frames) in the Parameter 1 column. Use the Bar Range/Time Base col- umn to specify the time base. Note that the position for Bar Range is measured in ticks related to the start of the bar. Here, the Project Logical Editor will find all elements at the PPQ posi- tion 5.1.1. in the project. If you select Inside Range or Outside Range in the Con- dition column, you set the start position of the range in the Parameter 1 column and the end position in the Parameter 2 column. You can also change the time base using the Bar Range/Time Base column. The Project Logical Editor will then find all elements inside or outside this position range. If you select one of the Bar Range options in the Condi- tion column, the Bar Range/Time Base column will show a graphic bar display. You specify the range within the bar by clicking and dragging in the bar display (the specified Bar Range is indicated in blue). The Project Logical Editor will then find all elements starting inside or outside this Bar Range, in all bars (within the current selection). Here, the Project Logical Editor will find elements starting around the second beat in each bar. Condition An element will be found if it… Equal …has the exact same value as set up in the Parameter 1 column. Unequal …has any value other than the one set up in the Parame- ter 1 column. Bigger …has a value higher than the one set up in the Parameter 1 column. Bigger or Equal…has a value that is the same as or higher than the one set up in the Parameter 1 column. Less …has a value lower than the one set up in the Parameter 1 column. Less or Equal …has a value that is the same as or lower than the one set up in the Parameter 1 column. Inside Range …has a value that is between the values set up in the Pa- rameter 1 and Parameter 2 columns. Note that Parameter 1 should be the lower value and Parameter 2 the higher. Outside Range …has a value that is not between the values set up in the Parameter 1 and Parameter 2 columns. Inside Bar Range…is within the “zone” set up in the Bar Range/Time Base column, in each bar within the current selection. Outside Bar Range…is outside the “zone” set up in the Bar Range/Time Base column, in each bar within the current selection. Before Cursor …is before the song Project position. Beyond Cursor …is after the song Project position. Inside Track Loop…is inside the set track loop (see “The independent track loop function” on page 257). Inside Cycle …is inside the set cycle. Exactly match- ing Cycle…exactly matches the set cycle. Condition An element will be found if it…
396 The Project Logical Editor Searching for elements of certain lengths 1.Select Length in the Filter Target pop-up menu. This allows you to find elements of a certain length only. The Length pa- rameter is interpreted via the time base setting in the Bar Range/Time Base column, i.e. in PPQ, seconds, samples, or frames. 2.Open the pop-up menu in the Condition column and select the desired condition. For lengths, the following options are available: If you select any condition other than the Range options, you set up a specific position in the Parameter 1 column. Here, the Project Logical Editor will find all audio parts and events in the project with a length smaller than 200 samples. Searching for properties 1.Select “Property” on the Filter Target pop-up menu. 2.Open the pop-up menu in the Condition column and select the desired condition. When the Property option is selected, the Condition column has two op- tions: “Property is set”, and “Property is not set”. 3.Open the pop-up menu in the Parameter 1 column and select the desired option. This sets which property will be searched. The options are “Event is muted”, “Event is selected”, and “Event is Empty”. ÖNote that “event” in this context refers to all the Project window elements that can be modified, e.g. MIDI parts, audio events and parts, or transpose, arranger, and auto- mation events. Three examples: Here, the Project Logical Editor will find all muted MIDI and instrument parts. Here, the Project Logical Editor will find all elements that are selected but not muted. Here, the Project Logical Editor will find all selected audio parts that are empty. Combining multiple condition lines As described above, you can add condition lines by click- ing the Add button (+) below the list. The result of com- bining condition lines depends on the boolean And/Or operators and the brackets. The bool column By clicking in the “bool” column to the right in the list, you can select a boolean operator: “And” or “Or”. A boolean operator combines two condition lines and determines the result in the following way: If two condition lines are combined with a boolean And, both conditions must be fulfilled for an element to be found. The Project Logical Editor will only find MIDI tracks. Condition An element will be found, if it… Equal …has the exact same value as set up in the Parameter 1 column. Unequal …has any value other than the one set up in the Parame- ter 1 column. Bigger …has a value higher than the one set up in the Parameter 1 column. Bigger or Equal…has a value that is the same as or higher than the one set up in the Parameter 1 column. Less …has a value lower than the one set up in the Parameter 1 column. Less or Equal …has a value that is the same as or lower than the one set up in the Parameter 1 column. Inside Range …has a value that is between the values set up in the Pa- rameter 1 and Parameter 2 columns. Note that Parameter 1 should be the lower value and Parameter 2 the higher. Outside Range …has a value that is not between the values set up in the Parameter 1 and Parameter 2 columns.
397 The Project Logical Editor If two condition lines are combined with a boolean Or, one of the conditions (or both) must be fulfilled for an ele- ment to be found. The Project Logical Editor will find all parts or events that match exactly the cycle. Using brackets The bracket (parenthesis) columns let you enclose two or more condition lines, dividing the conditional expression into smaller units. This is only relevant when you have three or more condition lines and want to use the boolean Or operator. You add brackets by clicking in the bracket columns and selecting an option. Up to triple brackets can be selected. Without brackets, the conditional expressions are eval- uated according to their order in the list. Here, the Project Logical Editor will find all audio parts and events whose name contains perc as well as other parts and events (e.g. MIDI parts) whose name contains drums. Maybe you want to find all audio parts and events that ei- ther had the name perc or the name drums (but no other parts or events named drums)? Then you need to add some brackets: Here, all audio parts or events will be found whose name contains perc or drums. ÖExpressions within brackets are evaluated first. If there are several layers of brackets, these are evaluated “from the inside out”, starting with the innermost brackets. Specifying actions The lower list in the Project Logical Editor window is the action list. This is where you specify any changes that should be made to the found elements, relevant for the function type Transform. You can perform two different kinds of actions: track-based actions (such as Track Operation, Name) and event-based actions (such as Position, Length, Name). There are also actions that only take effect on automation data (Trim). The handling of the action list is similar to the filter condi- tion list, but without the brackets and booleans. You sim- ply add lines by clicking the Add button (+), and fill out the columns as required. To remove a superfluous action line, select it and click the Delete button (-). Action Target This is where you select the property that should be changed. The Operations determine what to do with the Action Target. Below, all available operations are listed: Position Adjusting this value will move the elements. This parameter is interpreted via the time base setting in the Bar Range/ Time Base column, with the exception of the Random set- ting, which uses the time base of the affected events: !When you add a new condition line, the boolean set- ting defaults to And. Therefore, if all you want to do is set up two or more conditions that all must be met for an element to be found, you do not have to think about the boolean column – just add the required lines and make the usual filter settings. Operation Description Add Adds the value specified in the Parameter 1 column to the Position. Subtract Subtracts the value specified in the Parameter 1 column from the Position. Multiply by Multiplies the Position value with the value specified in the Parameter 1 column. Divide by Divides the Position value by the value specified in the Para- meter 1 column. Round by This “rounds” the Position value using the value specified in the Parameter 1 column. In other words, the Position value is changed to the closest value that can be divided by the Pa- rameter 1 value. For example, if the Position value is 17 and Parameter 1 is 5, the result of rounding will be 15 (the closest value that can be divided by 5). Another word for this type of operation would be “quantizing”, and it is actually possible to use it for this, by specifying a quantize value with Parameter 1 (in ticks, with 480 ticks per quarter note).
398 The Project Logical Editor Length Lets you resize the elements. This parameter is interpreted via the time base setting in the Bar Range/Time Base col- umn, with the exception of the Random setting, which uses the time base of the affected events: Track Operation This lets you change the track status. Name This lets you rename the found elements. Trim This Action Target is used for automation only and lets you trim the found elements. Set Color This lets you set the color for an element. For this Action Target the only Operation available is “Set to fixed value”. To use this, insert the name of a track color in the Param- eter 1 column, e. g. “Color 7” to use dark green as track color. Set Relative Random Values betweenThis will add a random value to the current Position value. The added random value will be within the range specified with Parameter 1 and 2. Note that these can be set to nega- tive values. For example, if you set Parameter 1 to -20 and Parameter 2 to +20, the original Position value will get a random variation, never exceeding ±20. Set to fixed valueThis sets the Position to the value specified in the Parameter 1 column. Operation Description Add Adds the value specified in the Parameter 1 column to the Length. Subtract Subtracts the value specified in the Parameter 1 column from the Length. Multiply by Multiplies the Length value with the value specified in the Parameter 1 column. Divide by Divides the Length value by the value specified in the Para- meter 1 column. Round by This “rounds” the Length value using the value specified in the Parameter 1 column. In other words, the Length value is changed to the closest value that can be divided by the Pa- rameter 1 value. Set to fixed valueThis sets the Length to the value specified in the Parameter 1 column. Set Random Values betweenThis will add a random value to the current length. The added random value will be within the range specified with Parameter 1 and 2. Operation Description Folder Opens, closes or toggles folders. Record Enables, disables or toggles the record enable status. Monitor Enables, disables or toggles the monitor status. Solo Enables, disables or toggles the solo status. Mute Enables, disables or toggles the mute status. Read Enables, disables or toggles the read enable status. Write Enables, disables or toggles the write enable status. EQ Bypass Enables, disables or toggles the EQ bypass status. Inserts Bypass Enables, disables or toggles the inserts bypass status. Operation DescriptionSends Bypass Enables, disables or toggles the sends bypass status. Lanes Active Enables, disables or toggles the lanes active status. Operation Description Replace Replaces names with the text specified in the Parameter 1 column. Append Names will be appended with the string specified in the Pa- rameter 1 column. Prepend The name will be prepended with the string specified in the Parameter 1 column. Generate NameThe name will be replaced by the text specified in the Param- eter 1 column, followed by the number set with Parameter 2. The number will be increased by 1 for every found element. Replace Search StringYou can specify a search string under Parameter 1 that should be replaced by the text specified in the Parameter 2 column. Operation Description Multiply by Multiplies the Trim value with the value specified in the Parameter 1 column. Divide by Divides the Trim value by the value specified in the Para- meter 1 column. Operation Description
399 The Project Logical Editor Selecting a function The left pop-up menu at the bottom of the Project Logical Editor is where you select the function – the basic type of editing to be performed. The available options are: Delete Deletes all elements found by the Project Logical Editor. ÖWhen you delete automation tracks and undo this op- eration by selecting Undo from the Edit menu, the automa- tion tracks will be restored, but the tracks will be closed. Transform Changes one or several aspects of the found elements. You set up exactly what should be changed in the action list, see below. Select This will simply select all found elements, highlighting them for further work in the Project window. Applying Macros In the Macro pop-up menu you can select a macro that will be executed automatically after completing the actions defined using the Filter and Action lists. This is useful if you would like to extend the already powerful Project Lo- gical Editor features even further. To use this, you set up the macro that you need in the Key Commands dialog (see “Setting up key commands” on page 480) and then select it in the Project Logical Editor from the Macro pop-up menu. For example, you could use the filter conditions to select all tracks that contain automation data for a certain auto- mation parameter (such as “volume”) and use the macro “Select all on Track + Delete” to remove the automation events from these tracks (without deleting the tracks themselves). Applying the defined actions Once you have set up filter conditions, selected a function and set the required actions (or loaded a preset), you ap- ply the actions defined with the Project Logical Editor by clicking the Apply button. Project Logical Editor operations can be undone just like any other editing. Working with presets The Presets section in the bottom right section of the win- dow allows you to load, store and manage Project Logical Editor presets. A preset contains all settings in the window, which means you can simply load a preset, edit the settings (if necessary) and click Apply. To load a preset, select it from the Presets pop-up menu. If available, an explanatory text appears to the right of the menu. When setting up your own presets, you can click in this area to enter a description. You can also open the Edit menu and select Presets di- rectly from the “Process Project Logical Editor” submenu. This allows you to apply a preset directly, without having to open the Project Logical Editor. Storing your own settings as a preset If you have made Project Logical Editor settings that you want to use again, you can store them as a preset: 1.Click the Store Preset button to the right of the Presets pop-up menu. A dialog for specifying a name for the new preset is displayed. 2.Enter a name for the preset and click OK. The preset is stored. ÖTo remove a preset, load it and click the Remove Preset button.
400 The Project Logical Editor Organizing and sharing presets The Project Logical Editor presets are stored within the ap- plication folder in the Presets\Logical Edit Project subfolder (see also “Where are the settings stored?” on page 478). While these files cannot be edited manually, you can reor- ganize them (e.g. putting them in subfolders) like any files. This also makes it easy to share presets with other Cu- base users, by transferring the individual preset files. ÖThe list of presets is read each time the Project Logi- cal Editor is opened. Setting up key commands for your presets If you have stored Project Logical Editor presets, you can set up key commands for them: 1.Pull down the File menu and select “Key Commands…”. The Key Commands dialog appears. 2.Use the list in the Commands column to navigate to the category “Process Project Logical Editor” and click the plus-sign to display the items in the folder. 3.In the list, select the item to which you wish to assign a key command, click in the “Type in Key” field and enter a new key command. 4.Click the Assign button above the field. The new key command appears in the Keys List. 5.Click OK to exit the dialog. For more information on Key Commands, see the chapter “Key commands” on page 479.