- This topic is empty.
-
AuthorPosts
-
-
December 28, 2017 at 1:21 am #114519_olsenParticipant
Hi,
the H3000 Facrory Plugin isn’t recognized by logic x since
updating to High Sierra. It’s simply gone.
I tried a reinstall, but I got no luck.
I installed my audio library via
symlink ln -s to an external harddrive.
Any hints ?
-
December 29, 2017 at 3:59 am #148001
Hi-
When reinstalling, did you download the latest? (https://www.eventideaudio.com/support/product/52/installers)
Does it show up in the Logic X plug-in manager?
-Tom
-
December 29, 2017 at 4:51 pm #148004_olsenParticipanttlongabaugh wrote:
Hi-
When reinstalling, did you download the latest? (https://www.eventideaudio.com/support/product/52/installers)
Does it show up in the Logic X plug-in manager?
-Tom
yes, I took the latest version and it’s not showing in Logic.
Should I reinstall Logic ?
-
-
January 2, 2018 at 10:20 pm #148018
Hi-
I wouldn't think a reinstall of Logic X would be necessary.
First, to get the obvious out of the way: I'm guessing you have other plug-ins on the external HD, that ARE showing up in Logic, right?
Second, do you own any other Eventide plug-ins? Does this issue occur with them as well, if so?
Can you try unlinking and re-linking the audio library to the external HD?
-Tom
-
January 3, 2018 at 8:47 pm #148030_olsenParticipant
Ok, I unlinked the audio library and installed the plugin to my internal drive,
after changing the ownership to root:admin the plugin was found by logic.
My external drive has a ownership “username”:staff. Maybe it’s an security problem ?
-
January 3, 2018 at 10:30 pm #148032_olsen wrote:
Ok, I unlinked the audio library and installed the plugin to my internal drive,
after changing the ownership to root:admin the plugin was found by logic.
My external drive has a ownership "username":staff. Maybe it's an security problem ?
I would guess it is a permissions issue, possibly related to sandboxing (security protocol on macOS). It is possible that Logic X will refuse to load plugins that are not in specific locations (e.g. the default AU location on macOS), or which do not have appropriate permissions such as "username":staff. Changing the ownership of the drive could fix this, but be careful (though it seems you have some knowledge of permissions). It's also possible that the drive you have is not in APFS format, and it needs to be (this is purely speculation on my end).
-Tom
-
January 29, 2018 at 1:37 pm #148275radioman521Participanttlongabaugh wrote:_olsen wrote:
Ok, I unlinked the audio library and installed the plugin to my internal drive,
after changing the ownership to root:admin the plugin was found by logic.
My external drive has a ownership “username”:staff. Maybe it’s an security problem ?
I would guess it is a permissions issue, possibly related to sandboxing (security protocol on macOS). It is possible that Logic X will refuse to load plugins that are not in specific locations (e.g. the default AU location on macOS), or which do not have appropriate permissions such as “username”:staff. Changing the ownership of the drive could fix this, but be careful (though it seems you have some knowledge of permissions). It’s also possible that the drive you have is not in APFS format, and it needs to be (this is purely speculation on my end).
-Tom
Changing ownership of the drive or changing permissions won’t help – I’ve yet to see a daw program find plugins that aren’t in the default locations in the OSX system drive. For samplers it’s different – you can put the content anywheres and all you have to do is to point the sampler to the right content path. For instance all my samples are on a separate drive from my system drive.
-
-
-
AuthorPosts
- You must be logged in to reply to this topic.