Logic Pro 11.2(.2)

[LoveEnigma18]

What I was afraid of! Thank you both for confirming. I appreciate it.

At least good to know one step bigger is doable, and it would still offer increased screen real estate I am after (than my current 2560 x 1440 monitor).

The only worry I have is if I end up using 2560 x 1440 with 32" 4K monitor, I won't see any benefit of real estate and I guess I won't gain anything in terms of visual improvement compared to my existing 2560 x 1440 monitor, which is very comfortable for me and the type of visual comfort I am aiming for with 32" 4K with added screen real estate.

Does 3008x1692 look blurry or the quality is still as good as native resolution?

At 2560x1440 I see 25 horizontal tracks at default size and 33 tracks in the mixer.

At 3008x1692, 30.5 and 40.

At 3840x2160, 40 and 52.5.

If you use it at 2560x1440 I don't think you would gain real estate but you would gain definition. If I put my 4K at 1920x1080 everything is way more define than on a real 1920x1080. It still feel a 4k monitor... it's just that everything is bigger...

But if you are coming from a 2560x1440 I don't know if the improvement worth the money.

Does 3008x1692 look blurry or the quality is still as good as native resolution?

It is still as good. No matter the resolution you chose it will looks sharp. Even at 1504 x 846. It is just the scaling that changes.

Excellent information. Thank you so much. You figured out what I had in my mind and have been extremely helpful.

One of the reasons of having added vertical resolution/screen real estate over 1440p is that we now have "Long faders" option in the Logic Pro's Mixer, which causes Mixer height to increase and we lose a couple of tracks view. Not a big thing, but one nice to have reason for more screen real estate.

Looks like 32" 4K would provide some options that I currently miss, so while not necessary, based on this discussion it is clear that "32 inch 4K" would indeed be the size and resolution for my next monitor. It's been 8 years since I am using my current 27 inch 1440p monitor, so I may upgrade sooner or later.

If you don't mind asking, what is your Mac model?

[Jolaff]

If you don't mind asking, what is your Mac model?

I tested it with an M1 Mac Mini

[Jolaff]

This is with the long fader...

[LoveEnigma18]

Thank you once again for your time and help. Screenshots are very helpful. The last screenshot at native resolution looks barely useable.

[aMUSEd]

So why is ARA still broken in Logic? I don't understand it - it works in other hosts on Apple Silicon

[CinningBao]

Because the OG Logic engine was a MIDI thing, then they added an audio transport layer to it. Keeping that audio layer slightly distant from the core engine means when plugins crash, the whole program doesn't. So it's a stability thing.

ARA plugins have a closer relationship to the core audio engine than most 'normal' plugins (processing audio block by block), and the distance Apple have kept between the core audio engine and plugin layer means that distance can't be bridged, as it were.

Honestly, without a complete rewrite of the Logic audio engine, it will never change.

I will be corrected if any of that was wrong

[Ploki]

Because the OG Logic engine was a MIDI thing, then they added an audio transport layer to it. Keeping that audio layer slightly distant from the core engine means when plugins crash, the whole program doesn't. So it's a stability thing.

ARA plugins have a closer relationship to the core audio engine than most 'normal' plugins (processing audio block by block), and the distance Apple have kept between the core audio engine and plugin layer means that distance can't be bridged, as it were.

Honestly, without a complete rewrite of the Logic audio engine, it will never change.

I will be corrected if any of that was wrong

It works via rosetta and on intels. Plugin process is separated only for Apple Silicon architecture, and yes that’s why it’s broken.

So you’re partially right.
But it’s not due to OG logic being midi only, it’s because they added this separate process when migrating to silicon - i assume initially because that’s the only way to run Logic itself native while having mixed architecture plugins (as logic opens a separate rosetta process for non-native plugins). This is unique to logic, other daws are either native or Rosetta and dont do mixed architecture plugins

So why is ARA still broken in Logic? I don't understand it - it works in other hosts on Apple Silicon

TLDR, other hosts (and Logic intel) don’t run plugins in a separate process.

[surferman]

The stem splitter works great. I too have a bunch of old cassette recordings of my band. Been using Izotope RX and Ozone to make them sound better but this splitter is so much better than RX that there is no comparison.
We had covered Teacher but the guitarist played completely clean. Sounded fine but we always talked later about wishing he would have added a little dirt. I was able to use stem splitter and add a distortion pedal using amplitude. Really amazing to be able to do this to a previously recorded song.
Will have to revisit some older tunes!

[medienhexer]

Because the OG Logic engine was a MIDI thing, then they added an audio transport layer to it. Keeping that audio layer slightly distant from the core engine means when plugins crash, the whole program doesn't. So it's a stability thing.

ARA plugins have a closer relationship to the core audio engine than most 'normal' plugins (processing audio block by block), and the distance Apple have kept between the core audio engine and plugin layer means that distance can't be bridged, as it were.

Honestly, without a complete rewrite of the Logic audio engine, it will never change.

I will be corrected if any of that was wrong

Logic has supported audio tracks since the mid 90s. There have been several very dramatic rewrites of the audio engine. Remember, it was Windows and Mac OS until 2001 (intel and PPC, classic OS and OSX, Win9x and Win NT). It was able to serve as frontend for ProTools TDM and use the DSP based audio engine for plugins and summing. It used to offer grid computing via other ethernet connected Macs. I don‘t remember when the engine wasn‘t sample accurate. I don‘t think the fact that MIDI was first has anything to do with ARA.

The current way AU plugins are processed relies on an audio processing server outside the core application. A sandbox mechanism. That‘s one of the reasons why Logic doesn‘t get crashed by plugins anymore. And it IS the result of another major rewrite. It used to be inside Logic and it did crash back then. Which is one of the reasons for requiring plugin scanning.

So ARA has to work from the sandbox. And since ARA tries to grab the audio from the entire track and not just an audio stream during real time playback, it could be running into the security features which protect you from malware trying to access data from other apps or storage locations.

[aMUSEd]

When did they dumb down the AU validation tool? It used to give very useful verbose reports of incompatibilities- now if you rescan a failed plugin it just runs for a few seconds then says 'Done' - even if it is not compatible it doesn't even say it has failed let alone why

[qtheerearranger]

When did they dumb down the AU validation tool? It used to give very useful verbose reports of incompatibilities- now if you rescan a failed plugin it just runs for a few seconds then says 'Done' - even if it is not compatible it doesn't even say it has failed let alone why

this has to be a bug im guessing

[LoveEnigma18]

Based on history, I think we can expect a bugfix (11.2.1 update) this month.

[aMUSEd]

When did they dumb down the AU validation tool? It used to give very useful verbose reports of incompatibilities- now if you rescan a failed plugin it just runs for a few seconds then says 'Done' - even if it is not compatible it doesn't even say it has failed let alone why

this has to be a bug im guessing

Yeah looks like it - I think the validation tool is broken in this release

[LoveEnigma18]

11.2.1 is out. Stability and bug fixes only.

https://support.apple.com/en-us/109503

[aMUSEd]

Hope they have fixed auvalidation