Jump to content

MikeShapiro

Member
  • Posts

    678
  • Joined

  • Last visited

Personal Information

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

MikeShapiro's Achievements

  1. Confirmed that this works with Kontakt 5. If you toss your K5 plugin, loading a Logic patch that instantiated K5 will now load the same patch with K7 instantiated instead. Loading doesn't seem to be any slower, so I'm not sure it's necessary to re-save older patches at all. I'm really glad I asked about this. I might have otherwise spent tens of hours rebuilding my patch collection, and worried about having to do the same in the future. Thanks again wonshu!
  2. For anyone else interested in the solution Wonshu described, here is Native Instruments' documentation on the subject. Note that it claims to work down to Kontakt 3.5 (though I haven't tested this yet). https://support.native-instruments.com/hc/en-us/articles/12972701353757-Notes-about-Auto-Migration-of-Kontakt-Versions-in-DAW-Projects#:~:text=IMPORTANT%3A Auto-migration only works,still working on your project!
  3. I like the "have the assistants do it" solution. 🙂 Your automated re-save technique is definitely an elegant version of brute force. I wish there was a better way, but I may try it for the K6 migration. Thanks for the suggestion.
  4. Native Instruments seems to release each update to Kontakt as an entirely new plugin. An unintended consequence is that any Logic Patch instantiating Kontakt has to be manually updated with each new release, or else slowly fall towards obsolesce. I learned this the hard way when I upgraded Macs and found that all my Kontakt-5-based patches were suddenly nonfunctional. I'm curious how others handle this problem. Do you use aupresets instead of Patches for Kontakt-based instruments? (It seems that aupresets can be re-used across successive generations of Kontakt.) Do you just rely on Kontakt's internal browser, in its many forms? Other?
  5. Anecdotally, I had this problem the other day. I was recording a single audio track with nothing else going on, and on an Apple Silicon Mac. I'm almost relieved by the possibility that it could be a bug in Logic rather than a weird processor issue.
  6. I had this problem too; old projects with Blackhole reported an error message. There's a discussion of the issue over in Eventide's forums. The upshot is that the devs are aware of the issue and looking into it.
  7. Grousing update: even though I'm annoyed by the Mastering's UI space waste, the actual plugin seems to provide unexpectedly decent results. It seems to do a static analysis of your project, without the need to manually play the loudest portion in realtime (a la Ozone's tool).
  8. Feedback to the Logic team is dev/null. Whereas grousing to my colleagues has positive psychological value. 🙂
  9. It is an oddity. I appreciate that it's not fixed at the bottom of the strip, even if the "launch button" is. What would make me feel better about these shortcuts (including the dedicated EQ/compression affordances on individual tracks) is letting us remap them to third party options. Or remove them...
  10. Ugh, the Mastering plugin appears to have a dedicated interface slot whether you want it or not. Even if you don't remove the plugin, the slot is staring at you in the face at all times. Anyone find a way to remove it?
  11. When I saw that on Logic iPad I was REALLY excited. Hopefully it'll evolve into a Mac equivalent.
  12. My dream of a revamped Patch Library with tags will have to wait another six months.
  13. Thanks for that tip. I'll keep that fix in mind in case I run into this again!
  14. And also interestingly: I restarted Logic and the problem went away, even with my big template. So perhaps it was just a memory issue of the moment.
×
×
  • Create New...