Symptoms
The microphone is recorded locally but is absent from the guest call. This guide addresses the specific difference between what still works and what fails. It uses a controlled comparison instead of a general reset: Record a short test in the audio workstation and compare the conferencing app's input meter. The goal is to restore the documented behavior while retaining the original data and configuration.
- Primary symptom: The microphone is recorded locally but is absent from the guest call.
- Baseline measurement: Record a short test in the audio workstation and compare the conferencing app's input meter.
- Normal path to preserve: A short test file or consented stream contains the expected audio/video output.
Why It Happens
Monitor knobs, capture channels, live output and recorded tracks can all carry different mixes. Trace the signal from source to final output before changing gain or reinstalling software.
Three plausible explanations should be checked in sequence; none is proven merely because it is common on similar devices.
- Wrong USB send bus. Treat this as a testable explanation for the observed difference; compare against the stated baseline rather than assuming it is the cause.
- Mix-minus not configured. This may affect the specific step that fails while leaving the comparison case intact.
- Call app input selection. If the first two possibilities are excluded, use the deeper diagnostic described below to check this layer.
Before Making Changes
Use a consenting test participant and avoid recording private calls without permission.
Inspect the actual recorded or streamed output: direct monitoring and preview meters may represent a different signal path from the exported result.
Take a screenshot or short written note of the original values. If the test needs a file, export, print or recording, create a disposable sample or work on a duplicate; do not replace an irreplaceable original. Do not alter shared or managed equipment without appropriate permission.
Problem-Specific Diagnosis
The table separates observations, interpretations and next actions. Start at the top and stop as soon as the expected outcome is restored.
| Test | What it distinguishes | Next action |
|---|---|---|
| Record a short test in the audio workstation and compare the conferencing app's input meter. | Whether the failure is tied to the original condition or also affects the control. A difference supports investigating wrong usb send bus. | Select the mixer's intended USB send channel as the call microphone and verify the routing preset. |
| Check the setting or route involved in: Select the mixer's intended USB send channel as the call microphone and verify the routing preset. | If only the affected path improves, mix-minus not configured is worth inspecting next. | Restore previous settings if the expected result does not change. |
| Inspect mix-minus configuration, loopback channels and sample-rate agreements without sending guest audio back to themselves. | A second-layer difference can support investigating call app input selection without treating it as certain. | Use vendor-specific guidance or authorized service for the isolated layer. |
| A remote participant hears the host clearly without an echo while the local track records. | A stable result after normal reconnection is more persuasive than a transient indicator. | Retain the working configuration and document the observed pass condition. |
A useful negative result is not wasted effort. If the first comparison does not isolate the fault, note exactly which variable stayed unchanged. This prevents moving from a narrow symptom to a factory reset without evidence.
Choose Your Fix: Beginner or Advanced
Beginner is a reversible first route; Advanced investigates different components when the baseline comparison and first correction do not explain the issue. You do not need to perform both paths if the first one fixes the problem.
Step-by-Step Troubleshooting
Choose the reversible Beginner route or the deeper Advanced route based on your comparison.
Capture a baseline for creator audio & streaming
The microphone is recorded locally but is absent from the guest call. Record a short test in the audio workstation and compare the conferencing app's input meter. Record the exact result and one comparison that behaves normally. Note the device, app or model involved; a simple before/after note is enough.
Preserve the working configuration
Use a consenting test participant and avoid recording private calls without permission. Keep a copy of any file, job profile, schedule or setting that could be affected. Inspect the actual recorded or streamed output: direct monitoring and preview meters may represent a different signal path from the exported result.
Apply the least disruptive correction
Select the mixer's intended USB send channel as the call microphone and verify the routing preset. Do only this specific adjustment for the first trial. Do not erase data, reset the full device or rewrite unrelated settings to chase a local symptom.
Repeat the original practical test
A remote participant hears the host clearly without an echo while the local track records. Reproduce the same comparison described in the first step. If the result is unchanged, undo the last reversible adjustment and proceed to the Advanced route rather than repeating resets.
Separate three plausible causes
Investigate wrong usb send bus, mix-minus not configured and call app input selection as independent hypotheses. Record a short test in the audio workstation and compare the conferencing app's input meter. The failure following one path is stronger evidence than a generic status icon.
Inspect the second technical layer
Inspect mix-minus configuration, loopback channels and sample-rate agreements without sending guest audio back to themselves. Record exact supported option names, event times and physical observations. Do not change hardware settings or permissions until a controlled comparison identifies the relevant layer.
Cross-check against a working control
Test the unaffected condition again without applying the beginner correction a second time. Ask whether the evidence points to mix-minus not configured rather than wrong usb send bus; use one known-good cable, file, profile, network or environment only where safe and available.
Escalate with evidence and a rollback plan
If this remains unresolved, record the two test outcomes, model and supported firmware/software versions, and the observed difference. Use a consenting test participant and avoid recording private calls without permission. Share a redacted summary with authorized support rather than changing unrelated components.
Common Mistakes to Avoid
- Treating wrong usb send bus as a proven cause without comparing the failing condition.
- Repeating select the mixer's intended usb send channel as the call microphone and verify the routing preset while ignoring evidence pointing to a separate technical layer.
- Changing several independent controls together and then losing track of which change mattered.
- Skipping this precaution: Use a consenting test participant and avoid recording private calls without permission
How to Verify the Fix
A remote participant hears the host clearly without an echo while the local track records.
Perform the same practical check again after a normal restart, reconnection or next scheduled cycle, as appropriate for this device. Confirm that the original unaffected function still works and that the correction did not introduce a new problem.
If the result cannot be reproduced reliably, retain the notes and classify the problem as intermittent rather than declaring a permanent fix.
If the Problem Continues
Move to the deeper test only after the first correction has been measured: Inspect mix-minus configuration, loopback channels and sample-rate agreements without sending guest audio back to themselves.
Provide authorized support with the exact symptom, model identifier, relevant software or firmware information, timestamps, first comparison and actual final result. Do not upload passwords, QR codes, account tokens, student records, private recordings or personal location details.
A limitation documented for the device or service may require a supported alternate workflow; a damaged component, hazardous appliance or account-policy restriction needs professional or administrator assistance rather than an improvised bypass.
Prevent Recurrence
Save a note of the working configuration and keep original source files, profiles and service permissions available for recovery. Repeat the same short comparison after major changes to firmware, installed applications, cable routing, profiles, schedules or storage.
For this problem the most useful periodic check is the actual outcome: A remote participant hears the host clearly without an echo while the local track records.
Frequently Asked Questions
Why does this happen if another related function still works?
Because wrong usb send bus, mix-minus not configured and call app input selection affect different stages. Record a short test in the audio workstation and compare the conferencing app's input meter. That comparison is more useful than a broad “connected” or “ready” indicator.
What is the safest first change?
Select the mixer's intended USB send channel as the call microphone and verify the routing preset. Use a consenting test participant and avoid recording private calls without permission. This first action is limited in scope; it is not permission to remove protections, overwrite original files or reset every setting.
How do I know I fixed the actual problem?
A remote participant hears the host clearly without an echo while the local track records. Reproduce the original failing situation and repeat the check. If the result returns only briefly, keep the evidence and investigate the deeper layer: Inspect mix-minus configuration, loopback channels and sample-rate agreements without sending guest audio back to themselves.
Solution Checklist
Use the checklist to distinguish a tested correction from a change that merely hid the symptom.