Strange Plugin Behavior

[Jerome Gilmer]

Lately I've had issues where I instantiated a plugin and then set it as desired. Upon closing the plugin window the plugin behavior changes completely, like a major change in volume, eq or other setting. It's happening with Slate, Waves and MOTU plugins. Baffling and frustrating.

Using 9.02 on El Capitan (Yeah, I know. changed too soon)

[MIDI Life Crisis]

Not seeing this at all. Have you tried saving settings as a preset? Will it let you do that? Sounds like a permissions problem.

[mikehalloran]

Using 9.02 on El Capitan (Yeah, I know. changed too soon)

Many of us are doing so with no problems.

If not on 10.11.4, update the OS — many issues were fixed. Not all but most.

Sounds like a permissions problem.

You're not supposed to have to but MAS comes up in the list anyway so a very good idea to Repair Permissions. You do this in Terminal now but it's painless. Copy the following and paste into Terminal, then Enter or Return. It will ask for your admin password. You are done when it asks for the next command.

sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

Cool Terminal trick: when done, quit Terminal but do not close the window first. Next time you open the app, you will see the command in the window so that you can copy and paste it again.

[bayswater]

Cool Terminal trick: when done, quit Terminal but do not close the window first. Next time you open the app, you will see the command in the window so that you can copy and paste it again.

If it's there, do you need to copy and paste? Can't you just press the "up" button to get the last command back? Works here.

[MIDI Life Crisis]

sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

Cool Terminal trick: when done, quit Terminal but do not close the window first. Next time you open the app, you will see the command in the window so that you can copy and paste it again.

Just now repaired permission in El Cap for the first time. HOLY COW!!! Repaired pages and pages of permissions. YIKES!

Thanks, Mikey

[bayswater]

Just now repaired permission in El Cap for the first time. HOLY COW!!! Repaired pages and pages of permissions. YIKES!

I thought EC was supposed take care of permissions in background or during startup.

[mikehalloran]

Cool Terminal trick: when done, quit Terminal but do not close the window first. Next time you open the app, you will see the command in the window so that you can copy and paste it again.

If it's there, do you need to copy and paste? Can't you just press the "up" button to get the last command back? Works here.

Yea, I forgot about that. Thanks for the reminder.

[mikehalloran]

Just now repaired permission in El Cap for the first time. HOLY COW!!! Repaired pages and pages of permissions. YIKES!

I thought EC was supposed take care of permissions in background or during startup.

Widely reported. Absolutely false.

Also untrue is that a Safe Boot rebuilds permissions—it only resets the caches to default and disables 3rd party extensions (useful for troubleshooting).

I tested both of these last year and posted them in an old thread somewhere around here.

After a reboot, I get three lines of permission errors involving displays. They apparently do no harm. Running it again makes them go away till my next reboot.

I did have a MBP last week that left me with a dozen lines starting with usr and involved location sharing. I did a re-install of 10.11.4 from the repair partition (option-boot, select) and on the second time around, those lines went away.

[bayswater]

Just now repaired permission in El Cap for the first time. HOLY COW!!! Repaired pages and pages of permissions. YIKES!

I thought EC was supposed take care of permissions in background or during startup.

Widely reported. Absolutely false.

Also untrue is that a Safe Boot rebuilds permissions—it only resets the caches to default and disables 3rd party extensions (useful for troubleshooting).

I tested both of these last year and posted them in an old thread somewhere around here.

After a reboot, I get three lines of permission errors involving displays. They apparently do no harm. Running it again makes them go away till my next reboot.

I did have a MBP last week that left me with a dozen lines starting with usr and involved location sharing. I did a re-install of 10.11.4 from the repair partition (option-boot, select) and on the second time around, those lines went away.

This seems odd. So permissions do get corrupted or altered, the tool to fix that has been removed, and expecting the mass of general users to use Terminal is out. What are they thinking?

[mikehalloran]

What are they thinking?

Damned good question. Apple engineers I know are dumbfounded as well. The line I usually hear is that Disk Utility is broken and not likely to be fixed till after OS 10.12 is released.

The official explanation is that app developers are supposed to fix them so that it's not an issue. Yes, really.

The idea that there are older apps which require permissions repair to work properly in 10.11 somehow must have escaped the project managers.

I don't know for certain that DP 9 requires it but there is no doubt whatever about 7.24 and 8.x, both of which install and run fine in El Cap if Repair Permissions is run. Frankly, I am not holding my breath for DP 7.25 and 8.08, ya know?

Most of the 'pages and pages' are for files that install with the OS. Uhhh… yea…

[MIDI Life Crisis]

There were tons of scanner and printer permissions. Second run: clean!

[Grigri]

Lately I've had issues where I instantiated a plugin and then set it as desired. Upon closing the plugin window the plugin behavior changes completely, like a major change in volume, eq or other setting. It's happening with Slate, Waves and MOTU plugins. Baffling and frustrating.

Using 9.02 on El Capitan (Yeah, I know. changed too soon)

It could be that your plugins runs in pre-gen mode. Make sure that you run the plugins in real-time mode.
In pre-gen mode, the plugins takes a little time to create the modified sound once you close the window.

David

[David Polich]

El Crapitan. Still have no desire to ever install it. Will wait for the next O.S. which will probably
be "Shasta" or something like that, and that will fix what's wrong with El Crap.

[daniel.sneed]

No need of Terminal here.
AFAICT, OnyX does repair permissions on El Capitan.

[Shooshie]

El Crapitan. Still have no desire to ever install it. Will wait for the next O.S. which will probably
be "Shasta" or something like that, and that will fix what's wrong with El Crap.

I waited and waited. Finally, Yosemite was giving me so much trouble that I decided the lesser of evils had to be El Capitan. Now I wish I'd done it in the beginning. No problems. Well... a few left over from previous OSes, but nothing new. Even got MenuMeters working again after someone posted a link to a patch-job.

I was mostly afraid that I'd lose Wallander Instruments, since Arne W. isn't too active anymore, but I wrote him and he said it worked, so I tried it and sure enough, no problems. Despite the difficulties others seem to have with the WIVI interface, I've found true nirvana there, and I'd stop upgrading the Mac if I had to do so to save Wallander. But no problems found.

I don't have a lot of the plugins that others have; mostly Waves, Altiverb, MOTU, Blue Cat, and a few others. Also, I don't use plugin automation except in rare cases, opting to go about such automation in different ways when possible, to avoid crowding of data. So, YMMV, but it sure seems benign. Everyone told me to go ahead and upgrade to El Cap. For the longest time I couldn't make myself do it, but when I finally took the leap a month or so ago, I found there was never a cliff. Just a nice path to the other side. My doubts were in vain.

Shooshie