drakeholloway

Hey guys, I can definitely say this SOLVED my issue! I am so grateful for you guys. Upon opening a session I have been needing to wait for 45min + for the spinning wheel of death to stop at which point I finally get the midi timeout message. Not anymore.. 🙂

This is great info thanks so much. I usually rename regions to handle this but the default format sounds great

That’s a cool way to do it. How do you know which take is which in order to get 11 channels of take 1, take 2, etc all dragged in together? Ahhhh ok great to know. They all had same start but different endings. That’s a game changer thanks!

Hey guys, I wish I would have tried this. I ended up recording 11 channels of drums and 1 channel of electric bass live with track alternatives. It was kind of a nightmare as we couldn’t really comp and I had to select all the alternatives and create a take folder (this always has its own issues as you lose your track colors and MUST name your regions in your alternatives before creating a take folder or else you don’t know which take is which). I will be using take folders from here on out! Also, oddly I was having some grouping issues even with Quantization lock and editing checked where my HH and OH-L tracks were not responding to the quick swipe comp as the other 9 tracks were (groups were enervated). It was maddening as I had to manually go and swipe the comp on those two tracks.

Hey guys, I usually record vocals in new session to bounced two track and import all my takes back into main session but I have had issues where the imported content is totally wrong, I lose take folders and only get the comp, or even the audio is warbled and things that were recorded in one place on the timeline are in a different place. Usually the work around is to unpack take folders, import all channels separately then repack in the main session after import. Anyone else having this issue?

Absolutely. I am on OS Big Sur-Logic 10.7.2 I have hundreds of third party plugins. This has occurred on multiple sessions, one had no third party plugins on the session. Also I am on a Mac Book Pro i9 64 GB

Hello Logic users, I am encountering very odd behavior which is intermittent and gets solved temporarily with a quit+reopening Logic. See the attached video the dropbox link to hear an electric guitar part that sounds like a robot and notice that visually the waveform is destroyed and choppy. It has happened on vocals (with an artist in the room sadly) and synths as well, all through different inputs on myself system which is an Apollo x8p paired with an x16. I have spoken to UAD and they reminded me that if I am not hearing it in my Cue system while recording (which I am not) it must be a Logic issue. They mentioned perhaps it has to do with read and write and to try it in another DAW to troubleshoot but that doesn't solve anything as I am strictly a Logic guy. In case this is sample rate mismatching, Logic and my UAD console software are always matched at 44 or 48 depending on the session. It seems to be happening more and more now as well. Since I couldn't attach a .mov file here is a link to a dropbox folder with the issue. https://www.dropbox.com/sh/njdh16h4lc2r0z5/AADm8gqMVmT67bm1tEeg_YFNa?dl=0 Thank you all kindly, Barry

Hey guys, Just wanted to follow up and say thanks for your thoughtful responses. I went ahead and started a fresh session (not from a template to make sure nothing innately wrong there) and imported all 130 tracks through the LPX file browser. The session is playing perfectly and with 25% or lower cores usage. Lastly, I did get one overload on the new session and found that after deleting the LEAD VOCAL BUS everything was fine. I had 4 channels of lead vox running through one bus which may have been the maxed out core.

Okay I will hunt it down. Thanks very much for the help here.

It seems that the far left core of my 16 core lines (8 cores multithreaded) spikes initially when I hit the spacebar to play the session and then I get the Overload message. I have attached a pic here. The I/O meter seems to spike to full capacity when I hit play as well but that seems typical regardless of project size.

Other projects that are decent sized do work fine here. I see you are thinking the issue could be global here. Would you suggest I open a fresh session and import each channel one at a time? That is all I can think of at the moment..

I have never had to do this but realize it could help possibly. Thanks for this tip here and I love Speakerfood plugins!

Hey there, I will try to look at the nvram reset. Also, thanks for the De-ess tip. I do like to stage them because the more I compress the more it needs to be De-Essed obviously.

Hey LPX community, I am going mad here trying to finish a mix that is due this week and cannot play my session at all. System Overload alert instantly every time I hit play. I have attached my Preferences which is optimized for CPU power and still nothing. I work on a maxed out Mac Book Pro running a 2.4GHz 8-core i9 Intel chip. I have 64 GB RAM and am on Big Sur. Every track is frozen (pre fader) except busses and even on my LEAD BUS I disabled my plugins. Other than that it is a few plugins on my MIX BUS. I even tried exporting all tracks and imported into a fresh session and even that won't play (all audio tracks zero plugins). I am trying to attach a screenshot of prefs but it won't let me for some reason. My PREFS are: 44.1 sample rate 1024 buffer Multithreading-Playback Buffer size- LARGE Summing 64 bit (I tried 32 and it still won't play) Thanks for any help you can offer here.

Yes I agree completely. What I have found is when my buffer is at 1024 the midi fires early and my audio ends up early (from the real time bounce of my external synth). But when my audio buffer is 32 the midi fires late and thus the audio is late. I found 128 to be the sweet spot which gets it pretty darn close but still not perfectly on the grid. Maybe just better to zoom/slice at first transient/realign.