Quote:
Originally Posted by
miguelmarques
Not sure about the latest update since it just came out and it’s the weekend but talking about the initial release and like other folks reported: I had no presets and the output folders where not stored. So I had to manually create each action every time and it’s destination.
But to me the worst was the SRC settings that were also not working properly, I had to double check each rendered file to see if it actually applied SRC or not. Sometimes loading a setting or changing sliders on the SRC window wouldn’t actually render those settings. I had to open/close the settings window 2-3x for it to actually store those settings.
Also, multiple output formats doesn’t really interest me in the way they’re implemented since I have to do different processing for each one of those. For instance, I can’t output a 96/24, 48/24 and 44.1/16 WAV from the same source 96/32 since I need to have different SRC settings for each of those. Exception only for creating a 44.1/16 and MP3 simultaneously, since those would have had the same SRC settings and that can indeed be done.
The “new” batch processing in RX8 feels like the same limited and basic batch processing tool we’ve had before with a couple extra settings and a new interface, it still isn’t the batch processor most of us wanted. And because it was released with a ton of bugs it only made things worse! I have used alpha and beta releases of plugins and applications that where more stable than the batch processor on the RX8 release version.
Hi Miguel and thanks for expanding..
However the biggest complaint mentioned at previous posts seems to be resolved with the update.
I wrote it seems, because I have old full RX4 adv version at other DAW, RX7 elements at other NLE (for quick voiceover cleanups) and just testing RX 8.1 std, but the demo won't allow you to save output or start the batch process to fully test that.
But if you use custom naming suffixes and output folders, it's now correctly recalled with presets.
So to me it looks like it's functionally equivalent to previous RX versions.
I see, the overhauled RX batch processor UI doesn't seem to bring so much to the table for power users. You're true, that if you want to use different outputs with different sample rates, it wont help.
But on the other hand, I have always took batch processor there like nice addon for simple things (like resampler to 32 bit for later processing) and the main point of RX is in restoration and spectral editing.
It's another question, whether iZotope would like to promote this functionality in the editor to batch processor with all bells and whistles (like the Myriad).
I can imagine, it would require to rethink whole concept to allow building of complex "workflows" with branching (like process start of the chain in native input sample rate with some modules, then mult that to several different outputs, each with individual additional modules (like resampler, loudness normalization, limiter, dither) and finally output each to different respective format.. essentially build node based flowchart of batch process.
Then some missing editing functions there.. like some parametrized trimming or silence detection trimming. Furthermore some formats could be added there, AAC for example. Then it would be nice to include proper batch tagging according to some input or derived metadata.. someone would definitely like watchfolders and so on..
So with all of that, it depends, if they want to include it to a tool primarily developed for restoration and broaden its functionality that way.. or whether it will be better suited to some other tool aimed for batch processing and compete with Myriad or so..
I don't know.. of course, just thinking loud
Michal