dundergufs

EDIT: Admin please just delete, someone posted this as I was typing! Release notes is at the same link as earlier in the thread: https://support.apple.com/en-us/HT203718

This is fixed in Logic Pro 10.8.1. 😮‍💨

I often work with sound design in Logic (either within a production or as prep for future music production), in this context MIDI notes might have multiple meanings and being able to also shuffle MIDI notes would be very useful for me in that setting. I can also easily see it being helpful when working with slices in loop-based sample instruments that are often chromatically spread (which is what the original poster's screenshot indicates).

Upon loading projects created with earlier versions of Logic Pro, version 10.8 will not load Native Instrument's Guitar Rig 5, 6 and 7 plugin if it was inserted as an MFX plugin (able to receive MIDI). Logic will report: The plugin "Guitar Rig " is not available on this system. The only workaround for now is to stay on 10.7.9. (Probably many of us has always used Guitar Rig MFX as effect in our projects - for me this is a delicious mess, huge amounts of old projects are completely unusuable if I'm to go forward with 10.8) The issue is known by NI and possibly by Apple via NI. From Eddie on the NI team in their forum: "Further analysis shows that the new limitation is that FX and MFX versions of the same effects are apparently not allowed by Logic 10.8. We don't know why that is and will need to get in touch with Apple about this. We are very sorry for the inconvenience." Hope this warning reaches others thinking of upgrading, before you tear your hair out 😉 I wasted half a day figuring it out myself why Guitar Rig seemingly randomly did not load (since the non-MFX versions still works!)... (And Logic naming the missing plugin just "Guitar Rig " without reporting version or MFX suffix DID NOT HELP). Once I figured out what was happening, searching for it and found it is already discussed in the NI forums: https://community.native-instruments.com/discussion/18366/guitar-rig-6-mfx-patches-gone-when-updating-to-logic-10-8#latest

After some back and forth with helplful NI support Kontakt developers, the gist of the matter from them is "we thought it would work on 12.x, but since it works on 13.x and above, we're not gonna do anything about this, sorry!" Which I can unhappily understand and accept. And now that Logic 10.8 also demands 13.5 and above, I'll be forced up at some point soon anyway. Gah, the sonomania of progress!

I have (had) all versions, on all of these systems I removed K3, K4, K5 and K6, leaving K7. On the macOS 13 system, K7 loads all the missing versions fine. On the macOS 12 systems, it doesn't.

Native Instrument's Kontakt has a feature for auto-migration from older versions to the latest. It is supported by Logic. https://support.native-instruments.com/hc/fr/articles/12972701353757-Notes-about-Auto-Migration-of-Kontakt-Versions-in-DAW-Projects This auto-migration works perfectly fine on my travel / backup-system, a 14" M2 MacBook Pro running 13.6 and Logic 10.7.9. On that system, every instance of Kontakt 3, 4, 5 and 6 is automatically replaced with Kontakt 7 upon loading projects using older Kontakt versions. Everything is super, it works exactly as promised, great. However, it does NOT work on my main studio system, a 16" M1 MacBook Pro running 12.6.1. I also tried an older M1 Mac Mini also on 12.6. On both of these systems, instead of Kontakt 7 replacing older versions, I consistently get "The plugin Kontakt x is not available on this system" for each and every instance of older Kontakt plugins. No auto-migration takes place. Kontakt 7 loads fine in itself, it just won't auto-migrate like the other system. On all systems, all previous versions of Kontakt has been thoroughly uninstalled, as instructed by the article linked from the Migration article. What I've tried, made no difference -Rosetta mode on/off for Logic -Reboots -Reinstalls of Kontakt 7 Is the problem simply the difference in macOS, 12 vs 13? Does this work fine for you, and if so what macOS are you on? Any idea or experience why this happens on my systems, what could cause it? What more could I try? Workarounds: I could theoretically manually open aaaaaall old projects on the travel system where this actually works, and then re-save them with updated Kontakt 7, but that is insane amounts of work, thousands of projects, a very stupid way of solving this. (The reason I *have* to do this migration, is because on Apple silicon, Kontakt 5 loads user-generated instruments completely blank, with zero warning, I have thousands of these, so I am constantly loosing work loading old projects. I have to replace these K5s with K7s.)

This is lucky reply nr 88 in this thread I'm here to announce my numerical excitement for the day I will be running Logic Pro 11.1.1 - or someday even perhaps 11.11.11 ! 🤩 (I might be okay with 10.10.10 too, allthough it is even...)

This free app "Recording Indicator Utility" works for Ventura and Monterey to disable the orange dot. Maybe the programmer might update it for Sonoma and that update would also work for this new audio input notifier? (Or maybe it already works, I have no idea and won't update to Sonoma or future macOSes until I'm forced up.) https://github.com/cormiertyshawn895/RecordingIndicatorUtility One has to disable SIPS (System Integrity Protection) to use this tool. That disables some other features, see the FAQ. But the compromise works for me, I'm using macs for live audiovisual productions and can NOT have that dot there on huge projections. To be clear: I don't know if this would work on Sonoma. It works on Monterey for me. I haven't tested it on Ventura. It's insane there is no official way to disable these indicators.

Same here, I'm still using Dropbox with zero problems, syncing projects and assets all the time on multiple systems. I'm on macOS 12.6, Dropbox is version 181.4.5678. However worth to note, they have NOT transitioned me automatically to the new "Dropbox for macos on File Provider", this has not been enforced on me on any system (yet!). I got a notification some time ago that asked me if I wanted to shift; "you are eligible for the updated Dropbox" (sneaky wording trying to make me do it, they clearly want you to). But they left the decision up to me, and kept "old" Dropbox regularly updated separate from this The same actually happened on a brand new system running 13.5, there too I was given the choice and declined. So also my macOS 13 system is still using vintage Dropbox. I guess at some point I'll HAVE to transition to that file-provider-version, but at that moment in time - probably when I get a new mac and then being forced onto a new macOS which might not run vintage Dropbox or something else critical for me - then I'll revise the situation then, at that crossroad. (My expectation is that by the time I will be forced to do this upgrade, all bugs and problems with file provider will have been solved and/or sensible alternatives has appeared.) This is only my experience, others might have different. I have no experience with projects disappearing, sorry to hear that. You might be able to figure out what happened by visiting the folder on Dropbox and see the history.

Not a solution, but a temporary workaround in case you haven't tried this: Since you can open older projects that contain K7 and those load fine, could you open one of those and then save one of the Kontakt channel strips as a channel strip preset? And then in new projects, just load that channel strip preset whenever you need Kontakt plugin, until a proper solution is found?

Mfritzicator Pro X

Same here, got tons of stuff in there with dependencies. Apparently when the update happens, it will create a symbolic link ~Dropbox at the previous (your current) location of Dropbox, so theoretically everything depending on files being located in ~Dropbox/YourFolderStructure should practically work as before. If it doesn't create this symlink, you can create that link yourself. But I don't know, I also really don't like these changes 😒 In particular I don't like this update being forced on me automatically, AFAIK there is no way to turn off Dropbox autoupdating itself and at the same time keep using Dropbox as normal. I would very much like to do this update manually, when I have time to be conscious about it and verify that everything works. At best I'd wait until I have to migrate to macOS 13. Though, it *might* be fine, who knows. I'll update here when it happens to me, at the moment it hasn't updated for me yet.

Headsup: The Dropbox service is now transitioning to Apple native, and this shift introduces changes: https://help.dropbox.com/installs/macos-support-for-expected-changes One of the issues for macOS 12 (but not macOS 13): * Certain files, such as .fcpxml (Final Cut Pro) and .logicx (Logic Pro), may not sync. I'm on macOS 12, but my Dropbox isn't updated yet so don't have any practical experience yet. Been using Dropbox for decades (!) with zero problems and great benefits, including syncing all projects and sound libraries. (My syncing is for backup, backup versioning and duplicate my work on multiple systems.) Up until now Dropbox has technically and practically been perfect for me, and a much better service than iCloud, but now.... Not enthusiastic about these changes, though it might turn out unproblematic in the end. Many other cloud storage services also introduce similar restricitions. There are more practical details and experiences in this Hacker News thread and here's a Macrumours article on the change.)