Jump to content

karlingen

Member
  • Posts

    39
  • Joined

  • Last visited

karlingen's Achievements

Newbie

Newbie (1/14)

  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done

Recent Badges

2

Reputation

  1. Can't believe this is still an issue. For anyone interested in reporting this to Apple, here's some text you can copy and send to them. Logic Pro version: 10.7.7 The Plug-in Delay Compensation is incorrect when Plug-in Latency is set to "All". Please see this example project: https://www.dropbox.com/s/ndhbhh621hswdcj/PDC_bug_example.logicx?dl=1 1. Set Logic Pro Settings > Audio > General > Plug-in Latency > All 2. Start the playback Note how the ducking sound is out of sync with the metronome. And here's a workaround: 1. Set Logic Pro Settings > Audio > General > Plug-in Latency > Audio and Software Instrument Tracks 2. Start the playback Now the ducking is in sync with the metronome.
  2. Does anyone know what font is being used in the track titles?
  3. Only after you used the relocate function: https://support.apple.com/en-us/HT208892#move Only the Sound Library is moved—Apple Loops, Impulse Responses, and third-party content stay in their original locations on your Mac. Source: https://support.apple.com/en-us/HT208892
  4. Well I was right Can you please tell us when they'll finally fix PDC once and for all and also when they'll implement plugin searching? :P
  5. For me it is more Like, "Reaper is missing all Logic Instruments and Effects", and what about MCU implementation ? Well, you could always use both DAWs. If there's a specific sound you want from Logic then simply bounce it out to Reaper.
  6. Good luck with Ableton. When I have some downtime, I'm going to start using Ableton so I can properly compare it to Logic on my own system. I was always reluctant to do this in the past because I thought Logic devs would have these issues resolved by now. The thing is that I don't use a ton of 3rd party stuff. My set up is very basic, so there is no reason that Logic should be so temperamental. It very annoying being forced to use a different DAW, but I have been left with no choice. It's clear that Logic will continue to be very buggy for a long time to come Reaper is also a very good alternative, if not the best .
  7. Hi. I don't know why this is happening, but I can confirm that I can reproduce this on my system as well, so it looks like yet another bug. Logic is riddled with them. Did you report it to Apple? Over the last few months, I've spent more time finding workarounds for bugs than I have making music. My previous system was plagued with problems. Almost every time I sat down to produce, something would go wrong and I'd have find a workaround. I eventually took the huge step of upgrading my computer and installing EVERYTHING from scratch on the new machine. Although that solved some of the bigger issues, I am absolutely disgusted to see that a lot of the problems I was having on my previous system are present on the new one as well. I just don't understand how/why Logic is so buggy. I haven't had much experience using any of the other DAW's, but surely they can't all be as buggy as this? Exactly this. The past year (and especially the past months) have been horrible in terms of flow inside of Logic. The bugs have been killing my creativity. I'm slowly migrating to Ableton Live and it's been a treat to work with so far. Still going to use Logic when I need to open older projects or when I need a specific sound or instrument from it by bouncing out stems and importing them into Ableton.
  8. Wow, that's messed up! You should report that to Apple together with that video and a demo project. https://www.apple.com/feedback/logic-pro.html For me, I'm moving over to Ableton since I'm sick of all the bugs in Logic.
  9. I doubt. That, Audio Chase pref also appears when switching the documentation to 10.5... Besides, there would have been mention about same in the release notes or the other documentations I have read... Well, according to a dude on Apple's forum, it's there in 10.6.2: https://discussions.apple.com/thread/253063293?answerId=255753388022#255753388022
  10. That's strange, neither do I! It's probably a feature that will appear in the next version. Hopefully it will solve those kind of issues. I am posting here the screen capture of their Audio Chase settings online help, in case Apple decided to withdraw it... Screenshot 2021-08-13 at 03-21-46 Chase Audio Settings in Logic Pro.png That's the documentation for 10.6.2. Perhaps they removed it from 10.6.3.
  11. Here's a demonstration of the bug but with the use of reverb: As you might notice, I'm clicking at the exact same spot every time and sometimes it plays with the reverb and sometimes it does not. Demo project can be downloaded here: https://www.dropbox.com/s/7uk6e7wxcyuimjd/automation%20points%20bug.logicx.zip?dl=0
  12. Strange, I'm not seeing Chase Audio under the Audio tab (I'm on 10.6.3 and have advanced tools enabled). It's there for MIDI though.
  13. Sometimes, some plugin parameters get stuck at an old automation value even though the Playhead is at a point where the automation value should be entirely different. Here's an example: 1. I add a gain plugin to a track. 2. Add automation points so that the gain goes from 0.0 dB to -96.0 dB at a specific part of a region. 3. Play the track and Pause when the playback is in between the two automation points so that the Gain plugin is now showing -96.0dB. 4. Move the Playhead to another part of the region where it is supposed to play at 0.0dB. The gain plugin will be stuck at -96.0dB until it reaches an automation point that sets the value back to 0.0dB. As shown in this image, if I would hit Play here, the gain is still at its old value (-96.0) until it reaches the 0.0 dB automation point. This happens to me a lot of times, but not always. Shouldn't the plugin parameters values follow the automation lines at all times, or do I have to add multiple automation points to an automation line even though the value hasn't changed? Logic Pro 10.6.3 macOS Big Sur 11.5.1 Macbook 2020 M1
  14. Do you have an example project that you could share with us?
  15. +did you check the fix?+ I did! It's fixed!! Extremely happy that they fixed it
×
×
  • Create New...