![]() ![]() Each track is assigned to a particular channel strip in the MixConsole. Tracks are listed from top to bottom in the track list and extend horizontally across the Project window. They allow you to import, add, record, and edit parts and events. Tracks are the building blocks of your project. ![]() You must create and set up a project to work with the program. ![]() In Cubase, projects are the central documents. The Project window provides an overview of the project, and allows you to navigate and perform large scale editing. Here, you can also set up group and FX channels, external effects, external instruments, and the Control Room. To play back and record in Cubase, you must set up input and output busses in the Audio Connections window. To use Cubase, you must set up your audio, and if required, your MIDI system. Here you will find detailed information about all the features and functions in the program. This is the Operation Manual for Steinberg’s Cubase. You can find it under 'Audio Performance' → 'Reset Processing Overload Indicator' in the 'Key Commands.' settings in the 'Edit' menu.The following list informs you about the most important improvements in Cubase and provides links to the corresponding descriptions. The overload indicator can also be reset with a key command now. It is reset by clicking on it or whenever the engine is reinitialized due to audio device setting changes or when the reset button is pressed. For example, this might occur if the prefetch (ASIO-Guard) buffer runs empty due to a too high real-time load. The processing overload indicator at the right indicates dropouts if the processing load exceeds 100% or if the audio engine is restarted due to the internal detection of too high processing delays. The metering of the current disk engine load is identical to the one used in previous releases. If this meter peaks/clips, it will cause an audio dropout (see below). ![]() Shows the highest measured load (in the latency critical real-time processing path). If the audio interface is set to a small block size, it is a bigger block size than for real-time processing. The block size depends on the ASIO-Guard settings found on the 'Audio System' page of the 'Studio Setup' dialog. Shows the average audio processing load of the processing path, which can be processed in advance (prefetched). It is always processed with the block size of the audio device settings. This is the case for all live inputs or monitoring activated channels. Show the average audio processing load of the latency critical processing path. Often, this needs to be investigated further. One example could be plug-ins which create a sporadic high peak load or which have an issue that directly affects the engine performance. The purpose of the distinction between real-time (average) and real-time (peak) is to identify issues which are caused by a high deviation between average and real-time. This not only offers a quick overview of the overall system load, but also provides a detailed indication of the source of the current system load. The metering toolbar displays the current real-time, ASIO-Guard and peak loads. To achieve this, a new algorithm to separately measure the load for real-time and prefetch (ASIO-Guard) threads has been implemented. The purpose of the new Audio Performance Meter is to give you a more detailed feedback on the audio engine load situation and to allow for a quick diagnosis of audio engine issues. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |