Babe

Did some more testing. The non problem is only when I use more than 1 instrument. If I assign all the tracks to the same instrument, all's well.

I've had Logic for many years but haven't used it much. I've had problems with automation and getting the tracks to attack at the same time. Every time there has been an update, I try again to see if the problem still exists. With 10.5, it still does. I've done some experimenting and can't find what's causing the problem. I put 4 multi instruments though VEP 7. Each instrument had a instance of Kontakt 5 with Berlin Strings. 1st Vln, 2nd Vln, Vla, and Cello, each in their own instance. Each instrument is playing a divisi sustain chord. (Changing articulations doesn't solve the problem.) If I start play right on the beat, one of the instruments will sound before the others. If a solo/unsolo a track, that is the track that will sound first. If I solo/unsolo 2 or more tracks, the first one I soloed will sound first. If I start play 2+ beats before the downbeat, everything is as it should. If I start 1 beat before, the 2nd Vln won't sound at all and the volume on the Vla and Cello is about 7 db softer. Solo/unsolo doesn't make any difference. Starting 1/2 beat before results in results with too many variations to mention. Sometimes one instrument will sound, sometime with lower volume. Sometime with two. I checked all automation for strays. I have sample accurate automation checked. Unchecking doesn't change the behavior. I've tried various buffer settings. I have no external controller.

Try Rewire

Solved the problem. I turned off chase long notes.

I'll have 2 keyswitches, let's say C0 and E0. If I start play before the keyswitches, everything works fine, C0 will show up on the left of the capsule switch window and E0 on the right. If I start play in the middle of the keyswitch, they switch positions. E0 left, C0 right. This happens even if I start one of the keyswitches before the other. If I start EO before CO so as to have E0 be on the left, if I start play in the middle, E0 will be on the right.

Let's say I use cc6 but it's only present in some regions. In the regions where I don't want to use this effect, I want it set to whatever value, let's say 0. In a region where I use cc6, I have to return the value to 0 at the end of the region. If I don't, it will stay at whatever was the last value was in the region. This is true in all future regions or if I go back to an earlier region where cc6 is not in use. Even if you return cc6 to 0 at the end of the region, if you stop play in the middle of the region, then go to another region, the value won't go back to 0. One could enter the default value for every parameter in every region, but this is time consuming. I can't find anyway to set a default value for a parameter that would be in effect if that parameter doesn't have any automation in a region. Am I missing something? There has to be a way to not have to worry about at what value a parameter is set when in a region that where the parameter is not being automated.

No on VCA. Can't have a sub control a sub.

Oh, I can use VCA faders.

I didn't explain my setup correctly. I have a folder stack 'strings', which shows in the mixer as a sub. Inside, I would have another folder stack for each part of the string section, which also shows as a sub. Then inside the level 2 folder stack, I has the summing stacks. Changing the level on the top level strings has no effect. Guess you can't have a sub controlling a sub.

If you want a good sounding mockup, use a DAW. If you want a good looking score, use a notation program. If you want both, use both.

Correct. Stacks not regular folders.

When I have a summing folder(s) inside a track folder, the controls for volume don't work on the track folder. Doesn't change anything. Is this the proper behavior. If not, help.

I traded my late 2008 Mac Pro for the coffee can Mac. If you want fast disks, this is for you. There are 6 thunderbolt ports. Get SSD thunderbolts and there is nothing faster. The computer is small and quiet. My only complaint is that it doesn't have enough power for the USB ports.

For a given passage to sound as it should, I have to start play a second or so before the passage is actually starts. Starting sooner, and any automation parameters (CC1 and 11 for sure) at the beginning of the passage won't have any effect. Starting after the beginning of the passage, chasing back to the settings at the beginning is very inconsistent. I work exclusively in midi and using region automation.

Now that you can have 2 different automation value on the same tick, the step editor doesn't work like it use to. Let's say you using a cc to change articulations, use to work great. Enter one value in step editor, then later, another. The cc used to jump. Now it ramps from one value to the other which of course, can't be used for changing articulations, among a host of other parameters.