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 kommentar(er)
