Solidcom C1 Pro: connection, groups, Zoom and Dante

Start with the master assignment, the connection of each remote and TALK mode at each microphone. A steady light on the master only confirms that it is powered on; it does not confirm that all remote headsets are connected.

These steps apply to a system without a hub. The master has a red nameplate and the remotes have blue nameplates. One master supports up to seven remotes. The master cannot pair with a hub; a hub-based system requires the exact base model and compatible remotes to be identified before assigning users.

1. During an event, agree on a pause or an alternative communication method with the director before making changes. Record the assigned master and remotes, headset variants, region and firmware. Headsets brought in from another kit may still be paired to a different master.
2. With charged original batteries, turn on the master and the remote being checked. A flashing remote indicator means it is not connected; rapid flashing means pairing is in progress. Once it stays on, test both directions: master to remote and remote to master. Record who can hear whom.
3. Check TALK/MUTE at both ends. A short press toggles TALK and MUTE; holding the button gives push-to-talk (PTT), with the microphone returning to MUTE on release. Steady red means muted. Steady green means ENC is off and steady blue means ENC is on. None of those colors replaces a voice check.
4. If the remote is disconnected and needs to join this system, follow the No Hub manual: with the headsets powered on, hold A on the master and remote for five seconds. Wait for pairing to finish, then repeat the two-way voice check. B does not create a second group without a hub. Add the remaining remotes and check every position.
5. If pairing succeeds but voice still does not pass, compare firmware and compatibility before pairing the whole kit again. The December 20, 2024 notes list V1.0.9.3 for both master and remote headsets. The March 13, 2026 note instead covers HUB V1.0.6.6 with headset V1.0.9.X. These numbers refer to different devices and do not identify the firmware installed in your kit.
6. If an update is needed, use the procedure for the exact configuration and schedule it outside show operation. Hollyland warns that updates can reset settings and introduce errors. Record the starting configuration, maintain sufficient power and leave USB connected until completion. The headset-only tutorial then calls for pairing again; repeat the full communication test. If voice still fails, continue with a verified working kit and send the affected equipment for service with the test record. Do not assume there is an undocumented reset.

Use a voice source that is already reaching a working headset. If other users hear the affected headset microphone, that establishes an outgoing audio path; it does not prove that incoming audio or the earpiece works.

Sidetone is your own voice returned to the earpiece, and its level is not adjustable on the C1 Pro. Hearing yourself does not confirm that the director is reaching you. Have another person speak and record your own voice, incoming voice and local alerts separately.

1. At an agreed time, have only the master or a known working remote speak. Confirm the same source on a reference headset in the same link context. Raise Volume + gradually on the affected unit to a comfortable listening level. Its TALK/MUTE control changes the local microphone, not listening volume.
2. If the affected unit is a remote and its indicator flashes, restore its connection before suspecting the earpiece. In a hub-based system, also record its A/B group assignment. This headset-only test does not verify routing inside a hub.
3. Compare the affected headset with a working unit in the same location, both with charged batteries. Change one condition at a time. If the reference receives the source and the fault stays with the same headset, take that headset out of service and repeat the check away from show operation. This narrows the fault without identifying an internal component.
4. Record whether local alerts are audible. The single-ear V2.0.0 manual describes a chime at maximum volume and a tick when microphone-boom movement turns the microphone on or off. Do not force the volume or move the boom just to trigger an alert; a missing alert alone does not establish a failed speaker. The double-ear V1.0 manual does not list these alerts in the same way.
5. If incoming voice is present but noisy, compare ENC at the headset of the person speaking: that is where the noise cancellation is applied. When no voice arrives at all, ENC does not replace link and receive-audio checks. Restore the starting setting after the comparison.
6. If the symptom persists, issue a spare that has passed a two-way communication check. Keep the model, firmware and results with the affected unit for service. Confirm both incoming and outgoing audio before returning it to the show.

Check the PGM assignment in the group settings. The PGM menu on the hub display adjusts input gain; lowering it does not select A or B and is not the same as muting the input.

This procedure applies to the Solidcom C1 Pro Hub covered by the linked manual, with Group, Customize and PGM controls. Read the model label and check Hardware Number and Version Information under Info before using these steps. They do not apply to a system without a hub or to the Roaming Hub.

1. Record the preset and current PGM destination before changing them. Under Group, AB group includes devices in both groups; Customize enables web configuration. Also check Group Review and the A/B buttons at each position: a headset participating in both groups can hear both.
2. Open the web configuration for that hub using the IP address shown under Network → Wired Network Setting. In Group Settings, find PGM under A Group and B Group. Assign the input to the intended group, select Confirm and read back the selection. Keep a screenshot of the original matrix so you can restore it.
3. During rehearsal, feed an identifiable signal only to PGM at a moderate level. Listen with one headset assigned only to A and another assigned only to B. Record where the signal is heard. If it reaches both, first check that the headsets are not participating in both groups and that the same signal is not also entering through UAC or 4 Wire.
4. With multiple hubs, record which hub receives PGM and where the signal appears. Compare the local path with the complete system during an agreed pause; do not disconnect a cascade during operation. If the saved destination differs from what you hear, retain the firmware, preset, assignments and signal path for review. Restore the original settings if the test disrupts required communication.

Separate network access from the audio path. Use the hub’s network RJ45 ports to configure it. The 4-Wire socket also uses an RJ45 connector, but it carries audio and is not the port for connecting the computer.

For the Hub covered by the linked manual, Group Settings lists 4 Wire In and 4 Wire Out separately. Checking one direction leaves the other untested. The front-panel A/B buttons select groups for the operator’s wired headset; they do not replace the external port assignment.

1. Under Network → Wired Network Setting, record the IP address, subnet mask and DHCP state without resetting the hub. Connect the computer through a network RJ45 port and use a different address in the same subnet. For example, with the factory hub address 192.168.218.10 and mask 255.255.255.0, the computer could use 192.168.218.20 if that address is free. Open the address actually displayed by the hub. If Wi-Fi access failed, try a wired connection to separate that path from the web server; Hollyland documents both methods.
2. If the connection times out, check the port, cable, selected network interface and subnet before changing audio routing. Reaching the login page confirms web access, not group separation. One official FAQ uses both .10 and .11 in its example; follow the address displayed on the hub. Use its current credentials and restore the computer’s original network configuration when finished.
3. After identifying the hub and agreeing on a pause, check Group → Customize and the web matrix. For a layout with cameras in A and the external intercom in B, check that 4 Wire In and 4 Wire Out are assigned to B, excluded from A, and consistent with the headset selections. Select Confirm and read back the saved state. On connected headsets, an orange A or B button indicates participation in that group; test each group separately.
4. Test external system → B, B → external system and the absence of that signal in A, using identifiable sources and one active path at a time. If one direction fails, identify the other system’s interface and adapter and compare both manuals before changing Standard/Cross or making a cable. Line Sequence Switching changes the contact order, not the A/B destination. If the groups remain mixed, retain the test record for review and restore the routing needed to continue.

Check both audio device selections in Zoom and both UAC assignments on the hub. Computer detection confirms the USB connection; it does not establish the send, return or headset group assignment.

Hollyland documents connecting the Solidcom C1 Pro Hub to a computer with a USB-C to USB-A cable. The computer recognizes it as Solidcom C1 Pro, with one input channel and one output channel. This path requires that hub: a headset-only system does not provide the UAC connection. Identify the hub, firmware and Zoom version before changing settings.

1. During an agreed pause, record the current audio devices and group matrix. In the Zoom desktop app, open Settings → Audio and select Solidcom C1 Pro for both Speaker and Microphone. Also check that you joined with computer audio and that the microphone is not muted.
2. In the hub’s Group Settings, UAC In receives audio from the computer; UAC Out sends hub audio to Zoom’s microphone input. Check both rows in the intended group and the headset’s A/B selection. Save with Confirm and read back the matrix. One UAC channel in each direction does not provide separate A and B channels.
3. Test the return first: under Speaker, select Test speaker at a moderate listening level. The tone should reach a headset in the assigned group. If it plays through the computer, check Speaker. If it does not reach the position, follow UAC In, the active group and listening level. Do not raise every gain at once.
4. Next, put the headset in TALK, select Test microphone and speak a short phrase. Watch Input volume and listen to the playback. If there is no signal, check Microphone, UAC Out and TALK/MUTE. A moving meter does not identify the voice being captured: listen to the recording and make sure you have not selected the computer’s built-in microphone.
5. Finish with a proposed remote Zoom test: check local voice → remote participant and remote participant → group using different phrases. If the local tests work but the call fails, check audio joining, mute state and device selection at each end. Record the affected direction and restore the initial settings if the test disrupts required communication.

That connection joins two USB audio devices without a host to manage them. Hollyland documents the hub’s UAC connection to a computer; Audinate specifies the AVIO USB-C ADP-USBC-AU-2X2 as a USB 2.0 audio device. Matching USB-C connectors do not establish an audio path between the two.

To evaluate a computer-based bridge, separate three parts: hub → USB, local device → Dante, and Dante return → hub. Dante Via can bring USB interfaces onto the network. Dante Virtual Soundcard (DVS) presents a network audio interface to applications; simply opening DVS does not bridge another USB device to it.

1. Identify the hub and adapter from their labels. Before adding Dante, connect UAC to the computer as Hollyland describes and check both audio directions using the previous answer. If the operating system does not recognize Solidcom C1 Pro, resolve cable, port and detection first. Changing a Dante Controller subscription cannot fix that part of the path.
2. If using Dante Via, check the license, software version and operating system against its release notes. Use wired Ethernet. The guide requires Dante devices at 48 kHz without pull-up. Record existing routing before stopping DVS: Via and DVS cannot run together on the same computer. Do not change the sample rate of an operating network for this test.
3. In Via, find the hub interface as a local audio source and destination. Enable Dante for the resources you need. The guide places them under the computer name in Dante Controller. If they are missing, first check that setting, the selected network interface and compatibility of the installed version.
4. Proposed test: subscribe the intended Dante receiver to the hub send, and route a Dante return source to the hub’s USB destination. Identify channels and check connection permissions. Test each direction separately, then both together. Check UAC In/Out and group assignments; do not feed a copy of the return back into the send, which can create a loop.
5. For a path without a computer, evaluate an analog interface through 4 Wire using the hub and exact adapter manuals. This guide does not specify pinout or levels for an unidentified converter. If the proposed bridge fails the test, remove it from the operational path and restore the saved routing. Keep the results to prepare another configuration.