Skip to main content

jaxpee - Voice Prompt Editor for TurtleBeach PX51 and XP510

After searching all over the net for the best wireless surround gaming headset compatible with about every console and PC I ended up with a TurtleBeach XP510.

Actually this peace of hardware is programmable in about every way you can think of, like simulated angles of speakers and stuff like that. The only thing I found not to be editable are the voice prompts of the headset, so I decided to write a program for creating custom voice prompts.

The result you can find here: jaxpee BETA v0.9 (modern HTML5 browser required, JavaScript must be enabled!)

If I get enough feedback on this I will adjust jaxpee for the Tango headset - just need someone to test the files since I don't have a Tango.

DEMO file (with some Super Mario sounds) [PX51XP510]-jaxpee-mario.mem



  1. You can record directly from your mic into the website.
    Since the size of the chip is VERY limited it is better to use some programs like Audacity to cut unneeded space away before uploading the files. You can upload wav, mp3 or ogg-files.
  2. Use short commands!
  3. Don't rename the file!
    The "Advanced Sound Editor" checks validity of the mem-files by their name! For PX51 and XP510 they need to start with "[PX51XP510]"
  4. After each upload or undo the mem-file is generated.
    So you actually can always download the current mem-file (as long as the files are not too large)


The TurtleBeach voice prompt files are "mem"-files for an integrated chip manufactured by nuvoton. I guess its an ISD2130 with 1MBit memory (which is 128KByte - the size of the mem-files)

This mem-files contains some header and configuration bytes (not to mention here), the voice prompt files and voice macros which tell the chip how to play the voice prompts. The problem of just replacing the voice prompt files is the size of the file (only 128KB) and the codecs of the files. Since the chip is made for voice it uses some adpcm-codecs, which you also can find when it comes to VoIP. To make the wav-files small enough the codecs are somewhat optimized, so the standard G.72x-adpcm-codecs do not seem to work or the files are to big. (For the freaks: the chip uses up to four steptables, not just one like "normal" adpcm.)

Actually you cannot brick the headset. If you upload a wrong file the voice prompts just don't work. Just re-upload the default voice prompts. Anyways: NO WARRANTY!