What's new

Logic Pro 10.4.5 Update

Dewdman42

Senior Member
What was wrong with 10.4.3? Not that I'm a power user, but I'm still on it and I've noticed more bugs in previous versions. Should I upgrade to 10.4.4? This latest update sounds great, but I'm nervous as I'm on a Hackintosh and the last time I tried to install High Sierra its performance was abysmal.
I know someone else that upgraded their hackintosh to Mojave and saw real performance improvements, but make sure you have a metal card.
 

prodigalson

Senior Member
Anyone else having issues with the playhead becoming disabled after a period of time? It works normally on opening but after some time it suddenly become inactive. scrolling back and forth works but the playhead won't move and its not possible to click on the timeline to move it.

To me, it's kind of a deal breaker bug!
 

5Lives

Senior Member
Disabled tracks was one of the main reasons I bought the Cubase 10 cross grade a while back but this update really is making me consider going back to Logic. Personally find it much cleaner and more streamlined - and I like the articulations system better too. Never crashes on me which is more than I can say with Cubase. Hopefully Apple adds folder track nesting and multiple CC edit lanes soon.
 

jonathanwright

Senior Member
After working with it for a short while, I’ve found that the best approach with disabled tracks is to use them in tandem with automatic loading of tracks.

So I’ve manually disabled all of the tracks in my template (alt on/off button), to prevent accidentally enabling tracks by selecting them when I load up a new project.

I’ve assigned a key command to switch tracks on, to save having to navigate to the track header every time.

Then when I load the project later, Logic can still do its automatic thing.
 
Last edited:

Gaffable

New Member
I’ve assigned a key command to switch tracks on, to save having to navigate to the track header every time.
Just curious - which key command are you using? In Logic 10.4.5, the "Toggle Track On" command (Option-M) does not work properly. It only turns off tracks. It doesn't turn them on.
 

jonathanwright

Senior Member
Yep, that's the same command I'm using, I've set it to '+' on the number keypad.

I still need to alt-click the on/off button to disable a track, I can only think the key command doesn't switch off a track because the user may only want to bypass the CPU, rather than unload everything.

Hopefully they'll expand on the key commands in subsequent updates. As it stands, any tracks I don't need will be disabled on the next project load anyway.
 

Alex Fraser

Senior Member
After working with it for a short while, I’ve found that the best approach with disabled tracks is to use them in tandem with automatic loading of tracks.

So I’ve manually disabled all of the tracks in my template (alt on/off button), to prevent accidentally enabling tracks by selecting them when I load up a new project.

I’ve assigned a key command to switch tracks on, to save having to navigate to the track header every time.

Then when I load the project later, Logic can still do its automatic thing.
Yep, I found the same. Plugins springing to life when clicking the wrong track gets old quickly. It's great that we can manually override it. It's a nicely thought out system and something that I've been fantasising about for a long time.
 

stonzthro

Senior Member
Okay, so I've now finished replicating my Cubase disabled track template in Logic. They are almost identical with regards the number of VI's and both run to just over 600 instrument tracks.
How large is the actual template file? I tried creating one of about 400 tracks and it was over 1.3GB, which seems like a lot for a template! Not talking about RAM loaded, but the actual file size.
 

jonathanwright

Senior Member
How large is the actual template file? I tried creating one of about 400 tracks and it was over 1.3GB, which seems like a lot for a template! Not talking about RAM loaded, but the actual file size.
It's 439MB. Although the project file I was working on to create the template was much larger, as it included backups etc.
 

babylonwaves

Senior Member
How large is the actual template file? I tried creating one of about 400 tracks and it was over 1.3GB, which seems like a lot for a template! Not talking about RAM loaded, but the actual file size.
did you clean up the project before you've saved it? File > Project Management > Clean Up
 
  • Like
Reactions: Vik

Guavadude

New Member
The move from Sierra to Mojave and then Logic 10.4.5 was seamless for me.
Except that whenever the Alphatrack bundle is in Logic’s midi devices folder, Logic crashes as soon as I add an instrument. Does anyone have an Alphatrack they could test and lmk if they are getting a similar issue.

I hate to lose my flying fader with touch automation and the newer Presonus Faderport isn’t a good replacement with Logic from what I’ve read.
 

Nick Batzdorf

Moderator
Moderator
Does this mean leaving the load pref on or off? Thinking I could use the auto function but put a region in the tracks I want to be initially loaded like my drum VIs.
For me it's mixing and matching.

I figure I'm always going to want a piano loaded for working out ideas, so I leave that on. But I don't always need my favorite Omnisphere patches.
 

Guavadude

New Member
Got the Alphatrack working!!!!!!!!!!!!
The problem was obviously in the Alphatrack bundle that goes in the midi devices folder. As soon as I remove that, Logic stops crashing. I left all of the other Alphatrack files in place, trashed the CS prefs one more time and tried the Alphatrack in HUI mode. No luck.

So I tried it again in Final Cut Pro MCU mode on the Alphatrack Manager and manually added the MCU Pro control surface in CS setups in Logic. Eureka!!
Flying fader, touch automation and even the transport functions seem to be working. I typically only use the fader but that's working without a hitch. (almost)

You can grab these super cheap and having a single motorized fader makes a big difference when you just want to tweak something quickly. The fader can be a little noisy so I just unplug it and plug it back in when needed.

Say what you want about me, I'm a tenacious MoFo!!! Never give up, never say die! They may take our lives but they will never take.... our Freedom!!

Actually went back and the Baby HUI module in Logic with the Alphatrack in HUI mode is working best. Still having an issue with it not following selected tracks like it used to do with it's own midi device profile so I'm having to scroll to the track I want to automate. I may try doing a custom control surface setup when I have more time.
 
Last edited:

Dewdman42

Senior Member
Scripter appears to be broken in 10.4.5, perhaps badly. Anyone depending on Scripter for articulation management or other things should strongly consider using 10.4.4 until further notice.

Some very simple scripts may work fine, some may not.

Anyone interested in following developments related to this can go here:

https://www.logicprohelp.com/forum/viewtopic.php?f=45&t=142778

Please come report the issues you may be having with it.
 
Top Bottom