From 9edb5d8185a5ae97c7ec46bc1de4902f8d133f4d Mon Sep 17 00:00:00 2001 From: Ed Ward Date: Thu, 12 Jan 2017 20:11:12 +0100 Subject: [PATCH] Documenting the satus bar --- master-doc.txt | 25 ++++++++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-) diff --git a/master-doc.txt b/master-doc.txt index b4b1828..d3aed91 100644 --- a/master-doc.txt +++ b/master-doc.txt @@ -7009,16 +7009,35 @@ title: Status Bar part: chapter --- -

Add content

+The status bar +

The status bar is an informative bar at the top of the window, showing:

+ +

The buffers are labelled as p for playback and c for capture. If the +system is fast enough, these buffers should be 100% full at all times, showing the system has time to precompute +all the data before delivering it to the audio system. A buffer constantly under 20% is a sign of an underpowered +computer system or of too much processing.

+ +

An Xrun (short for buffer over- or under-run) happens when the system has been forced to skip audio frames, e.g. if the latency +asked is too short for the computing power of the machine. It usually results in clicks, pops and crackles if it happens while recording.

+ +

The log button turns yellow when a warning is shows, and red when an error occurs. Clicking the log button gives acces to the log.

--- title: Transport bar and times part: chapter --- -

There is no discussion of starting playback anywhere in here. Starting/stopping needs to be explained

-

Ardour offers many ways to control playback of your session, including the transport bar, key bindings and remote controls. You can also use markers to define locations or ranges within the session and rapidly move around between them.

-- 2.37.2