What's new

Now here...MOTU DP11

They keep on saying they plan to post them, but yes, they want to edit them for content. The ones with professional guests also have expletives and trash talk on other famous people. More than once Matt used the beta to do the demo and crashed the program, so that sort of thing would be edited out.
 
I understand the need to edit content for the reasons listed above, but I don't understand why MOTU doesn't chip away at the list to make more webinars available.

For cryin' out loud, Club Cubase events over three hours long per session with some awkward moments are made available immediately after the live stream.
 
I understand the need to edit content for the reasons listed above, but I don't understand why MOTU doesn't chip away at the list to make more webinars available.

For cryin' out loud, Club Cubase events over three hours long per session with some awkward moments are made available immediately after the live stream.
Besides the valuable knowledge that these webinars could offer to the eager user base the marketing opportunity MOTU isn’t taking advantage of seems like a complete oversight and borders on baffling.
 
Besides the valuable knowledge that these webinars could offer to the eager user base the marketing opportunity MOTU isn’t taking advantage of seems like a complete oversight and borders on baffling.
It doesn't border there, it crossed that line when they stopped doing webinars at the exact moment DP11 came out. Plus not releasing but four webinars. They shoot themselves in the foot IMO.
 
The fact is DP11's release was kind of kept quiet, the press releases came out after we heard about it.

And the roll out to the trade was rather slow take up too. In the meantime other DAW developers were quick off the mark about the same time, with the usual blaze of fanfare.
 
Has anyone fully tested this on Windows 10? Is it stable enough?
Just based on chunks & the articulation maps negative delay options alone I'm ready to switch from cubase 11!
Does Motu offer competitive crossgrades?
 
There’s a 30 day demo of DP11 on their site, enough time to work out configuration and see if your plugins etc. are compatible with DP11. Cross grade is $399, but I’ve seen it for sale used for $200 often enough.
 
Has anyone fully tested this on Windows 10? Is it stable enough?
Just based on chunks & the articulation maps negative delay options alone I'm ready to switch from cubase 11!
I have DP11 here on Win10. It is stable. The only negative with DP on Windows that has been there since the beginning, is that it isn't as snappy as Cubase, especially with large templates. Scrolling through the mixer can be a chore, and navigating, starting and stopping playback can have some noticeable lags. This is not plugin compensation or buffer related (i.e. anything the user can solve). It may be graphics, or just DP not being as optimized for Windows. My video card is more than sufficient. I've tested it many times trying to find ways to improve DP's responsiveness with large templates, using identical plugins, routing, VEP connections as I have in Cubase, and even using alternate reverbs, and routing approaches/simplifications that seem more efficient in DP specifically.

Busses and VEPro connections (VRack or within a Sequence, doesn't matter) seem to be the main culprits for DP, where Cubase scrolls effortlessly and responds quickly with exactly the same template configuration (I duplicated my template in both to compare). I still like a lot about DP, but it just doesn't feel smooth and responsive on Windows (8 or 10). I am curious if it is better in that regard on OSX.
 
Last edited:
I have DP11 here on Win10. It is stable. The only negative with DP on Windows that has been there since the beginning, is that it isn't as snappy as Cubase, especially with large templates. Scrolling through the mixer can be a chore, and navigating, starting and stopping playback can have some noticeable lags. This is not plugin compensation or buffer related (i.e. anything the user can solve). It may be graphics, or just DP not being as optimized for Windows. My video card is more than sufficient. I've tested it many times trying to find ways to improve DP's responsiveness with large templates, using identical plugins, routing, VEP connections as I have in Cubase, and even using alternate reverbs, and routing approaches/simplifications that seem more efficient in DP specifically.

Busses and VEPro connections (VRack or within a Sequence, doesn't matter) seem to be the main culprits for DP, where Cubase scrolls effortlessly and responds quickly with exactly the same template configuration (I duplicated my template in both to compare). I still like a lot about DP, but it just doesn't feel smooth and responsive on Windows (8 or 10). I am curious if it is better in that regard on OSX.
curious, does Vienna publish a MAS VEP plug in for Windows? if not that could help, what with 0ver 700 possible MIDI tracks to the server..
 
I am curious if it is better in that regard on OSX.

I haven't had those kinds of issues on OSX. I encourage you to try to work with MOTU tech support to see if its resolvable, or often not that could get attention for fixes to the software. DP was only brought to windows a few years back...for decades it was a MacOS only product. what are the specs of your Windows machine in terms of CPU, GPU and memory, etc.?
 
curious, does Vienna publish a MAS VEP plug in for Windows? if not that could help, what with 0ver 700 possible MIDI tracks to the server..
Yes. I use the MAS version exclusively. I even tested with only MAS plugins. It's simply a matter of project size. I just tested with 500 midi tracks, and switching between the Tracks and Sequence editors is slow. Opening the mixer is very slow, as is scrolling through tracks in the Mixer. Scrolling the Tracks window is fine.
 
I haven't had those kinds of issues on OSX. I encourage you to try to work with MOTU tech support to see if its resolvable, or often not that could get attention for fixes to the software. DP was only brought to windows a few years back...for decades it was a MacOS only product. what are the specs of your Windows machine in terms of CPU, GPU and memory, etc.?
I have reported several issues to MOTU, including this one a few versions back. I'll contact them again and see what might come of it. The system is an i7, 64G ram, GTX 960 card (2G VRam). It's plenty for Cubase, ProTools, etc, so this sluggishness could be unique to Windows, or Windows plus some system element neither MOTU or I am aware of.

I see you have a MacPro 5.1. If it runs well there, then this is likely Windows related, not system. My i7 is comparable (6 physical cores, 12 virtual, 3.6GHz). I would be curious to see how a new M1 (even with only 16G Ram) performs with DP11 and VEPro linked to external slave PCs. If it is fast and responsive, that could be an option, at least for some looking to switch to DP.
 
Ok I take it back. I just create quickly a 500 track project.... first of all switching between tabs in the consolidated window takes a very long time. its like DP is rendering a lot of stuff before it will switch. Secondly I can't even scroll the mixer at all.

So whatever is going on, is not just Windows. And I view this as fairly serious if you are in need of large templates.
 
I have reported several issues to MOTU, including this one a few versions back. I'll contact them again and see what might come of it. The system is an i7, 64G ram, GTX 960 card (2G VRam). It's plenty for Cubase, ProTools, etc, so this sluggishness could be unique to Windows, or Windows plus some system element neither MOTU or I am aware of.

I see you have a MacPro 5.1. If it runs well there, then this is likely Windows related, not system. My i7 is comparable (6 physical cores, 12 virtual, 3.6GHz). I would be curious to see how a new M1 (even with only 16G Ram) performs with DP11 and VEPro linked to external slave PCs. If it is fast and responsive, that could be an option, at least for some looking to switch to DP.
It could be your video card. the only beyond OS difference I see is I’ve got the RX 580 8gb, maybe take a look at GPU resources?
 
MW did you try to create a 500 track project? I immediately had similar results even with just 500 empty tracks... I also have the RX580. I don't think that's the issue.
 
Top Bottom