Yamaha CL5

Check who has permission to edit the routing and whether a device is locked before rebuilding connections. A working audio path does not prove that its patch can be edited: existing Dante subscriptions can keep passing audio while Device Lock restricts changes.

If the venue network also carries emergency announcements or other services, agree any changes with the person responsible for that system. Do not bypass its controls to regain patch access.

The CL5 has separate Dante and internal console patches. For example, a rack input arriving at DANTE 7 does not automatically feed CH 7: the mix channel must select that input port in GAIN/PATCH. Check both assignments when tracing a source.

1. Save the current patch and note the physical source, Dante transmitter and channel, Dante receive channel, and mix channel. Record the exact message shown when the edit fails; it is more useful than a note saying only that the connection failed.
2. Open SETUP → DANTE SETUP → SETUP and check DANTE PATCH BY. THIS CONSOLE allows Dante patch edits from the CL. DANTE CONTROLLER prevents those edits on the console and may produce “This Operation is Not Allowed”; it does not prevent edits from Controller. Agree which operator will make the change before switching this setting.
3. Look for DANTE DEVICE LOCKED on the CL and LOCKED on mounted devices. In Controller, check the padlock in Routing or the Device Lock column in Device Info. If a device is locked, arrange for its owner to unlock it with the correct PIN. Changing DANTE PATCH BY does not remove Device Lock.
4. If the network uses Dante Domain Manager, also check LOCAL: Read Write permits editing; Read Only does not. Record this permission separately from Device Lock.
5. Once editing is authorized, check the subscription from the source to DANTE 1–64, then the input port selected in the mix channel's GAIN/PATCH. For an output, follow bus → OUTPUT PORT/DANTE → rack output. Changing one assignment leaves the other unchanged. Do this outside the live program.
6. Test one agreed route and listen at its destination without altering other routes. If the patch changes but audio is missing, follow the meters through each stage. If editing is still refused, keep the message and permission states for support. Do not start by initializing the console.

Check that remote control is assigned to the head amp supplying the audio. The Dante subscription carries the signal; REMOTE HA ASSIGN selects the HA device that the CL controls. Receiving audio does not confirm that this control assignment is correct.

VIRTUAL means the configured device is not present on the network recognized by the console. It may be a planned device that has not yet been connected. CONFLICT and DUPLICATE are different warnings involving device type and ID. Yamaha fixed a missing duplicate-ID indication for Rio-D2/D3 in V5.91, so the absence of that warning alone does not rule out duplicate IDs.

Take particular care with WITH RECALL when FOH and monitors share a head amp: it applies stored HA settings at console startup and scene recall. If another CL has already configured that shared HA, leave WITH RECALL off on the additional console. Remote HA control is still available without it. Device Lock does not, by itself, prevent R-series HA control that is unrelated to Dante settings.

1. Record the full rack model, including its suffix, console and rack firmware, UNIT ID and complete Dante label. Save the current GAIN/PATCH, DEVICE MOUNT and REMOTE HA settings before changing assignments.
2. In SETUP → DANTE SETUP → DEVICE MOUNT, compare the device, model and ID with the connected rack. REFRESH updates the list. If a device shows VIRTUAL, first check that the intended rack is powered on and connected to the correct network. Do not use CLEAR ALL to investigate a single device.
3. Open REMOTE HA ASSIGN and check the label and model in each slot. If the correct rack is not assigned, select its slot, open REMOTE HA SELECT and choose the actual device from DEVICE LIST. Review WITH RECALL with the other console operator before confirming with OK.
4. Compare the IDs of connected devices with those prepared in the console. Avoid conflicting IDs; Yamaha also recommends avoiding overlaps between different models where possible. If an expected warning is absent, compare the actual IDs anyway and check the relevant firmware notes. Schedule any update outside the event, with a backup and compatibility check.
5. In I/O DEVICE → I/O, open the HA rack and compare its control with the channel's GAIN/PATCH. If NOT CTRL appears, check CONSOLE ID: OFF disables that control. Coordinate any ID change so it does not duplicate another CL on the network.
6. Use an agreed test source and channel, with output destinations protected and the monitor operator informed. Watch A.GAIN while making a small change, then restore the original value. With GC (Gain Compensation) active, the level sent to Dante can remain steady even when A.GAIN changes; check GC and AG-DG LINK before interpreting what you hear. If only D. GAIN responds, continue checking control of the physical head amp. Do not toggle +48V or recall scenes to test an input without knowing what is connected.

Start with GLOBAL RECALL SAFE → INPUT PATCH. It can preserve the patch even when that channel's SAFE button is off. Then check the channel's Recall Safe settings and the destination scene's Focus settings. An exclusion in either function can keep the parameter unchanged.

A scene stores the assignment from input ports to mix channels. Subscriptions from transmitters to the CL's Dante receivers are managed separately. Switching GAIN/PATCH between DANTE 58 and 59 concerns the internal patch. If you expect the same Dante receiver to change from a Rio source to DVS, also check the DANTE INPUT PATCH library.

1. Back up the starting state and note both scenes, the channel and its expected input port in each scene. Compare the stored value with the value after RECALL, outside the live program and with outputs protected.
2. Open CH JOB → RECALL SAFE. Press the GLOBAL RECALL SAFE area and inspect INPUT PATCH. This global protection also covers INSERT PATCH and DIRECT OUT, so releasing it can allow changes to those paths. Avoid CLEAR ALL: it disables global and individual channel protections together.
3. Select the channel and check INPUT PATCH together with SAFE. A green parameter button can indicate protection inherited from Global Recall Safe. For individual channel protection, both the parameter selection and SAFE must be enabled; checking the channel name alone is not enough.
4. In SCENE → FOCUS, open SET for the destination scene and check which channels and parameters it can recall. Focus belongs to that scene; Recall Safe applies across scenes. Enable only the changes required, retaining protections for the rest of the event.
5. Recall both scenes in turn and check GAIN/PATCH, inserts, Direct Out and the intended audio path. If the input port stays fixed, record the three protection selections and the show-file version. If the port changes but the wrong source arrives, trace the Dante patch before changing the mix.

Use STORE to save the current settings into the scene number you intend to update. Use Recall Safe or Focus to determine what changes when that scene is recalled. STORE captures the current mix; recall restrictions do not mean that only the last control you touched is being saved.

Before changing the original scene, save a variant to a free number and back up the show. Identify what should change, such as an agreed send level, and what must stay fixed: routing, other channel levels and shared HA settings. For a shared head amp, also agree WITH RECALL with the other console operator.

Open SCENE and verify the destination number and title. A flashing number indicates that the selected scene differs from the loaded scene. LAST SCENE selects the most recently recalled scene; use it to locate that scene before choosing where to store. Keep MULTI SELECT off for this update: when multiple numbers are selected, STORE writes the same settings to all of them. A padlock or R indicates write protection; choose a free number for the variant.

1. In SCENE LIST, press STORE, keep or edit the title and comment, then execute STORE in the save window. Verify the destination before confirming. STORE CONFIRMATION can be disabled in preferences, so do not rely on that dialog as your final check.
2. In CH JOB → RECALL SAFE, select the parameters that must stay fixed and enable SAFE for the channel. To restrict one particular scene instead, configure its FOCUS and check that it is enabled. Do not select ALL as a default recipe: choose protections to suit the event's signal paths.
3. Rehearse recalls in both directions outside the live program. Compare the send that should change with the controls that should stay fixed. If the send does not respond, check Recall Safe and Focus for that parameter. If another channel changes, review exclusions and channel links before storing again.

Check the selected load data and the three conditions for applying the .CLF's Dante patch: WITH DANTE SETUP AND I/O DEVICE enabled, CONSOLE ID set to #1, #2, #3 or #4, and DANTE PATCH BY set to THIS CONSOLE. If those conditions are not met, the current Dante patch is retained. Other data may still have loaded, so inspect each part before repeating the operation.

This SAVE/LOAD option also applies DANTE SETUP, I/O device and word-clock settings. Page 247 of the V5.8 reference manual labels it WITH DANTE SETUP AND I/O RACK; pages 248 and 264 use I/O DEVICE. SECONDARY PORT and CONSOLE ID do not change with this option. Record the label shown by your version and check wiring and IDs separately.

Before loading, turn off connected equipment and/or lower its volume so an immediate signal from the console cannot cause a problem. Agree this with the system operator, make a backup and load outside the live program. A .CLU is a user authentication key; console settings use .CLF.

1. Open SETUP → SAVE/LOAD, select the .CLF and record its date and source. In LOAD SELECT, check the console version used to save it and choose the data and destination: ALL, SCENE or the specific sections required. USER LEVEL can prevent some settings from loading.
2. Decide whether to keep the current network settings or apply those in the file. Check WITH DANTE SETUP AND I/O DEVICE, CONSOLE ID and DANTE PATCH BY before LOAD. Do not enable the option as a trial recovery on a network shared with announcements, recording or another console. Agree the routing and clock configuration first.
3. If editing or loading settings remains restricted, check Device Lock and network permissions. Loading a file does not remove those restrictions. Wait for ACCESS to finish before removing the USB drive or powering down the CL. Canceling a load can leave the data already processed applied to the console.
4. After loading, compare DANTE INPUT PATCH, GAIN/PATCH, OUTPUT PORT, rack destinations and HA assignment. LOAD SELECT → SETUP → Dante In Patch selects the Dante input patch library; SCENE selects scene memories. If OUTPUT PORT was loaded separately, also load and recall the scene containing its channel assignments.
5. Verify an input, an output and the shared HA before returning the system to operation. Recheck Recall Safe after loading ALL. The V5.90 notes document a fix involving Recall Safe and Channel Link during that load. Compare the installed version without assuming that bug explains the fault or updating during the event.