It could definitely cause you a problem. But when he loads the project, it lags; but then he mentioned that after that it just runs poorly. Wouldn't it give you an error message about a bad plugin? I think it would complain.

You can always rule out all the plugins if you lookup the keyboard shortcut to open the daw without the plugin manager loading anything. That is what you normally have to do with projects that contain a bad plugin in them, because they will often crash your DAW before you even get to the interface.

 

i just replied, ive encountered crashing VSTs before.

These 11 projects even run bad in 12 with NOTHING in them. Crazy eh..

 

I use Logic primarily and do not "customize" my install in any way. So if I was to delete say Logic 10.4, and upgrade; I would delete Logic.app, install the new one. But I would not lose anything, because it is 100% stock aside from a few custom keyboard shortcuts. But you get the idea.
It is extremely easy for me to be back working in as long as the install process takes. If I had agreed to Beta a version of my DAW, it would be completely painless. I have installed Ableton before but all I can say is that it did not take very long, and I was not checking it for any sort of migrated data.

I mostly run an old Mac so I have a lot of experience with newly installed plugins crashing my DAW, because I like to see what I can get away with installing. If I install a crashing plugin, it is scanned and evaluated by a utility called AUvaltool. This includes opening the DAW to an empty project. It crashes before the DAW even tries to load an existing session or creating a new one. To get past it, I need to kb shortcut my way into Logic without AUvaltool even scanning them. Once the Plugin Manager gets a hold of them, they are already in use by the system.
It doesn't matter if they are in a project or not. You have to disable all plugins when it happens.

If I had your problem, I would look into getting Ableton open with no plugins visible to it's plugin manager, Rule that out.
After that, I would consider moving all my plugins from the folder they are in, where the DAW can "see" them; and moving them all into a backup folder that I can just as easily put them back. Then try again. If it doesn't help, put them back to your normal plugin folder.

After that, I would remove 11. Test 12 with only it installed. If still wrong, I would remove it with Revo Uninstaller. Reboot. Reinstall only Ableton 12 again by itself. Test again. Now you have removed any traces of 11, cleanly reinstalled 12. If 12 is the same, your problem is 100% related to 12, and you won't be able to fix it yourself. Remove 12 and go back to only 11 on the machine.

Then put 12 back if you want, knowing it is not a good build # for the machine, or whatever it might be. You want to rule out the impact of having them both installed at the same time, not cleanly updated, or whatever the problem is. But you would have the real answer to the situation.

 

PDC problem still there

 

11 is still running fine in parallel to 12. A few days back I tried renaming vst dir so it couldn't see them and projects are still slow.
So i think your right, next ill try a super clean install of 12 and test.

 

Not a big surprise, but thanks for checking.

Maybe you will find something interesting for them to fix because of your testing. Lots of this audio software stuff can be figured out and fixed, but some there is just nothing you can do about it. "It is what it is". You accept that is the correct answer confidently, and then do something about it. Another program or plugin, or a workaround.
Sometimes the fix is worse than just putting up with it.

 

Update - Its groups causing slowdown. Anything made in 11 using a group runs badly in 12. Remove the group, load same elements in 12 and it runs fine.


At least i understand the issue and how to fix a project in 11 to make it run in 12. But i have hundreds of tracks all using groups, so i need a proper fix really.

Filed bug reports and contacted tech support but they wont deal with it until release next week when its properly released.