Tronam

I know this thread is <gulp> 11 years old, but does anyone know if this has been updated or improved yet? The notation editor reflects key signature changes properly, but if I'm in a key like Eb-minor, the piano roll still shows all accidentals as enharmonic sharped notes. I guess I could just stick to sharp keys only, but something like D#-minor is a bit unusual, at least in my experience with most piano music. Perhaps it's more common with certain types of orchestral players.

Does anyone know where Logic Pro looks in the MacHD/Library folder to figure out where the Sound Library files are supposed to be located? Every time I load Logic after a while it'll suggest the link is broken and if I say to keep it on the main system drive it'll ask for my admin password to install a Helper. Once completed I get no error messages, but I suspect nothing actually changes because it'll keep doing this over and over again. The only option I ever see under the Sound Library menu is Reinstall Sound Library.

I'm experiencing the same issue as many in this thread and there are no external drives involved. The only option I can choose is "Reinstall Sound Library" and each time I do a blue progress bar redownloads what appears to be the essential ~1.5GB of sounds. I've done it several times and can't ever select the sound library manager. It didn't used to be this way, but it must be some recent combination of Logic Pro (10.7.1) and macOS (Monterey 12.0.1) updates that broke something. Unfortunately I don't have an older version of Logic Pro to downgrade to.

Well, after more than a month of head scratching bewilderment and all sorts of trial & error troubleshooting with a new admin account deleting Logic preferences, clearing caches and anything else I could think of... I think I found the cause: My display profile was set to sRGB. Setting it back to the default Color LCD appears to fix the issue. It's odd because prior to discovering this every time I deleted the Logic preferences/caches it would load *once* without issue, but then all subsequent loads would exhibit the GUI corruption. Because of that I was convinced that some 3rd party plugin may be the culprit. Anyway, hopefully this thread is helpful to someone out there. Native Logic has no trouble with different display profiles, but apparently under Rosetta it does, at least in v10.6.1.

Apple doesn't even call it Logic Pro "X" anymore, making the versioning even more arbitrary than it has already been over the past 7 years. I suspect it'll remain a buy-once-free-updates application into the future. They subsidize the cost of these pro apps through hardware sales.

For anyone here dabbling with music production on an M1 Mac, I would love to know if the windows display properly for you when running Logic under Rosetta. It doesn't occur for me at all when running Logic natively, but on two separate MacBook Pros (I exchanged for a larger SSD) under Rosetta I get strange graphical glitches with all of the main windows. I've included some screenshot examples: totally blank when loading previous projects or missing GUI elements with empty new projects where none of the track elements can be seen. If I move my cursor to where a plugin slot or control *should* be, I do see the tooltip and they do open when clicked. The previous projects play back as well, but the only thing I can see is the playhead. I'm really puzzled because I've seen so many reports from other users who have no such problems. I'm usually pretty good at troubleshooting, but I'm pretty baffled here. I did not restore from backup, so it's a clean install, but maybe something has been carried over from iCloud? Any ideas on what I might be able to try to troubleshoot this?

The Fabfilter plugins are M1 native now, as are those by Aberrant DSP: SketchCassette and SoundShifter. All of Valhalla's plugins I've checked so far including Room, Vintage, SuperMassive, Modulator all have M1 native betas available to registered users now.

I think I've finally resolved the issue. There are two folders in ~/Library/Caches that appear to be used by LPX as working areas before writing to the main Preferences folder: Logic and com.apple.logic10. Removing those folders finally made it possible to reset the preferences, but that only partially fixed it. I then found an Apple Support thread with a brute force root user command here: https://discussions.apple.com/thread/6669899 This was the only permissions command that actually helped. Neither Disk Utility or the home/ACL recovery mode reset method made a difference: YMMV. Thanks!

That would be my first guess, although I wish I knew what LPX is trying to do that it can't. I've done every method of permission/ACL reset I'm aware of for all accounts on the system including root. I've even added my specific account to its read&write permissions list. After erasing everything, redownloading and then launching Logic it recreates all of the preference files, seemingly without issue, but then it acts like it can't change them afterward. These settings won't change either: https://dl.dropboxusercontent.com/u/614947/Forums/LPX-Prefs2.mov Project preferences save just fine, though. No other programs behave this way. Very perplexing.

I really appreciate the responses. I've tried both trashing the preferences files and relaunching Logic, but also redownloading it from Apple. When it relaunches the preferences files do get recreated, so it does appear that the Logic application at least has permissions to write into that directory. The flickering that happens when trying to check or uncheck those advanced tools is just Logic refreshing the screenset. I'm pretty sure it does that normally whenever you enable or disable certain functions. Is there perhaps another cache folder somewhere that Logic uses or needs access to in order to successfully save preferences changes? In the other tabs I can enable or disable various features, but those settings won't stick if I quit and relaunch Logic. Very peculiar. EDIT: I created a new administrator user and launched Logic on that account. No issues there, so something must be wrong with my main account home folder. I've already tried repairing permissions via Disk Utility, which didn't help, then going into recovery mode to reset the home folder permissions and ACLs, but that didn't resolve it either.

I have an odd issue with LPX that has me stumped. Any changes I make in global preferences don't survive a reboot of Logic and some changes, such as the Advanced settings can't be modified at all. This is what happens when I try: https://dl.dropboxusercontent.com/u/614947/Forums/LPX-Prefs.mov I've tried trashing LPX along with com.apple.logic.pro.cs and com.apple.logic10.plist from ~/Library/Preferences, then re-downloading LPX, but this didn't help. Using the internal factory templates made no difference. Any ideas?

I think it's important to bear in mind that requiring AU plugins to be sandboxed doesn't automatically mean "only sold in the App Store". That was a hypothetical possibility which many folks ran with in the thread, but not a foregone conclusion at all. Sandboxing essentially restricts an AU plugin's ability to access other areas of the host operating system. A more interesting byproduct of this could mean the potential for AU plugin support in iOS with future iPads. If so, those would no doubt require an App Store purchase, but I'm doubtful they'd take a step like that with the OSX desktop.