Logic Pro 11.2(.2)

[Sascha Franck]

Files peaking below -35dB still not "registered" properly. Time for Apple to just f*** off, seriously.

[Ploki]

Files peaking below -35dB still not "registered" properly. Time for Apple to just f*** off, seriously.

You mean the truncated waveform render engine from literally logic5 or is something else fundamental broken that i missed

[Sascha Franck]

You mean the truncated waveform render engine from literally logic5 or is something else fundamental broken that i missed

When you record something and the peak of the file is below -35dB and then try to, say, normalize it, Logic will tell you it contains absolute silence. Waveform zoom in the arrange won't work on those files, either.
And before you ask: When using amp sims and the volume pot of your guitar (pretty typical thing), it's easy to end up with files peaking so low.

This is very very likely related to flashback recording (even if the bug appeared earlier, but I'd bet that they were already preparing flashback recording), which has a hidden threshold built in. IOW, when you play back something and have a record enabled audio track, flashback recording needs more than -35dB on the input to work at all. This has really thrown me at first, as I was sitting there with my guitar noodling around and the volume dialed back quite a bit - as a result, flashback recording didn't work, even if it did before.

So, there's a number of things that would need to be adressed:

- All recorded audio files need to be treated properly. It's totally inacceptable for a flagship DAW to ignore around 2/3 of the dynamic bandwith of 24bit recordings in some situations. No excuses for that.

- The threshold for flashback recording to work needs to be user definable.

- And talking about flashback recording, there needs to be an option to switch it off entirely. Sometimes it seems to cause hickups (wenn you noodle around over a cycle for a long time).

These things are known to Apple since a long time and they don't give a shit.

[Ploki]

You mean the truncated waveform render engine from literally logic5 or is something else fundamental broken that i missed

When you record something and the peak of the file is below -35dB and then try to, say, normalize it, Logic will tell you it contains absolute silence. Waveform zoom in the arrange won't work on those files, either.
And before you ask: When using amp sims and the volume pot of your guitar (pretty typical thing), it's easy to end up with files peaking so low.

This is very very likely related to flashback recording (even if the bug appeared earlier, but I'd bet that they were already preparing flashback recording), which has a hidden threshold built in. IOW, when you play back something and have a record enabled audio track, flashback recording needs more than -35dB on the input to work at all. This has really thrown me at first, as I was sitting there with my guitar noodling around and the volume dialed back quite a bit - as a result, flashback recording didn't work, even if it did before.

So, there's a number of things that would need to be adressed:

- All recorded audio files need to be treated properly. It's totally inacceptable for a flagship DAW to ignore around 2/3 of the dynamic bandwith of 24bit recordings in some situations. No excuses for that.

- The threshold for flashback recording to work needs to be user definable.

- And talking about flashback recording, there needs to be an option to switch it off entirely. Sometimes it seems to cause hickups (wenn you noodle around over a cycle for a long time).

These things are known to Apple since a long time and they don't give a shit.

I wasn't intending to bitch about why you record low peak, it's a legitimate scenario. i.e., you're recording a very dynamic singer or video production tracks is usually lowpeak often as well.

I didn't know about this bug, thanks

[andypryce]

This is miserable on another level

Screenshot 2026-01-29 at 02.05.15.png

[nightjar]

This is miserable on another level

Screenshot 2026-01-29 at 02.05.15.png

These things all look great to me!

[trancema]

Oh myyy. This update is ridiculous.
Suddenly Studio (One) Pro 8 update doesn't look so bad anymore.
All major DAWs failed with latest major updates in past year, except Bitwig 6, but that one is still in Beta.

[Sascha Franck]

I wasn't intending to bitch about why you record low peak,

Didn't mean to intend that. It's just that plenty of folks seem to wonder why someone would end up with recording levels that low. And it's defenitely not the norm, either (especially as a Logic user, I try to go for some pretty high recording levels as the arrange window's waveform display is just horrible - with the zoom function not helping much).

Which is also why most people don't run into this bug and sometimes even keep telling me it wouldn't be all that bad.

But in this case, it's not about rare occasions or whatever - but simply about just how lousily they have implemented this very threshold thing. It's not communicated/mentioned, it's not transparent at all, it's not user definable and you can't switch it off in case it's getting in your way. And it makes Logic look as if it's seriously broken in some situations (unless you invest some time to find out what's going on under the hood). A lose-lose situation.

[Papuzzo]

It seems we still have not reached perfection in the DAW world. I am beginning to wonder if perfection cannot exist in an imperfect world filled with imperfect people all demanding custom solutions to their needs.

[jules99]

Almost every DAW release these days is accompanied by a choir of disappointed users. I can't remember a single release in the last few years where the majority was positive.

My guess is that due to the competitiveness of the DAW world, we're constantly looking left and right and feel envious how DAW XYZ has that and our favorite DAW doesn't, but DAW makers themselves tread carefully.

Because one example of DAW makers rushing to implement a feature that they thought users were desperately asking for is clip launchers. Because of Ableton's success, Logic, Studio One, Tracktion Waveform, they all spend precious development time and rushed to implement these, only for many users to rarely use them.

[syntonica]

Don't forget DP! Lol

I wish DAW makers would focus less on new features (AI junk, specifically) and focus more on bug fixes and usability. And in that order.

[Ploki]

This is miserable on another level

Screenshot 2026-01-29 at 02.05.15.png

These things all look great to me!

What everyone else wanted was ARA though, not another f**king AI player.

[Sascha Franck]

What everyone else wanted was ARA though, not another f**king AI player.

This.
But let's also not forget an audio editor that would deserve to finally not look as if it was still 1998 anymore.
Or how about improved stretching and pitch shifting?
Or what about some more intense bug fixing?

But hey, we have Chord ID now. Because it's so great to drag some pre-fabricated Splice loops into Logic and add some semi-pre-fabricated synth playing to them. Possibly so we can compete with Suno.

[LoveEnigma18]

I wonder if updates will be faster than typical 6-month cycle considering there's a subscription model now.

I am already waiting for Logic Pro 12.1 with the same hopes.

[The irony of my case is I moved from FL Studio to Logic Pro (for various reasons) when FL Studio improved its Browser significantly and I ended up desiring Browser updates in Logic Pro.]

[nightjar]

What everyone else wanted was ARA though, not another f**king AI player.

AI features can be incredibly useful for many people. Seeing them rapidly evolve is to be expected. You might as well shout at the wind.

ARA is fundamentally at odds with how Apple has decided to design the memory handling of its ARM apps and 3rd party code. So it might never happen the way many want.

Instead, I would hope for Apple to develop native functions within Logic that lessen the desire for 3rd party ARA plugins..

Just being real here.