How many Audio products disavow DP?

[Timeline]

Sadly today I was told by UA Does not support DP. (see below redacted response)

****************

Mar 22, 5:35 AM PDT

Mornoing, Gary.

I'm not sure when we stopped supporting DP, but I've been with ** for about a year and for at least the previous 3-4 years I don't believe ** has supported Digital Performer. I always reference the DAW Compatibility ** article to determine what is supported and tested/known to work.

Sorry to be the bearer of bad news! I will log into your account and remove the newsletter subscription for you as well.
Best Regards,

********
Customer Support

When Antaries disavowed DP I was pissed but find I can get around the issues.

How many more companies will throw MOTU under the buss and why is this happening?
As I told UA the other day please remove me from your system as I will not be buying plugs for the foreseeable future.

I don't get it. Who is not playing nice with compatibility and getting along? I have been with MOTU products now since the late '90s and dislike finding myself with a DAW that is being pushed away from the industry especially now that it works so well for me. Who is responsible for this ???

Answers are needed here....

Gary rant Audio Engineer/Producer/Writer

[Gravity Jim]

When a plug-in maker says they "don't support" DP, they just mean they don't test their products inside DP. It doesn't mean they don't work.

The reason they seem to ignore us is that there just aren't that many of us, compared to users of other cheaper and more accessible DAWs.

[Michael Canavan]

More or less what Jim said. Although I'm much more likely to throw money at companies like VSL, Audio Ease, and the like that actually make a MAS version specifically for DP, and less likely to throw money at companies that do not actively support DP.

DP on OSX isn't actively supported by many plug in developers I would guess, them assuming most of us are using AU still, but I mostly use VST and have little issues.

[Timeline]

Thats interesting. I had contacted UA because precision De-sser crashed DP when inserting it and selecting split while it was in play. They told me then. I'm using 9.52. I guess I need to upgrade so I cam implement VST better.

[Michael Canavan]

Thats interesting. I had contacted UA because precision De-sser crashed DP when inserting it and selecting split while it was in play. They told me then. I'm using 9.52. I guess I need to upgrade so I cam implement VST better.

In my experience it's case by case though. Slate Trigger crashes VST validation and works as AU, same with Metric Halo Transient Control. So I use the AU versions. This is an advantage of having both AU and VST, although third party plug in developers aren't using DP specifically to test AU and VST they are using Logic and Cubase for that purpose for sure. So if MOTU come close to those DAWs level of support for the plug in formats you're going to be fine. I would guess in general developers are testing only on Logic, Cubase and Live. DP is not alone in terms of not being directly tested for.

[Timeline]

Thanks Michael.

[mikehalloran]

...an advantage of having both AU and VST...

To my knowledge, Antares has never supported DP. Can’t drop support when it never existed. In reality, Autotune works as a plugin but automation is not fully functional. Perhaps with VST3 support in DP10, that may change—who knows—but that’s why they say test first.

I find that, on the extremely rare occasions I want to automate AT, that Logic Pro makes a good stand-alone host for $199. By “extremely rare”, I mean almost never but it’s the client’s dime...

[Timeline]

Hi Mike.
Yea I never use the auto functions of AT. Didn't know that about them never supporting DP.

Thanks for the tip. Cheers, GB

[Schweats]

Another example of a lack of integration , I think…

I'm not having any luck with integrating my brand new Native Instruments Kontrol S61 mk 2 MIDI keyboard controller… If anyone has been successful with integrating this controller inside DP 9.x please let me know…… The controller works perfectly in stand alone mode but not inside of DP - Many TIA
Schweats

p.s. I've searched the Native Instruments site with no info for integrating DP only for Ableton, Logic , Cubase, PT … AND I have found no place on the website for tech support that would handle questions via email …

[Timeline]

Yea were witnessing the freeze out it seems. Maybe MOTU should at the least test some of the big VI's and report compatibility. They won't I would guess. Kontakt 5-6 seems good here though. I'm running a MIDI MOTU interface though, not USB although USB works but adds a double note so I don't use it.

[terrybritton]

Another example of a lack of integration , I think…

I'm not having any luck with integrating my brand new Native Instruments Kontrol S61 mk 2 MIDI keyboard controller… If anyone has been successful with integrating this controller inside DP 9.x please let me know…… The controller works perfectly in stand alone mode but not inside of DP - Many TIA
Schweats

I would not bring up NI as an 'example' to cite the lack of industry support for DP. They do not even support the Mackie MCU standard (yet! - they say they will), and the 'integrations' they provide for the few DAWs they've provided scripts for vary widely in the item count of what you can do from the keyboard on a NI device. Still, what you CAN do from the surface when hooked up through Komplete Kontrol or Maschine is awesome - a dream come true for many of us.

If you want total integration with a NI keyboard, you buy the keyboard and then use one of the DAWs they support. They aren't 'locking out' DP - they are simply being VERY slow to roll out the integrations at all. (Bitwig, Harrison Mixbus, Samplitude/Sequoia, Studio One, FL Studio, and many others feel just as 'locked out' as we DP folks do!)

I think it is a case-by-case kind of thing where you look at manufacturers and plugin makers individually and see what they've done or not done to provide universal support across all DAWs.

I keep a full wireless computer keyboard (one with a keypad) on top of my NI S-88 to control DP with. The keypad handles most of the transport needs, and the DP built-in and/or custom single-key and modifier-plus-key commands fill just about every need imaginable. I don't NEED NI's play and record buttons to work on my DP transport, and am not interested in holding my breath waiting for NI to give me Mackie Universal support.

(I am a Native Instruments beta tester for their Komplete Kontrol and Maschine software and also beta-tested the S-49 MK-2 49-key keyboard offering before it was released. I respect that company greatly, but EVERYONE on the beta team is a bit frustrated at times by the glacial pace of new requested improvements being released sometimes!)

p.s. I've searched the Native Instruments site with no info for integrating DP only for Ableton, Logic , Cubase, PT … AND I have found no place on the website for tech support that would handle questions via email …

NI has always done all their individual support - in conjunction with the larger community helping out - via the forums. They also rely upon a knowledge base and expect you to search there. See https://support.native-instruments.com/hc/en-us

Terry

[Michael Canavan]

Another example of a lack of integration , I think…

I'm not having any luck with integrating my brand new Native Instruments Kontrol S61 mk 2 MIDI keyboard controller… If anyone has been successful with integrating this controller inside DP 9.x please let me know…… The controller works perfectly in stand alone mode but not inside of DP - Many TIA
Schweats

p.s. I've searched the Native Instruments site with no info for integrating DP only for Ableton, Logic , Cubase, PT … AND I have found no place on the website for tech support that would handle questions via email …

This is probably the same limitation that Arturia, AKAI and other MIDI keyboard controllers with transport controls are experiencing. They mostly use MMC (I do not know if NI do), which is "partially" supported by DP. DP can send transport controls via USB and MIDI etc. but it cannot receive them via USB, the workaround in AKAI is to use the MIDI outs instead of USB out and Clockworks with a MOTU interface to receive MMC and send it to DP. <--- This is more or less how it works, I'll dig up a thread on Gearslutz I saw soon on this.

Anyway, in the case of Arturia and AKAI, it's a DP limitation, not necessarily the controller keyboards that are limited... DP supports Mackie and Eucon for transport controls. Maybe one of these years they address this with their MMC support.

[MIDI Life Crisis]

dis·a·vow
VERB
deny any responsibility or support for.

And maybe that's a sign that these companies have their heads up their butts.

straw man

NOUN
strawman
an intentionally misrepresented proposition that is set up because it is easier to defeat than an opponent's real argument.

[Michael Canavan]

Here's the gearslutz thread on transport control in MIDI keyboards and DP.
https://www.gearslutz.com/board/motu-di ... hlight=mmc
Would love MOTU to start supporting MIDI controllers more. IMO it's as much up to the DAW developers as it is up to the hardware manufacturers. Bitwig gets some great end user support for control surfaces because they use Java and open up the controller sdk for end users. This guy develops some insane levels of control surface support for Bitwig and other DAWs he uses.
http://www.mossgrabers.de/Software/Software.html

It's IMO one area of DP that's pretty disappointing, Mackie and HUI support is nice, but it would be cool to see MOTU spend some time getting a better modern control surface support setup going in DP.