DP9 Not Remembering Fader settings for MIDI tracks

[Killahurts]

I honestly can't tell if this has been covered in the two or three threads about MIDI volume already, but my problem is simple- DP does not remember where I set the fader for MIDI tracks. If I set a fader to, say, 74, when I reopen the project, it will play at 127, even though the fader still displays 74. If I nudge the fader, it instantly goes to the correct volume. I have automation turned off. The VIs are in a V-Rack. There is cc information in some of the tracks, but they should not affect the actual track fader.

I've tried a couple things mentioned here with Event Chasing and Automation setup, but they don't appear to work for me. From my point of view as it stands, it's a bug, because why would you not want the fader to maintain control of the volume in any circumstance? Am I missing something?

Really frustrating because I'm mixing an album right now and I have to reset most of the MIDI levels with every song.

[Killahurts]

I should add that it just happened again, this time with a track that has no cc information.

[MIDI Life Crisis]

In my recent experience DP doesn't remember I've recorded tracks (MIDI and audio). They will disappear in the middle of a session. Perhaps DP 9 has a memory leak of some sort?

[Killahurts]

That's happened to me too lately, first thought it was that I didn't have it selected or something, but that's not it. Going to the TO and double-clicking on it, brought it back in the SE.

[MIDI Life Crisis]

You're the first to confirm this. We should both report it to MOTU. I will. Maybe they'll see this as well. I'll reference it and my other thread in techlink. If you want to see that search for "disappearing tracks."

[HCMarkus]

This could explain… from Magic Dave:

In DP9, the Event Chasing preference has been changed to enable volume and pan to be sent from the mixer each time you press play. This happens whether you have volume and pan automation in the track or not. If you want to mix your VI instruments from within the VI, go to the DP Setup menu>Event Chasing, and disable CC#7 (volume) and CC#10 (Pan).

Dave

[Killahurts]

Tried that, didn't work. Besides, if it's sending volume and pan from the mixer, wouldn't it give me the correct fader setting? For me, this only happens when I first pull up a project.. once I "toggle" the faders, they are normal for the whole session, until I open it again.

Since I'm mixing on a tight schedule, I'm doing a volume automation overwrite for each MIDI track. Apparently, the damn thing insists on having it just so the volume will stay put.

[MIDI Life Crisis]

You could use snapshots, no? It's an extra step but it should work.

[Killahurts]

You could use snapshots, no? It's an extra step but it should work.

Hate 'em.

[MIDI Life Crisis]

Me too. It's only a workaround until it gets fixed.

[toodamnhip]

DP 9 has had various not ready for prime time” issues. I have also noticed that when in “touch” mode, the MIDI faders tend not to snap back to correct positions when letting go of them. Sometimes they do, sometimes they don’t. If theres an upcoming CHANGE to MIDI volume, the faders will indeed snap back to it. But let’s say you were at 100, grabbed a fader in touch, pulled it down to 50 and then let go? That fader will often NOT go back to 100 until replay.

Also, there’s been more of the problem of MIDI notes ceasing to play/dropping out, when automating MIDI volume. There is definitely something going on under the hood with faders and MIDI.

It has been quite awhile since an update to DP 9. I would rather MOTU release smaller updates or “hot fixes”, than to go months without an update. Maybe it’s not possible but some companies do release hot fixes.

[Michael Canavan]

It has been quite awhile since an update to DP 9. I would rather MOTU release smaller updates or “hot fixes”, than to go months without an update. Maybe it’s not possible but some companies do release hot fixes.

Agreed, I haven't had every problem you guys are getting, though I get a lot of crash on opening DP crash on quitting.... and it's hard to trouble shoot a MIDI fader issue when it seems the change in behavior also included a bug..

[jimmy330]

This could explain… from Magic Dave:

In DP9, the Event Chasing preference has been changed to enable volume and pan to be sent from the mixer each time you press play. This happens whether you have volume and pan automation in the track or not. If you want to mix your VI instruments from within the VI, go to the DP Setup menu>Event Chasing, and disable CC#7 (volume) and CC#10 (Pan).

Dave

THANK YOU!!! This did the trick for me! There are 2 other treads about this situation...there's no easy way to phrase the question so a lot of people can't find the proper thread. I discovered this when using Spectrasonics Stylus, (Stylus mixer kept resetting Vol & Pan to full & 12 o'clock), then while sussing it out I discovered it was happening in all Spectrasonic, Kontakt, RealGuitar, even MOTU VI's. However Ivory & EZdrummer were not affected. Happens with new and old projects, with or without data... really annoying, only work around was messing with MIDI faders in DP (which I never touch when working). I can't see the purpose of this new change from DP8 to DP9, can someone from MOTU explain why they did this?

[Tobor]

Thanks for the info! Driving me nuts for quite a while as well, was avoiding my Kontakt instruments because I couldn't figure out how to disable the 'feature'. Also noticed the odd volume jumps in Omni and thought my mixing skills must be eroding dramatically.

[Killahurts]

Finished mixing the album. I ended up working around this problem by toggling the MIDI faders and then doing an automation overwrite of just the faders. That stuck, though it was a huge time waster. The disappearing tracks slowed me down too, I'm gonna report it to MOTU like MLC said.

I uncovered a lot of problems with DP9 while mixing this record, most of which I didn't notice while tracking, or when I mixed the big video back in the summer.. it's like there are new issues arriving daily. I tried reinstalling DP, to see if it might have been corrupted, but it changed nothing..