Why did Izotope remove some key Batch Processor Features?

Hi iZotope Team,

I’ll try not to sound like I’m ranting… though I suppose I am, a bit.

I would consider myself a power user who routinely batch-processes hundreds — sometimes thousands — of files at a time.

There are several things I’m really missing from earlier versions of RX:

1. The ability to run multiple batch processes and simply walk away for hours
2. Being able to clearly see the FX/process preset name for each step without having to click into it later just to confirm the correct preset was used
3. Not having to mouse-click close buttons simply to exit a preset display or verification view

With RX 11, I now feel like I have to babysit batch processes for hours, which is a significant regression for my workflow.

Please tell me I’m overlooking something fundamental. I would genuinely love for this to be user error on my part.

I’ve been an RX user for well over 15 years and routinely upgraded from version to version up through RX 7. RX 7 met my needs extremely well, and I didn’t feel compelled to move beyond it until compatibility requirements essentially forced the upgrade.

Thanks for taking the time to read this, and I appreciate any clarification you can offer.

Cheers,

Andrew K

Find more posts tagged with

Accepted answers

All comments

Sunborn

https://community.native-instruments.com/discussion/49601/why-did-izotope-remove-some-key-batch-processor-features

Hello,

The changes to the iZotope RX Batch Processor (including any feature removal) are largely the result of a complete architectural rewrite of the software.

Starting around RX 10 and continuing into RX 11, iZotope moved the application to a new core engine to support modern standards like Apple Silicon (M-series) native compatibility and VST3 hosting. In software development, "rewriting from the ground up" often means that features from the old code base aren't "removed" so much as they haven't been "re-implemented" yet, or they were replaced by a new system that works differently. For more details you need to ask the tech support team.

So, i assume that, sooner or later, any useful feature will be re-appear in future updates. However, this is my personal conclusion and has nothing to do with "official report" or anything like this.

LACompserguy

Hi,

Thank you for the explanation regarding the RX 10/11 architectural rewrite. I understand and appreciate the need to modernize the codebase for Apple Silicon, VST3 hosting, and long-term maintainability.

However, I want to clarify why I’m struggling with the current Batch Processor behavior, and why I don’t believe this is inherently tied to Apple Silicon or the new DSP engine.

The workflow I’m referring to — the ability to queue and execute multiple batch presets sequentially and walk away — is fundamentally an orchestration/scheduling feature, not a DSP or CPU-architecture concern. From a technical standpoint, this is a job-queue and UI/state-management issue rather than something dependent on x86 vs ARM, plugin hosting, or processing internals.

In RX 7 and earlier, this capability was essential for large-scale workflows. In RX 11, the requirement to manually supervise batch execution for extended periods represents a significant regression for high-volume users, independent of processing performance or engine correctness.

I completely understand that features may not yet be re-implemented during a major rewrite. What I’m trying to understand is:

• Whether the removal of serial/delayed batch execution is intentional or temporary
• Whether there is an equivalent workflow in RX 11 that I may be overlooking
• Whether this functionality is planned to return, or if the current behavior is now considered “by design”

As a long-time RX user, batch processing at scale is central to my work. I’d really appreciate confirmation from someone closer to the product or engineering side as to whether this regression is acknowledged and whether there’s a roadmap for restoring feature parity with RX 7 in this area.

Thanks very much for your time and clarification.

Best regards,
Andrew K

Sunborn

https://community.native-instruments.com/discussion/comment/253436#Comment_253436

As i wrote, only iZotope's Tech team can answer such questions. However, most probably, they can not. And more likely because they bounded with non-exposure agreement contracts.

Kymeia

Also annoying is the 'remove all files' disappears if there are a lot of files in the batch converter window

Vocalpoint

I believe the BP was changed back starting RX8 - so it should not come as any surprise here in 2026 that this is different.

Unless of course if the OP was running RX7 since 2019 and suddenly moved to RX11 - effectively jumping 4 complete versions and is now caught off guard.

LACompserguy

https://community.native-instruments.com/discussion/comment/253519#Comment_253519

Vocalpoint is correct.

I’ve been living quite happily in RX 7 until now and only upgraded because I purchased a new Mac Studio (M4 Pro). I moved to RX 11 fully expecting feature parity at a minimum—only to discover through Vovalpoint that queued batch processing was removed back in RX 8, meaning I now have to babysit batch jobs in real time.

That is a massive regression for anyone doing serious batch work.

What’s especially discouraging is that, years later, queued batch exports still haven’t been reinstated. That does not bode well. This isn’t an edge-case feature—it’s fundamental to large-scale workflows.

To make matters worse, there is no clear visual indicator that a batch export has completed (aside from files being grayed out). If there were a reliable completion indicator, I could at least script sequential batch execution using something like Keyboard Maestro. As it stands, even that workaround is extremely difficult.

It’s genuinely disappointing that queued batch processing is gone. I understand that “it’s been this way for years”—but that doesn’t make it acceptable, and it certainly doesn’t make it any less disruptive for long-time users who relied on RX for exactly this kind of work.

Cheers,

Andrew K

Vocalpoint

Andrew

Surprised to see you just moving from RX7 to 11 now. 7 was a masterstroke and I used it extensively.

That said - iZotope 2019 is not iZotope 2026. The company has shifted radically since way back then and it is not surprising what was once considered key for some users - no longer is.

FWIW - I have used RX for 15+ years now and I will speculate that batch processing - while extremely handy - was never really the focus of this program and it's no surprise to me that less attention was paid to it over the years.

I also remember circa RX7 (and prior) the Batch Processor was an actual standalone executable process (launched from within the RX main UI) and I also remember releases notes circa 2021 - saying this entire process was changing. To build on what Sunborn mentioned - I also think this change had a lot more than just Apple Silicon in mind when implemented.

To close - this function is most certainly never coming back so it's probably not healthy to burn brains cells on it.

If it were me - and this was critical to my workflow - I would try to rollback to v7 and call it a day.

LACompserguy

Vocalpoint,

"If it were me - and this was critical to my workflow - I would try to rollback to v7 and call it a day."

I think before I do that I'm going to explore using Reaper as a host and see how well the RX 11 plugin modules behave inside Reaper. Reaper has very powerful export features… and queueing 😉

If all else fails, I still have my old system with RX7. RX7 (I believe is Intel based) so won't run on Silicon (AFAIK).

Thanks for your help and confirming I wasn't missing something obvious.

Cheers,

Andrew K

LACompserguy

Follow-up…

Reaper appears to be working great with no appreciable hit compared to RX efficiency in stand-alone (AFAICT).

So… Goodbye RX Batch Processor…. hello Reaper! I've been working with Reaper for years… so it's no big deal for me. Thanks everyone!

Cheers,

Andrew K

Quick links

Unanswered questions