Jump to content

luckyal

Member
  • Posts

    241
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

luckyal's Achievements

  1. Actually it's used all the time. I was initially going to use Pro Tools, but after doing some extensive research, the supposed efficiency of Logic's built-in plugins, I was sold on the idea of going with Logic. I've been a logic user since 1999, so it's a DAW I am by far most comfortable with.
  2. I think this might be it. Typically scripted is executed on MIDI tracks, but these are audio tracks which are grouped into summing tracks, being monitored through plug-in processing and recorded live into Logic. I'm curious on where I would get started.
  3. I did. No discernible difference.
  4. Unless AAX Plugin versions are more efficient than their AU counterparts, there should (theoretically) be no difference. In fact, if anything, Logic, being an Apple product, should be optimized far better than Pro Tools for macOS. After all, in Logic, a lot of the plugins I'm using are native to Logic. Also, I'm using the same Audio Interface in both cases. The only difference is the DAW.
  5. I have 64 tracks condensed to 13 VCAs. For me precision is essential, both for fader speed and setting. Can't achieve that manually.
  6. Is it possible to create macros for making smooth volume/pan adjustments? I'm mixing a LIVE show and need to execute consistent fader movements between 'scenes'. For example, I have background music playing and wish to execute a smooth fade out while fading in up to 8 handheld mics quickly. I understand that I could probably utilize a Stream Deck to some extent, but how exactly would this work in Logic? I don't want the MIDI triggering to be dependent on my timeline at all. If that were the case, I would just create an automation lane. I need to be spontaneous in the execution of those commands, but the consistency of fades and desired levels is a must, which doing this by hand is not really possible when handling more than 8 faders.
  7. Wondering if you had a chance to test?
  8. Not sure if you have all the plugins I do, but go ahead and drop your own audio files into the tracks, enable software monitoring, input monitoring and record enable. https://drive.google.com/file/d/1-lQ4_Fos79hToHCoiVs-9l0iikFZ80ff/view?usp=sharing
  9. I have 32 inputs coming into Logic. All are separate channels. I have input as well as software monitoring enabled for ALL of my tracks. I have to hear the adjustments I'm making in my EQ's, Compressors, etc.
  10. Yes, I am using lots of plugins in realtime monitoring/software monitoring mode. It's a specific requirement that I have. In the case of Pro Tools, I'm relying heavily on 3rd party plugins, whereas with Logic, I'm using a lot of stock plugins. Essentially I had to recreate the session in Pro Tools using 3rd party plugins where I used Logic's plugins. E.g. Logic's plug-ins are supposedly optimized for Logic/Apple and yet... As for your comment regarding record enabled tracks - that's a nonstarter for me. As I am recording/monitoring, I am also using a control surface to adjust volume as needed. This is done in both DAWs. Pro tools is steady with evenly distributed processing among all available cores. Logo, not so much. I would much rather prefer to work in Logic because I have about 32 tracks condensed to Summing/Routing folders. In Logic, I can collapse those folders and expand them as much as I want without input monitoring being disabled, whereas in Pro Tools, it automatically disables Recording/Input monitoring for the "hidden" tracks. In PT, this is by design apparently.
  11. In ALL cases, Logic on Intel, Pro Tools on Intel, and Logic on M1 they are all record enabled and input monitoring is enabled.
  12. For comparison, here's that same project on an 14" M1 Max Macbook Pro.
  13. I've had a few instances where I needed to record about 32 tracks of real time audio at 96/24 into Logic, while using Logic's Software Monitoring. After several bouts of system overload messages, I gave up and moved onto using Pro Tools - URGH! I noticed that Pro Tools (FRIGGIN PRO TOOLS) does a much better job at distributing processing amongst all of the cores, whereas Logic front loads most of the processing onto the first core. Is it possible that with the arrival of the M1 chips, Apple is optimizing its apps to work exclusively with M1 while sabotaging intel performance?
  14. Found my answer on my own. I had the two tracks assigned to a group as it was a multi-mic’d instrument. That group was active when I made clones of the tracks which retained the same group settings.
  15. I have a track that I recorded and then decided to break up into 3 separate tracks. But now when I select one of the regions for editing, Logic selects ALL regions in my song. Any ideas?
×
×
  • Create New...