RaiderPro – Real-Time Audio Rider & Automation Plugin (Early Access Ends March 31)

[diegorcortega]

Hey everyone,

I’m Diego Ortega, developer and founder of Casa Occidente. I want to share with the KVRAudio Forum folks RaiderPro, the latest plugin that I launched with early price December last year. This platform has been very helpful to index my software in the internet and I want to participate more on these forums. Thank you KVRAudio folks for this platform

RaiderPro is a real-time volume riding & automation plugin designed to maintain consistent levels without manual automation or compression artifacts. Have you experienced the pain of automating volume manually? Is pretty time-consuming. Do you use tools that won't add coloration to the sound like compressors?

It works great for:
• Live sessions
• Vocals
• Podcasts / voice over
• Instruments

Key features:
– Target level control
– Attack modulation for fast dynamic changes
– Range-based movement
– Vocal and music sensitivity
– Sidechain input
– Automation writing

There’s a fully functional 7-day free trial available.

Early Access pricing ($28 USD) ends March 31.

RaiderPro UI:


Check the demos here:
RaiderPro used in rock band live session:
RaiderPro used in a podcast vocal:
After-Before-After demo:

The plugin is also available at KVRMarketplace https://www.kvraudio.com/marketplace/ra ... -occidente

Would love to hear your thoughts or answer any questions.

https://casaoccidente.com

[metalifuxx]

I’m sure it’s just entirely pure coincidence that it looks exactly like Waves Bass Rider? It’s not a hardware device so the GUI could have been anything you wanted it to be…

[diegorcortega]

I’m sure it’s just entirely pure coincidence that it looks exactly like Waves Bass Rider? It’s not a hardware device so the GUI could have been anything you wanted it to be…

I get why it might look similar at first glance — tools in this category tend to follow a familiar workflow so they’re easy to use right away.

RaiderPro is a fully original implementation built from scratch, with a focus on performance, low CPU usage, sidechain support, and attack control for more responsive behavior.

One of the goals was to make it flexible across different use cases, including working with multiple types of audio sources through its adaptive behavior.

I’ve also been putting a lot of work into stability (auval / pluginval) and ensuring smooth real-time performance without added latency.

If you’re curious, there’s a free 7-day trial — I’d genuinely love to hear how it behaves in your workflow.

[hightyde]

Ironically I came here to ask the same question. Except instead of waves bass rider, I was going to say it looks exactly like waves vocal rider except it uses bass riders color scheme. Like the above commenter mentioned, it’s not based off hardware so it literally could have looked like anything else. There’s plenty of gain rider plugins that look nothing like the waves version. My worry is in potential design lawsuits that could be filed by waves, potentially? Obviously I support the cause and I love new plugins, but man does it look just way to similar to the waves version. Maybe in future updates, I’d like to see some sort of UI change/uograde to separate itself from the waves counterpart.

[diegorcortega]

Ironically I came here to ask the same question. Except instead of waves bass rider, I was going to say it looks exactly like waves vocal rider except it uses bass riders color scheme. Like the above commenter mentioned, it’s not based off hardware so it literally could have looked like anything else. There’s plenty of gain rider plugins that look nothing like the waves version. My worry is in potential design lawsuits that could be filed by waves, potentially? Obviously I support the cause and I love new plugins, but man does it look just way to similar to the waves version. Maybe in future updates, I’d like to see some sort of UI change/uograde to separate itself from the waves counterpart.

Thanks for the thoughtful comment — I really appreciate you bringing this up.

RaiderPro is a fully original implementation, both in terms of DSP and code. The UI follows a familiar layout mainly to keep the workflow intuitive for users already used to this type of tool.

That said, I understand your point about visual differentiation. It’s something I’m actively considering for future updates as the plugin evolves.

My main focus so far has been stability, performance, and compatibility across different setups, but improving the UI identity is definitely on the roadmap.

If you get a chance to try it, I’d love to hear your thoughts on how it feels in actual use.

[diegorcortega]

**RaiderPro – 2026 Roadmap (All updates included)**

Hey everyone,

Quick update on what’s been added and what’s coming next for **RaiderPro – audio level automation**:

**Jan**

* Offline usage enabled

**Feb**

* New attack modulation algorithm
* Improved Range / Rider / Output sliders
* Target fader value display

**Mar**

* Apple-signed AU/VST3 builds
* End of Early Access

**Apr**

* Clipper / Limiter
* New UI

**May+**

* UI refinements
* Optional features (based on feedback):
1.Noise Gate
2.Compressor

**Pricing**

* $28 (Early Access) → $35 Current Price → $40 May 2026 price

All updates are included with a single purchase.

Thanks again for the feedback — it’s directly shaping the plugin.

— Diego / Casa Occidente Plugins