![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
|
![]() |
|
Thread Tools | Search this Thread | Display Modes |
#11
|
|||
|
|||
![]()
So even with no plug-ins after deleting preferences it crashes loading plug-ins. Well that is a head scratcher.
__________________
Pro Tools, Studio One Pro 2022 Mac Studio M1 Max 64GB-1TB NVME OWC Thunderbay Mini (4TB SSD) OWC Express 4M2 (4 X 2TB) Interface: Presonus Quantum Presonus Faderport & Faderport 8 Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128 BM5A, KRK VXT4, Equator D5 2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig) |
#12
|
|||
|
|||
![]()
I am extremely new to this and have no idea what you are telling me to do.
|
#13
|
|||
|
|||
![]()
Indeed.
|
#14
|
|||
|
|||
![]()
__________________
Pro Tools, Studio One Pro 2022 Mac Studio M1 Max 64GB-1TB NVME OWC Thunderbay Mini (4TB SSD) OWC Express 4M2 (4 X 2TB) Interface: Presonus Quantum Presonus Faderport & Faderport 8 Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128 BM5A, KRK VXT4, Equator D5 2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig) |
#15
|
|||
|
|||
![]()
Edit: lots of good posts and more info in posts above from after when I drafted this reply, walked away from my computer and later posted it
![]() I know you are new to this, so I'm not trying to criticize you. I want to just get the clearest info to you for this and future problems. And I wish this stuff was not so buried/hidden from new users. Look up the top of each DUC web page under "Help Us Help You" and read the standard troubleshooting steps. You should be trying those when you have problems, before you decide to upgrade Pro Tools or your OS, or before posting here (and when you do post describe exactly what you tried/what happened). Did you check all the installed plugins are up to date and compatible? Especially after updating Pro Tools and your macOS. Especially *always* start troubleshooting by trashing prefs (use Pete Gates lovely free PT Prefs program). https://petegates.com/pgptprefs.html. Make sure you are using Pete's PT Prefs, it's too easy to miss something, or follow the wrong instructions, if trying by hand. And especially *always suspect plugins* which means you'll be doing the standard troubleshooting tests like moving all .aaxplugin files out of the plugin folder, I also always trash prefs after doing that, and restart Pro Tools and seeing if the problem still occurs. Pro Tools will automagically reinstall it's core plugins when it restarts, just try to see if it can work with just those, and yes all the other plugins won't be there -- when you do this confirm that pro tools is restarting with only the core plugins, and the first startup there after moving the .aaxplugin files out of the Plugin-Ins folder should be slow as Pro Tools rebuilds the plugins cache... which would have been deleted by trashing prefs. If it works OK... then you start reinstalling plugins that you need. Checking as you go doing that, starting with the most important plugins you need. Reinstalling can be a better idea than copying back the plugins if you go to the plugin vendors' websites and download the latest/best compatible plugins. And just in case it's a driver/hardware issue you'll try using the Mac's audio output as the playback engine and see what happens. You'll also try repeating all this from a newly created admin account on the Mac. Normally those and other standard troubleshooting steps are much more productive than just reinstalling or upgrading stuff (unless you know a bug was fixed in a later release). Reinstalling or upgrading Pro Tools does nothing to remove potentially toxic plugins (which can cause problems and crashes just by being installed in Pro Tools, even if you don't instantiate them in a session). Again *always suspect plugins* and *always start by trashing prefs*. Trash prefs between other steps as you troubleshoot stuff. I suspect you also did an insitu upgrade of macOS. That's not something I'd recommend (and Avid has recommended against it) when jumping major versions. You are better off leaving the old system in place and doing a clean install of everything on another boot volume. Advice for next time you have problems is ask first, don't start doing stuff, flounder then ask for help, by then it might be too late. Worse case here you'll be doing a clean macOS install on a new boot partition and going from that. But try the standard troubleshooting steps first, then if you are stuck I would just jump into a full clean macOS Ventura install and install Pro Tools 2020.12 on that. Ideally do that on a new volume on a SSD and don't delete the existing boot volume until you have everything working and all sessions and documents moved over. Do not use the macOS System Migration Assistant (Assassin) to move applications or drivers across, reinstall all that from scratch. Using it to move user accounts and documents is OK. Last edited by Darryl Ramm; 01-08-2023 at 05:41 PM. |
#16
|
|||
|
|||
![]()
Got you. Creating a more accurate post that I learned from Help Us Help You right now. Thanks.
Quote:
|
#17
|
|||
|
|||
![]()
Sorry for the latency. Been moving. Dump file? Like i said im dead ass new to these termonologies and what not if you can break all of that down. I brought up textedit. What are dump files?
|
#18
|
|||
|
|||
![]()
"Close Pro Tools and launch Finder.
Click Go and select Go to Folder… Enter ~/Library/Preferences/Avid and click Go. Delete the Pro Tools folder. Restart your computer and launch Pro Tools." Last edited by Professor X; 01-18-2023 at 04:13 PM. |
#19
|
|||
|
|||
![]() Quote:
Trash *everything* with PT Prefs. Especially tell us what shows up on your screen? How far into the boot/splash screen do you see? What is it say it's doing? Go through the other things suggested in troubleshooting. You should especially be testing just opening Pro Tools with no session, trying with the Mac's built in audio output device as the playback engine, and try creating a new Mac admin account and repeating all the tests from there. And I'd repeat moving all the .aaxplugin files out of the plugin folder, confirm the folder is empty, start Pro Tools, confirm it automagically puts back the core plugins, and just leave stuff like that while you keep troubleshooting. If this an old Mac that has had multiple macOS updates applied in-situ then at some point you should be willing to give up and do a clean macOS install and reinstall all the apps from new (don't use system migration assassin (assistant) to move apps or drivers). Plan how you will save/move over all your user documents etc. before you do this. |
#20
|
|||
|
|||
![]()
I'm having this problem as well. I'm on Monterrey 12.6.2 Intel iMac Pro 2017 and everything was working for awhile on Pro Tools Intro.
I moved all my plugins to a separate SSD then I used the Petegates software and deleted preferences, restarted and tried to launch Intro with the app doing one hop on the dock right before the crash reporter takes its place and intro vanishes. I tried logging on as admin as a new user account and retried the method above to no avail. |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
What good is "Save Copy In..." options "Session Plug-in Settings Folder" and "Root"? | ZerglingPhilosophy | Getting Started | 1 | 09-02-2022 03:43 PM |
"Pro Tools could not load the following plug-ins" on Native Instruments plug-ins | Joachimoj | Windows | 6 | 08-14-2015 04:42 AM |
Pro Tools Crashes during "Restoring Tracks" portion of startup | rhythmator | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 11 | 12-28-2014 10:42 AM |
Pro Tools Crashes on Startup During "Setting Up I/O Paths" | ChrisIQ | Pro Tools 10 | 3 | 08-24-2013 05:27 PM |
Pro tools 9 crashes at startup "Bus error" in thread "MainThread", at address 0x0 | danball | macOS | 2 | 09-26-2011 04:49 PM |