Participant

Question

Premiere project with iZotope plug-ins hangs 3/4's in at start-up

Forum|Forum|4 years ago
January 25, 2022
7 replies
6939 views

Hi,

I've been plagued with this issue for a while now, across many projects, but it's just worsened with PrPro2022 to a point where I can't launch certain projects anymore. The triggering factors seem to be 1) the use of iZotope Neutron 3 plug-ins and 2) the accumulation of a certain number of those plug-ins accumulated through all sequences.

The start-up progress bar basically "jams" 3/4's into its full length and there's nothing else to do than kill the process. Then it's a painful process of restart/kill/repeat until it goes thru in full. Sometimes a full reboot helps, but not much. Typically the project will finally open at the 4th or 5th attempt, but not today...

There does not need to be many plug-ins, nor a huge number of them, even in pretty simple sequences... Disabling all of the plug-ins before exiting a successful launch does not help; resetting the Preferences or the Plug-ins cache do not help either.

The resource monitor shows very little activity: 2% CPU usage and a few MB of memory (out of 64GB alloted to PPro, of a total of 128GB).

I've just duplicated the project on another drive, thinking it could trigger the Relink UI and perhaps help things out, but the Relink UI did not come up; same hang.

At this point, it's pretty useless to be honest, for this given project I've lost the last hour trying to get into it...

What are my options? Is there a magical shortcut I could use to bypass the plug-ins at start-up? A log file that could display the issue at hand?

Using the latest 2022 Cloud version on Windows 10. Intel Core i7-6800K @ 3.40GHz, 128GB of RAM, 500 GB SSD system disk (200 GB free), 1TB SSD Scratch disk, many TBs of NAS storage over 10GigE...

TIA for any help --Alain

This topic has been closed for replies.

M

mstegner

Community Manager

Hi All,

I've generated a bug to investigate whey this is taking so much longer than other effects. I'll try to remember to add any updates when I can here.

jacksonfilm

Participating Frequently

Same issue here using Izotope RX10 Elements on a project. M1 Max MBP, using PP22. Projects open in the end but takes a good 10-15 mins. Interestingly I have RX7 Elements and sequences that use that do not have an issue opening. So definitely something about RX10 is not liked by Premiere.

collierlandry

Participant

Any update to this for anyone? I'm literally just having to make new projects every time I want to use these plugins. It's infuriating. Adobe blames Izotope, Izotope blames Adobe.

The end user is the big loser!

Collier Landry

jacksonfilm

Participating Frequently

I just don’t use izotope anymore. 'Adobe Podcast' AI app does a much better job

M

MaoSoto

Participating Frequently

I'm having the same issues with projects using izotope RX 10 on Premiere 2023. My project can take 30 minutes to open. I have been troubleshooting everything and have narrowed the problem to the izotope RX 10.

I applied hum remover and cleanup assistant in all clips in my timeline, and since then, every time I open the project, it hangs.

Another issue, which was prompting me to restart Premiere, was that after playing my edit for more than a minute, Premiere would freeze while the audio kept playing, but the video froze. My first thought was it was an issue with the media, so I tried:

1)Cleaned up cache and preferences (no change, still hangs)

1)Tried using and not using proxies, connecting and disconnecting them. (no change)

2) I replaced all media with newly transcoded ones. (no change)

3)Export sequences as premiere (hangs for hours)

4)Import project into another project (hangs for hours)

3)Reinstalled premiere (still hangs)

5)uninstalled video plugins (still hangs)

6)uninstalled izotope (still hangs)

7)removed attributes/removed izotope plugins on all clips in all timelines, saved, closed, and reopened. Then it works fine. In conclusion, The problem is definitely izotope RX10 plugins on clips on timelines, whether the plugin is installed or not.

I have not tried applying the plugins to the track in the track editor. I can't waste more time troubleshooting.

To be able to have decent audio during my edit I'll have to export all the clips with the audio cleaned, then relink all media to the one with clean audio. Then course I'll get rid of izotope from everywhere in the project.

A

Alain D.

Known Participant

MaoSoto,

Very sorry to hear that, both for yourself and collectively speaking, as I
was hopeful this truly was behind us. As you paid for your iZotope
plug-ins, I can only suggest to get in touch with their Tech Support and
let them know. Beware they can be slow to respond unfortunately. And yes, I
hear you, it's a lot of work and wasted time to be troubleshooting this
much.

Can't say that it would be a fix, but from my experience over the last few
years using RX in Premiere, clip-based plug-ins do seem to cause more
problems than track-based ones. Perhaps too resource-intensive at the clip
level?

I've come around it by sticking to track-based usage for smaller needs, and
when things become heavy duty, I just tend to export a raw 32-bit float
.wav file out of Premiere and deal with the issues in the stand-alone RX 10
audio editor.

On my side, ever since the RX 10 & Neutron 4 series of plug-ins have been
installed, the problem has not returned. Although I must admit I remain
cautious and remain on the limited number of plug-ins used in Premiere. But
I can confirm that the trigger problems that were in N3 are gone. One big
caveat: the N4 mothership plug-in was not loading last time I checked...
Hopeful this will be resolved soon in a .X release.

Regards,

Alain

--

Alain Durocher
Video Editor

Nick Lear

Inspiring

Just to add that I've experienced this as well. I'm actually on 3.7 and I still experience it. I also find importing a project into a new project doesn't always work. All in all Neutron 3 at least is just not friends with Premiere. Not sure if anyone has tried Neutron 4?

A

Alain D.

Known Participant

Update for posterity and if this can help someone in the near future... There is an issue with the plug-in, but also with Premiere itself.

*Important workaround found*
You can Import your problematic Premiere project into a New Project with success. All of it - not just one sequence or two. But as soon as you Save this new project, exit and try to Open it again, you are back to square one, in which case the Import route is your only option.
*Problem found with Neutron3 v3.8*
An issue was found with the version of the Neutron3 plug-in used (3.8). We first removed it completely and then re-installed it in Windows Safe Mode, with no change. A downgrade to 3.7, the previous version, "fixed" the issue.
Numerous tests were done with iZotope Support as well by myself, throuhgout numerous Premiere projects with/without plug-ins (to test potential Premiere issues independently from the plug-in).
Some problematic projects (but not all of them) have in common that they were created from a base project (with a given folder organization and pre-built template sequences) that I duplicate and rename accordingly.
There are issues with Premiere projects WITHOUT the plug-in. You can see the Open-Project progress bar "stall" 3/4's in with some projects; most of them will follow through after a delay of 15 to 60s, but there was at least one that never made it through the as if it had the plug-in. Using the Import option above on those projects, I realized some of Premiere's internally generated components end up in the "Recovered" folder (Black, Color Matte for example). Deleting those components, saving and restarting the project has helped, but is not an absolute guarantee of success.
iZotope Support has my system info and I am waiting for further instructions. That being said, the project duplication path on Premiere's side does not seem to be 100% trustable. I will recreated my base project from scratch and continue to monitor this. This base project has been evolving over a few Premiere versions over the last couple of years.

B

Baffy19

Legend

Great news 🙌

neil wilkes

Legend

It certainly sounds like a problem with the plugin itself to me.

Have you tried contacting iZotope at all?

B

Baffy19

Legend

Currently, the problem is with how Premiere works with each third-party plugin. I have the same problem with the RX 9 Izotope. If there are third-party processing effects in the sound on the timeline (not native Premiere effects), then the export will hang and the project will not be output. Prior to version 22, Premiere worked perfectly with third-party plugins with both video and audio. You need to understand the Premiere itself. It was possible to change the code in the program and it is not compatible when working with third-party plugins. This is particularly observed with other video plugins from the company AIS, Sapphire, Maxon and others. I will not believe that the developers of third-party plugins have done something wrong. Previously, everything was fine with compatibility. Now the trouble is for many creatives

A

Alain D.

Known Participant

Hi Baffy19, thanks for your input.

I understand your view, but I must say I'm not experiencing the same thing as you. Once I am into the project, I can properly playback and export. So I can stack up a mix of Rx9's "Mouth", "Breath", "Neutron3", "De-Ess" and top it with an "Insight" analyzer, and both the playback and exports are A-OK. I had this particular issue in PrPro 2021 with Rx8 and Rx9 plug-ins as well, but it seems to have gotten worse in 2022.

But yes -- I totally agree that some updates from the main app may not work well with other apps or drivers. On PC, I regularly see this when an NVidia driver update is made available -- at least 50% of the time, the NVidia update is not playing well with Premiere and I need to downgrade + wait for the next Premiere update to update NVidia again. This is the downside of software development nowadays, especially with Support resources being very limited with pretty much all software companies.