Not an issue but a Option for me to help

[SelfishEagle]

If you take a look on my github page I do have a semi somewhat working App you can build off For Multi Channel processing with linux for the Rodecaster pro2. The mixer is a daily driver for me and i am starting the move to linux so started up a project :) . Please feel free to take a look and build off it

[TheInfamousAlk]

I have no coding experience at all, but I have a rodecaster duo and I'm running CachyOS. I can help with testing or other things on my hardware.

Currently all virtual devices work fine for me, but I'm interested in this software for managing buttons and functions of the device.

[SelfishEagle]

I have no coding experience at all, but I have a rodecaster duo and I'm running CachyOS. I can help with testing or other things on my hardware.

Currently all virtual devices work fine for me, but I'm interested in this software for managing buttons and functions of the device.

We need the Rode App for the Rodecaster pro 2 to be reverse Engendered as much as possible so that we know what triggers what and how its trigger so that we can make all features of the Windows version work on Linux.

My current version Allows for the Multi Channel Processing ( Current 3 in the app ) And can be controlled over the mixer.

I saw this project and decided to help as much as i can and thats where i got to on my project. It is fully open source for anyone to download and use and improve on.

If you able to revers engineer the app as much as you can that would help people like myself and Jordan out a lot.

Just keep in mind. I dont reverse engineer i ususaly just code. It took me roughly 2-5 days to figure out how to reverse engineer just the Audio Sliders to get them working properly and even now they are still buggy af.

[Jordan-Milner]

Hey! Thanks for the note - yeah I started noodling with this a bit and haven't been able to spend much more time with it - at one point I nearly bricked my Rodecaster 2 so I got a little spooked away from it. When I get some time I'll take a look at your project and see how I can contribute.

[SelfishEagle]

Hey! Thanks for the note - yeah I started noodling with this a bit and haven't been able to spend much more time with it - at one point I nearly bricked my Rodecaster 2 so I got a little spooked away from it. When I get some time I'll take a look at your project and see how I can contribute.

No problem I have Channel's Working like i said only 3 as of now. Game Chat and music. You can easily set the channels and controll the volume with the sliders. I need more Reverse engenire to be done so i know what protocall the Buttons use and what protocall the software uses when a Sound is uploaded to the sound board.

Ive noticed a lot of the stuff is handles via the mixer's built in software and not by the Windows APP. From what ive noticed the windows app is purly for uploading sound board clips and configuring some of the stuff on the Device. The rest of it is done on the device its self.

[parzival-space]

Hi, I just found out about this repository. I recently started (late 2025) working on getting as much of the RODECaster Pro II working on Linux as possible.

Recently my PR for the Alsa UCM device config of the RODECaster Pro II was merged with PR 656 in alsa-project/alsa-ucm/conf, so Virtual Devices should work out-of-the box in the future on all major distros once that gets released. Until then people can still use my, at parzival-space/rodecaster-pro-2-virtual-devices-pipewire pubished, pipewire configuration to get them working. Arch Linux users should already be able to install them now using yay -S alsa-ucm-conf-git.

A few months ago I also started playing around with the devices USB protocol with the goal of building a simple configuration utility in rust (similar to what this project wants to accomplish).
My goal is to create something like the GoXLR Utility but for the RODECaster Pro II (and possibly other RODE products).

Currently I am trying to understand the protocols frame format. So far I think I understand most of the header including the general packet structure.
I published the project as parzival-space/rodecaster-utility and track my notes of the USB protocol with the issue Reverse Engineering the USB Protocol #1, but any help is greatly appreceated.

I am posting here because I think we all might be able to work together. Anyone that is able to help figureing out the protocol structure will be a hughe help.
I mentioned some usefull guides on gettings started in USB reverse engineering in my first comment on said issue.

Currently I am able to initialize the device and make it start sending device update messages (faders moved, channels muted...), but I am not yet able to understand them.

So if you guys learn anything new about the protocol, or want to help 😄, I would like to kindly request to also post your finding in Reverse Engineering the USB Protocol #1. Thanks :)