craike

@David Nahmani I get what you're saying, and I understand the behavior now, but even at 40 or 60 instead of 50 things go really wonky instead of "swung." It's probably a case of my specific workflow being affected and not many other people's, and ultimately it's a relatively minor issue. Thank you, David, for your tireless dedication to this community. I always know I can get a good answer when I have a question!

I'll contact Apple about this directly, too, but I just also want to state here in case someone else comes across this someday: understanding that the behavior changed doesn't help me (but thank you @David Nahmani for pointing me to this thread!). The new algorithm, at least for me, is plain bad. It doesn't behave as expected at all, or produce remotely usable results, even understanding that it has changed. It's not something I would say I use regularly, but when I did I literally never had issues in years of using it before. I can't get it to do anything useful now. Moreover, the only reference to the change that I can find at all in the release notes is "Swing settings are now displayed consistently between the region inspectors, Piano Roll and Step Sequencer." I guess if anyone has tips on how to get this new approach to behave well, I'd be glad for them, but this honestly just seems like a bad UX move all around.

Has anyone else been having issues with quantization in 10.7.8? The algorithm is off. I thought I was going crazy for a few weeks until I saw someone else posted a video illustrating the issue on Reddit. I tried to search to see if someone had posted about it here already, but I don't see anything. Here's the video:

I very specifically have it set to only record enable the selected track and aggressively un-select anything that accidentally gets selected, but I wonder if this code limitation is what it's glitching and interacting with. If nothing else, polanoid, you may have made an Apple Engineer very happy 🙂

This is definitely a bug. In the process of creating a sample project file to upload, I was dragging tracks around. Moving tracks above the 35th "row"/position results in them functioning normally, moving tracks below the 35th position results in them exhibiting the behavior I describe above. So far, it doesn't otherwise seem matter which tracks are below or above the MIDI tracks, or whether or not any of those tracks are muted. Bizarre, but I have a workaround for the time being I guess.

I've had an increasingly common issue that I don't see described in past posts, so I at least want to create a post to document the issue. Given the numerous problems I've had with CoreAudio on my M1 Air, I'm inclined to think it's a bug, but I'm hoping maybe I am missing an obvious setting somewhere. ---- Hardware: 2020 M1 MacBook Air MacOS: 12.5.1 Logic: 10.7.6 (running in Rosetta) The problem is that, often abruptly, I can't hear input monitoring for any software instruments whether or not I am recording. This is true whether I'm using musical typing or an external MIDI controller. Things that work while this is happening: - MIDI is registered properly (channel, velocity, note) from all control surfaces in realtime via MIDI input monitoring - MIDI is actually recorded by Logic, and is audible via software instruments when that portion is played back after recording - Audio-in tracks via my audio interface (guitar/vocals) appear unaffected, and both monitor and record properly Things I have tried that do not resolve the issue: - turning Software Monitoring on or off - Record-Enabling a track and/or turning off Record Enabling - changing the channel of MIDI inputs - turning Low Latency mode on or off - selecting "Reset all MIDI Drivers" from the General > MIDI > General pane - restarting Logic - running Logic natively rather than in Rosetta I can resolve the issue by creating a new Logic file, but, if I import the "silenced" software instrument tracks into the new file, they are still still silenced in the new file, despite other software tracks in the file working as intended. So my projects are essentially stopped in their tracks.

Thanks, David! I came across that post of yours in my searching, but hoped there was a simpler way. Since it seems there's not, I very much appreciate you creating it.

I've done lots of searching and can't find an answer to this. Here is what happens now: 1. I select two channel strips, one muted, one not muted 2. I press "M" (which is labeled "Toggle Channel Trip Mute") 3. The muted channel strip unmutes, unmuted channel strip stays unmuted Here is what I would like to have happen: 1. I select two channel strips, one muted, one not muted 2. I press "M" 3. The muted channel strip unmutes, unmuted channel strip mutes 4. As I keep pressing "M," step 3 repeats according to each track's respective mute state The same thing happens for soloed tracks. Is there any way to make a key command a true toggle, that simply inverts the current state across tracks, regardless of their current state?