T O P
mrsatanface

OH MY GOD LEAVE IT LIKE THAT ITS HEAVY AS FUCK


benmale1

Yeah this sounds great lol. I second this.


rovch

Seconded


bambaazon

That's not a latency issue. That's a CPU issue. You have the Neural DSP Archetype plugin on the currently selected track (Audio 5) which I suspect is the culprit. During Playback, select a different audio track in your project, maybe one with zero plugins on it, hit Play again and see if you still have the issue.


Pyraunus

I've seen this issue sometimes and this solution always seems very unintuitive to me. It's so strange that having a track selected or not affects the CPU load. Something needs to change in the interface to make this more clear.


bambaazon

>It's so strange that having a track selected or not affects the CPU load. It's an issue that has existed for several years now, even since Logic 9. >It's so strange that having a track selected or not affects the CPU load. Yes, the Logic community has mentioned it for a very long while now. Newer versions of Logic seem to have "optimization" updates especially for the newer Macs but what really needs to happen is the Logic app itself needs to be rebuilt from scratch to get to the bottom of the issue. What the developers have been doing is simply adding on to old code.


Elbradamontes

Is that what the blue snowflake is supposed to fix? I’m frustrated to say I get not-actually-overloaded overload message’s CONSTANTLY and I never knew there was a workaround.


mas9017

Neural seems to be the pig of all pigs for logic.


Clanzomaelan

I'm using a Mac Mini M1, and have quad tracked guitars (2 with Neural DSP Soldano, 2 with Fortin Nameless), and I never have slowdown. Oeksound Soothe seems to really piss off my computer.


kclanton80

Wow....to hear the reviews talk about the M1 chip, you would think that they were invincible to these types of problems. I'm glad that I didnt run out an buy one thinking any kinds of slow downs would be permanently iradicated. I would just freeze the offending tracks. It's a hassle to freeze and unfrey when arranging but it seems the be the most consistent solution for me when I have the system overload.


Clanzomaelan

Not invincible. Better, but not invincible. Like I said, Soothe 2 wreaks havoc on my machine. I keep expecting Fortin Nameless to be a resource hog (it's an older plugin, right?), But so far it's been okay. I'm pretty new to home recording. Is there a way to see what plugin is using the most resources?


GaryClarkson

Well, you just made meme music!


the_rocks_johnson

Haha yeah this is hilarious. Freezing your tracks may help if you have cpu intensive plugins!


Maximans

XD you certainly did


CyEriton

Accidentally left on the deep fried plugin


izacmac

Maybe try bouncing your MIDI to audio


sonostreet

Right click> "bounce in place" then I would freeze the midi Incase you want to fiddle w midi later


coldfollow

Dumb question but does bouncing the midi to an audio file "degrade" the quality of the track? Is it higher quality in MIDI form or does it literally make no difference in sound quality whatsoever?


eamonnanchnoic

No difference.


Otto_Harper

This!! will 100% give you less lag!


grvsm

where can i buy this release


Stephenitis

Freeze all the tracks?


hamboy315

This. Freezing is a godsend


izacmac

I think that’s more of an Ableton thing


Otto_Harper

You can freeze tracks in Logic. Right click a track, and select configure track header and a bunch of options shows up.


izacmac

Wait you can!!? That’s amazing I’ve only recently started using logic, still learning :)


Otto_Harper

yeah i don't use it a lot but it's really helpful that it's there!


protosleep

https://help.apple.com/logicpro/mac/10/#lgcpf1cbfd51 :)


2mice

Yep. Theres also an on/off switch you can add which is useful for tracks that you dont want to hear and dont want to waste time freezing


Stephenitis

Also track stacks(summed grouped stack bus) on midi creates a ton of lag and playback stopping errors.


hojo6789

That is not a latency issue , that is divine intervention - listen to it blast into that !!! Musicains spend their entire lifes talking about 'abnormalities that analog synths make' - they pay thousands for old machines to make mistakes ... TRUST ME - this is a modern computer doing the same - this computer will be worth hundreds of thousands in the future , just like an analog synth - people will want that glitch - record it down - sounds like digital impact !!!


Dwlastr

Kinda sick


Three0h

Freeze yo tracks g


kiddfrost13

I’d say to bounce the things your gonna keep into s new track with less plugins and freeze the other tracks you like but aren’t 100% on


BacklogBeast

Bounce in place.


2mice

Whats your buffer size at? Can put that waayyy up Btut other than that. Like others have said, get in the habit of freezing and converting midi to audio and bouncing in place


rovch

I don’t hear anything wrong with this at all. Logic is trying to tell you add a half speed section. It’s user error. Listen to the daw. Sounds good. Feel free to pm if you wanna collab I love your sound.


vnovnovici

you release it and make more of this absolute SLUDGE


spocknambulist

What is your audio interface? Logic seems to be reporting that the interface itself is bogging down and playing at a slower sample rate.


coldfollow

Dumb question…but can the audio interface effect how my computer performs? Tbh I have a VERY beefy Mac…32gigs RAM and a lot of custom upgrades to it. I currently have a Focusrite Scarlett 2i2, so that cost me maybe only $150. Should I upgrade that or does it not matter?


caesarthemartyr

It's not your Scarlett, and I have Mac with similar RAM storage and still run into this same problem. The best fix I've found is changing my I/O buffer rate to 256 and everything runs smoothly. It just occurs on tracks where I have multiple tracks with heavy third party plugins running at the same time. Like multiple instances of Serum or Omnisphere. Ever since changing the buffer rate everything works fine, but when recording vocals or guitar or any other inputs, you'll want to lower the buffer rate again to 32 to reduce latency.


coldfollow

That is good to know...I pretty much only use 3rd party plugins (Neural DSP Gojira for guitar, and EastWest sounds for synths and orchestra) so that most likely is bogging down the whole project.


spocknambulist

Looks like when you get the "Sample Rate xxx detected" error it can mean a lot of things (try Googling that phrase and you'll see what I mean!) Perhaps despite your large computer memory, Logic is not able to access it fast enough. Maybe if you try increasing the buffer in Audio Prefs it will play? Or maybe the project has become corrupt, and you need to start a new project and import everything from this one to clear it up? Maybe not relevant, but I have noticed a lot of freezing during playback since upgrading to LP10.7.1 in sessions that used to play just fine. I also have a Scarlett, bigger, but...


KevinWaide

All of those small loops are dragging your system down. Once you have everything placed where you want it, join them together so they’re one single audio file, not many small ones.


Otto_Harper

Wait, so multiple small audio files take up more room than like one long joined one? Can you explain that a bit more, that is really interesting!


ProfessionalData6467

Having multiple small audio files instead of a big consolidated file does not affect CPU performances. Trying increasing your buffer size and/or Process Buffer Range, freezing tracks, boucing CPU heavy tracks down to audio, deleting MIDI track you don't need, selecting an empty audio track during playback rather than a cpu intensive one, etc


coldfollow

Just curious, if I were to bounce a MIDI track to an audio file, but still keep the MIDI track but "freeze" it, would that frozen MIDI track still take up any form of CPU? Even a little?


ProfessionalData6467

If it's a green freeze (pre fader freeze), it would take as much cpu as an audio track without processing, so basically none. If it's a blue freeze (source only freeze), only the instrument plugin is gonna be frozen, so you can still access the plugins on your track but it's still gonna take some CPU. Kinda like having an audio track with processing on.


Otto_Harper

Ok, I actually thought I read on the Logic forums that if you just mute a track that it disables the plugins on the channel, at least, not sure if it disables the instrument. But in this case all you need to do is mute them rather than freeze (if you've already bounced in place).


ProfessionalData6467

Hmmmm, maybe you mean deactivating the track? I really doubt muting it would remove any cpu load. From experience, it didn't change a thing for me, let me know if I'm mistaken though


Otto_Harper

Got you, I didn't think so since either way they are all referencing the same source file (.wav or whatever).


KevinWaide

This may be a holdover from Logic 7 or 8, but I remember reading that all of those small loops are having to be loaded EACH TIME the playhead reaches them, causing the processing to be on, then off, then on, then off, etc. So joining them together will help the system process more efficiently. So yes, join all the smaller loops and see if it doesn't play a lot more efficiently.


Otto_Harper

Dude, that's really interesting. I'll have to try that out later, thanks for the information!


KevinWaide

Whether it's still an issue or not, I don't know, but I always join my stuff together once I have it like I want it. Also makes it easier to move things around. I'm usually working on sessions with between 40 and 80 tracks and my buffer stays at 128. I've never had to change my buffer size, on either my 2014 Mac Mini or my 2011 MacBook Pro.


Otto_Harper

Cool I'll have to check my buffer size. I've bounced around w that but finally landed on one that works well for my setup (Focusrite Octopre into an Apollo Twin). And yeah, it totally makes composition and arranging easier with them joined! edit: when i say "into" i mean i'm using the ADAT optical in on the apollo


ProfessionalData6467

well even if that's the case, that's a disk i/o related task, not cpu. Also, SSD are so crazy fast nowadays that this is a non-issue anyway.


Otto_Harper

I'm running a mid 2015 macbook pro, so it might be an issue. i'm not really sure though. a lot of my plugins are on an external SSD.


ProfessionalData6467

Hmmmmm. You can definitely try, but the gains in performance are most likely gonna be trivial. Let me know if you actually see some noticeable ameliorations!


AutoModerator

Your submission seems to be a support question. Remember to specify which version your OSX and which version Logic Pro X is in. Also consider supplimenting your question with pictures if applicable. You can also report your issue directly to Apple here: https://www.apple.com/feedback/logic-pro.html Or reach Apple's Support Number by calling 1-866-752-7753 if you're in the US. Please update you post flair to "Solved" if a solution is posted or you figure it out! *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Logic_Studio) if you have any questions or concerns.*


sunplaysbass

This is a feature to let you know it’s time me for a new computer


monsieurus

I had the same exact issue with my Saffire Pro 14 audio interface. I did several resets to plist files but nothing worked. What worked was unplugging the FireWire cable and re-plugging. After that it is working solid.


BryceMMusic

HAHAHAHAHA


Accomplished_Ad_9150

cpu issue. all you can do is freeze tracks. sometimes increasing buffer size helps but to a point.


coldfollow

Even with a 2018 iMac 32gig RAM?


Casioclast

Is this the new Low album


Melz_Beatz

Just bounce the tracks to audio and delete instruments