Zebra making VST plug scan very long on Windows...?

[MrJubbly]

Isn't there an option to omit plugin scans upon Ableton Live's start-up?
Why should any DAW need to always automatically scan each plugin every time it's launched?

Apologies if this sounds like an ignorant question. But I'm used to FL Studio launching in around 2 seconds flat. No needless scanning of plugins required, since the user can manually do so easily and quickly at any time they want (if they've recently installed any new plugins, etc.)

Btw, I'm also using Windows 11 and have Windows defender running. But plugin scans in FLS are super fast for u-he plugins and always whizz by each of them in just a few seconds (in all formats: CLAP, VST, VST3).

Have you tried disabling the "Scan on Startup" internal setting within each of the u-he plugins themselves? Would that possibly help mitigate the Ableton Live scanning time issues?

[tasmaniandevil]

Have you tried disabling the "Scan on Startup" internal setting within each of the u-he plugins themselves? Would that possibly help mitigate the Ableton Live scanning time issues?

This has nothing to do with the plugin scan done by the host.

[golemus]

What I'd be more concerned about is the length of the scan. We scan all our files, too, and it takes a split second. Seems like they are investigating files a little deeper even if those definitely can not be a plug-in (e.g. a .png file or a preset file). Doesn't make sense to me, I'll inquire with them as to why they do that.

Did you find out anything about this?

Also the Zebra.data link was .lnk file.

In your opinion should there be difference in 1. Performance of Zebra, 2. DAW startup or plugin scanning speed whether Zebra.data link is:

1. .lnk file like during the test
2. NTFS Directory Junction Link
3. NTFS Directory Symbolic Link

I use links so rarely that I still have a bit of difficulties understanding which is best to use.

File explorer does only .lnk files which is why I use them a lot but after this case I have started to think whether using Junction or Symbolic link would increase speed.

As I've understood Junction is oldest and supposed to be fastest? Some texts claim that you cannot do junction to different volume or storage device but I believe I have been able to do that.

My typical use case is that zebra is on C:\Program Files\Vstplugins or .../Common Files/VST3, Zebra2.data is on F:\Sample Libraries\Zebra2.data (same for ZebraHZ.data), they are both volumes on same NVMe. In older computer sample libraries are on different SATA SSD or nvme.

[Urs]

My inquiries led nowhere. I'll start another attempt...

[Urs]

Ok, we have an answer.

So, Ableton are now aware of the issue, acknowledge it and will look into it. They have not yet said when and what they do to fix it though.

They do however recommend that we send affected users to Ableton support as there are options that their support team can explore and help with straight away.

[golemus]

I think I have solved the issue for now. There does not need to be Zebra.data folder or its link at all under VstPlugins folder. Why didn't anybody mention it here? It seems to be defined in registry under following key:

Datapath at HKEY_CURRENT_USER\Software\U-HE\Zebra2 (and ZebraHZ)

And if you move the folder there comes a dialogue which asks for new folder and updates the key automatically.


But there is another key that I dont understand. What is role of this key?:



Datapath at HKEY_LOCAL_MACHINE\SOFTWARE\U-HE\VST

[Urs]

I'd have to ask one of our Win Devs about those... I think one os for the installer, the other might be for the software?