27 Replies
Unfortunately for some things that the GoXLR can do, it can be more difficult or impossible to replicate all the functionality of the GoXLR on most "equivalent" audio mixers and interfaces.
If you mean the RODE RODECaster Duo, it should be able to replicate most of the functionality, although the effects processing might be a bit more difficult to use and be less intuitive to some.
Other than that, it can be made to do pretty much everything else out of the box, as far as I know. Just has a bit of a learning curve in comparison.
I'm actually not sure about the voice FX
But everything else should be doable
I know the effects can be applied to a source, not sure if they can be applied with a button press
Probably though
Unknown UserOP•2y ago
Message Not Public
Sign In & Join Server To View
Also the free and open-source replacement application is being actively developed and will probably replicate all of its features if not more
GitHub
GitHub - GoXLR-on-Linux/goxlr-utility: An unofficial GoXLR App repl...
An unofficial GoXLR App replacement for Linux, Windows and MacOS - GitHub - GoXLR-on-Linux/goxlr-utility: An unofficial GoXLR App replacement for Linux, Windows and MacOS
Unknown UserOP•2y ago
Message Not Public
Sign In & Join Server To View
Especially since the official app still works for the forseeable future
Unknown UserOP•2y ago
Message Not Public
Sign In & Join Server To View
The utility actually seems quite good
From what ive seen its already added more functionality than the "supported" software has
Yeah, it appears to at least be 99% functional
There are some open GitHub issues, but IDK if they affect most use cases or if they are able to be worked around, etc
Yeah the GOXLR isnt dead. The compnay laid off staff. Allot of content creators capitalized with clik-bait over the announcement so it got blown out of proportion. I am keeping mine, although I do not currently need it. The GoXLR on Linux looks dope.
...ooops deleted post on accident
I've got the Rodecaster Duo. It will do most of what the GoXLR does, but the workflow is very very different. You're going to do all your mixing and submixing on the device, and it uses the two Mic (Duo Main stere/multitrack and Duo Chat) as your only input into OBS. You don't use the desktop audio at all. Just spent over an hour on a call with Rode confirming this. If you do it the traditional way, using Mix Minus, you'll end up with a loopback in windows to the Mic input from your playback sources. According to Rode, that's the way they built the device.
If your GoXLR is still physically functional, I'd stick with it until it breaks, or Rode figures out what it's going to do with the next firmware update, which is supposed to add additional virtual channels.
If you use the USB 1 connection you get two stereo devices available on windows with stereo in + out. You aren't limited to only capturing the mic inputs or the multitrack. You can create a submix on every output of the mixer. Furthermore, if you connect the second USB connection to the same PC you get another input & output.
With both USB connections OP could route his discord, game, and system volume to different sliders. Use one of the 3 available USB inputs to route his mic/pads/fx back into the PC using a submix with no loopback issues.
It's worth noting that if you wanted to connect video game consoles, especially ones that don't support audio over USB (like the analogue pocket); you'd be best off getting the Rodecaster Pro II. As you can use mic/line inputs 3/4 with an HDMI audio extractor to pipe console audio into the mixer.
It's true that Rode is working on an update to add additional channels over the USB connections, but based on what OP wants the current version of the Duo can do everything requested. Even with additional digital channels he'd likely already be using 6/7 sliders (4 physical + 3 digital).
1. mic
2. discord / voice chat
3. game audio
4. system audio
5. pads / fx
6. phone over bluetooth
This would be another reason to consider the Pro model. If you end up wanting a few more sliders down the line; the Pro has a total of 9 (6 physical + 3 digital).
It doesn't matter if you get the Pro II or the Duo. You're going to have the same issue with the way the USB works in Windows with the cross loop from each output into the input. Even with no monitors attached, the playback from Main output shows up in Main Input in OBS or Reaper if you actually use the outputs in Desktop Audio and/or Desktop Audio 2, unless you go into custom routing and remove all of the outputs, which is fine, but it doesn't allow you to use the submix option.
According to Rode, this is how the devices are intentionally designed. When I connected with them, they had me remove the two outputs from Desktop audio and only leave in the Main for Mic/Aux. If you want multi track, they advise you to use the Asio driver functionality, which would be fine, but it fails on the two machines I've tried to use it on, and you don't see the channels. Both in OBS and Reaper. In OBS, you only see mute.
I own both products and I don't understand the issue you're describing. If you disable the multitrack option in settings you can submix on every output without exception. There are no loopback problems.
The reason Multitrack fails is because you're initializing both chat and main in another application, or just in windows itself. For multi-track to work you can't send output to main from windows. You have to send output to main from the application that is hooking the asio driver.
Because of this limitation multi-track is kind of dead on arrival for streamers. Maybe when they add more virtual channels you can still use multi-track and send more than one output over USB 1 outside of the ASIO connection.
My advice is to disable multitrack and use custom routing on select outputs.
In OP's case, he'd want to configure everything as follows
single pc
mixer
- disable multitrack
- enable custom routing on following outputs
- speakers - route everything but your mic
- usb 1 chat - route only your mic & soundboard
- bluetooth - route only your mic & soundboard
windows
- output
1. set default output device as USB 1 main
2. set default communications device as USB 1 chat
3. route game audio via windows volume mixer or directly in game settings to USB 2
- input - USB 1 chat
discord (optional)
- output & input - USB 1 chat
obs
- ouptut capture
1. USB 1 main as system audio
2. USB 1 chat as discord audio
3. USB 2 as game audio
- input capture
1. USB 1 chat as microphone/soundboard
2. Bluetooth as phone
dual pc
mixer
- disable multitrack
- enable custom routing on following outputs
- speakers - route everything but your mic
- usb 1 main - route only USB 2 (sends game pc audio to capture pc)
- usb 1 chat - route only your mic & soundboard
- usb 2 - route only your mic & soundboard
- bluetooth - route only your mic & soundboard
game PC
windows
- output & input - USB 2
stream PC
windows
- output
1. set default output device as USB 1 main
2. set default communications device as USB 1 chat
- input - USB 1 chat
discord (optional)
- output & input - USB 1 chat
obs
- ouptut capture
1. USB 1 main as capture pc system audio
2. USB 1 chat as discord audio
- input capture
1. USB 1 main as game pc audio
2. USB 1 chat as microphone/soundboard
3. Bluetooth as phone
Happens both in multitrack or stereo. Unless you disable the monitoring as described and shown in my screenshots, you get a loop into the opposite input in windows.
It also doesn't matter whether you use the Main or Chat microphone. It'll loop back from the Main output to the Chat input, or vice versa.
It also doesn't mater what you have chosen as default in the Sound Control Panel.
These screenshots are with no externally, so there is no chance that the mic was picking up any sound.
The problem is...I shouldn't have to exclude each device. Mix minus should do that.
According to Rode, the way this works is on purpose. You're supposed to just be using the Main Mic into OBS because the mixing is supposed to take place on the device, and if you want Multitrack use Asio.
Sounds like you have a principled issue with the default functionality of mix minus... but you can just use custom and create the mix minus you desire, excluding the one source that loops back.
Whatever the case, with proper custom routing you don't experience loopback. And every source arrives in OBS isolated.
Some people like to have the mix that they hear go to OBS, or a mix that's slightly different but still changes with their physical faders. I've always found this to be undesirable. Rather, I want a clean feed of each source individually mixable on OBS. So I can create a static mix for the audience.
If you use custom routing to remove all other channels for both USB1 and Chat, such as pictured in the attachment, then yes. It works fine. But then you're left with an inability to mix using those channels to create submixes. If you do you get the cross channel loop back from the outputs into the input, within Windows.
Mind you this only happens in Windows, and not on the device. Because, as Rode told me directly both on the phone and in a remote session onto my machine, the device is designed that way. To mix on the device and then used in the manner described in my last post. They had me put ONLY the Main Mic into Mic/Aux in OBS, leave Desktop Audio and Desktop Audio 2 disabled, and said that if I wanted multitrack recording to use the Asio driver (which also doesn't work either on OBS or Reaper).
And there's nothing wrong with that inherently, but that's not the way any of us use an interface...or the way any other interface I've owned with built in mixers, work (GoXLR, Presonus io24). There should be complete separation between what windows sees as in input, and what it sees as an output, particularly if they're going to market it as a device for streamers.
This is the Video Rode just sent me to watch in as a reference the current Tech support email chain about the issue with the second unit, where they tell me they can't reproduce the issue. https://www.youtube.com/watch?v=GvioikJxv1Q
Check the 5:29 mark. That's the way they expect the unit to be used. You do not use the USB Main or Chat outputs in OBS.
They can't reproduce the issue because they don't expect the unit to be used the way most streamers are going to use it, and then return it because it doesn't work the way they expect.
This isn't a deal breaker. It's an outstanding piece of gear. You just have to change the way you do things and your expectation for multi track recording.
KidShadoe Studios
YouTube
How To Setup Your Rodecaster Duo For Streaming
This video shows you how to setup your Rodecaster Duo for Streaming, as well as setup your mic EQ and routing for stream and discord!
#rodecasterpro #streamer #streamingtips
-----------------------------------------------------------------------------------
KICK ►► https://kick.com/kidshadoe
TIKTOK ►► https://www.tiktok.c...
I personally wouldn't recommend using your mix, or any volume variation of it. I understand that it's "simple" and that makes it desirable. But it's better to use custom routing and have isolated sources in OBS. Why? Because OBS has awesome audio mixing capabilities that allow you to create static mixes per scene.
If I'm not on a scene showing my gameplay I don't want my stream to hear my gameplay audio. Same principle for all sources. Sure, you could mute sources via the mixer as needed, but there won't be smooth audio transitions, and it's super hands on. If I'm playing a game like Valorant I want my game audio excruciatingly loud in my mix, but not my audiences mix. With the Rodecaster series you can link two different levels to the same fader... but I really don't want my fader controlling what the audience hears at all.
If you have access to individual sources within OBS, and you properly mix them; your audience will only hear what's relevant to each scene at pleasing volume levels. This also allows for nice audio transitions between scenes and no need for constant management.
Anyways, didn't mean to jack this thread. I just wanted to chime in to say the Rodecaster series is absolutely a great replacement for the GoXLR. And it continues to get better with every update. Soon enough we should have additional channels over USB and networked audio via ether (not sure if NDI or Dante).
I'm honestly shocked by how much thought they've put into the feature set. The only better system is hyper-expensive modular professional gear, like RME sells. For most people completely overkill.
Don't get me wrong, I'm not using it the way Rode is recommending. I'm using pretty much the same way I used my previous interfaces with mixing capability. Custom routiing in the devices allows you to isolate the channels, and then set up your scenes/sources as you always have if you had a GoXLR or Io24, etc. I am not using the device the way they suggested in that video.
This is a great piece of kit, and I agree...they've really put together something special. The sound quality is excellent and the possibilities and use cases are very wide.
The the only real "issue" is more of a fundamental difference in thought about the way the device interfaces with Windows than how cometitors have done it. I've now had multiple conversations with Rode Technical support and gone back and forth with them, and Sweetwater's tech team, over various methods of setting this up to work with OBS and/or a DAW. The design and thought process comes down to the fundamental truth that the RCPII and Duo are mixers that are designed to allow you to interface with windows and allow you to use a source on windows as an input. They have designed the device to work like most every other mixer in that you are bringing in external sources, mixing them on the device, and sending that mix to Windows as a single mixed output. Which would be fine if you didn't intend to use multiple channels in OBS to record, and have a need to use multiple playback sources as separate channels. The USB1, Chat and USB2 connections to your PC(s) are not isolated from one another in Windows between the Playback and Recording channels by default, which is what you need to assign applications to each of those channels. Without using custom routing, they loop back across each other into the recording device (Chat to Main, and Main to Chat) even with mix minus on. It's overcome with custom routing, but not well documented how to do so.
How they have designed this device, and expect it to be used, is even more starkly realized if you use the multitrack capability of the Main on USB1, and use ASIO with Rode's ASIO driver. According to Kurtis from Rode Tech Support, the ASIO driver will need exclusive access to the USB1 Main device, so if it happens to be in use in a different program, it won't be able to run or take access for itself. If you select RCPII/DUO Chat or RCPII/DUO Secondary as the Windows Default system output, it allows the main output to be available for the ASIO driver. You then can use ASIO with the OBS plug, or in your DAW (I use Reaper). It's actually lower latency that just using the standard outputs in the manner outlined earlier.
When you do this, you can't route any audio from an application to Main Multitrack/USB1. The applications just won't route there in OBS, and if you have it set up to route there, with nothing playing, set up your ASIO sources, and then play something back that is routed to Main, that application will give you a sound error (in a brower it'll tell you that you need to restart windows). If you open OBS up with something using Main, the ASIO sources will only have mute available.
You can only use one application at a time that uses ASIO, so you can't have your DAW open and use something like ReRoute into OBS.
So while you will are able to use the full multitrack capability of the RCPII or Duo with it's full mixing capability, you lose Main as a playback channel from Windows.
All of this may become a moot point as the plans are to add further virtual channels to the firmware within the next 2 or 3 releases, as it is THE most requested feature, and while they won't give a timeline for when that will be, Rode has announced it is going to happen in their official Discord
At that point you'll have several options for setup. They are just poorly documented by Rode and reviewers.
Yeah I tried to explain that bit earlier
The reason Multitrack fails is because you're initializing both chat and main in another application, or just in windows itself. For multi-track to work you can't send output to main from windows. You have to send output to main from the application that is hooking the asio driver.Just to link the message in question.
I got confirmation from Rode yesterday that the next update is to add more USB channels.
Hopefully that either allows for
1. ASIO on main + a couple extra channels to make up for the lost output channel
2. enough channels that you can route everything individually without ASIO in the first place
Option 2 is still superior IMO as WDM channels are accesible system wide and not locked to a single application during use.
I do agree though that most people who reviewed these products have missed the optimal routing configuration. I'd like to make a video on this soon.
Sorry about that. I misunderstood what you were talking about at the time. I thought you meant in OBS, not in Windows Sound itself. Didn't sink in.
I could live with either solution, but I agree...I'd rather not use ASIO outside of my DAW. I've tried it before with OBS and never really cared for the workflow. Too complicated and too fragile.
Most of the people who have reviewed the product have completely ignored the routing configurations for the way a streamer or content creator recording video, with multiple Windows audio sources, would want to use it. All the way back to the first RCPII videos 2 years ago. That video I posted was what Rode sent me as the "solution" for how to set it up correctly with OBS. They don't seem to understand what is being asked for, every time I talk to them.
Hopefully a couple of firmware upgrades down the road (or Rode I guess) will give us the additional channels they've talked about and we'll see where we go from there.
npnp, this stuff is pretty complex