Jump to content

onerob

Member
  • Posts

    6
  • Joined

  • Last visited

onerob's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I think, if I'm picturing it correctly, that you will have PDC working (correctly added) with that configuration, which is what you want. But if your compressor was placed on an aux track, and that aux track had a latency inducing plugin as well, then you wouldn't want to feed the compressor's sidechain with the Klopfgeist track itself, but only from another aux track that Klopfgeist was being sent to. And that's what you've set up, by the sounds of things. The problem occurs when a lack of PDC is added to the sidechain signal, causing the compressor to be triggered too early. But it only seems to happen in the specific scenario described above, so you don't have to worry when sidechaining between two regular tracks, for instance.
  2. There is at least this remaining issue in 10.6.2 that was identified by someone on Gearspace: If you have a latency causing plugin on an aux track and you are sending audio to it from a regular track, that audio will correctly have PDC added, but any sidechained audio will not add PDC. So that will cause compressors to be out of time if you're using sidechain (unless you send the sidechain source to another aux and go aux-to-aux for sidechaining). I sent feedback to Apple and likewise received an email back from them asking for an example project, which I duly sent. That was a few days ago. Looks like they want to get on top of this.
  3. Thanks. I'll avoid 'let' in the script I'm currently working on, as I may be posting it online at some point.
  4. I'm wondering if it's OK to use let instead of var in some cases in a script, specifically with relation to backwards compatibility. Safari didn't support let until 2017 and I'm wondering if that has any bearing on Logic, e.g. if Logic uses the js engine from Webkit and therefore changes over the years. This would mean that let was not available when MIDI scripting first appeared in Logic and so any scripts making use of it wouldn't be backwards compatible with older releases. Or does Logic have its own internal js engine?
  5. I'm guessing it's not a bug, exactly, but I can't see any practical advantage in having fader data/automation values that relate to a plugin slot rather than the plugin itself.
  6. If you use region automation to change the value of a plugin parameter and then change the position of that plugin in the effects chain, the automation doesn't keep up with this re-ordering and continues to apply its value changes to the effects slot that originally held the plugin. You have to use the Events List to select the automation entries and update the midi channel number to get it to work again. Is this a feature or a bug? Perhaps the idea being that the region is seen as independent from the track that it's currently being hosted by and is therefore detached from any changes made to it? The first version of Logic I used was 10.2, so I don't know the history, whether it's always been this way or not.
×
×
  • Create New...