Crashing with scanning au

[osha]

Very frustrated as HH3 crashes every time I scan my plugins folder and it is the AU's not the VST's but I cannot find a way of telling HH not to scan my AU folder. I've tried taking out the offending AU's but it makes no f=difference..it seems to pick random AU's to crash with. So then I took the whole AU folder and trashed it..and it still found AU's to crash with! Please help. Thanks

[sephult]

maybe some cleanup here could be the answer?
ConfigPlug-Ins

[osha]

No that didn't help but thanks
Is there a way to say "Do not use AU's" ?

[sephult]

So you said you removed AU from the scanning folder and still crashed???
That is odd....

OSX or WIN?

I'm primary Win10 x64
So under your configplugins what files you have? Logs with errors and corrupted scans?
If you have no AU even in the normal path of scan...I don't know how you would pick up unless you still have previous info of the location or scan still in config.

Last resort..you can backup your config folder, pull out the .ini and plugins folder and let regenerate.

-s

[nay-seven]

@Sephult : On Mac OS version, you can't configure the AU folder it's automatic and imposed by the system, plug-ins path is only available for VST

[sephult]

Thanks for the explanation, that's what I am assuming what was happening.
That is a bummer, I hate restrictions.

So does HH still catalog the AU on OSX as recognized like it does with the VST?
Or is this just a hardcoded HH3 points to the system, the system provides, and Usine has no control type of thing?

Interesting to learn though, sorry for your troubles osha.

So question is...even though your AU folder is empty...what about the hidden user folders that can also contain the AU?
Are these somehow being scanned as well and containing the offending plugin?

-s

[osha]

Thanks both. It is very strange not to be able to tell HH not to use AU, but there you go! So even if I delete them all, yes I still get the same errors. This basically means I cannot use plugins with HH as the scan never gets to VST's!

I will investigate further....

[nay-seven]

Can you try to read the init files in config/plug-ins with TextEdit?
specially this 2:
CorruptedPlugins.init
ErrorPlugins.init