anyone encounter this on OSX?

 

Agree, I'd like to skip 10.0.1 and wait for a more stable update.

 

I'm assuming there is no way around this for a new Ableton 10 install, not having used 9 before hand?

 

it is stable,must be you

 

Actually, I was too afraid to lose my settings and plugins, so I tried and succeded in a sort of... PORTABLE installation.

To test it, I installed ableton 10 in a virtual machine, then renamed the old one and copied the 'programdata\ableton' folder to the physical machine.

Restored the user\appdata\ableton (I already explained that the first attempt was destroying almost all the links with my plugins) and voilà.

With ALL plugins working, even the bridged ones.

I don't konw if avoiding the installation exec caused some other issues, but at the very moment all is working perfectly.

 

Thanks for this.

 

It's a bug I actually had to deal with in Live 9 more so than 10 so far (only with 1 or 2 plugs). These issues were prevalent in 9 as well.. Has nothing to do with 10, but no matter, you aren't hurt anyone by sticking with 9 because of superstition.

 

Superstition? Walking under a ladder and believing in 7 years bad luck if you crack a mirror. These are superstitions. Not moving to Live 10 until I feel it is more stable is nothing more than a precautionary measure.
Calling it a superstition amounts to nothing more than floccinaucinihilipilification!

 

1. Cut vst's dll and put it somewhere out of vst folder
2. Open Live 10
3. Paste dll file again in the vst folder
4. Rescan vst folder
This is the only thing that works for me so far. Thanks all for your answers

 

Did you try a deep scan?

Go to preferences > File/Folder > Turn the `use VST plugin folder off` and hit rescan. This may take some time.

I had no problems at all with Live 10, it just used my default settings of Live 9 incl. my template.

It loads faster compared to Live 9 so satisfied so far........

 

lol thanks so much for explaining the generalities of superstition. ableton 10 is stable; believing that it isn't, just because you're afraid of updates, off of the same base code, is superstition - a widely held and unjustified belief.

 

It's unjustified because of the context.. It isn't a new code base, is actually more stable on my system than previous builds, and with great improvement in some regards. The vst scan problem has nothing to do with it being live 10, given that the issue has existed in the past. The general belief that something is less stable because it is updated is absurd, and unwarranted, and contextually inapplicable. It's not a rewrite.

 

Last edited: Feb 11, 2018

Whilst I do enjoy a good down to earth, friendly and light hearted discussion about whether or not, updating to version 10 of Live should or should not be considered a superstition, I have been using live since version 5, and I have never once had a vst locating issue, on ANY computer I've owned, I am willing to concede you can call it a superstition, but I am still calling it a bug!

 

Run it with win 8compability

 

Yup, here .. I think that’s nothing OS related stuff. The hookup gets generated by „faulty“ VST plug-ins ... unfortunately live does not recognize which plugins create the error .. in the past it did that by itself and missed that bad plugin on the new scan .. dunno why live 10 can’t?

 

Mine stalled on a really long vst scan and I force stopped it but I'm not sure what it missed. AU's had no issues.

 

Thats exactly what I also experienced .. lets wait for an Update.