RX Editor Batch processing - send multiple clips from PT to be batch processed
iZotope renders much faster than PT, so I'd like a smarter way to send multiple clips to the rx batch processor for rendering. a workaround is select clips and use any audiosuite plugin without processing, clip by clip, individual, 8sec handles. close pt, open audio files folder select clips and drag n drop to rx batch processor. don't you think there is a smarter way? every scene is different and audio suite dialogue isolate on 10-20 clips per scene where needed takes a looooong time.
Christian Scheuer @chrscheuer2022-09-16 06:45:03.381ZHi Daniel,
Have you checked out the Dialog Editing iZotope package? There's a series of commands to automate sending via Connect to RX Audio Editor, process things there and get them back into PT.
Daniel Perez @daniel_perezit will only send one clip at a time or up to 32 clips to the editor in individual tabs though. i was really interested in sending multiple clips to the batch processor window in rx. dx isoalte, mouth declick, de crackle etc, are much faster to render within rx standalone.
Christian Scheuer @chrscheuer2022-09-16 06:49:39.999ZIf you use the iZotope RX deck inside of that package, there's a button called Composite View, which will collapse all of your sent clips so that any operation you do will operate on all of the clips. There's a video that should show off this workflow.
Maybe not 100% what you're asking for, but it does allow you to process files in parallel (and yes, as you say, much faster than with AudioSuite) :)- Daniel Perez @daniel_perez
the thing is with the composite view it will take the same process and apply it to all clips globally. if you edit a click in composite view for example, it edits this same piece/part in all clips, which only makes sense in very specific cases like the same hum on all clips. i didn't find any use for composite editing at all yet.
- Christian Scheuer @chrscheuer2022-09-16 06:53:04.453Z
I thought your point was you wanted to batch process entire clips? Composite view does that for you.
- Daniel Perez @daniel_perez
if you open rx batch processor (command+b) you can set up chains or individual processes which are rendered on all clips within the list individually and one by one, which is more or less the way to go.
- Christian Scheuer @chrscheuer2022-09-16 06:56:42.922Z
Absolutely, just wanted to point you to a direction with scripts that are already implemented :)
If you haven't checked the video for the package I was referring to, in my opinion it has a very neat workflow. It also includes a script that allows you to batch process clips (it'll send your clips to RX, then switch to composite view, then render each of the modules one by one, then send it back to PT).
- Christian Scheuer @chrscheuer2022-09-16 06:57:28.543Z
I think there's been people asking about the batch processor in the past. Selecting presets in iZotope can be tricky with UI automation, so it may or may not be difficult to achieve what you're asking for - hence why I was pointing to existing automation workflows that might be of use.
- Daniel Perez @daniel_perez
i saw the script with the module chain for individual cclips in tab or composite view. the main thing would be to bring the clips from pt into the rx batch processor, without closing pro tools, opening the audio files folder and drag and drop to the batch processor window.
- Christian Scheuer @chrscheuer2022-09-16 07:05:00.702Z
Could you explain a bit more about why this is the way you'd prefer to approach it?
If you operate directly on audio files in the PT folder, you'll need to manually recalculate waveforms etc. once the files have been modified outside of PT, and you might need to reopen your session in PT if it has cached the files.
This is at least one reason for using Connect.
Is this because you're interested in operating on a very large collection of production sound files for example?
- Daniel Perez @daniel_perez
i worked like this on fast turnaround shows, because i assumed composite view will handle all clips like it is one single clip. like it does when editing in composite view.
- In reply todaniel_perez⬆:Daniel Perez @daniel_perez
processes like mouth de click or dx isolate have to be done for all clips individually.
- Christian Scheuer @chrscheuer2022-09-16 06:53:44.668Z
DX isolate works just fine for me in composite view, unless there's something in your request that I'm missing.
- Daniel Perez @daniel_perez
depends how you use it. for roomtone reduction which is consistent on all clips yes. for noise -20 dx 0 amb preserve 70-80 it won't work. try compsoite view, make a selection and command cut it. the whole will now be on all clips, which diesn't make any sense at all for most of our tasks.
- Christian Scheuer @chrscheuer2022-09-16 07:00:48.561Z
I know.. I just don't understand why that is a problem if what you want is indeed to batch process clips with predefined module settings across all clips?
I'm not talking about using composite view for doing edits (obviously). But there's no difference from running a Dialog Isolate batch preset on 5 clips vs. loading the 5 clips, switching to composite view and running that same Dialog Isolate preset.- Daniel Perez @daniel_perez
aha, so if you apply de click or mouth declick in composite view it will actually process the clips one by one individually? and not apply the same de click which it does one clip to all clips at the same area? i will try that.
- Christian Scheuer @chrscheuer2022-09-16 07:05:53.696Z
Yes :) I've used this for years. It's only manual editing that is not great in composite view (for the very reasons you state).
- Christian Scheuer @chrscheuer2022-09-16 07:07:35.773Z
Think of composite view as "do the same operation on all clips".
If the operation is - cut from second 1 to 2, then that'll obviously be super weird to do on all clips.
But if the operation is, "run dialog isolate" on all clips, then that'll work just fine.The algorithms don't have a concept of "analyse from one clip, apply on multiple clips".. it just runs the processes in parallel on all the clips (ie. same as batch processing)
- Daniel Perez @daniel_perez
oh man, how can they not write this in the manual? you saved my life, chris. haha.
- Christian Scheuer @chrscheuer2022-09-16 07:32:25.704Z
Haha nice! Yea it sounds like their manual doesn't do a good job of explaining just how useful this feature is :)
- Christian Scheuer @chrscheuer2022-09-16 07:33:08.320Z
The key is to not make any selections in composite view when running the tasks. This way, you're sure they'll operate on complete clips no matter their lengths etc.
- In reply tochrscheuer⬆:Daniel Perez @daniel_perez
what's with that?:
Composite View assumes that all files start at the same point.
Use the Signal Generator module to Insert silence
If needed, you can adjust file start times by inserting Silence with the Signal Generator or using edit commands to modify timing before collapsing your files into a Composite View tab.
- Progress