Cubase 15 Issue: Initializing: ARA Service scanning plugins - SOLVED

Cubase
1

On startup, Cubase 15 Pro stalls on Initializing: ARA Service scanning plugins. It takes > 120 seconds every time.

2

What ARA plugins do you have installed?

1 Like
3

SynthV V2.1.2. No issues with Cubase 14.0.40

4

Hmm .. everything is business as usual here; Melodyne, AutoTune, VocAlign ect working as expected, but obviously something has changed.

I think you should engage with the developer on this one, but if something major has broken in Cubase i’m sure threads will pop up in here as more people update.

1 Like
5

Thanks for the assist! Appreciated!

6

I had the same issue in Cubase 13 with my Intel 14600K. In my case, I disabled hyper-threading, and it takes just a bit over 10 seconds to load in Cubase 15 with Synth V2 Pro.

1 Like
7

Thanks for the response, greatly appreciated. If I was encountering an issue in Cubase 14 I’d consider turning off hyperthreading but I’m not, so I think Steinberg should have a look at this. I should add that in the past I have switched hyperthreading on and off to examine overall performance implications and on my rig it’s better when it’s on, so I would prefer to maintain current levels of performance rather than sacrifice for faster startup.

8

I wonder if it may be something specific to SynthV? FWIW, I don’t see this issue (scanning ARA is just as fast as with Cubase 14 (pretty quick). My ARA plugins include Melodyne, VocAlign, RePitch, WaveLab, and SpectraLayers. (I haven’t tried using any of those in Cubase 15 yet, so I’m just talking about Cubase Pro 15 startup. My system is Windows 11 25H2 and Core Ultra 9 285K CPU.

1 Like
9

I went back to look at the history of ARA startup/scanning complaints and they go back as far as Cubase 12 with no specific remedies. It sounds like it’s something I’ll just have to live with. The goodthing about being old and retired is that I’m in no rush.

10

Turns out it was SynthV. I had a special build to resolve a crash problem when changing Cubase tempo track values. I uninstalled the special build, reinstalled 2.1.2, and all is well. I have advised Dreamtonics.

1 Like
11

I have exactly the same issue, also installed the new november beta of synthesiser V 2 and it seems to show that melodyne takes more than 3 minutes to start. I’m going to see if a new version solves this problem

1 Like
12

On my rig, the latest beta takes thirty seconds to get past the ‘ara scan’ initialization sequence, so its better but still not great.

13

yes with the latest 2.2 beta3 it takes less time but still too long, It’s not great if you just want to whip up a little project time in between other things

1 Like
14

Completely agree!! I have raised this with Dreamtonics. Hopefully it will be sorted in the release.