What a Signal Path Diagram Is and Why a Review Starts With One

The term, in plain words

A signal path diagram is a drawing that follows a picture or a sound from the moment it is captured to the moment it leaves the building. Each box is a piece of equipment, each line is a cable or a network link, and the arrows show which way the signal travels. That is all it is, yet it is the first thing we ask a studio for when a workflow review begins.

People sometimes call it a block diagram or a flow chart, and in a small studio it may exist only as a pencil sketch taped inside a cupboard door. The format matters far less than whether it matches what is really installed. A diagram that was accurate three upgrades ago is worse than none, because it sends people looking in the wrong place when something fails.

When I coordinate a review enquiry, I explain this early, because clients often assume we want a formal engineering drawing. We do not. A tidy hand sketch, photographed and sent over, is a perfectly good starting point for the written report that follows.

What the diagram shows at a glance

Once the path is on paper, patterns appear that are hard to see while standing in the room. You can count how many times a signal is converted, for instance from analogue to digital and back, or from one video format to another. Each conversion costs a little time and can introduce a small error, so a long chain with many conversions is worth questioning.

You also see where signals split and where they merge. A camera feed that goes to the vision mixer, a monitor wall and a recorder has two splits, and each split is a place where a distribution amplifier, a cable or a setting could go wrong. Seeing those points named makes fault-finding far quicker for whoever is on shift.

Finally, the diagram makes single points of failure visible. If every source passes through one router or one patch bay, a fault there stops the whole studio. Knowing that in advance lets a manager decide whether a spare, a bypass or simply a clear written procedure is the sensible answer.

• Number of format conversions in the chain
• Places where one signal is split to several destinations
• Single devices that everything depends on

Latency and delay: the number a review wants

Alongside the diagram, a review looks at latency, which means the time a signal spends passing through each device. Video processing usually takes longer than audio, so a picture can arrive after the sound that belongs with it. That gap is what viewers notice as lip-sync drift, and it is rarely caused by one dramatic fault. More often it is the sum of several small delays.

Manufacturers publish typical delay figures for their equipment, and these are a sensible place to begin. Real installations add their own: a frame synchroniser, a scaler on a monitor feed, a streaming encoder. Writing the delay beside each box on the diagram turns a vague complaint into a short list of causes.

Our audio synchronisation work picks up where a review leaves off, but the review itself only needs the delays recorded honestly. We measure what we can, note what we could only estimate, and say which is which, so nobody mistakes an estimate for a measurement.

Labelling, and why it is not a small matter

The least glamorous finding in many reviews is that nothing is labelled consistently. One engineer calls an input Cam 2, the vision mixer shows it as Source 4, and the patch bay says Studio B Left. Each name is reasonable on its own, but together they cause delays at exactly the moment a live show needs a quick fix.

A good diagram settles on one name per signal and uses it everywhere: on the drawing, on the equipment labels and in the operating notes. The change costs very little, yet crews tell us it removes a surprising amount of daily friction, particularly for freelancers who work in the studio only now and then.

Where cabling is concerned, we look for labels at both ends and a record of what each cable carries. A cable that has been moved and not recorded is one of the commonest reasons a diagram and a studio fall out of step, so we treat the labelling check as part of the path itself, not an extra.

• One agreed name for each source and destination
• Labels at both ends of every cable run

What happens to the diagram during a review

The sequence is straightforward. The studio sends its existing drawing or sketch, and one of our engineers walks the real path to compare the two. Differences are noted, delays are recorded, and the diagram is redrawn so that it matches the room as it stands on the day of the visit.

From the corrected drawing, we write the report. It lists what is working, what is fragile and what we would change first, in an order that reflects the effort and cost involved. We avoid recommending a purchase where a setting change or a relabelled cable would do the same job, and we say so plainly.

The studio keeps the redrawn diagram and the report. Many clients pin the new drawing in the control room, and some ask us to revisit it after a later equipment change. Because it is a living document, it only stays useful if someone updates it when the room changes.

Preparing before you contact us

If you are considering a review, a little preparation makes the first conversation much more productive. Gather whatever drawings exist, even outdated ones, and list the main equipment by make and model, including the vision mixer, routers, converters and any playout or streaming systems. A photograph of the rack and patch bay is surprisingly informative.

It also helps to describe the symptom that prompted you to ask: occasional audio drift, a feed that drops on certain days, or simply a studio that has grown by additions and nobody is sure how it fits together. A clear description lets us scope the visit sensibly and give a written quotation that reflects the real work.

You can send these details through the contact form, and Thomas, who reads every enquiry, will reply with what we need and when a visit could be arranged. There is no obligation to proceed once you have seen the quotation.

• Any existing drawings, however old
• A list of main equipment by make and model
• A short note on the problem you want solved