robertg

That's a good suggestion. But you know what I think? This entire way we do digital audio is in need of a major overhaul and redesign. Computing power has increased tremendously to say the least since this whole "buffer based" and "plugin" system was invented sometime around the late 90s or so. I refuse to believe that near-perfect latency recording was possible for only a few short decades before my time and now on the cutting edge of the future we are forever stuck with stupid latency workarounds and limitations. It also stands to reason that the buffering system was more important when CPU and memory were more limited. Now with 8+ cores being the norm (which logic still can't make optimized use of) I really hope that this s#!+ gets better in a hurry. I want to hit record and go on any channel without ever worrying about whether it lines up. And besides the miniscule ADC latency the rest should all be realtime by now.

50 ms. The midi jitter is insignificant and probably no more than 10, which is acceptable. I don't really understand why logic isn't compensating. Not sure if I can eliminate MIDI since getting that aligned to the recording is the whole purpose of this

I went through all those videos just to make sure there wasn't anything in there I wasn't aware of. They say that logic is supposed to use its roundtrip delay calculation to offset the recordings properly. That doesn't seem to be happening at all, the 1024 buffer recording is way off and I'm not sure why.

Heh, I'm not sure if I buy that. I realize there is a few ms of jitter where midi is concerned but this is a huge amount, 50+ that's directly tied to the audio buffer size.

It would appear that the setting of I/O buffer size affects the precision of audio recordings. This is nuts, I don't ever remember this to be the case. Could it just be me? This is an empty project, no plugins anywhere. Except an external instrument plugin is triggering an external synth with quarter notes to test, and I am recording that to an audio channel. Note how early and terribly off the recording is at 1024 buffer. It's a little late, but much closer at 128. I thought logic was supposed to compensate for this.

I always found this to be the most laughable workaround ever. So we should introduce pain in the ass complexity and have to keep track of unnecessary routing all because logic is not as efficient as it should be. I really hope it's improved in the next version.

If he's able to give that thing more automatable parameters besides "input volume" then I'm all ears.

this method works fantastic! The CC data is ending up in automation lanes. Although I'm discovering that I can't get parameters to show up on euphonix based controllers because there is no plugin, just midi lanes. I wonder if an "external instrument" type of plugin exists that has midi CC as automation parameters? Maybe I'm reaching.

aux channels

Okay, I'm not great in the environment but if someone knows of a way to accomplish this I would be very impressed. When playing back live external synth midi and monitoring there is a roundtrip audio delay that logic doesn't account for, for me between 12 and 16 ms depending on buffer size. Strangely enough it does account for this in record mode, meaning I have to turn it off and on between playing and record (at midi preferences > sync > delay all midi output) I would like for logic to advance all midi going out of my motu's ports by a certain value except when it is in *record* mode. Possible? If I have to toggle it on and off with a key command that still definitely beats my current method.

Is there any way to turn MIDI CC hyperdraw region information into track automation? I'm asking for control surface purposes. I know about 'move all region data to track automation' but that only works for plugin or channel parameters, not for midi CC. If it's not possible, maybe there is a plugin similar to external instrument which has automat-able CC parameters built in? or maybe.. some environment wizardry. The goal is to be able to move euphonix faders around and those only respond to automation and can't be mapped otherwise. thanks in advance

Check out AUSampler.. had no idea

all you have to do is change to another sound with the value +/- keys in multi mode

no, you can edit patches in multi mode.

your regions can be made any color you want, not just the limited palette by pressing option-c, but all of those colors can also be customized by double clicking them. the more you know..