I’m having trouble with RX 11 and Nuendo 13. Sending audio from / to Nuendo (using Direct offline processing with RX connect) doesn’t always work. Sometimes the audio is sent to RX but clicking “send back” in RX does noting. Or sometimes trying to send audio to RX from Nuendo doesn’t even open RX.
I also have RX 9, that seems to work fine. I recently updated my Mac to OS14 (Sonoma Mac Studio M1). According to Izotope, RX11 should run under Sonoma. Anybody have an idea what’s causing this issue?
iZotope has grown to be downright dependable as it “matures.”
In other words, one can count on there being problems with it for at least one update cycle (more like two or three over the last couple of versions, the one finally making it work with Cubendo taking over a year after 10’s initial release).
The good (and bad) news is that in the big picture RX’s utility hasn’t really improved since v9 (the only thing I’ve found useful that 10 has and 9 doesn’t is the apparent ability to load Accentize dxRevive as a plug-in). So… if RX is an essential part of your workflow (it still is for me, as much as I’d like to ditch iZotope at this point), I’d recommend not using 11., and considering the advice of @mattiasNYC .
At least that’s where I am right now. SpectraLayers is not there for me yet, batch-processing wise, but I’m hoping to be iZotope free in the near-ish future, by hook or by crook. I’m definitely, absolutely not “upgrading” to 11; the first time I haven’t gone to the latest version since RX2 came out. Unless something radically changes, iZotope is cooked.
Agreed. But for me, Spectralayers Pro is still pretty cumbersome. Project save times become very long as soon as even 1 clip uses the extension. And the whole session feels sluggish. (i9 12900 128GB ram, SSD’s etc, everything ripping.)
The way I work around it is by using SL on a clip by clip basis, and committing to the results before going to the next. It is not ideal, but I think its the way ARA handles things in Nuendo for the time being… Other apps in ARA are similarly “delicate”. Using RX Connect was no better in this regard, since you had to send the audio back and commit anyways. At least with ARA I can undo without losing the work altogether.
My comment was part facetious. I use Spectralayers when I need it and when I do I don’t leave it “active”, I just render to new files and move on. I still rely on RX for spectral editing and some modules but I hope to switch over from it completely next year. I might get a new computer and if I do perhaps that’ll speed up things.
Anyway, same for me, which sucks, because iZotope sucks.
I don’t think it’ll help. I have a completely insane Ryzen 9 9750x rig that I tried it on briefly too. Same deal…. What the hell, Steinberg? I’ve wasted more time trying to implement Ara2 than I care to admit. Still completely useless and actually slows me down. Melodyne, vocalign, spectralayers. They all suck under Ara2
Since RX8, RX Connect never works as before. They 1st promised to make it soon but then there is nothing, as I know, it will never work. (As they support Protools, Studio One, and Logic). I own RX 10 Advanced. I paid a lot for Everything Bundle for years, since last month, I decided to pay for Spectralayers Pro instead of upgrading to RX 11. It works good enough for me now. I always render finished tracks and remove extensions, It saves time.
I don’t think that will help unfortunately, Mattias.
My main computer is pretty new and fast, but ARA2 is still buggy as hell.
Just as buggy and slow as it is on my much more modest laptop.
I’ve been in contact with Izotope and they are aware of the issue and working on a solution. they advise me to use RX9 for the moment when working with RX connect.
For me RX still does a great job cleaning up audio in my daily work (audio postproduction). So sure, it is easy to start bashing it, but that was not the initial question of this topic. I simply wanted to know if anybody else had the same experience and / or has a solution. Every software has bugs and every company has “lousy” support. So…?
However, every software company does not sell upgrades that offer little or no change from the preceding version… (three years/ times in a row!) nor do they tend to break a fundamental utility for sometimes more than a year (in this case, being able to use it with RX connect) for its last four versions.
No question that RX is still useful (it’s an essential part of my workflow, too). But iZotope’s support has been markedly substandard in a sea of underachievers, even as their value diminishes with competition.
And the issue you’re having-- at this point its evolution has moved from beyond annoying to chronic. I don’t think it’s iZotope-bashing to point it out. It’s identifying the problem.
For iZotope to suggest that you revert back two full versions (and I say that even as I have been working that way myself since v9) is ridiculous, unacceptable and a very red flag in terms of my confidence in the company and the package’s future. And I have friends who worked there-- up until the NI takeover, when things really seemed to take a downwards turn. I have been strongly suggesting my colleagues consider not upgrading anymore–which to me feels like a solution, given the growing field of options.
I understand your point and I agree with that. But my point was that the discussion about the (lack of) support of a company, or upgrades that provide little improvement, was off-topic, and that I didn’t start this topic to discuss that. I simply wanted to find out what the problem was with RX connect.
I upgraded from Rx9 to Rx11 because I updated my Mac OS and according the the Izotope website (and other users) there may be a compatibility issue. (which turned out not to be true).
I must say that some tools in Rx11 are better than Rx9. (Like the dialogue isolate). In hindsight, would I have upgraded if I had know all this? I guess not. But there was a good offer during Black Friday to upgrade so I did.