Skip to content
About

A soundboard made by gamers for gamers.

The story behind CrossVoice, told by the person who builds it.

About CrossVoice

I love games like Mordhau and Hunt: Showdown, and I always liked the voice-line system in Mordhau, and in Chivalry 2 as well. At some point I started wondering how I could use that same mechanic in Hunt: Showdown, and why not, in any other game with voice chat.

That idea became a first prototype in Python that worked through virtual audio devices. The concept worked, but for various reasons the project sat on the shelf for several years.

Later I came across soundboards like Soundpad and what they could do by playing sounds through the microphone. But every soundboard I found worked the same way: one key, one sound. That pushed me to pick the project back up and take it much further than the original prototype. I started experimenting with C++ to build a native audio solution that gave me real control over how sound is handled and transmitted.

From there I built the rest of the application in C#, starting with an interface for managing Profiles and setting up voice commands. I soon realised that playing sounds was only part of the problem: everything also had to work with each game's voice chat, including games that use push-to-talk. That led me into audio routing and low-level keyboard handling, so those key presses could be managed reliably.

CrossVoice Overlay in the Tactical style

As development went on, CrossVoice grew. Profiles evolved to organise commands into Pages, with keys and modifiers, audio Variants, and settings such as volume, pitch and playback speed. I also added a persistent Overlay so you can use and control the app during a match, without leaving the game.

My goal has always been that CrossVoice doesn't depend on any particular game. You set up your Profiles your way and use them across games, without game-specific integrations and without the app needing to know what you're playing.

At that point it didn't make much sense for all that work to stay in my own Profiles. Why not let players share theirs and enjoy what the community creates? That's how the Community side of CrossVoice took shape.

That's how CrossVoice grew from a Python prototype into the project it is today. What started as an idea while playing Mordhau and Hunt: Showdown became a far more ambitious project, in which I've built and extended practically every part of the application.

— Raúl Mateo

Raúl Mateo

About me

My name is Raúl Mateo Sanguino. I studied Computer Application Development and started my career in software development in 2006.

For many years I worked in pharmacy software, building and maintaining management applications, integrations with external systems and solutions that automate pharmacy processes. Over time I took on more responsibility and became head of the programming department at Farmalog, until the company was acquired by a multinational group.

Throughout my career I have worked with many technologies and programming languages, but I have always been especially interested in understanding how things work inside, and in solving problems that rarely have a simple answer.

I am currently studying for a degree in Video Game Design and Development at UNIR, to keep learning and to approach game development from a more creative side.

Outside work, video games have always been one of my great passions, and CrossVoice was born from exactly that mix of programming and games.

How it is built

Out of your way, never inside your game.

Never touches the game

No game memory access, no code or DLL injection, no changes to game files. The Overlay is a separate window on top of the game.

Keyboard first

Every command is one key, so your mouse stays on aiming. Interaction mode pauses your keys whenever you need to type.

Your real microphone

No virtual cable and no new device to select. Lines join the microphone your games already use, and your own voice keeps working.

Local and light

Everyday use runs as a normal Windows user, and your Profiles stay on your PC. During the beta, each start checks your beta key with our server; other data leaves your PC only when you use the Community or send a report.

Try CrossVoice

CrossVoice is in beta. Ask for a beta key and download it: during the beta, you need the key to open CrossVoice.