How to Delete Recordings from Rode Interview PRO on Linux
The Rode Interview PRO wireless microphone stores recordings on internal flash. When you connect it via USB, it shows up as read-only mass storage — you can copy files off, but you cannot delete them from the host. Rode’s official software (Rode Central) handles the delete, but it only runs on Windows and macOS.
This guide shows you how to delete all onboard recordings from Linux using krode, an open source tool that replicates the delete command via the device’s USB HID interface.
Requirements
You need hidapi installed:
# Debian/Ubuntu
sudo apt install libhidapi-dev
# Fedora
sudo dnf install hidapi-devel
Installation
The easiest way is the prebuilt Debian package. Download the latest .deb from the krode releases page and install it:
sudo dpkg -i krode_*.deb
This also installs the udev rule that lets you run krode as a regular user, without sudo.
After installing, add yourself to the plugdev group, then log out and back in for the change to take effect:
sudo usermod -aG plugdev $USER
Manual install (without the .deb)
If you prefer to build from source or are on a non-Debian distro, clone the repo, run make, and install the udev rule yourself:
sudo cp udev/99-rode-interview-pro.rules /usr/lib/udev/rules.d/
sudo udevadm control --reload-rules
Then unplug and replug the microphone for the udev rule to apply.
Usage
Connect the Interview PRO TX unit via USB, then run:
krode delete
The microphone wipes its onboard storage and returns a success code. That is it — there is no per-file delete because the device itself does not support that. The only operation is “wipe everything.”
Notes
krode has been confirmed working on TX unit 1 (USB PID 0x0063). The second unit (PID 0x0068) uses the same protocol but has not been explicitly tested for the delete command — if you try it, please report back in this thread.
If the command fails silently, check that your user is actually in the plugdev group (groups | grep plugdev) and that you logged out and back in after adding yourself.
Discussion
Questions, bug reports, or successful confirmations on PID 0x0068 are welcome below. Source code and protocol details are on GitHub.