iZotope workflow with protools 10

[JChappell]

My sessions start on ISIS. I prefer in most cases to use the iZotope stand alone app. I select the clip that I want to use with iZotope. Consoldate region saves it to my local drive. I then open with iZotope from the finder. When I save from iZotope I can see the changes in the finder. The audio in my session does not change. If I drag the file from the finder and spot it back in I still hear the uniZotoped audio. I am guessing that because the file is the same name it still plays the audio that is stored in ram. If I quit and restart the session all is well. Does anyone know if there is a way to force the timeline to reload into ram without restarting the session.

Thanks

[browniespeaks]

Are you batch processing the audio from your session audio files folder. I am using about the same workflow and changes are visable on pt re launch after batch processing

Sent from my MB200 using Tapatalk

[laki]

If you change the size of the RAM Cache, it will reCache the timeline. This will give you your updated audio without opening and closing the session.

You need to wait for the entire timeline to be cached before playing though otherwise you run the risk of it not updating. You'll also need to recalculate the waveform overview if you want to see that change.

Its not perfect but it works.

[BobbyDazzler]

I always close the tools project(not quit), then enter standalone Izo. Works for me quite well.
While on the subject if iZotope, has anyone noticed RX2 doing some strange things in Audiosuite? I was declicking today, opened the audiosuite plug, and when I selected whole file, I would end up with silence in the new clip about 10% of the time, but when I used the normal handles option, it worked fine.

[Kasper]

Originally Posted by JChappell

My sessions start on ISIS. I prefer in most cases to use the iZotope stand alone app. I select the clip that I want to use with iZotope. Consoldate region saves it to my local drive. I then open with iZotope from the finder. When I save from iZotope I can see the changes in the finder. The audio in my session does not change. If I drag the file from the finder and spot it back in I still hear the uniZotoped audio. I am guessing that because the file is the same name it still plays the audio that is stored in ram. If I quit and restart the session all is well. Does anyone know if there is a way to force the timeline to reload into ram without restarting the session.

Thanks

I'm assuming RX is the application ...

"Save as" from RX with a different name.
"Set Output Options" - uncheck "preserve non audio data"
Drag from the finder, not from a Digi browser.

It's a giant PITA, as there is no way to default those settings. I have talked to iZotope about it, they acknowledge it's a bug, but they haven't fixed it yet.

kasper

[laki]

Originally Posted by BobbyDazzler

I always close the tools project(not quit), then enter standalone Izo. Works for me quite well.
While on the subject if iZotope, has anyone noticed RX2 doing some strange things in Audiosuite? I was declicking today, opened the audiosuite plug, and when I selected whole file, I would end up with silence in the new clip about 10% of the time, but when I used the normal handles option, it worked fine.

This is a known issue introduced with PT10. Izotope isn't the only plugin behaving like this in AS. I think Serato PnT was another. Neyrinck Dolby E had it but there has been a fix on Neyrinck's part. Best to just turn handles off for now.

AFAIK it is in the hands of the plugin makers to do the fix to accommodate the new handle feature.

[Vedat]

Looking forward to RX fix the handles issue. It is the plugin that handles do need to work properly for.

[Kasper]

Originally Posted by laki

This is a known issue introduced with PT10. Izotope isn't the only plugin behaving like this in AS. I think Serato PnT was another. Neyrinck Dolby E had it but there has been a fix on Neyrinck's part. Best to just turn handles off for now.

AFAIK it is in the hands of the plugin makers to do the fix to accommodate the new handle feature.

That may be the case (I'm still mostly on 9) but not the issue the OP has. He's taking about opening/exporting from the stand-alone app, not a plug.

Anyway ..... would be nice to get all the bugs fixed, eh.

kasper

[SBP]

Seems like a good (and reasonably simple) addition for Avid to add to PtX would be an option to 'refresh' a clip from Hard disk into RAM. -or/and refresh all clips. for those that have workflows where the original file is changed using a different application.

We're still on Pt9 and also work often by destructively overwriting sound files with new versions -Pt needs to be able to update and play the new versions on the fly.

I guess you could also move the cursor to a new location in the timeline and the ram would eventually load the new version of the audio.

Is there really no way to force PtX to reload from disk into RAM? -other than the 2 time-consuming workarounds mentioned.

Thanks to OP for mentioning this issue.

Bruno

[Berkesound]

When working with iZotope or other noise reduction plugins, my workflow is to make a duplicate playlist of the track I'm working on and apply the FX as audiosuite there. That way, to hear the original audio all I've got to do is switch back to the unaffected playlist. I realize this doesn't exactly answer your question, but it's an alternate way to go about it.

-- Ryan Dorp