Steinberg Cubase 8 Manual
Have a look at the manual Steinberg Cubase 8 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+.
File handling Exporting and importing standard MIDI files 1021 • “Import at Timecode Position” will insert the elements contained in the OMF file at their original timecode positions. This is useful when you want to position every imported element at its exact timecode position, i. e. as it was saved in the OMF file. This way, the elements will end up at their correct time positions even when Cubase uses a different frame rate than the OMF file. This is usually required in a picture-related context. • “Import at Absolute Time” will insert the elements contained in the OMF file starting at the timecode position saved in the file and keeping the relative distances between the elements. This is required when the relative positioning of the elements inside the OMF file needs to be maintained after importing it into the Cubase timeline (even if Cubase is set to a different frame rate than the OMF file). This is usually required in music contexts, where the timing between objects has highest priority. • If the OMF file contains video event information, you are asked whether you want to create Markers at the start position of the video events. This allows you to manually import the video files, using the Markers as position references. A new, untitled project is created (or tracks are added to the existing project), containing the audio events of the imported OMF file. Exporting and importing standard MIDI files Cubase can import and export standard MIDI files, which makes it possible to transfer MIDI material to and from virtually any MIDI application on any platform. When you import and export MIDI files, you can also specify whether certain settings associated with the tracks are included in the files (automation tracks, volume and pan settings, etc.). Exporting MIDI files To export your MIDI tracks as a standard MIDI file, open the File menu and select “MIDI File…” from the Export submenu. A regular file dialog opens, allowing you to specify a location and name for the file. When you have specified a location and a name for the file, click “Save”. The Export Options dialog opens, allowing you to specify a number of options for the file, e. g. what is included in the file, its type and its resolution (see below for a description of the options).
File handling Exporting and importing standard MIDI files 1022 You will also find most of these settings in the Preferences dialog (MIDI–MIDI File page). If you set these up in the Preferences dialog, you only need to click OK in the Export Options dialog to proceed. The dialog contains the following options: Option Description Export Inspector PatchIf this is activated, the MIDI patch settings in the Inspector – Bank Select and Program Select (used for selecting sounds in the connected MIDI instrument) are included as MIDI Bank Select and Program Change events in the MIDI file. Export Inspector Vo l u m e / P a nIf this is activated, Volume and Pan settings made in the Inspector are included as MIDI Volume and Pan events in the MIDI file. Export AutomationIf this is activated, the automation data (as heard during playback) are converted to MIDI controller events and included in the MIDI file. This also includes automation recorded with the MIDI Control plug-in (see the separate PDF document “Plug-in Reference”). Note that if a continuous controller (e. g. CC7) has been recorded but the Read button is deactivated for the automation track (i. e. the automation is effectively switched off for this parameter), only the part data for this controller will be exported. If this option is deactivated and the Automation Read button is activated, no Continuous Controllers are exported. If the Read button is deactivated, the Controller data of the MIDI part are exported (these will now be handled like “regular” part data). In most cases it is recommended to activate this option. Export Inserts If this is activated and you are using MIDI modifiers or any MIDI plug-ins as insert effects, the modifications to the original MIDI notes that occur as a result of the effect(s) will be included in the MIDI file. A MIDI delay, for example, will produce a number of repeats to a MIDI note by actually adding additional, “echoing” notes at rhythmic intervals – these notes will be included in the MIDI file if the option is activated. Export Sends If this is activated and you are using any MIDI plug-ins as send effects, the modifications to the original MIDI notes that occur as a result of the effect(s) will be included in the MIDI file. Export Markers If this is activated, any markers you have added will be included in the MIDI file as standard MIDI file marker events.
File handling Exporting and importing standard MIDI files 1023 NOTE The MIDI file will include the tempo information of the project (i. e. it will include the tempo and time signature events of the Tempo Track Editor or, if the tempo track is deactivated on the Transport panel, the current tempo and time signature). NOTE Inspector settings other than those specified in the Export options are not included in the MIDI file! To include these, you need to convert the settings to “real” MIDI events and properties by using the Merge MIDI in Loop function for each track. RELATED LINKS Automation on page 576 Markers on page 281 Basic track settings on page 644 Merge MIDI in Loop on page 675 Importing MIDI files To import a MIDI file from disk, proceed as follows: PROCEDURE 1. Select “MIDI File…” from the Import submenu of the File menu. 2. If there is already an open project, a dialog opens in which you can select whether a new project is created for the file. If you select “No”, the MIDI file will be imported into the current project. Export as Type 0If this is activated, the MIDI file will be of type 0 (all data on a single track, but on different MIDI channels). If you do not activate this option, the MIDI file will be of Type 1 (data on separate tracks). Which type to choose depends on what you want to do with the MIDI file (in which application or sequencer it should be used, etc.). Export ResolutionYou can specify a MIDI resolution between 24 and 960 for the MIDI file. The resolution is the number of pulses, or ticks, per quarter note (PPQ) and determines the precision with which you will be able to view and edit the MIDI data. The higher the resolution, the higher the precision. Choose the resolution depending on the application or sequencer with which the MIDI file will be used, though, since certain applications and sequencers may not be able to handle certain resolutions. Export Locator RangeIf this is activated, only the range between the locators will be exported. Export includes DelayIf this is activated, the delay of the MIDI track will be included in the MIDI file. Song name for Ty p e 0You can use this text field to change the name of the MIDI file as displayed when loading this file in a keyboard. Option Description
File handling Exporting and importing standard MIDI files 1024 3. Locate and select the MIDI file in the file dialog that opens and click Open. If you choose to create a new project, select the project folder. Select an existing project folder or create a new one. RESULT The MIDI file is imported. The result depends on the contents of the MIDI file and the Import Options settings in the Preferences dialog (MIDI–MIDI File page). The Import Options are as follows: Option Description Extract First Patch If this is activated, the first Program Change and Bank Select events for each track are converted to Inspector settings for the track. Extract First Volume/Pan If this is activated, the first MIDI Volume and Pan events for each track are converted to Inspector settings for the track. Import Controller as Automation TracksIf this is activated, MIDI controller events in the MIDI file will be converted to automation data for the MIDI tracks. If this is deactivated, controller data for the MIDI Parts will be imported. Import to Left Locator If this is activated, the imported MIDI file will be placed so that it starts at the position of the left locator – otherwise it will start at the beginning of the project. Note that if you choose to have a new project created automatically, the MIDI file will always start at the beginning of the project. Import Markers If this is activated, standard MIDI file markers in the file will be imported and converted to Cubase markers. Import dropped File as single PartIf this is activated and you drag and drop a MIDI file into the project, the whole file will be placed on a single track. Ignore Master Track Events on MergeIf this is activated and you import a MIDI file into the current project, tempo and signature track data in the MIDI file are ignored. The imported MIDI file will play according to the current tempo and signature tracks in the project. If this option is deactivated, the Tempo Track Editor will be adjusted according to the tempo information in the MIDI file. Auto Dissolve Format 0 If this is activated and you import a MIDI file of type 0 into the project, the file will automatically be “dissolved”: For each embedded MIDI channel in the file, a separate track will be inserted in the Project window. If this is deactivated, only one MIDI track will be created. This track will be set to MIDI Channel “Any”, allowing all MIDI events to play back on their original channels. You can also use the “Dissolve Part” function on the MIDI menu to distribute the events onto different tracks with different MIDI Channels at a later stage.
File handling Exporting and importing MIDI loops 1025 It is also possible to import a MIDI file from disk by dragging and dropping it from the Windows Explorer or the Mac OS Finder into the Project window. The Import Options apply as well. RELATED LINKS Markers on page 281 Support for the Yamaha XF data format Cubase supports the Yamaha XF format. XF is an extension of the standard MIDI file format that allows you to save song-specific data with a MIDI file of type 0. When importing a MIDI file containing XF data, this data is placed in parts on separate tracks called “XF Data”, “Chord Data”, or “SysEx Data”. You can edit such a part in the List Editor (e. g. to add or change lyrics). IMPORTANTIMPORTANTIMPORTANTIMPORTANT Do not change the order of events within the XF data or the event data itself, unless you have a lot of experience with XF data. Cubase can also export XF data as part of a MIDI file of type 0. If you do not want to export the XF data together with the MIDI data, mute or delete the tracks containing the XF data. Exporting and importing MIDI loops Cubase allows you to import MIDI loops (file extension “.midiloop”) and to save instrument parts as MIDI loops. MIDI loops are handy, as they contain not only MIDI notes and controllers, but also the number of voices, the associated VST instrument and instrument track preset settings. RELATED LINKS VST Instruments on page 599 Destination Here, you can specify what happens when you drag a MIDI file into the project: • If you select the “MIDI Tracks” option, MIDI tracks are created for the imported file. • If you select the “Instrument Tracks” option, instrument tracks are created for each MIDI channel in the MIDI file. Furthermore, the program automatically loads appropriate presets. • If you select the “HALion Sonic SE multi-timbral” option, several MIDI tracks are created, each routed to a separate instance of HALion Sonic SE in the VST Instruments window and the appropriate presets are loaded. Option Description
File handling Exporting and importing track archives (Cubase Pro only) 1026 Exporting and importing track archives (Cubase Pro only) You can export Cubase tracks (audio, FX, group, instrument, MIDI, and video) as track archives for import into other Cubase (or Nuendo) projects. All the information associated with the tracks will be exported (channel settings, automation tracks, parts and events, etc.). If you select the “Copy” option (see below), a separate “media” folder will be created, containing copies of all referenced audio files. NOTE Project-specific settings (such as tempo) are not part of the exported track archives. RELATED LINKS Track Presets on page 160 Exporting tracks as track archives PROCEDURE 1. Select the tracks you wish to export. 2. Open the File menu, open the Export submenu and choose “Selected Tracks…”. 3. When exporting audio or video tracks, you are prompted to choose between two options: • Click Copy to include copies of the media files in the export. A file dialog opens in which you can choose an existing empty folder or create a new folder for saving the track archive (as XML file) and its media subfolder, which will contain any associated audio or video files. Click OK to save the track archive. • Click Reference to include merely a reference to the files in the export. A file dialog opens in which you can choose an existing folder for saving the track archive (as single XML file). 4. Enter a name for the track archive and click Save. Importing tracks from a track archive The Import Track Archive function lets you import tracks exported from another Cubase (or Nuendo) project. NOTE Note that the sample rates of the active project and the track archive have to match. If necessary, you have to convert the sample rate, see below.
File handling Exporting and importing track archives (Cubase Pro only) 1027 PROCEDURE 1. Open the File menu, open the Import submenu and select “Track Archive…”. 2. In the file dialog that opens, select the XML file and click Open. The Import Options dialog opens. In the Project Settings area, you can see a comparison between the settings of the track archive and the active project. 3. Click in the Import column on the left to select the desired track(s) or click “Select All Tracks”. A checkmark is shown for all selected tracks. 4. Choose which media files to use. • Select “Use Media Files From Archive” if you want to import the track without copying the media files into your project folder. • Select “Copy Media To Project Folder” if you want to import the media files into your project folder. For the “Perform Sample Rate Conversion” option, see below. 5. Click OK. The tracks are imported, complete with all contents and settings. Sample rate conversion on track archive import A track archive may contain media files with a sample rate that is different from the sample rate of your currently active project. You can see the sample rate difference in the Project Settings area. • To convert the sample rate of a track archive to the sample rate used in the active project on import, select the “Copy Media To Project Folder” option and then “Perform Sample Rate Conversion”. Unconverted files with another sample rate than the one used in the project will play back at the wrong speed and pitch.
1028 Customizing Workspaces Workspaces in Cubase allow you to organize windows and specific dialogs for your common work routines. A workspace saves the size, position, and layout or setting of important windows and dialogs, such as the Project window, MixConsole, or Transport panel. You can define several workspaces. This allows you to quickly switch between different working modes, either through the Workspaces menu or by using key commands. You can define different workspace types that are either available for all projects on your computer or specific for one project. However, when you open a project, its last saved view is opened. A view is the window layout and setting that you defined for your project. The last saved view can either be a workspace view or a view that you saved without having any workspace selected. When you open an external project, the last used view on your computer is used. The Workspaces Organizer and the Workspaces menu allow you to create and modify workspaces. NOTE You can also work without workspaces. In this case, the last used view of the former project will be used when you create a new project. Workspace Types You can create different workspace types. Global workspace Allows you to save a specific layout of dialogs and windows for all projects on your computer. Global workspaces are indicated by the letter G on your Workspaces menu. Project workspace Allows you to save a specific layout of dialogs and windows that is saved with your current project. This allows you to open your project layout on other computers. Project workspaces are indicated by the letter P on your Workspaces menu.
Customizing Workspaces 1029 Workspace Templates Cubase provides sample templates that you can use as a starting point for your own workspaces. The templates are made for screens with a resolution of 1280x800 px (minimal) or for screens with a resolution of 1920x1080 px (HD). You can change these templates according to your needs. IMPORTANTIMPORTANTIMPORTANTIMPORTANT
Customizing Workspaces 1030 If you want to open the project’s original layout setting, you have the following options: • Select the project’s original layout from the project workspaces on the Workspaces menu or in the Workspace Organizer. • Deactivate the Open External Projects in Last Used View setting in File > Preferences > General. This opens all external projects in their original layout. However, this may lead to a modification of your own custom layout. To return to the view that you last saved without any workspace assigned, select No Workspace on the Workspaces menu. Creating Workspaces To save your current dialog and window setting for future use, you can create a new workspace. PROCEDURE 1. Select Workspaces > Add Workspace. The New Workspace dialog opens. 2. In the Name field, enter a workspace name. 3. Select the type of workspace that you want to create. •Global Workspace •Project Workspace 4. Click OK. RESULT The workspace is saved and added to the Workspaces menu. Editing Workspaces You can modify your created workspaces. NOTE To change a global workspace to a project workspace and vice versa, you must save it as a different workspace type. PROCEDURE 1. On the Workspaces menu, select the workspace that you want to modify. 2. Make your changes as required.