ncalonne

maybe "MIDI Defaults" has a quantization setting enabled? if you have no region selected, it just says "MIDI Defaults," which you should be able to see in the screenshots I attached. It's different depending on whether or not you have a region selected. If that's not it, I'm not sure! Good luck

They do, yes. I keep link engaged generally, and turn it off when necessary. Weird thing was, while the "snapping to DMD" issue was happening (before putting a midi sequence in), the link button was totally unresponsive from the screenset, it would just stay illuminated. It DID work however, when I pressed it from the arrange window piano roll. In retrospect though, I may have had a MIDI region in there by that point and just not realized that was the issue yet.

I've got this new error happening, and it's been happening consistently across projects. Basically, in my normal template I have screenset 2 assigned to a full screen piano roll. Normally when I have an instrument selected, then I hit 2, I'm taken to the full screen piano roll for that instrument. Basic enough. Now- let's say I have one track with whatever sound - it doesn't matter what. Next, I drag a sample to the lower left and do "Drum Machine Designer." In this case, dragging in a kick sample to start a new DMD instrument. NOW- whenever I go to screenset 2, it just snaps back to the DMD that was just created. Because of this, I am unable to use screenset 2 in the way I normally do, to get a zoomed in piano roll for whatever instrument I'm working on. I can't figure this one out, and was wondering if anyone had similar issues or could replicate? I will try to make a screen capture video if this is unclear. thank you *edit* i was able to open the "in window" piano roll (just the- non floating window, built-into the arrange window one) for the DMD, then disable link. after this, it started to work as expected, even after re-enabling link. irritating, but hopefully a consistent workaround *another edit* it appears to work as expected once there is a pattern programmed into the DMD. before adding any midi info, but after adding samples to the DMD, it will do the weird snapping thing I was describing earlier. once a pattern is programmed in, it seems fine... though I will add the reason I found this out is because they still haven't fixed that bug where hitting undo after recording onto a stack/drummer track completely wrecks the session and I had to redo everything 😞

Yeah, I mean, the region muted, so that implies it looped over I guess. Do you know if there are any settings I can change which will prevent this glitch?

Hi, Here are my settings. I didn't explicitly record using overlaps, but I tapped space to stop the recording right near the end of the cycle region, so it may have looped over?

Hello, I'm just stopping by to say I'm having the same issue. I'm not sure what's triggering it, it happens so suddenly. I'm on a new mac studio, monterey 12.5, and logic pro 10.7.5 anybody find a fix? -edit- ok- it seems to happen when I hit undo. one project open. recording midi drums using one of the logic default kits ("above and beyond" in this case). messed up on a part, hit undo to redo it, everything shifted. i think it happens regardless of kit though... further edits- -i didn't import any movie file, and i'm not using any channel strip settings except for stock logic. there are a few 3rd party instruments and plugins

Thank you!! This was driving me nuts, and solved it for me immediately as well.

Hmm... OK. Thanks for the reply. It seems to be working for me now, too. When it wasn't working, I also couldn't see any of my outputs in the dropdown, it just showed "busses" and that's it... hopefully just a one-off bug

Well- it started happening again today. Nevermind. "Solved" still doesn't apply!

hi. I can no longer delve into the guts of project files via the media browser (apple's answer to "import session data," a few releases back). i'm on the latest version of sierra (NOT high sierra) and 10.4.0 can anyone confirm this behavior? edit* I still see the list of project files, but NOTHING happens when I click them. I mean, they highlight, but they don't open that little list of assests like they did prior to 10.4.

An update- Logic 10.4.0 seems to have fixed the problem so far!!! Very happy about this Almost positive it had something to do with the micro lite, but i'm still using it... but for now, "solved" does apply. Since today.

my signature is out of date. -I’d update my sig, but I can’t right now, because I’m reverting back to sierra after high sierra just broke logic. thanks again apple! *edit: I've updated my signature. The problem is still occurring. Not "solved" for me. Wondering if it has anything to do with my MOTU micro lite. It used to work fine, however... probably 2-3 years ago.

Yo, for one, I have TONS of user-made channel strip settings, patches.. etc. The mere fact that these are completely broken is absurdly unacceptable.. Only solution is to go back to sierra and hope (even though they won't) they will "fix it." GM playback has been BROKEN in quicktime since LION. They haven't fixed one of these problems yet.

This is not solved. The problem happens ALL the time. Deleted anything Digi forever ago. Pretty much 2 out of 3 times Logic is opened this error pops up. Been happening for literally years now.

Just chiming in here... I've had this issue on and off for at least a year now. Nothing has fixed it yet. Tried deleting the Digi file from "MIDI Devices," and actually uninstalled Pro Tools completely... it seemed to help briefly, but then the problem started again. It's basically a crapshoot. If I open Logic, there's a random chance it will give me "Error initializing CoreMIDI." The only fix is to quit and reopen Logic until this no longer happens. I should also mention that it's not just an error message, but that it breaks all of my MIDI devices until Logic finally starts normally. With this and the total breaking of the QuickTime GM device back in Lion (yeah, it's been YEARS that GM is messed up, all across Apple - you ever try playing a GM in QT7 now? Hear all those horrible pumping artifacts? WTF?), I'm sad. I've definitely posted this very question multiple times before, but nobody ever knows the answer, and Apple never fixes it. It'll probably come back for you, OP...