alexandrehirlinger

Do you have any more ideas David? I'm truly at a loss here and it's making Logic basically useless for me

That's fine! I welcome all suggestions. If you have any other ideas, I'm all ears!

Most of the time, no. Under very rare circumstances I might, but 95% of the time I am only working in only one project at a time. The issue is definitely happening when I am only in one project.

It is happening across all projects, empty, new or old. It appears to be system-wide. When I first boot up Logic, it behaves as you would expect - it is including all edits in the undo history. Then after I'm working in any given project for a while, it randomly decides to drop all editing undo steps. This is when I start hitting command-Z expecting it to undo the last edit I made (i.e. trimming, moving, or copying a region), but instead, it starts executing the most recent plugin/mixer undo's. The only way to get Logic to behave as expected again is to quit and restart. I've been dealing with this issue for about a year, and I still haven't pinpointed any specific action or move that I regularly make that triggers Logic to start behaving incorrectly. It appears to be random. I have also been dealing with this issue through using Logic 14.6, 15.1, and 16.2. So it doesn't appear to be going away with updates...

Sorry, I think I might be explaining the issue wrong. The problem is not the inclusion of mixer undo steps. Instead, the issue is that Logic will randomly stop including actual editing undo steps (i.e. flatting of comp tracks, trimming of regions, copying/pasting of regions, etc.) The result is that I will make an edit (i.e. flatten a comp track, or move a region), and when I go to undo that edit, it skips the actual edit undo and will just perform an undo action from the last mixer/plugin undo step in the undo history instead. If I don't have mixer/plugin undo steps enabled, Logic just won't do anything.

Thanks for the recommendation, David! I usually work with Include Mixer Undo Steps enabled. However, I have tried deselecting and then reselecting that, with no luck.

I have had this problem for the last year now (around since when 10.15.1 came out) and it is the most frustrating bug I've ever experienced. Logic will randomly stop recalling editing undos. Plugin and mixer undo steps remain intact, but the editing undo's disappear. This bug has gotten so bad that I actually switched away from using Logic as my main DAW, as I would have to restart it up to 20 times a day for the bug to go away. I still have to use Logic occasionally, so I would love some help on getting this fixed as it drives me absolutely insane. I have done some digging on the internet and it seems like folks are having similar issues, but have yet to find a concrete solution. Any help would be GREATLY appreciated. Example: I might be working on an edit, and then if I make a mistake, I go to undo that edit, but it starts soloing the last thing I had soloed, or moving faders, or changing plugin parameters... Since logic doesn't do automatic backups (only every time you hit Cmnd-S, or if it crashes you can revert to auto backup), this can be catastrophic. For example, many times I might do something like flatten a comp track, but I didn't realize I was still on the main track alternative (aka I didn't have a duplicate of the original comp track on a different track alternative). I go to undo the flatten, but logic has stopped remembering undo's, so I just essentially deleted all the extra takes. The takes obviously still exist, but I have to comb through the audio bin of all audio files from the project and it has taken me hours to rebuild that one comp track. This has happened multiple times at this point, as well as in other editing scenarios. For this reason, I basically have to quit and restart logic any time the bug occurs as it can be disastrous if something goes wrong. However, it is getting ridiculous to have to do this so many times and it is quite unprofessional if there are clients in the room with me.

My exact thought, Steve. I've used Pro Tools off and on, with Logic being my main DAW, and I love PT's ability to autobackup. Bummed there isn't a version in logic. I save pretty often, but I don't think to do it after every take.

Can you give a specific example? For example, if you start a new empty project, create 10 audio tracks, and try to navigate the Mixer with the arrow keys in Tracks view, does it switch to All? Can't seem to emulate it in empty projects, but it's happening in all my projects with anything in them... Weird. Basically I like to have a gain plugin at the bottom of every single track so that I can often null the volume faders for finer resolution. I like keeping one gain plugin open in multi-mode so that when I switch channel strips, it automatically updates and I can have the trim of that channel within reach at all times. When I try and navigate between channel strips using the arrow keys, it seems to snap my mixer mode to "All" almost every time. If I manually move it back to "Tracks" view, it might work for about 15-20 seconds, but then it starts switching me back to "All" view. I could be wrong, but I use a lot of summing stacks, and the problem seems more intense when navigating over track/summing stacks to get to other channel strips.

Thanks for the response! Do you happen to know if there is any way of doing this without manually saving the project? Aka is there a way of telling logic to great auto backups that actually automatically happen? Seems like this behavior is based only on manual saves and I think that the problem was that I hadn't manually saved in about 30 minutes, so the revert didn't include the take folders. I changed that number to "100 auto backups" but that doesn't help me too much.

Ahhhh. Thought it fixed my issue, but I was incorrect. Any time I use my arrow keys to navigate channel strips in the mixer, it snaps to the "ALL" view. Any advice would be welcomed if anyone has any!

I know this is very old, and I'm not sure why I'm having this problem because I don't believe that I am using any multi-output instruments... But I couldn't use my arrows to navigate in my mixer without it taking me to the "ALL" view and it was driving me crazy. This just fixed that problem, so THANK YOU for the info!!!

Hello LPXHelp crew! Logic has been a bit buggy for me recently, and I will reach a point when I'm working on a project and it will randomly stop including actions in the undo history. I'm fairly reckless with my moves and then rely on the undo history. I'd love any explanation as to how to fix this! My main question is that, due to this problem, I accidentally deleted one of two take folder regions of a multi-miced acoustic guitar. I still have the take folder from the U87 mic, but lost the take folder from the 451. All of the audio files are still inside the project but they are in the audio bin, and sorting through which takes are which would be a NIGHTMARE. Is there a quick way of recovering this? I have no idea how I would tell which audio files from the bin would match the appropriate U87 takes. Or is there even any way of getting the takes back into a take folder so that I can actually edit the two mics as a time-locked group? Thanks!

Thanks for your reply David! You've helped me on a number of topics on here! REW is used in some professional circumstances to correct the room's EQ, but most people use it to get an accurate view of their room's coloration on the sound. This is generally useful information to have as it allows you to find the best listening position, monitor positions, acoustic treatment, and acoustic treatment positions while having verifiable results. This allows you to hopefully properly treat the main three problems with any room (frequency response, decay time, and RT60) using the best analogue, tried and true methods possible. Personally, from here, I like to use sonarworks to gently smooth out the phase issues between the left and right speaker as well as gently smooth out the frequency spectrum, but this is personal taste. I believe that it gives a near-flat and somewhat unifying listening experience across all control rooms, allows mixes to translate better; however I realize this is a personal opinion, and that many prefer to mix on non EQ-corrected systems. I realize that our ears are colored so perfect neutrality is impossible when it comes to frequency response, but I believe that things like sonarworks give somewhat of a unifying and trustworthy experience when moving from room to room. Also, to be clear, the makers of sonarworks (as well as hopefully all other room correction services) state that room correction should be one of the last pieces to the puzzle after great monitoring, positioning and room treatment. They do not claim it to be a cure-all. It's also important to note that the only real cure for room nodes and decay time is acoustic treatment - EQ correction obviously only operates on the frequency domain and not the time domain. -alex

Hey Mark! I apologize, I must have somehow turned off notifications for my posts on here, so I missed all of these replies... Although I wish I would have seen your reply earlier, because I have gone down quite the rabbit hold of room setup. I've spent almost the entire last two weeks solely devoting my time to it. I'm actually in the middle of creating a comprehensive room setup guide which will include everything from taking measurements with REW, to speaker placement, to phase aligning a sub, to acoustic treatment placement, etc. I'm mainly creating this as a guide for myself, but I plan on forwarding it along to anyone whom it could help. I'll be sure to forward it to this thread and maybe it will help you in some way. If you're already up and running then it probably won't help you too much, but who knows. (Also a lot of it is copy pasted, paraphrased, or summarized versions of things I've found on the web, so I in no way claim for it to be my own work, or be an expert on the topic.) From my reading, video watching and discussions directly with GIK acoustics, I've found the following to be true in regards to my previous questions: Single mic measurements are best for calculating things like time alignment, checking polarity, and room setup (this being the only one that I claimed to have tried). You want to use spacial averaging when getting results for corrective room EQ. The reason for this is that with SPM (Single point method), the slightest change of the microphone impacts the readings in dramatic and unrepeatable ways (usually in the high end). This makes the results unverifiable - the reason being that we don't hear sound at a single point the way that a calibrated microphone does. However, it still gives us a pretty good idea of where things are sitting in the frequency spectrum, which allows us to make general decisions about room setup without getting into the nitty gritty. It also allows us to do time alignment and check polarity since these are 1 or 0 operations that are either right or wrong. However, since we don't hear sound like a single mic in one position, you want to use the MMM (Moving mic method) in order to get an average of the space around the listening position. This allows us to get an idea of how our ears are actually perceiving the sound to make appropriate EQ moves. This can also be done by taking a number of SPM's around the listening position and averaging them, but the MMM using spacial averaging is a lot more time efficient. I also agree with you that using the RTA method with pink noise playing is best to get an idea for placement of the monitors and listening position. This allows you to get real time feedback. I would then begin to take a variety of SPM's in and around the listening position to get an idea for how things are sitting and tweak from there. Generally, its fine to measure Left alone, Right alone, Sub alone, all combined. That's plenty to get an idea of the room. Thanks for your help. I hope this helped in some way. I'll post that comprehensive guide as soon as it's finished. -alex