Jump to content

tedannemann

Member
  • Posts

    41
  • Joined

  • Last visited

Recent Profile Visitors

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

tedannemann's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Still no fix for the completely messed up Plug-in delay compensation in Logic Pro X 10.5.1. I'm not getting tired to ask all Logic Pro X 10.5 users to really report this long time issue of Logic Pro again and again: Just take 2 minutes and send a bug report to Apple about the missing plug-in delay compensation for automation, side chain signals and beat synced plug-ins. Thank you for your help! https://www.apple.com/feedback/logic-pro.html
  2. Still no fix for the completely messed up Plug-in delay compensation in Logic Pro X 10.5.1 All Logic Pro X 10.5 users please do report this issue: Just take 2 minutes and send a bug report to Apple about the missing plug-in delay compensation for automation, side chain signals and beat synced plug-ins. Thank you for your help! https://www.apple.com/feedback/logic-pro.html
  3. Still no fix for the completely messed up Plug-in delay compensation in Logic Pro X. I'm not getting tired to ask all Logic Pro X 10.5 users to really report this long time issue of Logic Pro: Just take 2 minutes and send a bug report to Apple about the missing plug-in delay compensation for automation, side chain signals and beat synced plug-ins. Thank you for your help! https://www.apple.com/feedback/logic-pro.html
  4. The last time I used Serato Pitch 'n Time LE was in a studio where I worked on a collaboration using macOS Mojave and Logic Pro X 10.4. I asked the Serato support about Logic Pro X 10.5 but they couldn't answer that question yet.
  5. Anyone using Serato Pitch 'n Time LE and can confirm that Logic Pro 10.5 still supports this 3rd party stretching/shifting algorithm under mcOS Catalina? https://serato.com/pitchntime-le
  6. Thanks! Keep up reporting the PDC issues, please.
  7. Right tin the feels! Even FL Studio has more plug-in delay compensation game than Logic Pro X 10.5 now: From the FL Studio 20.7 release notes: Now Logic Pro X is literally the last major DAW which can't get it's automation in time.
  8. Then watch these two videos and do make a bug report over at: https://www.apple.com/feedback/logic-pro.html Wait till you hear what happens to the automation as soon as the limiter (substitute for any other latency generating plug-in) gets involved: This is an audible demonstration of the problems occur when working with automation and latency generating plug-ins. In this example one additional plug-in with latency (Adaptive Limiter) destroys the Gain automation. The aim was to automate the word "two". In this simple demonstration just the gain knob of the Gain plug-in (as substitute for any other plug-in automation). The word "two" should be automated (muted) no matter what happens on the track - as it's the case in Cubase, Live, Bitwig, Studio One or Pro Tools (just to make it clear that this has been the standard for years now). However, this gain automation curve could be anything, an instrument like Kontakt or Omnisphere, an effect, de-esser, eq, a swell, fade-in/out of any parameter, a reverb automation, you name it. To emphasize, it doesn't matter if it's a hard or soft automation. The points, it's all about the points, they are at the mercy of the missing latency compensation and shift (won't get compensated) depending on what happens plug-in-wise on the track. Do you use plug-ins as from iZotope, Acustica Audio, Universal Audio, or especially plug-ins like Soothe, DynOne, Virtual Tape Machine, Gullfoss for example or any other heavy latency introducing plug-ins? If you stack such plug-ins on top of each other, any automation on these audio and instrument tracks will be out of order audibly and you will have to change the latency for each (latency) plug-in change you do "by ear" - such as slapping additional plug-ins on the track at a later stage, software updates of the plug-in itself (e.g. oversampling functions), different modes/presets of the plug-ins (high/low latency modes), deactivating a plug-in later on, exchanging for another one and so on). Therefore one should not trivialize the missing compensation for automation (as well as side chain signals) but seriously request it from Apple. This is a serious flaw. For those who don't hear it (many Logic users strangely do so...), this visual demonstration is hopefully an "ear opener". Hint: it sounds like what it looks like. Logic Pro X 10.5 test project to download: Missing ADC in Logic Pro X 10.5 - Visual Demonstration.logicx.zip Sorry for bringing this up again and sorry for the click baitish thread title. But please do make a bug report about the "missing plug-in delay compensation for automation and side chains" over at: https://www.apple.com/feedback/logic-pro.html Thank you!
  9. Yes, my fault! Sorry for that! It works for bar 1, 3, 5 and so on but not in every second bar 2, 4, 6 and so on (in case of 128 BPM). Still seems to be a problem with the aligning of the ticks/samples.
  10. Actually, that wasn't fast this problem goes back years. I just guess it's due to the new live loop mode - that loop work (syncing/looping) has to be spot on.
  11. Seems to be fixed in 10.5. Nope!
  12. Thanks for posting that, it was the first question I had after seeing the update. New features look fantastic but that is really bad news. Not only missing side-chain PDC but also still no plug-in delay compensation for automation. This can't be real!!! Please write to Apple and make a report: https://www.apple.com/feedback/logic-pro.html Information why you can't use UAD or any other high latency plug-ins to its full extent in Logic Pro X: viewtopic.php?f=1&t=145627&p=759021#p759021
  13. It seems to depend on the tempo, and most likely its effect on the relationship between your sample rate and the clock's tick resolution. For example, quick tests show that: That's an issue at 128 bpm and 44.1 kHz. No issue at 128 bpm and 48 kHz. No issue at 126 bpm and 44.1 kHz. That's an issue at 126 bpm and 48 kHz. Yes, it does go out of sync over a longish period of time if you loop a region that is not exactly one bar. One workaround is to not loop the region but repeat the region using Edit > Repeat Multiple adjusted to the Bar instead. Then the regions line up. Are there any approaches how to calculate which tempos are affected?
  14. I wonder how other DAWS handle it at tempos where a bar isn't a whole number of samples long. Do they fudge it and drop the last sample? I don't know what exactly goes on under hood but Cubase does exactly what I want it to do no matter if I work on a sample, millisecond or musical grid basis. In this example I can create a one bar marquee selection of two clap sounds and create a new audio file or bounce the selection in place then loop it till bar 500 and everything is exactly where it should be - no matter if working on 128 BPM or even such strange tempo as 55.879 BPM.
×
×
  • Create New...