Quote:
Originally Posted by Darryl Ramm
If I was aware of an issue in Ventura/apple silicon related to this I'd let you know. And other folks here who notice this thread would as well. (next time you might get more visibility for questions like that by titling the thread "Assert blah on Ventura on M1". But don't create a new thread now. Do you have a Monterey install you can test on? (the good news on Ventura is it's not a hugely invasive upgrade compared to other recent macOS updates, well so far, maybe you've found something).
Try backing up a bit and try other solution not specific to Ventura or Waves. Asserts tend to get put in the code by developers at major points where things might go wrong, they can have causes that last on for a while, or seemingly stuff that fixes some problems but not others... you should try them out, not assume it's only related to Ventura or hope somebody will know exactly a fix for your situation--they might but I've not noticed it being seen by others. And OTOH Avid seems slow about taking know assert causes and promoting them to plain error messages that would be more directly helpful... so we are all kinda left trying the pool of known related fixes/work arounds but at least that's usually quick to see if they work... and then if stuck it's maybe best to escalate to Avid support or Waves support. Often the plugin vendor support is a better place to start... they tend to hear about any version compatibility problems fast (and quite often they can fix any causes in their code).
This assert tends to clusters around file permissions/session issues which is why checking file permissions, making sure you are not using iCloud or cloud storage turns up repeatedly. And plugin code does get involved in writing to the session file, which is how this can tie together. And worse case you have a badly errant/incompatible plugin that is just scribbling all over memory, even if not being used/instantiated, potentially corrupting memory internally that then causes this assert.
You've already had a good go at standard troubleshooting, esp. trashing prefs, I'd also try creating a new admin account and testing from there. Spend time rereading those assert posts and try anything suggested there, And if still stuck I'd ping Waves support. You could also say try pulling out all the waves plugin files, leave on and the waves shell and see if that has the same problems... I expect waves support to have you try stuff like that.
files
|
hi, I placed a home folder on a external SSD and based on the structure that AVID uses to integrate themselves in your computer root etc the plugs will not load., as soon as I switch to the internal SSD home user it works..this is a bit concerning though cause AVID should is not an App Store developer so to have such access makes you wonder why.