Sir Hannes

Hahaha, yes I do 😉 It's a matter of brain muscles. I have to follow my guidelines to keep up logic. If I am working on sound and music, my creative flow must go on, and anything which blocks me, reduces my output. If I am doing crazy stuff which no computer nor system nor app is meant to be used, than I agree, I will then overthink and change my approach 😄

[I did not read through the posts, I directly answer to Holger] I agree with you, Holger. And everyone uses LogicPro for a different use case. Maybe I run into a lot of bugs, in my personal opinion, because I work like a chameleon: from sound design (in one track >12 automation tracks for 6-12 plugins, sometimes problems between VI's automation and plugins play a role here - sometimes only 100 audio tracks and already the interaction with Logic feels different) to music composition with many regions with midi notes plus region automation plus track automation. So I think I can understand both sides: If you mix music to picture 8h a day, building on audio tracks, you might see completely different problems. Or, like me, who has different areas every week, who wonders 10 times a week why something isn't logic at all. This is my personal opinion and I don't want to attack nor offend anyone. After spending a lot of time here in this forum, I sometimes get the feeling that people don't take me seriously. And I also admit that with my poor English I can't always explain everything in enough detail. 🙂

Solution/ fix under the premiss that you own any 3rd-party-App which overwrites Logics internal key commands. I use BTT (https://folivora.ai) and the trick is to differentiate left or right modifier as the bug appears only with the left shift-button. I solved it: 1. In LogicPro keep Shift+P 2. in BTT set up two commands: 2a) select differentiate and press left Shift + P => I sent out a short HUD "LogicBug, use right Shift" 2b) select differentiate and press right Shift + P 2c) add to the last the key stroke "Shift+P". At least for now this works and I can continue with my personal layout.

And I just returned from "Guest Mode" with a totally blank LogicPro, reassign that shortcut and experiencing: the same. This is one of the weirdes bugs.

Yes, I would agree its about another utility, although all of these I terminated for testing purposes. I figured out that this is only behaving weird with the plugin windows, but floating windows are not effected. There, the key command works as expected. Additionally these modifier+Y are working, others (below) not: Cmd+Shift+Y Alt+Shift+Y Missbehaving: Shift+Y Ctrl+Shift+Y Will investigated why this happens with plugin windows.

"Y" works as well. Could be a problem with modifier I suggest.

Hm, I tried Shift+Ctrl+P, then Shift+Ctrl+N - these all close all windows. I set it to another letter which was unused: only the selected window was closed. Haha, I am lost 😄 "2" is assigned to nothing, as it was assigned to "Close Window" before, by myself. Before I change key commands I delete the line to not interrupt with multiple commands.

Screensets are "banned" here, I do not use them so I deleted keycommands for them so they do not interact. Also, I would see if it is a screenset as the windows are collapsing and building up again. I checked macOS preferences in each single App where shortcuts are assigned: no Shift + P.

The "one command" is of course: Shift + P for "Close Window" (EDITED) I checked if this is double assigned, but no. I closed all 3rd party (also background) software, but the behavior stays. Weird!

Thanks for confirming, Forum! 🙂 Only one command is listed in the corresponding line in the keyboard window, no touchbar, no MIDI etc. Will investigate further.

Hi, key command "Close window" is on key "2" and closes every selected window. If I re-assign it to "Shift+P" the same entry closes now ALL windows, beside the selected one. Anyone can confirm?

Hi, in the key command menu, there is shortcut "Transpose region/ event by +1 half-tone or automation by +1 step" (or similar). My Synth-Lane is on +5% and I want to replace this mouse fiddlings to get it to zero, it changes the sound still and this behavior I experience a lot. I searched for key commands to decrease "steps" and set it to 1/64 and later to a sample. But this doesn't change the behavior. Neither 1/64 nor sample brings mir close to zero, they all stay within +/- 2 increments. Is the labelling "step" misleading here? Note: In the German version they use Schritt and Schrittweite, I translate this to Step and Stepwidth, but may vary in the english version. 🙂

As I just read about this feature and @des99 gave me the ultimate hint, I will report it now. Thanks for confirming!

Looking at the waveform it could be a voice, then true, no workaround. If it is a atmo, and thinking on surround/ ambisonics, these are often atmos, then it might be a workaround. 🙂

First I clarify, I am not searching for help, my intention posting this was to share with @Frankenhaus that there are many issues going on, and he and others might get too. I hope that he/ they then feels not alone with maybe anger about Logic. Screenshot is from yesterday, upper lane shows the actual number. A video would show, that the 17% is the value where the playhead is. If it comes closer to a ramp all 17% numbers changes parallel/ together. Also look at the first automation point: it should be a 0, right? 2nd lane the same: the automation point at the ramp should be 0, right? Hope I could translate it now better. 🙂