Jump to content

stormy

Member
  • Posts

    122
  • Joined

  • Last visited

Personal Information

  • Mac
    MacBook Pro 16" M3 Pro

Recent Profile Visitors

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

stormy's Achievements

  1. I've only now realized/remembered that you can export shortcuts and also filter the customized ones, so I can open my old machine and see what's what. For some reason I started my shortcuts from the Pro Tools preset, about 10 years ago. I haven't used PT for 20 years though...
  2. I just moved to a new MacBook Pro with a big jump in OS (Catalina to Sonoma) and Logic version (10.6 to 10.8) and I'm needing to reconfigure some stuff, like control surfaces (not sure why). Since most of my X-Touch One customizations are done by assigning keyboard shortcuts to the control surface, if I change to another shortcut set, I lose them. So I'm ready to start from scratch and redo my customizations, there are only a few. I have a Spanish keyboard but I use Logic in English. Should I pick the Spanish shortcuts or the US ones? Forgive the very basic question! I don't see very obvious differences between both sets of shortcuts, is there a way to check? I would hate to redo all my customizations and control surface assignments only to realize I had picked the wrong language...
  3. Unfortunately the fix didn't work for me. I've gone back to Reference 4 instead of SoundID so I can avoid this problem.
  4. Thanks @BobbyT! I will check and report back, I hope it will work for me too. I have a well treated studio and Sonarworks really did provide the final 5%. I've been a big fan but the latest releases have been too buggy, that's why I'm jumping ship.
  5. I just switched from Logic 10.6 to a new MacBook Pro with Sonoma and 10.8.1 and I’m having this problem too. Did you manage to fix it? Fortunately I also bought the new Arc Studio hardware unit and as soon as I calibrate the room with it, I’ll be able to get rid of the SoundID correction plugin.
  6. Thanks David! After diagnosing post-concert, I could see that the audio actually glitched before it stopped recording, so it didn't just went into play as I thought. I must have stopped then about a minute later it went into play, then I hit record. I know this because the empty space is shorter than it should be. However, your suggestion to always hit play before record is gold!!!
  7. 48kHz, 24-bit. Now that I know that Logic actually glitched, with distorted audio and a pause somewhere, all bets are off. That's why I carry a backup recorder for these gigs! However, you never really think you're going to NEED to use it...
  8. It was a laptop, on location, no peripherals and no accidental key presses. Recording to WAV files, the interrupted file was about 1.25 GB. Besides, with Mac OS formatting I don't think that should be an issue. SSD internal disk, more than 30 GB of free space. Long buffer. After getting to listen to the files, I can see that before the recording got interrupted there was some glitchy sound, so it didn't just randomly went into play. Also, the gap left between Logic stopping and me realizing and hitting record again was narrower than the actual time that went by. So it glitched, it stopped, it went into play, all while I was looking away. I guess it's just random bad luck. I haven't had anything remotely like this happen for the past 10 years!
  9. I’m recording a symphonic orchestra onto two stereo tracks. My heart almost stopped when I look at the screen and I see Logic has stopped recording and went into play! Of course this happened the only minute I didn’t have my eyes in the screen. I hit record again and it’s working. I haven’t been able to check yet if I can rescue the audio that should have been recorded in the gap or not. This happened about 1h15 into the recording. EDIT: No, there’s no audio to be recovered in the gap. Fortunately I’m also recording to a backup recorder so I should be fine. Is there anything to troubleshoot here?
  10. Ok, I will chalk it off to a Logic 10.6.3 problem. Thank you all!
  11. Yes, I've frozen my machines on Catalina, so that's as far as it goes. I've removed all third-party plugins and the problem is still there.
  12. Thanks! It might be a Logic 10.6 issue. I asked a friend that runs Logic 10.7 and he doesn’t have the problem either. I might remove all plugins from my second machine and see if that changes things. Will report back.
  13. Can you let me know if clicking on your Logic Pro menu item (leftmost in the menu bar, in case it's not clear) has some lag? I noticed this today for the first time because I was clicking and - nothing! Or a spinning beach ball. I had just updated a plugin, so I took it off and voila! problem fixed. However, I kept noticing the lag. Just compare it to the File menu, which is instant. Now, on a different computer with an almost default install of Logic, I can also see the lag... Is this happening to everyone?
  14. I've done it with two sends and two inputs, using a stereo I/O plugin. There are other possible variations, like using the I/O plugin on a second track without output (just the input for the second mic), and using the same ping figure, but I haven't tested if it syncs.
  15. Here's my final conclusions for future reference. 1. You can output via Aux send to an interface output and record via a normal input track with no latency. But this is not guaranteed to work across all interfaces and situations. 2. For a guitar reamp, you don't need 2 buses. You setup the I/O plugin in the DI track, ping it to compensate for all latency (including mic distance!), and then send the track to a bus, which can be set to no Output. Record that bus. I'll be happy to reply to any questions, after all the work triple-checking the setup 🙂
×
×
  • Create New...