Logic Pro 11.2(.2)

[LoveEnigma18]

Hope they have fixed auvalidation

Unfortunately, not fixed. I wonder if that's the new expected behavior.

[aMUSEd]

Hope they have fixed auvalidation

Unfortunately, not fixed. I wonder if that's the new expected behavior.

Yes just checked - still useless - I hope not

[stoopicus]

Anyone else still seeing the bug where resizing (esp autoresizing) plugins permanently lose QWERTY keyboard input after resizing?

I thought it was fixed but it just happened to me again.

[LoveEnigma18]

Anyone else still seeing the bug where resizing (esp autoresizing) plugins permanently lose QWERTY keyboard input after resizing?

I thought it was fixed but it just happened to me again.

Yes, it is happening here as well. I tried with some Arturia and UA plugins and can confirm it. You need to click outside the plugin window for the keyboard input to be working again.

However, it doesn't seem to be happening with all plugins. For example, I tried with Massive X and there's no problem.

It may be a recent bug, as I don't recall this behavior before version 11.2. I hope there will be 11.2.2 that fixes it.

[stoopicus]

This is an old old bug, it existed in 10 for me too IIRC, unfortunately. I quit using Logic for over a year because of it.

[LoveEnigma18]

I guess I don't remember then. Been using Logic Pro since 10.8 only. I am using "CTRL + CMD + P" key command to open plugin search window and it is annoying when the keyboard loses focus with some plugins. I noticed that I don't even need to do any resizing.

Simply opening any Arturia plugin, for example, causes keyboard to lose focus. I wonder if it is a bug at plugin manufacturer end then. It is a weird because sometimes clicking somewhere down on the plugin window works to restore the behavior and once it works it doesn't work only when you click top area of the plugin window. As I mentioned above, this isn't a problem with all plugins, and perhaps that's why I don't remember noticing it before.

[stoopicus]

It’s totally possible it never happened to you before recently. It’s maddening, in part because it doesn’t always happen

[LoveEnigma18]

Yes, maybe it wasn't as noticeable until I paid close attention, especially with some plugins.

[qtheerearranger]

I guess I don't remember then. Been using Logic Pro since 10.8 only. I am using "CTRL + CMD + P" key command to open plugin search window and it is annoying when the keyboard loses focus with some plugins. I noticed that I don't even need to do any resizing.

Simply opening any Arturia plugin, for example, causes keyboard to lose focus. I wonder if it is a bug at plugin manufacturer end then. It is a weird because sometimes clicking somewhere down on the plugin window works to restore the behavior and once it works it doesn't work only when you click top area of the plugin window. As I mentioned above, this isn't a problem with all plugins, and perhaps that's why I don't remember noticing it before.

hello this is an Arturia problem - I would be amazed if they aren't aware of the issue - Arturia plugins have issues closing if you have the wrong window clicked in s1 and cubase as well.

[stoopicus]

No, this is likely the same Logic issue I have been seeing for years now. Plugins that automatically resize simply lose keyboard input permanently.

It doesn’t happen every time for me but it happens regularly.

[Johnnyjohn]

I wonder if they will finally touch the UI once Liquid Glass arrives this fall, it looks so outdated already

[Sascha Franck]

Flashback Audio is such a messed up thing, it's really driving me bonkers. And you can't switch it off without deactivating all other advanced features. Quality assurance my a**.

[releasefromwithin]

Flashback Audio is such a messed up thing, it's really driving me bonkers. And you can't switch it off without deactivating all other advanced features. Quality assurance my a**.

Curious to know what the issue is. I've only used it a few times (and loved having it there), but it seems to me that unless you click on it, you'd never even know it's there.

[Sascha Franck]

Curious to know what the issue is. I've only used it a few times (and loved having it there), but it seems to me that unless you click on it, you'd never even know it's there.

Posted this somewhere else already:

---

I have just tested some things.

As we all (?) know, ever since version 11 Logic has issues to fully register audiofiles peaking below -35dB (and before anyone asks: When using amp sims and backing up your guitar volume pot, its very easy to end up below that).

Ok, I already suspected Flashback Recording to be a not well thought out thing. So I checked some stuff.

If you play at a “normal” recording level and don't record, then use Flashback Recording to get a retroactive recording of what you played, everything works.

But if the level falls below the -35dB peak mentioned above, it doesn't work - even though I can clearly hear the signal when playing.

Maybe this is even intentional, so that Logic needs a certain threshold value to "trigger" Flashback Recording at all, so that nothing is recorded in the background, especially in case nothing is being played, monitored or anything else. Perhaps not a bad thing in itself. But then I damn well want to define this threshold value *myself* and not have some programmers doing so, who are very obviously completely removed from everyday musical DAW work.

Furthermore, I suspect that this “feature”, even if it only appeared with 11.2, was already in preparation in version 11 and could therefore be the reason why the problem of low leveled audio files not being fully “registered” has existed since then.

But you can spin it however you like: what an incredibly miserable affair! Beta testers should be all over it. But either they're not proper testers anymore (not unlikely) or just getting ignored. Pick your poison.

Anyway, users should be able to switch the nonsense off entirely - but it's impossible without losing several other features as well (ever since V 11 you can only switch off the advanced features entirely).

---

Quality assurance has gone outta the window with Logic quite a while ago already, but this is horrendously embarrassing.

[Sampleconstruct]

With the broken AU validation tool it's impossible to remove a plugin from the validation list after de-installing it (it shouldn't be listed in the first place, once the AU component has been deleted). A total rescan of all plugins is the only solution atm.