MOTUnation.com

I am having a really confusing issue with DP8. I have all the latest drivers and updates. After I've written automation in (latch), any fader moves I do just to audition changes remain permanent..that is....the fader stays where I last left it (when automation record is not on) regardless of where it was automated. This is wreaking havoc on a project I've spent months on. It doesn't seem to happen in every project. I've trashed prefs and caches, repaired permissions..........I wonder if I need to do a clean install of DP 8.
Another issue I'm having with my UAD plugs is any preset names disappear after closing and reopening the project. Any help would be much appreciated!

Does this happen with audio or MIDI?

If audio, it should behave properly once you go back to the beginning of the track - or at least back up to before where you touched the fader.

Let's say it's a two minute soundbite. You have latch on/record off. You touch the fader at the one minute mark. It will stay in place. If you back up to before the one minute mark, it should follow as if you never touched it. This is how it has always worked for me. I just verified it on a recent project in DP 8.04. Worked as it always has.

Thanks Mike, It's just audio, and unfortunately once I touch a fader it stays there regardless of where I go in the song. The weird thing is that sometimes it does not happen when the project is first opened, then starts a short while later.

That is weird.

Update your signature so we can have a clue what you are running including hardware, OS, other software that may affect DP etc.

Really weird. Signature updated.

Possible workarounds...

"Duplicate Mix" before farting around, so you can get back to where you were.

Disable automation on the track... after messing around, does re-enabling automation restore the prior automation writes?

Ok, there is one thing I'm concerned about. I can't see your screen, so I have to ask:

When you say that you're "not in record," are you referring to Automation Record? Or Track Record? Track record is what you get when you hit [Keypad "3"], or you click the "record" button in the Control Panel.

Automation Record is the little red button right above the Pan knob in the Mixing Board.

If the Automation Record button is showing red, then it's going to record every move you make while playing back the music. Automation Record is not related to Track Record, but is a separate function so you won't overwrite your music when you try to record automation.

Forgive me if this is basic info for you, and if DP is really malfunctioning, but I had to ask just in case you had a lapse of synapse and forgot that the red button in the Mixing Board cannot be on if you are going to make trial moves without recording them.

Shooshie

Also, have you checked your settings in Automation Setup?

If the Automation Record button is showing red, then it's going to record every move you make while playing back the music. Automation Record is not related to Track Record, but is a separate function so you won't overwrite your music when you try to record automation.

So basic to me that I didn't consider it when reading the OP. The things one takes for granted...

Let me add that, when the red light is blinking, Latch works as it would ordinarily but when you touch a fader, it will glow steady indicating that you are now recording. Stopping the transport or clicking on this red light will stop the record process. If you stop the transport, it will go back to blinking indicating that it is ready to record / modify your automation. This will also affect most of your effects as well - touching them while the light is blinking will enable automation for their settings in the same way.

Shooshie and everyone..thanks for the replies! Automation record is never enabled when this happens. I've been mixing in DP for 7 years now and this is a first. The only explanation I can come up with is that I inadvertently did not specify "all time" when I took the automation snapshot. I ALWAYS choose "all time"....but..........it's possible I trashed prefs/cache and was careless in not choosing the correct time range when DP restarted. Hopefully that's all it is. It's only happening on a few projects and I basically have to start those mixes over to be safe. Time will tell.......I'm grateful for this community and the help!

Ok. I had to ask; one never knows another's experience level, and you only had about 6 posts. I had to wonder if you knew, even though it's basic stuff.

Yeah, the snapshot might be the answer, and I sure hope it is. If this is a malfunction in DP — and I'm not saying it is — then it's a pretty insidious one.

Shooshie

Sorry about my earlier post, pay no attention to that man behind the curtain. I misunderstood the problem when I first read it.

Phil

Shooshie, I hope the snapshot is the culprit too, but today I wrote in some automation on an effect, and sometimes it played back with the moves I made and sometimes not. This is on a song that had no prior issues. Nothing that I can't deal with, but I am ready to get this record mixed and out of my computer . I have done EVERYTHING I know to do including a clean install from the DP disk, and still having these anomalies, but hopefully I'll move on to the next project and all will return to normal.

Can you see and edit your automation points in the sequence editor? Clearly you are experienced in DP but I'll ask the obvious question no one has asked so far...

Is the track(s) in question enabled for PLAY in the automation section (i.e.- the triangle should be green)?

I had some confusion but with the exact opposite result last year, where regardless of what I entered, the value would jump to a set value. It ended up to be a MIXER snapshot issue. Once I deleted the snapshot, all was well.

But I am most interested in whether or not you can see automation points at all.

Ok, Here's what I'm thinking:

Load your sequence(s) into a new project. I think you've got some kind of corruption going on. I haven't seen that happen — ever — and I hope I never do, but when I get one-of-a-kind problems like that, I always immediately load them into a new project. 9 times out of 10, that fixes it.

See if it fixes your problem!

Shoosh