This is an interesting thread that has been on the DUC recently and relates to the best way to use Izotope’s RX noise reduction software. Do you use it as an RTAS /AudioSuite plug-in or do you use it in stand alone mode, and if so, how do you get files back and forth between the Izotope application and Pro Tools….
abayman65 asked…
Wondered if anyone can help. I read a thread a while ago about using the standalone version, and workflow within Pro Tools – but couldn’t find it!
Ive been consolidating clips within Pro Tool then dragging the file into Rx. What I hoped it would do is update the file in Pro Tools once Id processed and saved it in RX – it doesn’t update, so I have to save a copy and then import the new file. (which is a pain in the ass!). Anyone shed any light on a better way of working Rx and Pro Tools together. (without using Rx as TDM or RTAS but as standalone)?
Thanks
Originalscottyg replied…
Here is a workflow I developed for myself, maybe it will help.
This workflow is more suited to unsupervised dialog cleanup type sessions because it can be a bit time consuming, especially when closing and re-opening large PT sessions. Also, this only works with mono files as RX will load in dual mono files, but insists on saving them as interleaved for some reason.
1. Create a sub-folder inside your session folder called RX Pre-Process Backups.
2. Identify the parent file(s) you would like to process in the PT region list.
3. Close the Pro Tools session
4. Drag a copy of these files from your Audio Files folder to the RX Pre-Process Backups folder.
5. Open RX standalone and open the files to be processed from the Audio Files folder.
6. Process the files as you wish in RX standalone, then save, but do not Save As.
7. The newly processed file should be in the Audio Files folder, and the un-processed backup of the file should be in the RX Pre-Process Backups folder.
8. Delete the Fade Files from your PT Fade Files folder.
9. Re-open your PT session, select Re-generate missing Fade files without searching.
10. All regions derived from the processed parent file should playback with the correct processing.
11. To see the processing reflected in the waveform overview, select those regions in the timeline or the parent file in the region list and select Recalculate Waveform Overview from the Region List drop-down menu.
Hope this helps. It saves me a lot of time when I have many regions derived from the same parent files. Plus I get to use RXs spectrograph when using Hum Removal, which I find very helpful.
Jimlongo added…
When dealing with dialog, I usually just export the region as a file to the desktop (or some folder). Open it in Rx and Save. Then just drag the fixed file back into my Protools session. Might have to copy some automation, redo some fades, but you don’t have to close the session. Does require a way to monitor Rx.
Felix Rost posted…
1. select and consolidate/duplicate the desired audio in PT.
2. open FINDER, locate the audio files folder of your session, sort by modification time, you’ll find your consolidated file there.
3. Drag file to RX, fix it, save or close file
4. the region in PT now reflects your changes. recalculate waveform if you need
Matt-o- added…
I assume, as I work exactly as you describe, and experience the same problem, it could have something to do with the disk-cache.
- When you close and open the session, after modifying the file in RX, ProTools opens correctly the altered file.
- When you duplicate the file a 2nd time, it reflects the changes, also when you create a fade.
- Although the recalculation of the waveform works visually, the playback still plays the original – which leads me to the assumption it could have something to do with the disk-cache. I switched the disk-cache to the lowest setting, but could not find out till now, when the file no longer plays back from the cache, but is read newly.
Originalscottyg responded…
Just to clarify, it is not totally necessary to close the PT session, but if you leave it open, you may not hear your changes right away unless you trash the fades files and the wavecache file. I am not sure what the result of trashing the wavecache while the session is open would be.
That being said, I would not use this workflow on a large feature mix. It does, however, work really well for doing Documentaries and other projects where there are a lot of regions scattered throughout the timeline that are from the same parent file, as all regions will be updated by processing the parent file once in RX standalone.