Jump to content

realdealpeel

Member
  • Posts

    8
  • Joined

  • Last visited

realdealpeel's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I thought my explanation was good, but this is a lot more concise. Thanks! And here's another thank you to David as well!
  2. To reproduce this setup, you just need to create: In the MIDI environment: An external MIDI instrument track with the environment settings in the first screenshot (with the keyboard icon). A knob with the settings in the second screenshot (with the strings icon). A transformer with the settings in the third screenshot. Cable #1 to #2 and #2 to #3. And cable #3 to your main software instrument. In the arrange window, you will hide your software instrument track but show the external midi track, and this is where you will compose. Use controller 15 to automate the velocity. In the mixer, hide the external MIDi track and show the software instrument track. This is where you'll, of course, mix. Anyone please correct me if I'm wrong on any of this and I'll edit it!
  3. Hey David. This is great!! Version 10.4.2 here. Pre-story context: What I've noticed about Logic's automation: There is a significant delay - several milliseconds between an automation node (track or region, CCs etc) and an event. You cannot reliably put a node at the same time as an event and expect Logic to apply that parameter to the event. The delay is too significant and Logic doesn't know how to account for it. It only works OK for gradual changes. But if the automation is square shaped with the front of the square on top of an event, Logic will not see it in time. So as fantastic as the MIDI plugins are, especially the Velocity plugin - for controlling velocities via automation, the delay is just too significant for them to be useful, especially for drums. However, David has engineered this to somehow work unlike those MIDI plugins. So there is no delay! Brilliant! However (again), with this "hack" some of the UI and features change for some reason. And track automation now disappears, so becomes unusable. And No plugin parameters are available in the dropdown on the track header. So, no audio plugins can be automated. So this would require outputting the signal to an aux and mixing there. Pain in A to have multiple tracks for something so simple. But it's nice to know Logic is at least capable of reliably automating velocity curves! Mr. Nahmani, why doesn't Apple just hire you to engineer every part of their software? You figured this out 13 years ago. Yet, today Logic still cannot write velocity curves in any useful way. Thanks for these awesome and useful tools!
  4. I've discovered a bug with the anchor in ESX24. MIDI plugin automation will not compensate for the delay the anchor time causes. Even if one single sample has an anchor position greater than 0, every single sample in the instrument will be affected. Only seems to be per instrument, not for the whole project, thank goodness. Maybe it's more of a MIDI plugin automation thing that might get a fix?
  5. Just discovered a bug with the anchor in ESX24. MIDI plugin automation will not compensate for the delay the anchor time causes. Even if one single sample has an anchor position greater than 0, every single sample in the instrument will be affected. Only seems to be per instrument, not for the whole project, thank goodness. Seems like something so specific that it will never be fixed. Oh well. Maybe it's more of a MIDI plugin automation thing that might get a fix?
  6. There is an anchor parameter in the ESX24 editor. You can adjust the anchor for each sample and it will play in time no matter the tempo. It works, up to 10000 samples, or about 227ms* in 44.1kHz. Very capable. Why not use this? Is it something not in a previous version of esx24? *Did the math wrong
  7. Eric. Eric, Eric, Eric. You are a saint. a godsend. Now I can use the sustain pedal on all 16 channels at once!!
×
×
  • Create New...