What has happened to DP

[James Steele]

By the way... I have to recognize of course that without a common plugin standard, DAWproject would be very limited. I'd almost be happy with a better OMF. I haven't had time, but I've wanted to dedicate a day to figuring out a procedure from going from a DP Project to Pro Tools project (and likely vice versa) that's as painless as possible. Accepting that there will be pain and it will involve multiple steps. I don't want to have to just print all the audio from the same point and drag WAV files.

[stubbsonic]

I would love to see forward movement on CLAP and MIDI 2.0.

Both are addressing ancient short-comings, and will propel many new tools, powers/features.

[James Steele]

I would love to see forward movement on CLAP and MIDI 2.0.

Both are addressing ancient short-comings, and will propel many new tools, powers/features.

I'm not so stoked about MIDI 2.0. MIDI 1.0 has done the job for me. I would just LOVE true seamless project portability between DAWs one day, but that feels like a pipe dream.

[Michael Canavan]

I'm not as excited about CLAP. I could be totally wrong, but I don't see it ever catching on in widespread use. Apple has their own Audio Units.... Steinberg/Yahama has VST3... there's a "Not Invented Here" mentality often times and no incentive for these large corporations to go to an open standard.

I get that, the good part about CLAP is it's built to be a better initial format to code in than VST or AU are. The idea is that plugin developers have at this point to code for two entirely different architectures with VST and AU, never mind AAX, with CLAP it's set up initially with the idea of portability in mind, so developers code for it first, then a set of tools helps them quickly port to AU and VST, possibly even AAX. Right now all three plugin formats are so completely different, and not at all interested in coming up with a common architecture so developers have an easier time. So it really won't matter if Pro Tools, Cubase and Logic don't ever support CLAP, if the developers use it as a framework to to port it, and the DAWs like DP, Studio One, Live, Reaper etc. do support it directly. It might be the first time another format makes their lives easier not harder.
So IMO it will win out by being a logical developer choice, and it does have serious advantages. You can add LFO's and ADSR's etc. to a plugin, polyphonically. What this means in practice is any decent synth plugin can get ADSR support beyond it's given parameters, same with FX.

I have to recognize of course that without a common plugin standard, DAWproject would be very limited.

VST3 does work, it's just in my experience the most likely in DP to fail plugin evaluation and in any DAW to be unstable.
CLAP IMO should have happened right away when Apple announced AU, we would be talking about different things.

[James Steele]

VST3 does work, it's just in my experience the most likely in DP to fail plugin evaluation and in any DAW to be unstable.

Yes you may be right. I wouldn’t know because I seldom use VST3 except in instances where it is preferred like with Console 1 or Melodyne. I’ve also had some cases where AU was actually problematic and the VST3 worked when it didn’t.

[nk_e]

I am very hopeful about DAWproject. I didn't know about it. I think it would be wonderful to be able to seamlessly move a project from DAW to DAW and utilize the strengths of each one. For example, compose in DP... move to Pro Tools for mixdown, etc.

I’ve played around a bit with using DAWproject with StudioOne and Bitwig. It is surprisingly and pleasingly capable even at this early stage. MIDI, audio, common plugins and their settings, automation, some simple routings like sends (iirc), tempo, and a few other things port over.

I really hope manufacturers embrace it, though it’s easy to see why they would not. Proprietary project formats creates more friction to using more than one DAW. Wrong, short-sighted and silly, but that’s never stopped anybody before..