Automation Reverst to Wrong Envelope
I've been searching the forum and web, and apparently can't find the appropriate keywords to search. I come up empty handed.
Sonar X2A (all Sonar plugs)
- I record band practice using a project template. This template evolves over time, but is fairly consistent from session to session. I don't often listen back while mixing down, or even after, so I was unaware of the problem for months (I do not know when it actually started, or if it goes back to an update from 8.5.3 to X1 to X2 to X2A or whatever).
- I discovered months ago that tracks 5 & 6 had a mind of their own. The fader should be around -12, but keep turning to -2.2 (as if it was reading an automation file).
- No problem right? I must've accidentally bumped a virtual fader and/or recorded some automation. But the automation lanes did not show any such moves.
- I didn't see any automation, but maybe there's something hidden in one of the plugins, so I created a new track template and copied the audio to it (less events, etc...)
- Same thing happens in the new track.
- I turn off the read enable button. The volume still does what it wants.
- I finally managed to keep the faders down by drawing a volume envelope at approx. -12 that lasted for about 3 hours of session time (average rehearsal for us). It's not exact, but it seems to put a band-aid on it and let me get back to work.
So I basically gave up. I found my workaround and worked with it for the last few months. I figure I must've recorded some piece of automation that was buried deep within the original session.
Well tonight, I finally had a chance to create a new project/session template from scratch. That ought to solve the problem once and for all. No such luck. Now track #6 keeps reverting to -38.2 (at least it's not -2.2 blowing out my speakers everytime the floor tom hits).
Any ideas? Any hidden automation envelopes I can check? The only plugs are a couple of Pro Channel modules, no sends/returns, automation read/write is currently disabled. There are probably details I've left out, or things that I've tried but can't remember.I'll update if needed.
Any guidance, or links to related threads, would be greatly appreciated. My PC(s) have always been trouble free with Sonar. I'd be incredibly disappointed if this is actually a bug (hopefully X3 will be out soon enough). Thanks, Gregg
DAW: SONAR Platinum
PC: i7-2600 @ 3.40GHz, ASUS Motherboard, 16G RAM
OS: Windows 10 Home 64-bit
I/O: MOTU 8M / MOTU 8PRE / PreSonus DigimaxLT / M-Audio Oxygen 49