Hello (name would go here if you put it in your post like most people do), >Very strange indeed. I've got only one test track on a freshly installed >system, with no thinkable source of trouble. One sample with a >volume curve drawn on it. Everything done in the strictest default- >basic-no-tweaks way. Is your Logic device setup, set for 2 channels to & from the Live? It defaults (incorrectly) to 8 channels. Normally this would cause digital noise, rather than automation glitches, but I mention for completeness. >Well, I guess then I'm the only unlucky guy who took the time to beg >for help. Is that a smart-ass comment? >>Half second at full blast, is latency in responding to that initial zero >>volume point. Put that zero-volume half a second earlier. >Does this mean, that everything comes with a half second delay >even in the best case? >Or can it be compensated for with the Play Delay parameter? Sascha from Emagic said what the expected latencies were with Logic 4 & SB Live. If I recall it was 120 - 220 ms, but I use LAW 3.6 myself - eg I'm going out of my way to help you. I would recommend separating the automation into a separate part, on a separate track going (obviously) to the same audio channel. Then you can adjust the delay of the automation part in the part parameter box, setting a negative value to pre-delay it. And also you can extend the autoamtion to the left & set an initial value for the volume. Play delay in the audio settings affects timing of the audio sample output, which should be correct by default AFAIK. It does not compensate for automation latency. >Well, I'm not exactly getting those 128 steps. More like 50 or less for >a couple of seconds of smooth fade in. Are you fading from 0 up to maximum level (127), neutral level (90), or some lower level (maybe 50)? >It acts as if there's no change in the curve for a while, then jumps to >another value, which ISN'T the value drawn at that point. Not even >close.. At this stage you still haven't separated the expected latency from your problem behaviour. Test a sudden volume transition, eg from level 50 to 90, without cycle mode & starting play well before the transition. >The behaviour I described is how the native audio engine works. It's >not very good for automation. Emagic said they were working on >automation for next release (maybe 4.1 or something). >Where can I read that Emagic statement? I'd like to know what this >"not very good" means in practice. Try OneList archives, statement was made by Thorsten Adams from Emagic. There is no further detail to this statement. http://www.onelist.com/archive/logic-users >This is completely unusable. I need a card that has the same >features as SB Live without the problems, which, according to >Emagic, shouldn't exist; SB Live is COMPATIBLE. While you're at the archives have a look for a post from me, discussing the SB Live card. There are a few tips I mentioned which may be of assistance in other areas. >So what is the source of all this trouble? What should I try? Move the >card to another slot? Try with another SB Live? I guess I have to go >and install everything on another PC to see if the problem is my >motherboard. If Logic plays audio fine without automation, and the problem is not latency, and is not caused by cycling or starting play too near the automation events, then it would presumably be Logic misbehaving. Since Logic automates better on other people's systems, and I believe there are a number of users on version 4 with the SB Live!, maybe the installation is corrupt. Check the version of Logic, try re-installing, then try installing Logic & your Live! on another machine. >Has Emagic used audio automation with SB Live with no problems? Can someone else confirm that this works? Emagic are generally silent re audio on this list. Cheers, Thomas