Known issues

Faults I know about and have measured, so you can recognise one rather than wonder whether it is something you have done. All of these are the unit's own behaviour rather than something this app does to it.

The unit can drop off the USB connection when you reset it

About one time in five, a reset ends with the RØDECaster leaving the USB connection and not coming back on its own. I have reproduced it on my own Pro 2, and the reset command by itself is enough: nothing else has to be going on, no other software has to be running, and it happens just the same with nothing plugged into the unit's second USB socket. It is not this app holding the connection open, which was the obvious suspect and was ruled out with a test that holds nothing open at all.

• What you will see: Every control stops working and the app says it cannot find the unit, or that it is half connected. Your audio may carry on regardless, so silence is not the signal to watch for.
• What to do: Unplug the USB cable in the socket nearest the power inlet, wait a few seconds, and plug it back in. The Help tab, under "If the unit stops responding", has the rest of it, including RØDE's own procedure for a unit that will not come back at all.
• What it costs you: Nothing. The reset itself goes through, and no settings, pads or recordings are lost by the drop. The list on the Backups page will show it once the unit is back.

The unit can lock up when it restores its own backup, so this app no longer asks it to

Measured across a whole day on my own Pro 2, on 21st September 2026, with the app logging every command it sent. Restoring from the unit's own copy of a backup crashed it five times in thirty-one attempts, on three different backups. Restoring from this computer's copy did not fail once in nine attempts, including four long ones back to back.

So the Restore button now always uses this computer's copy. Backing up has not changed: the unit still makes its own copy alongside, because backing up has never caused this, and that copy is there if it is ever needed. Only the way a backup is read back has changed. It takes about two minutes instead of a few seconds, and it restores a little less, which is a price worth paying to not have this happen to you.

This is the unit's own fault, not something this app does wrong. It crashes inside its own firmware while it reloads its settings, and once it did that with a tone left looping on the headphone output. Nothing the app sends is incorrect, and no change to the app prevents it, which is why avoiding it is the only fix available. I am still working on it, and if a way is found to do it safely the faster route will come back.

• Why it matters more than it sounds: If your screen reader plays through the RODECaster, a unit that stops responding takes your speech with it until it is back. That is the reason this was worth changing rather than warning about.
• What it looks like: Audio stops and every control stops answering. Once, it also left a single tone repeating on the headphones, so that can happen but do not wait for it. Windows may still list the unit for a minute afterwards, so the unit disappearing from your sound settings is not the first sign.
• What to do if it happens: Unplugging the USB cable will probably not be enough, because the unit itself has stopped rather than the connection. Pull the power lead, wait half a minute, and plug it back in.
• What it costs you: Nothing is lost. The restore goes through before the unit stops answering, and the backups on the drive are untouched. Check your monitor speaker level when it comes back, because a restore moves it.
• Where it can still happen: Two places, both of which you have to choose deliberately. Resetting the unit to factory settings uses the same part of its firmware. And a backup the unit made on its own, with no copy on this computer beside it, can only be restored the unit's own way; the Restore dialog tells you when that is the case.

Voice effect pads that do nothing, after a reset from somewhere else

When the unit loads its default show, the six factory voice effect pads come back with the right name, type and colour, but the effects themselves do not come back with them. The pads read exactly as they should, and the unit accepts the press and shows the pad as engaged, but your voice is unchanged.

• When it happens: Only when the desk is reset by something other than this app: its own touchscreen, RØDE's software, or another tool. "Start again from factory settings" on the Backups page rebuilds the six effects as part of the reset, and so does restoring a backup with "Reset them to factory first", so you will not meet it there.
• How to recognise it: The SMART pads page says so in as many words: six voice-effect pads have no effect to play, so they do nothing. Nothing on the unit's own screen shows the fault at all, and a keyboard shortcut on one of those pads still reports the effect as on, because the press is accepted; there is simply nothing behind it to play.
• The fix: On the SMART pads page, Maintenance tab, choose "Restore the factory voice effects, Censor and Ducking". It rebuilds those six, and the Censor and Ducking pads with them, because all eight can be rebuilt from settings alone with no sound file needed. That means pads 9 to 16 are cleared and recreated, so move anything of your own off those positions first. Nothing past pad 16 is touched. It takes two or three minutes, and it is worth an ear-check on each one afterwards.