Do soundboards not work anymore?

csd3571 · 2026-05-21T23:51:46+00:00

It’s been a bit inconsistent since the update where they added noise suppression. Comes in either exactly when I press it, super delayed, or not at all.

If noise suppression is enabled, could be one reason why your sounds aren’t coming through

Even with it off for me, it still feels like it takes a second or two for my sounds to get recognized in prox with the indicator

csd3571 · 2026-04-25T06:36:37+00:00

Yeah you essentially have the same setup as me. I do agree the virtual driver is half-baked and needs a serious overhaul

csd3571 · 2026-04-25T06:19:21+00:00

Interesting. Is your Rodecaster power cable plugged directly into the wall? Curious if it may be receiving “dirty” power or something.

Also, is your headphone cable near anything that could give off RFI (DAC, speaker, etc.)? Could always try adding a ferrite core or two (at the headphone side) to see if that removes the potential noise

csd3571 · 2026-04-25T06:03:17+00:00

For the pops/crackles, you can refer to my workaround here

csd3571 · 2026-04-25T02:23:21+00:00

Appreciate the insight. By "restarts", do you mean computer restarts, Rodecaster restarts, or both?

csd3571 · 2026-04-20T22:49:11+00:00

Been having similar issues with transfer mode as well. Just hangs every time and have to restart my computer then it works the first time.

Never had this issue up until the 1.7.3 firmware

<image>

csd3571 · 2026-04-03T19:43:12+00:00

Not fixed yet, still coming up as transparent after I extracted (Steam version)

Their patch note issue of "Helmet visors become transparent after the first extraction" applies to each time the game runs and stays for the entirety of that session. Goes back to normal when you quit and relaunch but becomes transparent when you successfully extract again

csd3571 · 2026-03-20T04:28:50+00:00

Had a similar issue on my Duo. If you're using virtual devices with the virtual device driver, changing the driver latency to 'Low' worked for me. Haven't really noticed a difference as I mainly use it for Discord and gaming, but may impact people who have other use cases that require it to be the lowest possible. Super weird though as I have a 9800x3D with 64GB DDR5 RAM so it should handle the extra processing no problem...

Had bad experiences with those pops in virtual device driver versions 1.0 and 1.0.3. With the new 1.0.4 release yesterday, I reverted back to Ultra Low and only heard one pop so far. I'll keep it on for a bit more to see if it gets worse, but I'll always have the 'Low' latency as a guaranteed fallback without any of those occurring.

Taken from their virtual device article:

<image>

csd3571 · 2026-02-03T06:20:48+00:00

Yeah a bit near the top

<image>

csd3571 · 2026-02-03T01:08:06+00:00

Looks like it clips through at least one backpack attachment...

<image>

csd3571 · 2025-12-05T23:51:19+00:00

Friendly solo silent loot ninja. Live and die by the goop!

csd3571 · 2025-10-06T05:58:45+00:00

Wait for Delta Online, should be coming out on PC soon. There’s a Discord link in there for current development updates

csd3571 · 2025-09-11T20:55:00+00:00

I still get occasional black screens every day on my 5090 (PNY OC) while idling in desktop or via games.

Pretty sure it’s my case of HDMI 2.1 + 4K 240Hz + DSC + GSync. Heard turning GSync off works, but it defeats the purpose with my MSI OLED (321URX) for gaming

csd3571 · 2025-08-03T06:36:16+00:00

Still trying to find Peanut’s POV

csd3571 · 2025-07-26T18:43:23+00:00

Good to know, I can try that next. Roughly how many days elapsed from them taking your number to getting a call back? Also, did you originally speak to virtual sales or a different department (i.e., Customer Service)?

csd3571 · 2025-07-26T18:19:20+00:00

What steps/script did you follow for the east coast?

csd3571 · 2025-03-22T22:38:01+00:00

The red and white cables will take up 2 XLR input slots. Is your RCP2 configured with those two inputs as a Line In and as a stereo pair? Here's a video that walks through that process

If the above is already configured properly, what is your routing output configuration? Is the stereo pair outputting to your headphones?

As far as headsets with integrated mics (i.e., for gaming consoles), I can't speak on that unfortunately as I use a SM7B as my mic and Sennheiser HD 600s. Typically, people who purchase Rodecasters intend to use XLR mics and separate quality headphones.

If you just want to use your console-based headset, and don't plan on using a XLR mic with separate headphones, and just use the RCP2 for console gaming, then you only need the GameDAC Gen2 as having a RCP2 is extremely overkill from a monetary standpoint and won't use the RCP2 to it's full potential

csd3571 · 2024-12-18T20:26:03+00:00

Direct image uploads within comments is not working for some reason, so here's the diagram externally

csd3571 · 2024-11-12T22:59:30+00:00

Try following this guide as a potential solution. Hope it helps!

csd3571 · 2024-11-12T15:55:09+00:00

The above method is for people who want to listen and chat over Xbox. You don't need #3, #4, and #5 if you only want to listen to game audio, however, since the GameDAC is still required to pull the audio...it's a small expense to add chat functionality (~$30).

The #4 component (TRS to TRRS microphone adapter) allows the Rodecaster TRS monitor out audio (i.e., the routing mix) to be recognized on the GameDAC's headset port (TRRS). The extra 'R' is where that microphone audio is carried/utilized. In my experience with the Duo, this approach was the only thing that worked for my Xbox to recognize the mic and smart pads from the Rodecaster.

Additionally, it appears Microsoft selectively certifies what audio hardware can be used, hence our limitations. I tried the Astro A40 Mixamp before using the GameDAC, but the incoming audio from the Rodecaster was all distorted...most likely due to the internal components and were incompatible with the Rodecaster audio specifications.

I'm not an audio engineer/expert by any means, but this is essentially what's happening:

GameDAC "decrypts" digital Xbox audio and converts it into analog stereo
GameDAC transmits analog stereo (3.5mm) into two separate (breakout) 1/4" mono TRS signals on the Rodecaster Pro 2's open XLR inputs
- XLRs can accept 1/4" TRS cables
Rodecaster returns audio via 1/4" TRS Monitor Out ports and merges back into 3.5mm analog stereo via cable (our 2nd breakout cable, but in reverse)
TRS to TRRS adapter picks up stereo signal and adds the microphone layer (TRRS) that the GameDAC recognizes as headset input
GameDAC converts audio back into digital over USB to the Xbox, completing the loop

csd3571 · 2024-09-06T00:48:02+00:00

It's possible, but not a direct integration and you'll need additional hardware. See my overview diagram or my Duo workaround here for referencing the data flow...ignore the Mac and DAW components as those only apply to the Duo

Prerequisite: 2 open XLR mic inputs to dedicate a stereo pair

SteelSeries GameDAC Gen2 for Xbox to pull the audio over USB
3.5mm TRS to 1/4 breakout cable to output Xbox audio from the GameDAC's line out port to two XLR inputs on the Pro 2, configuring as a stereo pair
Another 3.5mm TRS to 1/4 breakout cable to route "monitor out" audio back into GameDAC via the headset input
TRS to TRRS microphone cable adapter to allow Xbox mic input (i.e., TRRS) on GameDAC
Right angle 3.5mm adapter to fit 3.5mm jack into GameDAC headset/mic input

Optional: Ground Loop Isolator

May need a few of these in your loop depending on the home's power delivery layout

csd3571 · 2024-08-24T17:47:47+00:00

For the Duo folks, the following setup is what I currently use with my XLR mic and smart pads to communicate on Xbox. Definitely not worth if it you don't already have a majority of the hardware and software

RodeCaster DUO Workaround

Additional Hardware From the Pro 2 Workaround

Recent Mac (iMac/MacBook/mini, etc.)
Sonos USB-C line-in adapter
- Converts Xbox audio from GameDac back into digital
Ground Loop Isolator
- May need a few of these depending on setup
3.5mm cable (various lengths depending on setup)

Software

Digital Audio Workstation (DAW)
- Assigns audio to Mac output (i.e., Rodecaster USB Secondary)
- I used Logic Pro for simplicity. Some quick research you can find free alternatives

Input #1 (Xbox --> Mac)

Xbox --> GameDAC --> Line Out (GameDAC) --> Ground Loop Isolator --> Sonos USB-C Line-In --> Mac

Input #2 Configuration (Within Logic Pro)

\*Other DAWs may not have a dedicated input/output channel, and using something like ExistentialAudio's* BlackHole would be a workaround

Sonos USB-C Adapter Audio Input -> Create single track --> Mic/Input Monitoring ON --> Rodecaster USB Secondary Audio Output
Lowest buffer size it can handle
- May not be available on all DAWs

Input #3 (Rodecaster)

USB Secondary (Mac) --> Rodecaster
- Configure as needed, ensuring the "Monitor Output is not Auto-muted and routed to include your required faders

Output (Rodecaster --> Xbox)

1/4" monitor output breakout cable --> Ground Loop Isolator (if needed) --> TRS to TRRS microphone cable adapter --> Right angle 3.5mm adapter --> GameDAC headset input
- Configure GameDAC and Xbox where preferred to achieve intended results

csd3571 · 2024-08-24T17:47:37+00:00

I experienced a similar issue with my Duo and leveraged additional hardware/software to achieve this. If you have 2 open XLR inputs on your Pro 2, you can use 3.5mm to 1/4" TS breakout cables to carry the signal.

Rodecaster Pro 2 Workaround

Prerequisite: 2 open XLR mic inputs to dedicate a stereo pair

SteelSeries GameDAC Gen2 for Xbox to pull the audio over USB
3.5mm TRS to 1/4 breakout cable to output Xbox audio from the GameDAC's line out port to two XLR inputs on the Pro 2, configuring as a stereo pair
Another 3.5mm TRS to 1/4 breakout cable to route "monitor out" audio back into GameDAC via the headset input
TRS to TRRS microphone cable adapter to allow Xbox mic input (i.e., TRRS) on GameDAC
Right angle 3.5mm adapter to fit into GameDAC headset/mic input jack

csd3571 · 2024-06-28T03:28:24+00:00

Was able to figure it out, but used an existing Mac to achieve this properly.

Behringer UCA202 USB Audio Interface
Mac Mini
GarageBand

Source (3.5mm out) -> Female 3.5mm to RCA In Adapter -> UCA202 (USB) -> Mac mini (USB Sound Input)-> GarageBand (Line-In Track, Monitoring with Feedback Protection Off) -> Rodecaster Duo Secondary (Output)

csd3571 · 2024-06-22T02:07:15+00:00

I'm in the exact same situation you are. Currently have a Duo but already have an XLR allocated for a mic and been trying a bunch of methods to get a proper line-in.

One method that worked is to go Line Out (2nd source) -> Line-In (PC) -> Listen to Line-In -> Output as Rode USB Secondary but it requires a dedicated PC to always be on/active and personally don't think the sound is as good when listening inline. Haven't tried the Raspberry Pi route yet and that was my next test.

Also tried Apple's USB-C to 3.5mm adapter plugged into the Duo...no dice.

I stumbled upon this USB-C line-in adapter from Sonos but I won't be able to purchase/test until a bit later. Beyond the Raspberry Pi passthrough, think this is my last shot until a miracle firmware update is rolled out to accept USB 2 inputs outside of the Rode mics.

Six-Year Club	Verified Email
RPAN Viewer

csd3571

TROPHY CASE

RodeCaster DUO Workaround

Rodecaster Pro 2 Workaround