kerems

this worked. all look ok now (quick look). i conclude my first reinstall was sort of unsuccessful, due to above, with no error messages. as a result i gave you wrong information from the start saying i reinstalled logic pro x, sorry for that. and thx for the help. i nearly gave up, you kept me going

Thx, yeah, I also started thinking my reinstall was not successful ... maybe due to a permission issue. So I found a more detailed uninstall instruction set and retried. I found out I (Admin) was not able to trash the ../Application Support/Logic folder (although I was able to delete it's entire content). I deleted it using the Terminal. I will try a second reinstall. Fingers crossed

new user with admin rights went back to the starting point. i.e. No plug-in for the MIDI Fx. Giving up for now. Thx.

Thx Atlas. No I didn't, did a quick one just to see if it would work. I will retry the way you proposed, may change everything Thx for all the help guys.

Nope, no change. It's odd really, Logic becomes new, remembers nothing but the problem persists Sad but not too critical, seems a very individual problem too.

I did it that way as far as I recall but will try again. Below's the instruction text I followed. One small difference though I have a "com.apple.logic.pro.cs" file instead of a "com.apple.logic.pro file" Guess not important but telling just in case. Quit Logic Pro X. In the Finder, choose Go > Go to Folder. Enter ~/Library/Preferences, then click Go. Remove the "com.apple.logic10.plist" file from the Preferences folder. If you upgraded from an earlier version of Logic Pro, also remove the "com.apple.logic.pro" file. Restart your Mac.

Anyway, thx David. It's obviously in the user.

Peh, they are available in a newly created user Bad face cause seems impossibly hard work transferring to a new user, espc with audo plugins. had numerous errors with installed licensers, special registrations, external dsp related plugins etc. Is there a way I can try repairing the original user (admin) user to a better state? Guess there's a residual within the admin user that is causing Logic to behave odd on these.

OK. Thx David, I'll try that soon ... and report back too. The thing is this is the only user and it is the admin etc. but let's see.

Yes, no other apparent problems in my daily life with Logic Pro. I was just not using the MIDI Fx, one day I tried and puf they're not showing. Sth interesting and new though, now I tried a Logic ready template instead of one of mine. The one named Electronic. In that on one of the tracks there are two MIDI Fx inserted (a Modulator and a Modifier) and they are working. I just can't get the list to show and insert one myself anywhere. Totally above me but does this somehow show there's something wrong with my "user"s relation with Logic. Any ideas?

It is/was enabled, unfortunately

All Advanced Tool prefs are enabled.

On all software instrument tracks. Haven't tried an external MIDI track. I only have the "essentials" part of the library downloaded. I am not a library user. Do you think it can be related to the library/presets not being complete or missing? Cause it's not sth I considered. Would you think completing the whole library download process could have an impact?

Hello, Quite an old Logic user but haven't been a user of MIDI Fx plugins. They weren't even part of my Channel Strip Configuration in the mixer. Lately had to use them and my MIDI Fx dropdown showed "No Plug-in". I remember trying MIDI Fx with no problems when they were first introduced but now can't get them to appear. - Tried reading rare threads looking similar with no solutions. - The user, is the only user I have always used (and installed) Logic Pro - no other users on this computer (except guest). - Did a delete of Logic preferences. - Did an uninstall/reinstall for Logic Pro X to no change (only the essentials part of the library). - I see the -plugins- under Plug-in Manager / Logic - their versions = 10.3.2, their Use chkboxes are checked. - I have Logic Pro X 10.3.2 (re)installed and working with no other apparent problems, on a Mac Pro (late 2013) w Mac OS Sierra 10.12.6. Thx in advance for any advice (other than the above .