Logic Pro Help

GrabtharsHammer wrote:

Sorry, but I am not impressed. People are super excited about a slight improvement of their projects‘ load times?
The last 1,5 years have been pretty boring as a Logic user.

there have been just enough improvements and enhancements with each point update to make it worthwhile. what is it you're expecting? perhaps 10.15 will do it for you...

GrabtharsHammer wrote:

Sorry, but I am not impressed. People are super excited about a slight improvement of their projects‘ load times?
The last 1,5 years have been pretty boring as a Logic user.

Slight improvements?
I would say massive improvement concerning loading times.
Did you try it with a big template?

[quote="Ninecows"]High Sierra as far as I can see. My 2011 iMac just made it.[/quote]

Same here. Had 10.4.4 running well on Sierra but everything is bench marking the same using HS.

This seems a good update, load time is soooo much better on larger projects.

AND, i can flick through plugins like Chromaverb during playback without it causing dropouts on my old Mac Pro - so something behind the scenes is improved in general CPU usage, whatever fine margins they've made up it's helped... yay!

rico wrote:

KikkoAndMoonman wrote:

Can't seem to get the update prompt in App Store for some reason.

Also, will the update's section about improved multi-core support for up to 56 cores have a good effect on 12-core systems?

Go to store menu and click reload page.

Thanks

I'm trying to think of the last time I actually paid for an update... hmmmm... I know it was before drummer... and alchemy... and the total overalls of the effects... addition of more drummers... hmmm... I'm good...

Just a quick read of the fixes and optimizations, it looks like they really combed through the code at a gut level.

jonljacobi wrote:

Just a quick read of the fixes and optimizations, it looks like they really combed through the code at a gut level.

Yeah, I was thinking this too, they really did some deep diving with it

Is anyone else getting some graphical oddities with this update? Icons in the mixer seem to lack anti-aliasing, and some text is blurred.




Note the crisp instrument names under the blurry track names...


I'm wondering if this is how they've "optimized" the mixer window behaviour.

JamesK wrote:

So for those who don't buy a new mammoth mac you get a redesigned de esser and the ability to drag multiple loops? Meh
10.4.4 will suffice!

I actually consider the updated DeEsser2 one of the major improvements ever to Logic. Not for me directly, but I'll benefit when I receive better vocal mixes.

Excessive sibilance is a ubiquitous problem and many people rely on stock plug-ins. Some have no clue how to dial in a de-esser, and getting a forced narrow band de-esser (like the old one) to work well without lisping artifacts is an uphill battle.

Logic's de-esser FINALLY got a shelving filter option and a GR cap, it'll do wonders for vocals everywhere.

I imagine something like the classic Waves Renaissance De-Esser default settings (more or less) should do the trick.

Freq = 5500 Hz
Max reduction = 6 dB
Mode = Absolute
Range = Split
Filter = Shelf

Set threshold based on chorus or loudest part. Make sure only sibilants or similar trigger, no sustained notes/air must trigger it. Off you go.

I'll have to play around with the Relative mode, but I imagine it's hit & miss like most automatic features.

anyone has a screenshot of the desser? i only have mobile internet in the studio and cant update it.

Sure, hang on.



DeEsser 2 parameters
Detection meter: Shows the input signal level. The maximum level is shown in the numerical display above the meter. Click to reset. Behavior of the meter changes in Absolute or Relative mode. See Mode pop-up menu description.

Detection meter slider: Drag to set the Threshold above which gain reduction is applied.

Reduction meter: Shows the amount of gain reduction applied. The maximum level is shown in the numerical display above the meter. Click to reset.

Reduction meter slider: Drag to set the Maximum Reduction level.

Threshold knob and field: Set the Threshold above which gain reduction is applied.[Holger's note: you can also grab the meter indicator, which is nice

Max Reduction knob and field: Set the amount of gain reduction applied.[Holger's note: you can also grab the meter indicator, which is nice

Frequency knob and field: Set the center frequency of the detection filter.

Mode pop-up menu: Choose Relative or Absolute mode. Relative is the default and works with low and high energy signals. [I'm surprised they went with Relative as the default, that might not be a good choice as it could result in over-de-essing/lisping in some cases and it's less predictable/controllable...]

Relative: In this mode the energy level of the band/high passed signal (determined by the Frequency and Filter settings) is compared with the full bandwidth energy level of the incoming signal. The Threshold parameter value determines the amplification of the filtered signal energy (because the energy of the filtered signal will always be lower than the full bandwidth signal). When the amplified signal is lower than the full bandwidth signal, the Detection meter shows a blue meter below the Threshold value and no processing occurs. When the amplified signal surpasses the full bandwidth level, the Detection meter shows a yellow meter above the Threshold value and processing takes place.

Absolute: The Detection level meter shows the energy of the incoming signal (band/high passed as set with the Frequency and the Filter settings). When the energy level surpasses the Threshold parameter value the meter display switches from blue (not processed) to yellow (processed). Low energy signals can only be processed in Absolute mode if the Threshold parameter is set to a very low value.

Range buttons: Set the filter frequency range. Split affects signals tightly centered around the set Frequency value. Wide affects a broader spectrum around the set Frequency value.

Filter buttons: Choose a highpass shelving or peak filter shape.

Filter Solo button: Turn on to hear the filtered signal in isolation. This is useful for setting Threshold and Frequency values.

this window (arrow) has been white with WHITE TEXT (ie, useless) since dark mode was first introduced; good to see it (finally) fixed!

[quote="jmmusic"]I'm on Mojave and I can't upgrade...I tried in System Prefs and in the App Store - I'm not given the option in either. Ideas?[/quote]

Same here - last time it took a couple of weeks for Australian users to get access to the LPX 10.4.4 upgrade - maybe this is the 'new norm'?

rz

Whoops, I spoke too soon - downloaded the LPX 10.4.5 update now.

rz

Not sure what I think about the optimized plugin loading. When I load my main template, I have to wait for plugins to initialize. When I turn this feature off, my template loads at the usual time (<1 minute). And the instruments are all there for me to be inspired.

rzzzy1 wrote:

jmmusic wrote:

I'm on Mojave and I can't upgrade...I tried in System Prefs and in the App Store - I'm not given the option in either. Ideas?

Same here - last time it took a couple of weeks for Australian users to get access to the LPX 10.4.4 upgrade - maybe this is the 'new norm'?

rz

perhaps it IS just region, and you'll get the update soon. either way, it will ONLY show up in the app store; only system updates (now) show up in system preferences.

have you tried reloading the app store?

GrabtharsHammer wrote:

People are super excited about a slight improvement of their projects‘ load times?

I've gotten really tired of waiting 3 minutes for Logic to start a basic template with one track. Any improvement is welcome as far as I'm concerned.

Anyone having trouble with beat mapping now? It's not behaving itself. As in, I can't use it....

I don't think they could get the type of performance improvement they're claiming by rendering the fonts differently or using bitmaps. More likely the interaction between the mixer and the environment, but who knows what kind of garbage code was in place. Given the speed of the computer I run it on, I've always thought Logic lacked snap. Hopefully, this will help.

And monkeying around in the places they're talking about is likely to introduce a few bugs, in re the beat mapping message. The good thing is, if you cleaned up the code and commented it properly, it should be much easier to fix stuff.

jmmusic wrote:

Anyone having trouble with beat mapping now? It's not behaving itself. As in, I can't use it....

Did it ever behave well in LPX? Not to my knowledge. One of the things seriously broken.