Missing Plug-in management control?

Seems that the plug-in management processing pipeline left the building in the latest version of Audirvana Studio 2.9.4… On MacOS Monterey 12.7.6…

It’s working just fine for me (macOS Sequoia 15.1) Audirvana Studio 2.9.4…
Screenshot while playing a 24/352.8kHz AIFF file:

Also notice 100% cpu usage!!! Ouch…

:thinking:

Try the solution of deleting the App and its preference file as detailed in the following post which worked for @ChiliHot. Important to remove the app and the preference file as detailed in the post (you can leave the database file)

1 Like

Hi @Ddude003

Well… on my system [Origin 2.5.18] the plug-in msnagement has mysteriously disappeared also… although DEBUG lists it as active…

Anybody?

Phil

Close AO and try deleting the Audirvana preference file located in

/Users/{username}/Library/Application Support/Preferences/com.audirvana.Audirvana-Studio.plist (I assume for Origin it will be com.audirvana.Audirvana-Origin.plist?)

The library folder is hidden by default. Just go to your home folder then right click in the finder window and “show view options”. Midway down the view options dialog there should be a checkbox to “show library folder”. Then just go to Library and then Application Support etc as detailed above until you find the preference file.

Re-start Audirvana. As per the linked post above, where @chilihot removed both the app and the preference file to solve his problem of the disappearing processing section. If you close Audirvana and just delete the preference file then restart this may work without removing and reinstalling AO

1 Like

Thanks @Djm1960… That seems to have done the trick…

Hi @philipjohnson, Follow @Djm1960 advice…

Hi @Djm1960

I appreciate your help… however…

I do not have in Application Support “Preferences/com.audirvana.Audirvana-Studio.plist”

What Am I missing here?

Phil

I don’t have Origin but I assume there is an entry like com.audirvana.Audirvana-Origin.plist ?

Perhaps show a screenshot of the folder you are looking at (there is a library folder under the main system folder also, the one you need is in your home folder and sometimes people get confused between the two).

Well that smack on the back of my hand seems to have worked… I EVENTUALLY found the said “Preferences/com.audirvana.Audirvana-Studio.plist” and a couple of others in that mode which I duly deleted…rebooted everything and all is in its correct place now and my EQ is set up proper…

Thankyou @Djm1960

Very helpful.

No worries!

No worries for you! For me quite an issue.

[That sounds a little aggressive now I reread it but I meant it in the sense that you @Djm1960 have great knowledge and managed to resolve my issue easily. Also, for some reason the plist file eluded my hunting.]

I may also say, it was only the first post in this session that alerted the issue to me. It may have been in place in previous updates.

Thanks again.

Phil

Just a preference file problem when updating. This happens on rare occasions in macOS. Main reason why when installing an OS update I always do a clean install to avoid errors in preference files.

:thinking: … In my entire user experience with Apple Inc. platforms (some 40 odd years) I have never had a problem with preference files concurrent with an OS update… I have had problems with preference files associated to specific application updates or some anomaly not associated to an OS update, that required a PRAM or NVRAM reset.

:notes: :eye: :headphones: :eye: :notes:

1 Like

I would agree it is far more common when updating an app rather than the OS. In my case I have seen issues probably on 3 occasions since I first started using macOS for both work and personal use in 1999. A clean install of OS is not required, but for me is more of a preference, “a blank, sanded, re-skinned and primed surface as opposed to painting over wallpaper”

As I test beta versions of the major macOS releases to ensure my in-house software is compatible I have become somewhat proficient at clean installs (takes about an hour to rebuild my system) and have had to do so on occasions where beta updates have rendered my mac unusable or a critical app refuses to run and I have to revert to a production release.

Again not necessary but a preference for me (a bit of OCD in there as well I think….)

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.