iZotope RX4 and Yosemite

[EMRR]

What happens if you move the analysis folder elsewhere and let it re-analyze? Of course that's probably even slower.....

[CT]

What happens if you move the analysis folder elsewhere and let it re-analyze? Of course that's probably even slower.....

The only way I can get DP to re-analyze is by re-opening the project.
Tried:
Trash the respective analysis file / Change background processing preferences = no re-analysis.
Trash the respective analysis file / Replace soundbite or Reload soundbite = no re-analysis, although an empty container folder is created in DP Analysis files.

Thanks for the idea. I don`t know if there is any way to force a re-analysis of a soundbite without re-opening the project?

[HCMarkus]

How about giving the file a new name after stand alone RX processing, then reimporting and moving to original timestamp?

[CT]

How about giving the file a new name after stand alone RX processing, then reimporting and moving to original timestamp?

I tried this and found that there is no need to re-import the file.

After erasing the analysis file, renaming the file and switching back to DP, DP still shows the corrupted waveform.
(a new, empty analysis folder is created with the modified name).

However, after 3 to 5 minutes it seems that Background Processing does a sweep and restores the waveform.

I have not found a way for this Background Processing sweep to be activated by an action:
- A new Bounce to Disk activates Background Processing for that bounce, but does not affect the corrupted soundbite.
- Reload or Replace Soundbite still need to wait for the Background Processing sweep in order to restore the waveform.
(not renaming the soundbite leaves the soundbite corrupted).

e.g.
RX: overwrite original file / Finder: erase the analysis file / rename soundbite / DP: after about 3 - 5 minutes Background processing rewrites the waveform = waveform ok! (The soundbite has the original name, although the file path shows the modified name).


Thanks for the idea HCMarkus! We now have a workaround, although it has yet to be tested in a real world, 30 minute project.