"Over 50 and it gets worse and after that it's over"

We still talking about Ableton here, or life in general?

 

Are You block Ableton in Windows Firewall?

 

Im on Mac , mojave

 

I don't know how it works on mac.
Blocking Ableton in Windows Firewall is just blocking access to internet connection out of Ableton and in to Ableton.

 

Not always. Moving to new MBP M1 with 11 is the best move I ever made. Performance and stability multiplied by 3.

I used to think "I need to not update, stay on Mojave blabla". This is so wrong, because technology improves so much and increasingly each year. By updating everything you solve performance issues and give a boost of speed to your setup.

 

you can fix most of these just by codesigning them.
if you get an error with “unsealed contents blabla” you need to remove all files named something with “icon” from the contents of the vst file. then codesign again.
if you still get an error, this time with “detritus not allowed blabla” run “xattr -cr “ on the vst. then codesign again.
as soon as you get them codesigned 99% of vsts will work.

Also, before you even do the codesign, it should only be needed for izotope stuff and a handfull of other things, rescan your vsts, hold alt and click rescan in plugin tab if abletons preferences.

For me, I am on mojave as well, the ones I really can’t get to work are Camel
Crusher and other camel plugs, they open but no GUI. exact same thing for all the MELDA stuff.
Anyone else experience this/have a fix??
love my camel crusher ;(

 

I still haven't pushed live 11 to the limit...
soon I will.

 

How does one do that ?

 

Oof, Ok.
Again, first rescan your plugins. open ableton preferences, go to plugins tab, click on rescan while holding the alt key.

then, for all plugins that still do not show up or do not open/crash when you put them on a track, do the following:

find the plugin file, so for vsts its the .vst with the plugin name, in finder. by default your plugins should be in library/audio/plugins and then vsts are in vst folder, au in components folder and so on.

now open terminal. it is in applications/utilities.

type the following into terminal(with all spaces including the one at the end): “sudo codesign -fs - “ and then drag the plugin file into the terminal window. it should now have copied the plugins file path behind the command. remove the space that is added at the end(after the filepath) and hit enter. it will ask you to type your admin password, you will not see anything when you type, but just type your password and hit enter. you should now see “replacing existing codesignature” and then it goes back to where you can type a new command(might take a second).

if that is the case, it worked and your plugin should now load in ableton.
(in some cases you might have to restart your computer and/or again rescan plugins in ableton, but generally if you see that readout things are looking good and it will mostly work right away)


now some plugins, specifically ozone stuff, will give you an error message though(printed in terminal after you execute the codesign command above) and it wont work.

if you get an error message something like “unsealed content, bundle blabla” do the following:
in finder, right click on the plugin file, click “show package contents”. now, inside the plugin folder delete files named “icon”, “_icon” or “icon?” or similar. could be multiple such files but mostly only one.
you should only see a folder named “content” in the plugin, no “icon” files.

now go back to terminal and repeat the codesign command above, exact same steps, type command, drag in plugin for filepath.
if it works now (you see the “replacing existing codesignature”, congrats, ur plugin should work now, see above.

however, for some plugins you might get yet another error readout in terminal, this time reading something with “detritus not allowed blabla”

in that case do the following: in terminal, type “xattr -cr “(again with the space at the end) and again drag in the plugin to add the file path, remove space after filepath, hit enter.
it should just run the command, no readout, and let you type again right away.

now once more repeat the first command, the “codesign” one, in the exact same way as before, on the plugin. now it should at last give you the “replacing existing codesignature” success message and your plugin should work.


should you ever get nothing, no error message, no “replacing codesignature”, after you execute the codesign command, can happen, to be safe just type it again and you should get the “replacing codesignature” success message.

this should get most plugins running and is the same process on vst3 and au also.


if a plugin gives you the successful “replacing” message but still doesn’t work you can try the second terminal command I wrote above, the “xattr” one, after successful codesign also. some odd ones that might fix. but generally if codesigning them doesnt make em run they probably wont work.

hope you understand, really cant write it any clearer though. good luck!

 

Thanks a lot ! i'll try these

Just reporting back to say that it worked ! thanks mate

 

Last edited: Feb 28, 2021

Hi to All,
I want to share a little problem that occurred when I installed live 11. Briefly, battery 4 of NI doesn't work. It's appear "vst 2 plug in is damaged and can't be opened". I tried to reinstall this plug in but this didn't resolve my problem.
Is there someone can help me, please?
Thank you for problem sharing.

 

Didn't test it so much yet and i still have a lot of plugins to try, from my personal experience until now i found out that vst3 versions of Zynaptiq plugins crashes Live every time i try to load it, i uninstalled it, they are cpu hogs anyway and i didn't use that so much, not a big deal, app crashes with "emit" max for live device from "inspired by nature" pack everytime i try to load it on any project already "in progress", no crashes if i start a new project and i add the device, really weird. Battery works, tried reaktor 6, Massive X and some Arturia plugins and they work fine, i will update as soon as i found something else, and yes, cpu meter is a pain in the ass.
I'm on Window 10 1903.

 

So far 8 times out of 10 when I close a project or switch to a different one it will crash with the error message to restart.
If it wasn't for the faster loading times I'd be mad,

 

So I have been having this wierd problem which I think should be PC related. Audio export in Live crashes Live (seems to be a conflict between Live and explorer). Not just that but it seems explorer is broken everytime you try to even add a folder. This started after a certain 10.1XX crack build. Fingers crossed, I thought installing the new 11 would get rid of that but that was indeed the first problem that presented itself to me when I even tried saving the machine id file for authorization. Anyone have any idea on fixing this? Like I said, I believe it's a PC related problem. But this has been killing me for well over 2 years now
PS. No problems so far. 11 seems a little faster. Windows 10 2004

 

ive got the same problem, in v10 also. before closing or loading another project i use "file - new live set". in 9 out of 10 tries live doesnt crash anymore while quitting or loading another project.

 

Hey. Thanks for your reply. The Templates thing was supposedly a new feature. A dedicated tab in the browser for various templates instead of just having one default project, or having to load into the same template every time you start Live. I can save as default from the preferences menu. When I save a template it does pop up in the User Library, but I was trying to save to the Templates tab. If you can't do that, that tab is basically useless.

EDIT - I just got home from work and started fiddling with it. Turns out the problem was caused by my having made a folder in my user library long ago called templates, but in all caps. I changed it to "Templates" and it works. Who knew

 

Crushing occur when Delete Halion in live 11 win10 but can replace