Equipment and operation for your event running order
Tell us what the audience needs to hear, the expected sources and feeds for stage, video or recording. Ask Eventos Globales to quote sound equipment, setup, testing and operation for conferences, presentations or shows in Argentina. Coordinate tasks with the venue and suppliers already involved; start without choosing a console or preparing a show file.
Yamaha CL5: patching, shared preamps and scene changes
For multiple operators or program changes, agree on routes and settings to retain. Preparing scenes, testing their differences and documenting operator handover are separate from console supply. The proposal can separate equipment, preparation and operation.
Model and application
- Manufacturer
- Yamaha
- Model
- Yamaha CL5
- Application
- Front-of-house and monitor mixing.
Patch, HA, scene and show-file checks
| What you see | What to check | Next step |
|---|---|---|
| The existing route passes audio; edits are refused | DANTE PATCH BY, Device Lock and LOCAL if DDM is present | Keep the exact message and arrange authorized edit access. |
| Dante receives the source, but the selected mix channel does not | Dante subscription and the channel's GAIN/PATCH | Trace the same source through both assignments. |
| Audio arrives, but the HA does not respond | DEVICE MOUNT and REMOTE HA ASSIGN | Compare the label, model and IDs with the physical rack. |
| VIRTUAL or repeated IDs | Absent or planned devices, CONFLICT and DUPLICATE warnings | Refresh the list and record its state before removing an assignment. |
| Two consoles share a head amp | HA assignment and WITH RECALL | Agree which console applies HA settings at startup and scene recall. |
| A scene leaves the previous patch in place | GLOBAL RECALL SAFE, channel SAFE and destination FOCUS | Identify the active exclusion; check inserts and Direct Out too. |
| Updating a scene for FOH and monitors | Destination number, MULTI SELECT and parameters that should change | Save a variant and compare changed and protected settings on recall. |
| Loading a .CLF leaves the Dante patch unchanged | LOAD SELECT, WITH DANTE SETUP AND I/O DEVICE, CONSOLE ID and DANTE PATCH BY | Agree whether to keep or load network settings; check each stage afterward. |
Two patch stages and permission to edit
Dante subscription delivers a source to the receive port; GAIN/PATCH selects the port used by the mix channel. If a working path cannot be edited, preserve the message and check DANTE PATCH BY, Device Lock and domain permissions where present. Audinate documents continued audio on a locked device’s existing subscriptions. Agree changes with the owner; do not initialize or bypass permissions as a test.
Coordinate a shared preamp
Compare the actual rack with DEVICE MOUNT and REMOTE HA ASSIGN. Receiving audio does not establish control of the correct preamp. WITH RECALL may apply saved settings at startup or scene recall; coordinate its use when FOH and monitors share an HA. The reference says control can work without WITH RECALL. A digital trim change does not establish an analog gain change.
Save a variant and define each scene’s recall scope
STORE saves current state to the chosen destination; RECALL restores a scene. Check number, title and multiple selection before saving to a free destination. Recall Safe applies across scenes, while Focus limits one scene’s recall; either exclusion can preserve a parameter. For unchanged input patching, compare GLOBAL RECALL SAFE → INPUT PATCH, channel SAFE and destination FOCUS.
Separate show-file loading from scene recall
Reference V5.8 conditions applying Dante patching from a .CLF on WITH DANTE SETUP AND I/O DEVICE enabled, CONSOLE ID #1–#4 and DANTE PATCH BY set to THIS CONSOLE. Other data may change the mix even when Dante patching remains. Agree which data to load and which network to retain; preserve recovery and compare off-air with protected outputs.
Patching and scene decisions
Why does audio continue while a patch change is rejected?
Separate editing permission from the working path. Record the message, DANTE PATCH BY and lock state; review domain permissions with the owner where applicable. Passing audio does not establish configuration permission.
Does channel audio establish control of the rack preamp?
No. Check device and HA assignment, gain owner and WITH RECALL when sharing a preamp. Test only an agreed change off-air with destinations protected.
Why does a recalled scene leave the previous input port?
Compare saved and recalled values, then Global Recall Safe, channel SAFE and scene Focus. Changing Dante subscription and changing GAIN/PATCH are different operations; follow the same source through both.
Do STORE and Recall Safe save only my latest change?
STORE captures current state; Recall Safe and Focus limit subsequent recall. Save a variant to a free destination and agree which parameters must change. Check multiple selection and write protection before saving.
Does loading a .CLF guarantee its Dante patch will apply?
No. Check data selection, WITH DANTE SETUP AND I/O DEVICE, CONSOLE ID and DANTE PATCH BY against V5.8. Loading does not remove Device Lock or permissions. Verify patch, channel, outputs and HA before returning to operation.
What should be prepared for the next operator?
Identification and versions, source/destination patch, HA owner, source/destination scenes, settings to retain, recovery copy and actual test results. A completed worksheet does not replace system testing; record pending checks and owners too.
Prepare the proposal and technical handover
Specify what your team provides and what you want to delegate: equipment, setup, patch preparation, rehearsal or operation. Add city, date and running order when known. Complete models, routes, scenes and schedules later. The worksheet is optional; downloading it does not send an enquiry.
Download patching, scenes and handover worksheet (TXT)
Can I enquire before knowing which console to hire?
Yes. Tell us what will happen, estimated simultaneous sources and each destination’s feed. We help choose equipment and setup, testing and operating tasks, completing models and connections with production.
Continue with the system and console
Documents by model and edition
Consult the series documentation on the official site; Owner’s Manual F0 is in English. For detailed patch, HA and scene controls, consult the cited V5.8 reference on the official site. Record installed software; document edition does not establish the console version.
Before finalizing a band or conference input list, separate the CL5’s capacity columns: the January 2013 brochure lists 72 mono and 8 stereo mixing channels, while its Dante interface is specified as 64 inputs and 64 outputs at 48 kHz. The local table lists OMNI IN 1–8 and OMNI OUT 1–8; 72 mixing channels do not mean 72 microphone connectors on the console, and the Dante limit is not the total mixing-channel count. For each source, record its physical location, local or Dante receive port and assigned mix channel. When inputs are split between stage and the technical desk, request the exact rack models and quantities being supplied rather than inferring them from a console photograph. The brochure lists 24 mixes and 8 matrices: record which destinations need mono or stereo before committing monitor and video feeds. Use these figures to define the system; an available route depends on actual patching and installed resources. This historical brochure helps identify capacity, while permissions, Recall Safe and file loading remain governed by the operating reference for the applicable version.
CL5/CL3/CL1 · Owner’s Manual F0 · EN
Open official documentation ↗- CL5/CL3/CL1 · Reference Manual V5.8, 10/2022 IP-G0 · EN ↗
Documentation consulted
Document review: October 30, 2026. Specific editions are cited; confirm unit version and test scope before changes.
