Sun Jun 04, 2023 2:48 am
I'm not sure why you are pointing to iZotope pages when this issue has likely nothing to do with any particular external process. It is true that iZotope plugins, including those associated with RX are not qualified for Resolve as a host, but that's quite a different matter.
Did you know, for example, that Resolve does not use RX Connect to establish a connection to the RX Editor? If it did, then this would be a problem because RX Connect is an unqualified plugin. Instead, Resolve uses a command line execution of the RX Editor executable, passing to it the name of the file to process. This file is a copy of the source clip on the Fairlight page.
Presently (with 18.5b3), Resolve creates the copied audio clip, successfully launches the RX Editor and passes the copied audio file path to the RX Editor. The RX Editor then opens the audio file for editing. The 'iZotope' part of this process works flawlessly.
What doesn't work is that Resolve does not add this copied file to its media pool (as a new source clip), nor does it layer this new source clip on top of the original source clip. The failure appears to be solely within the realm of Resolve and not iZotope.
Time Traveller
Resolve Studio 19.0b1 | Fusion Studio 19.0b1 | Win 11 Pro (22H2) | i9-7940x, P4000 (536.96, 8GB VRAM), 64GB RAM, M.2 boot, SSD scratch, RAID10 data | (laptop) 16" MacBook Pro M1 MAX, 32 GPU cores, 64 GB RAM, 2 TB SSD, Sonoma 14.4