How to describe an IEM problem when you need help

When an in-ear monitor problem remains unresolved, a useful help request explains your setup, what you heard, when it happened, and what you have already checked.

You finish rehearsal knowing something was wrong with your in-ear monitors, or IEMs. But by the time you message the engineer, equipment owner, or retailer, the description has shrunk to “my left ear sounded weird.”

That is a starting point, but it leaves the person helping you to reconstruct the session. Were you using a wired pack or a wireless receiver? Did the whole mix disappear, or only your vocal? Was this happening throughout rehearsal or just twice?

You do not need to diagnose the fault before asking for help. Your job is to hand over a clear account, including the gaps. Here is a practical way to do that without turning your message into a technical essay.

1. Separate what you heard from what you suspect

Start with the symptom, not the suspected cause. “The cable is broken” is a conclusion. “The left earpiece went silent twice while the right continued playing” is an observation someone else can work with.

Use ordinary listening language. Quiet, silent, crackling, distorted, muffled, or missing a particular instrument are all useful descriptions when you explain exactly what they refer to.

• Name the affected part. Say left, right, both, or uncertain. Also say whether the whole mix changed or only one source, such as the vocal or click.
• Describe the change. “The vocal became quieter than the guitar” means something different from “everything became quieter.”
• Give the timing. Note whether it happened once, repeatedly, or continuously, and roughly how long each occurrence lasted.
• Keep guesses separate. Write “I wondered whether the cable was involved” rather than presenting that possibility as a confirmed fault.

Context matters, but it does not automatically establish a cause. “It happened while I turned toward the drummer” is useful. “Turning caused it” goes further than that observation supports.

If describing the problem would require recreating a painful or unexpectedly loud sound, do not repeat it just to improve the report. Describe the event and flag that you stopped using the setup.

2. Fill in a report someone else can follow

A signal path is simply the route audio takes to your ears. A plain-language example is: mixer monitor output → audio cable → wired beltpack → earphone cable → earpieces. For a wireless setup, include the transmitter and receiver between the mixer and earphones.

List the equipment models you know, including adapters and any replacement cable involved. If a model or connection is unknown, say so rather than guessing. Use this outline as a copy-and-paste message.

Copy-and-paste IEM problem report

Help needed: [What would you like the recipient to help identify or arrange?]

Setup and signal path: [Audio source or mixer, output used, cables/adapters, wired pack or wireless transmitter and receiver, earphone cable, earpieces. Include makes and models where known.]

Affected side or mix: [Left/right/both; whose monitor mix; whole mix or specific sources.]

What I heard: [Describe the sound or interruption without assuming a cause.]

Frequency and duration: [How often, approximately how long, and whether it is still happening.]

Circumstances: [Rehearsal, soundcheck, or show; song or passage; movement; whether the same thing occurred elsewhere.]

Recent changes: [Anything different since the last session without the problem, or “none known.”]

Checks already completed and results: [Each change separately, what stayed the same, and what happened afterward.]

Not checked or still unknown: [Missing model names, untested connections, uncertain routing, or anything you cannot confirm.]

Attachments and availability: [Optional connection photo; when the equipment and relevant people are available.]

Make the results unambiguous

“Not checked” and “checked with no change” are different information. The first leaves a question open. The second records an action and its observed result.

Instead of “tried another cable,” write: “Replaced only the cable between the mixer and wired pack. The left side went quiet again during the next song.” If several things changed together, record that too. Do not credit one change with fixing the problem when you cannot separate its effect from the others.

For an intermittent issue, “did not happen again during ten minutes of playing” is more precise than “fixed.” Include the observation window rather than promising a conclusion.

An optional photo can show which sockets and adapters are connected. Keep connection labels readable, and leave unrelated personal details out of the frame. A recording may provide context, but it may not capture what reached your ears through that particular setup.

3. Turn scattered messages into one clear request

Hypothetical example: a vocal disappears from the mix

Imagine sending these messages after rehearsal: “Left side weird again.” “Maybe the pack?” “We changed a lead.” “Actually, just the vocal disappeared.”

That last detail changes the meaning of the first message. Gather the information into one report instead. Here is a hypothetical report with the unknowns left visible.

Help needed: Could you help identify where to investigate the missing vocal in my monitor mix before Thursday’s rehearsal?

Setup: Rehearsal-room mixer monitor output → audio lead → wired beltpack → earphone cable → IEMs. I did not record the mixer, pack, or earphone model names. The equipment owner can confirm them Thursday.

Symptom: My vocal disappeared from both earpieces twice during the final song. Guitar and click remained audible. Each interruption lasted roughly two seconds. My earlier message saying “left side” was inaccurate.

Circumstances: Both interruptions happened while I was singing at the mic. I did not notice the problem during the previous four songs. No recent setup changes are known to me.

Completed check: Before the final song, we replaced only the lead from the mixer to the pack because the vocal had briefly disappeared earlier. The symptom returned afterward.

Unknowns: We did not check another monitor mix, pack, or pair of earphones. I do not know whether the vocal was also missing from the room speakers. The engineer and equipment will be available before rehearsal Thursday.

Hypothetical example: one side cuts out intermittently

This second hypothetical report describes a different situation, using only observations and checks already available.

Help needed: Could you review this report and tell me what information you need to arrange an equipment assessment?

Setup: Venue mixer → cable → wireless transmitter → wireless receiver → earphone cable → IEMs. Makes and models are unknown to me; the equipment owner has the inventory.

Observations and circumstances: The entire mix went silent in my right earpiece three times during yesterday’s soundcheck, for about a second each time. The left continued playing. I was standing at the keyboard each time. I stopped using the setup afterward.

Recent changes: This was my first session with that venue’s wireless equipment. I used my usual earphones and cable.

Completed checks and results: The owner checked the receiver’s model label afterward, but it was unreadable. No listening checks were completed.

Unknowns: I do not know whether another musician had the same issue. No alternative receiver, cable, or earphones were checked.

These reports do not solve the fault. They give the next person a defined symptom, a connection map, recorded checks, and clear unanswered questions. If setup terms are getting in the way, the line check and soundcheck guide offers useful vocabulary for discussing signals and monitor requests.

Before your next help request, fill in the report while rehearsal is still fresh. Send one consolidated message, mark anything uncertain, and let the person helping you choose the next check.