Live 11 sloooooow vst scanning

[carrieres]

try https://learn.microsoft.com/fr-fr/sysin ... ds/procmon
and https://live.sysinternals.com/Procmon.exe
It is scanning all U-He presets ...

[kmonkey]

Interesting tool. I tried it.

It shows this (Related to Ableton Live)

Ableton Plugin Scanner.exe is scanning
and Ableton Index.exe is running and indexing something. What is this (from Procmon) interesting find, it says that Ableton Index.Exe is scanning through all my sample libraries, and sometimes (from Procmon) it results in success and sometimes in "path not found".

Whenever "path not found" appears I see in Procmon that this is related to "Ableton Folder Info" folder and a file in it called Properties.cfg

As if Ableton is trying to find this file in all of my sample folders and there is none. Perhaps that's the reason for slow VST scan? I mean maybe Live is reindexing on the first Run and after this process is done then it tris to scan VST folders for change?

FYI in my Live preferences, I turned off "Create Analysis File" so I am not sure what is it that Live is trying to find.

Is there a way to "reset" this indexing and to make it stop or finished?

[carrieres]

FYI in my Live preferences, I turned off "Create Analysis File" so I am not sure what is it that Live is trying to find.

it is not related to our problem. Live creates an analysis file when an audio file is brought into the program for the first time. The file contains specific information about the analyzed audio such as pitch, warp marker positions, and tempo to help optimize the stretching quality and speed up the loading time.

[kmonkey]

FYI in my Live preferences, I turned off "Create Analysis File" so I am not sure what is it that Live is trying to find.

it is not related to our problem. Live creates an analysis file when an audio file is brought into the program for the first time. The file contains specific information about the analyzed audio such as pitch, warp marker positions, and tempo to help optimize the stretching quality and speed up the loading time.

Okay, thanks. As someone mentioned, I noticed the Ableton Index thing on each run is scanning my u-he sounds, which are placed in my Documents folder - seems a bit weird to me because I never added this specific folder into any of the Live configurations nor it is added in the Live browser. Also when I run Live it is an empty session, an empty midi channel. There's no u-he plugin loaded. I don't understand why would it do that why does it scan u-he folders?

I wish I never installed this Procmon because I am getting too many of details which bothers me now hahaha

[carrieres]

I will work on a workaround and post it here.
It is important to find a solution because the long scanning is reducing the MTBF of our hard disk.
From Ableton Knowledge Base :
https://help.ableton.com/hc/en-us/artic ... on-Windows
The folder you select must exclusively be used to install .dll files of VST2 plug-in devices. Picking a system folder, hard drive, or directory containing other file types may cause Live to crash when plug-ins are scanned.
Completely unrealistic, Ableton should scans only dll file

[kmonkey]

I will work on a workaround and post it here.
It is important to find a solution because the long scanning is reducing the MTBF of our hard disk.
From Ableton Knowledge Base :
https://help.ableton.com/hc/en-us/artic ... on-Windows
The folder you select must exclusively be used to install .dll files of VST2 plug-in devices. Picking a system folder, hard drive, or directory containing other file types may cause Live to crash when plug-ins are scanned.
Completely unrealistic, Ableton should scans only dll file

Any progress on this? I followed your link to their article but I still don't understand why Live scans my Documents folder and a folder containing presets from 3rd party developers that are placed in the Documents folder because I, most definitely have all my VST3 plugins installed here;

C:\Program Files\Common Files\VST3 - as they suggest

Yet on every Live run, it scans tons of crap from other developers in folders I never asked it to do.

I monitored Reason 12 with Procmon and it most definitely does not do that when running.
Tried with Reaper - same thing.

[carrieres]

I finished the script to create shortcut, I will test in a few minutes
There is two scanners, one for the plugins and one for the indexing of the browser.
My workaround is only for VST2 folder which have 71 885 files, my VST3 folder has only 677 files mainly .vst3 type, so it is fine.

[kmonkey]

I finished the script to create shortcut, I will test in a few minutes
There is two scanners, one for the plugins and one for the indexing of the browser.
My workaround is only for VST2 folder which have 71 885 files, my VST3 folder has only 677 files mainly .vst3 type, so it is fine.

And I was under the impression that I have too many plugins...haha

[carrieres]

Maybe you have too many presets ?
Sorry for the delay but I was waiting the scanner to finish to scan my VST2 folder which have 71 885 files.
but after more than one hour, I canceled the scan with the button in the Ableton prefs.
I was discouraged because the scanner was following shortcut to the data folder of U-He plugins and I have a lot of presets (same thing for alchemy a lot presets)
After canceling the scan, I was able to change my VST2 folder to the new shortcut folder created by my script and Ableton scan took less than two minutes to scan !
I am still testing and will come back here ASAP

[carrieres]

It is not better, I restarted Ableton to take into account two new plugins and it is scanning like before
The only solution is to set the presets outside of the Plugin folder.
For the index process, the solution is to choose wisely what do you need in Places

[carrieres]

I opened a ticket to Ableton support

[elassi]

Thank you for your efforts, carrieres. :tu

[kmonkey]

It is not better, I restarted Ableton to take into account two new plugins and it is scanning like before
The only solution is to set the presets outside of the Plugin folder.
For the index process, the solution is to choose wisely what do you need in Places

But that's what I tried to tell you a few posts up. My presets are not in ANY Places and yet Ableton scans them.

Example - U-he presets are in my Documents folder. This folder is NOT defined in any Live browser or preferences yet every time I rub Live, with Procmon I see Live opening folders for u-he Bazille for example. Mind you Live upon opening is set to open an empty session without any plugin (just one MIDI channel). So I am stumped as to why it scans through my 3rd party presets folder.

All of my plugins are in the default VST3 path.

Anyway, thanks for all your efforts. Keep us informed of their response.

[NikkiA]

U-he plugins also have a link for the data folder of each plugin IN THE VST FOLDER next to the .dll, that is why it's all getting scanned, including all the UI elements.

[sQeetz]

I have almost all u=he plugins and don't have that issue at all.
Live starts almost instantaneously... click..bam...bam... one second later it's on with a blank template