Jump to content

noisyneil

Member
  • Posts

    218
  • Joined

  • Last visited

  • Days Won

    1

noisyneil last won the day on August 9 2022

noisyneil had the most liked content!

1 Follower

Recent Profile Visitors

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

noisyneil's Achievements

  1. @David Nahmani Yeah that's great if there aren't any tracks in that stack that you don't want to record over. 👍🏼
  2. Yup! I can confirm this. Thanks! Was driving me mad. Pretty annoying bug.
  3. Ah sorry David, I should have said. No, I'm up to date just like you.
  4. I've been using Logic for a long time and very few things flummox me, so I must be having a forgetful moment. I'd say 'senior' but I'm not that old! After I record multiple tracks of audio at once, one of those tracks becomes record enabled, overriding the ability to record again on all tracks. Please see the following gif, which should clarify what I mean. Can someone remind me why this is happening?
  5. Awesome! The only thing missing that my KM version will still be needed for it to list plugins that have not yet been categorised in Logic's Plugin Manager. I'll PM you now. 🏆🏆
  6. @des99, you already know I'm first in line for a test-drive! Hope you're feeling better now.
  7. https://support.apple.com/en-gb/guide/logicpro/lgcp55247cb8/mac Slip and Rotate!
  8. Hmm... Tricky one. Keyboard Maestro doesn't 'intercept' mouse clicks, so when you click a region and start dragging, regardless of what a macro does, you'll be dragging the region around the timeline too. One thing you might be able to do is to use Better Touch Tool to trigger keystrokes when using the scroll-wheel with modifiers held. For example: ⇧⌥ Scroll Down = Nudge right ⇧⌥ Scroll Up = Nudge left Unfortunately the scroll wheel can't be used as a trigger in Keyboard Maestro, so those are my best suggestions. All that said, THIS is still probably your best bet, if you want to keep things simple.
  9. Correction... I was wrong and bounce-in-place is also broken!
  10. Actually, I've tried that and there's no problem. 👍🏼
  11. This is one of those bugs that creeps up on you, so I figured my best bet would be to delete anything unnecessary from the existing project and resave it. So, I did just that. I deleted every track except the one with the example regions on, tried joining the regions and there was no issue. What?! I undid that and the issue returned. I then deleted each track one-by one until there were just two tracks remaining. I then found, through some investigation, that if I removed one plugin or one send from the other track, the issue would go away. Again, what?! I then closed the project, intending to zip it and post here. Before I did, I opened it to check the issue was still there after the save-close–reopen procedure... The issue was gone. Thrice... What?! I went through the whole procedure again and this time I took a screen recording. Notice that the first join creates timing issues; after removing one plugin on a different track the issue goes away! As I say, the issue seems to disappear after I save and reopen it. The confusing thing is that if I reopen the original project, the issue is still there! Unfortunately I'm not able to share that project on a public forum.
  12. Absolutely. I wish it were something as simple as that. It's repeatable and this particular recording was made especially to demonstrate this oddity, which I first noticed today on an entirely different region. It's worth restating that removing and replacing the region's tempo information fixes the issue, which I've now done in order to carry on working.
  13. Ok, it just happened again, so... The joined audio is pink and the original is blue. For the example I'm working with now, the region remains the correct length, but the audio within it seems to be mostly time-shifted. Hit 1: in time Hit 2: in time, closely followed by a late duplicate(?!) Hit 3 onward: equally as late If I cut the region and drag the third hit to the correct place, all subsequent hits are correct. I've checked this zoomed all the way in and it's sample accurate. Therefore, there's some time-shifting going on within the region. Yes. No. Yes. To be thorough, I just repeated the join with each of the other project tempo options, and the result is identical. It's already off.
×
×
  • Create New...