Weird Logic Behavior
May 31st, 2011, 07:36
Hey y'all,
Experienced some weird Logic behavior last night. I was working on 4 orchestral string parts, Bass, Cello, Viola, Violin, 4 separate exs24 instruments set up as a group (strings), with output set to a bus, so once I get the balance I want, I can control the volume of all of them to balance it out with the rest. I have a send on each of them to add a bit of 'verb, going to another bus. And I have the output of the strings in the arrange as a track, and I was automating some changes in volume. (I know, long set-up).
Now for the strangeness. I was making changes at the very end of the piece, and I couldn't hear the difference. At the end, I wanted the strings to be more subtle, and the samples kind of swell, so I was taking them down fairly dramatically at the end, and I couldn't hear it. So I took them all the way out, i.e. pulled the automation node on the track all the way down, just to see. And yep, I could still hear them. I checked all my routing, thinking I must have something going somewhere, or I'd bounced the strings to a track and hid it and forgotten about it. Just to be sure, I muted the string output track. Nope, they muted, just as expected. But no matter what I did, they would not follow the track automation that I had set up. I also shut Logic down and repaired permissions, then restarted the computer, but when I opened Logic back up, it was exhibiting the same behavior.
I'm not sure if this is what fixed it, but I did a "group clutch" and took them out of group mode, and shortly after that, everything was once again working as expected, and I was able to finish my edits. It also continued to work after I reactivated the group function. So not sure how likely it was that this was actually the reason things started working again.
Any clues as to what happened here? Do I need to trash my preferences? Is this file corrupt?
Recently installed Logic update 9.1.4, on Mac OS 10.6.7, 15GB RAM on a 2 x 2.66 Intel.
Best,
M
Reply
