MOTUnation.com

DP update on their site now.

Whoa. I'm not in a position to DL yet. Is there a read.me or changelog anywhere?

Mostly bug fixes btw. Very few enhancements.

cuttime wrote:Whoa. I'm not in a position to DL yet. Is there a read.me or changelog anywhere?

Link to the 10.13 Read Me https://www.freqsound.com/motuuserfiles/DP1013.pdf

And of course, the one thing I was looking for, the VCA bug, hasn't been fixed.

Your friendly neighborhood Phil

dix wrote:Mostly bug fixes btw. Very few enhancements.

Yeah, pretty much says that DP11 is around the corner in virtual winter NAMM, and/or that the whole pandemic slowed down development for them.

Trying not to be disappointed, but there's a lot of performance and workflow issues with the DP10 features, Clips and the way they make it impossible to edit or instigate loops in the Tracks window, the non-integration of Clips into the regular workflow of DP, I mean the idea that a pattern container can't access the Drum editor window is just wrong. Compare this to the way that any other Clip capable DAW handles percussion and it's in last place, period.

We're on a longer cycle between upgrades these days, but it's been two years since DP10 came out, and MIDI 2.0 was introduced formally last year at NAMM, so maybe DP11 is around the corner? Matt in the webinars really sold me on there being 'great things' coming to DP, he acknowledged that MOTU knows people want MPE and Articulation mapping etc. and it sounded like he meant in updates, so my whinging is partially his fault!

Phil O wrote:And of course, the one thing I was looking for, the VCA bug, hasn't been fixed

Nor has one of my pet bugs been addressed. Constrain-dragging between tracks in the SE is still not working. I reported and had this bug confirmed within a day of the launch of DP10. It's either too obscure or more difficult to fix than I would have thought.

There's lots to celebrate in the bug-fix department with this update, but I'm starting to think I'll just need to forget about SE constrain-dragging and continue using one of the many alternatives available for this operation.

dix wrote:…Nor has one of my pet bugs been addressed. …

Yep. I'll live.

This jumped out:

"Fixed a longstanding bug where Tap Tempo was not properly
averaging user input."

Phil O wrote:And of course, the one thing I was looking for, the VCA bug, hasn't been fixed.

Your friendly neighborhood Phil

Hey Phil, could you refresh me on this one... I have always used Subgrouping, but have been trying VCAs lately, with some weird things happening. Thanks!

I salute MOTU for throwing us a bone.

Nice to see that they are doing something for us.
Not easy these days.

Good news for me is that it works.
Not sure if tap tempo is better, but that is a big one for me. Will test.

My favorite bug fix is that I can now scale the whole world without crashing.
Probably a very limited request, but that alone is worth the upgrade.

VEP bug has been fixed!!! Whew. Color me excited.

HCMarkus wrote:

Phil O wrote:And of course, the one thing I was looking for, the VCA bug, hasn't been fixed.

Your friendly neighborhood Phil

Hey Phil, could you refresh me on this one... I have always used Subgrouping, but have been trying VCAs lately, with some weird things happening. Thanks!

Sure.
Try this:
Create a track group controlled by a VCA.
Set all volume faders to zero.
Move VCA fader up/down. Everything works as expected. Yes?
Set VCA fader to zero (if it's not already there).
Open Track Groups window and repeatedly click on the "on" button (toggling groups on/off). Nothing should happen.
Now set the VCA fader to a non-zero value.
Repeatedly click on the Track Groups window "on" button. Watch the volume faders. The faders will move by the amount set by the VCA fader on each subsequent "on" click.

The same happens when you save a project with a VCA fader set to a non-zero value. When you open the project the next time, your group faders will be moved (upon opening) thus changing your mix every time you open the project.

I sent a video of this to MOTU in a tech link and the tech guy that responded was able to reproduce this behavior:

Hey Phil,

Thanks for reaching out to us!

"I may have already reproduced this, but I want to be absolutely sure before passing this along to our engineers so that they may fix this. Do you mind sending over a screen-recording of this behavior from start to finish? It will help me make sure my steps have been the same. I can also use it for additional material for the bug log in the event this is indeed a bug (sounds like it already). Please let me know!

Best,

Matt"


So there it is.
Your friendly neighborhood Phil

Phil O wrote: Sure.
Try this... So there it is.
Your friendly neighborhood Phil

OMG. I'm sure this is exactly why client and I experienced a major mix F-up last night and I went to bed at 3AM this morning.

Thank you so much for that Phil. You da' man!

It looks like maybe a side effect of the parameter publishing for VEP in 10.13 has made the audio meters work in EUCON displays!? I didn't see anything in the release notes about it so who knows. A very nice and welcome feature if you're using an Artist Mix with DP. Someone should check to see if it's started working in the iPad Eucon app. I had to delete the Control Surface driver and re-add it to make it come up. Super Cool!