What's new

Now here...MOTU DP11

Dewdman42

Senior Member
I am definitely excited about using DP11 with the new articulation mapper and chunks! Spent the past 5 days watching DP videos and all the rest.

Pretty unimpressed by their plugin scanning at the moment.
 

kgdrum

Greetings
@Dewdman42
No sure if this will help if you can’t even get DP up and running but if I know what plug-ins are not passing AU validation I will designate them to be seen as VST instead of AU.I have some AU plugins that DP will not pass or recognize I setup DP to see them as VST.
From what I’m reading part of the issue might be DP and VST3 implementation. I have only bought a few plug-ins that I’ve downloaded and installed as VST3 plug-ins and I haven’t installed 11 yet,I’m someone who will always try to wait until at least a 11.01 before upgrading.
At least with DP you have a choice between AU & VST’s,I’m sure you will get this solved, patience my friend………….
 
Last edited:

ALittleNightMusic

Former Member
How is this better than Cubase?
Chunks are a pretty unique feature and can be super handy, especially for film scoring. On the flip side, I do think the UI is more complicated to pick up than many other DAWs (just in my experience as somebody who owns and is very adept at 4-5 DAWs). They do offer a 30 day demo which is nice but I found it too much effort to re-learn workflow in DP given their unique approaches.
 

Dave Connor

Senior Member
The note velocity graphics are now similar to the way Logic represents velocity. This was implemented in DP 10.
Except that in Logic you can grab any part of the handle and move it. DP still only allows for the tiny dot to be selected which remains an excruciating mouse move. Very disappointed by that.

Also, the Option-drag of a specific number of bars at the top of the midi editing window (which then expands the window to those selected bars) has become: select-menu-scroll-click. Really puts the brakes on workflow. [Unless anyone knows how to restore that function that’s been around a long time.]
 
  • Like
Reactions: EgM

JohnG

Senior Member
DP still only allows for the tiny dot to be selected which remains an excruciating mouse move.
Dave, you can grab the note more easily in the graphic editor -- you can grab any portion of the line if you do it in the area where the cc data is (at the bottom). Alternatively, you can change the preference of the graphic editor so you can grab any part of the note in the top part too.
 

Dave Connor

Senior Member
Dave, you can grab the note more easily in the graphic editor -- you can grab any portion of the line if you do it in the area where the cc data is (at the bottom). Alternatively, you can change the preference of the graphic editor so you can grab any part of the note in the top part too.
Thanks John, I was referring to the cc area at the bottom actually. I was unable to grab the handles there - only the small square to the left of the handle. Is there a preference to change that? I couldn’t find one.

I do understand that you can select the note in the graphic editor above and drag up and down for velocity now but didn’t try it. Essentially I was trying to work in DP as I normally do to see any enhancements or drawbacks from DP 8 or 9.
 

shropshirelad

Active Member
Sadly, I have to agree with you on this point.
+1 This caused me no end of problems when first installing. MOTU Tech have suggested just running Audio Units, which I'm doing. Not ideal, esp as I can't access certain features that require VST3s. Oh & Kontakt/BBC SO etc fail VST3 validation. Useless.
 

Dewdman42

Senior Member
I personally had more trouble scanning AU’s then VST. Vst3 has been very problematic. Still working through it now. The biggest problem is that DP’s validation engine crashes easily and then does t tell you why. Trying to figure out which of your 1000 plugins is the problem is very difficult unless you literally scan them one at a time, which is very time consuming.

But the best approach is to choose either VST or AU as the primary type, it will run a full scan and probably crash a few times. I had horrible results with AU, it got stuck in some kind of crash loop. Vst however managed to scan through with only only a dozen crashes and restarts. Ten or so plugins didn’t pass but examining those one by one from the plugin manager managed to pass a few more, not quite all.

After that pick and choose a few Vst3 or AU examine on an as needed basis. These should be done only one at a time just in case it crashes so that you’ll know which plugin is the problem. Sometimes also DP seems to keep some internal list of plugins you intended to validate so later on after a crash it will keep trying to validate that list again even though you didn’t ask for it. I finally found the way around that is by hitting the “mark the rest invalid” button which somehow clears that Internal list while canceling the scan. So if you only try to examine one plugin at a time you can figure out what works and what doesn’t. It’s time consuming but using this methodical approach can get to something that works.

I have found quite a few vst3 don’t pass

Motu tech support has not been very helpful to be honest. This is an area motu should improve the product IMHO
 

Toecutter

Let's end this peacefully
Motu tech support has not been very helpful to be honest. This is an area motu should improve the product IMHO
Yep they have people complaining about the locked webinars for over a year and nothing gets done. Imagine having hundreds of hours of educational material and choosing to alienate your customers (current and prospective) after a big release like DP11. It doesn't surprise me that Sound variations aren't even mentioned on the website or manual :thumbsdown:
 

Symfoniq

Senior Member
I personally had more trouble scanning AU’s then VST. Vst3 has been very problematic. Still working through it now. The biggest problem is that DP’s validation engine crashes easily and then does t tell you why. Trying to figure out which of your 1000 plugins is the problem is very difficult unless you literally scan them one at a time, which is very time consuming.

But the best approach is to choose either VST or AU as the primary type, it will run a full scan and probably crash a few times. I had horrible results with AU, it got stuck in some kind of crash loop. Vst however managed to scan through with only only a dozen crashes and restarts. Ten or so plugins didn’t pass but examining those one by one from the plugin manager managed to pass a few more, not quite all.

After that pick and choose a few Vst3 or AU examine on an as needed basis. These should be done only one at a time just in case it crashes so that you’ll know which plugin is the problem. Sometimes also DP seems to keep some internal list of plugins you intended to validate so later on after a crash it will keep trying to validate that list again even though you didn’t ask for it. I finally found the way around that is by hitting the “mark the rest invalid” button which somehow clears that Internal list while canceling the scan. So if you only try to examine one plugin at a time you can figure out what works and what doesn’t. It’s time consuming but using this methodical approach can get to something that works.

I have found quite a few vst3 don’t pass

Motu tech support has not been very helpful to be honest. This is an area motu should improve the product IMHO
Can you turn the problem into a "binary search"? In other words, move half the plug-ins into another folder, and then scan only the first half of your plug-ins. If you still have a crash, halve the number of plug-ins in that folder again, repeating the process until you don't get a crash. Still time-consuming, no doubt, but perhaps not as much so.
 

Leigh

Member
yea, for a while I was doing that this morning, painstakingly slow since I have something like 2000 plugins to get through including all three formats... but nonetheless I can't even do that now because I can't start up DP..it just crashes and no way to get past the scanning crash... no way to tell which plugin is causing the crash, though if I wanted to scan them one at a time, presuming I am able to start over again...I could at least know which one is causing the crash...and remove it form my plugins folder...even though some of them are plugins I actually want to use, but still I could probably get through it that way, but it will take quite a lot of time to do that....
So sorry you are in such a mess. Does holding down the Shift key when starting DP help with the crashing?

**Leigh
 

Dewdman42

Senior Member
Of course but that also disables audiio. When you enable audio DP immediately resumes the same plugin scan and crashes within a few seconds
 

JohnG

Senior Member
Thanks John, I was referring to the cc area at the bottom actually. I was unable to grab the handles there - only the small square to the left of the handle. Is there a preference to change that? I couldn’t find one.
Hi Dave -- honestly I don't know how you toggle it on / off. I actually would prefer to have it off but was working on some cc data and kept inadvertently selecting notes by their "tails," so I know with v11 you can do it. Don't know how!
 

kgdrum

Greetings
One thought just occurred to me and I’m wondering if other long time DP users here agree with me. I have NEVER seen a upgrade release of DP create so much buzz and excitement and it’s not just here, I see threads in all of the forums like GS,KVR & Motunation with more posts and comments (mostly positive) than I think I’ve ever seen before for a DP release.
This looks like a very promising new chapter for MOTU,DP and DP users.
 
Last edited:

JohnG

Senior Member
I have NEVER seen a upgrade release of DP create so much buzz and excitement
Nor I. But I can see why people are happy; it's so much smoother and more nimble than anything for a long time. Loving it. Lots of little fixes and I hear from Matt LaPoint that they put in "lots of optimizations."

The notation editor adds crucial bits that mean you could create finished parts more easily from it. I use notation all the time, so that's one that appeals to me. But lots of little, thoughtful things are helping. Example: clicking on a note in the graphics editor, when you have multiple tracks open in that window, automatically selects the track. Seems obvious and maybe overdue, but really welcome.
 

Dewdman42

Senior Member
Pretty unimpressed by their plugin scanning at the moment.

For anyone following this drama or in the future looking for help, I found a solution. The trick is run DP with the following command line option:

Code:
--disable_crash_reporter

You can read more about that here if you plug your nose while visiting this forum: https://www.motunation.com/forum/viewtopic.php?f=1&t=61800&p=525976&hilit=crash+log+script#p525976

Basically disabling the crash reporter caused DP11 to not crash at all for me while scanning all my plugins. Scanned them all, top to bottom, VST, AU, VST3....no crash.

Not all passed... but pretty much all my VST/AU did. AirWindows had a problem. There are more then a couple VST3 that did not pass, like Kontakt and pretty much all of U-He, but quite a lot of VST3 did pass. But more importantly, it didn't crash, I didn't get stuck in a crash loop and it was easy, all done in a few minutes...

So my advice is, use that mode whenever scanning plugins on DP. I might actually setup DP to always launch that way so that I don't ever forget or get caught in a situation where something tries to scan and starts crashing it again. it only means that if I have a legitimate crash while using the program, MOTU won't get a report about it.

I suspect there are problems in DP's crash reporter mechanism where when plugins fail scans in some cases, it pukes up the program rather then sending a report and going on to the next plugin. This option just makes sure to scan all the plugins and ignore a report to MOTU.
 
Top Bottom