DP11 is here!

[Michael Canavan]

I must be the only one here on an M1 Mac using VSL virtual instruments. Thank God I ran the 30-day demo before plunking down cash! DP11 will not recognise Vienna Symphony's MAS nor VST plug-ins. You will get an error message the first time you run a project which contained them indicating a long list of the instances which cannot be located. The only option is to re-assign them — one by one — to Vienna's AU plug-in.

If you revert to DP10 and open that same project, you'll get a bit of a scare to receive the same warning, but fortunately in this case DP only disabled the MAS plug-in. Re-enabling brings joy back to the world.

NOTE: If one is a glutton for punishment, one can force DP11 to run in Rosetta mode ("Get Info" in the Finder) and it will recognise the MAS/VST plug-ins. The Map Articulation only seems to work with Synchron Player using the VST plug-in which is another hassle if you've been using the MAS version all this while.

If I had paid MOTU $195 for their advertised compatibility with Apple Silicon...after the wait from November 20th without a peep from them... I would not want to be on the receiving end of THAT phone call.

The VEP plug in is not Apple Silicon compatible yet, it has to be run in Rosetta. This is on VSL not MOTU. Logic supposedly can run Rosetta plug ins in the M1 version, but nobody recommends doing it, i.e. it runs badly.

[stubbsonic]

I just saw a nice little DP11 announcement article over on CDM. It mentioned a little thing I didn't catch before now.

"Also, here’s a tiny feature with huge implications, by user demand: you can strip silence by dB threshold and not just percent. That solves a ton of workflows in a range of use cases."

That's nice to see. It's how it always should have been, but better late than never. Nice!

[Tritonemusic]

Cool! Thanks for pointing that out, Stubbsonic.

[terrybritton]

I just saw a nice little DP11 announcement article over on CDM. It mentioned a little thing I didn't catch before now.

"Also, here’s a tiny feature with huge implications, by user demand: you can strip silence by dB threshold and not just percent. That solves a ton of workflows in a range of use cases."

That's nice to see. It's how it always should have been, but better late than never. Nice!

Geesh! Weren't we just raging on about that a few years ago??? Fixed already??? What influencers we are.

Terry

[dix]

I just saw a nice little DP11 announcement article over on CDM. It mentioned a little thing I didn't catch before now.

"Also, here’s a tiny feature with huge implications, by user demand: you can strip silence by dB threshold and not just percent. That solves a ton of workflows in a range of use cases."

That's nice to see. It's how it always should have been, but better late than never. Nice!

Geesh! Weren't we just raging on about that a few years ago??? Fixed already??? What influencers we are.

Hmm. What I recall clamoring for was an indicator on the waveform that showed what the the Strip Silence threshold value was referring to (as some might remember StudioVision had). I'm not sure if dB will be much more useful than %.

Anyone spotted any other undocumented DP11 changes?

[stubbsonic]

I'm not sure if dB will be much more useful than %.

For me, dB is 100dB more useful than %.

[monkey man]

... which is 90% better in your case, Stubbsy; I'm almost 100% sure of it.

Personally, I'd love a graphic indicator that updates as one adjusts the threshold.

Realtime splitting of the soundbites according to threshold-parameter adjustments as a further indicator would be awesome too IMHO.

[Timeline]

I love the fader stretch idea but wonder if resolution follows.

[bayswater]

I love the fader stretch idea but wonder if resolution follows.

I didn't think of that. I'll have to check. Should be testable.

[Tritonemusic]

I love the fader stretch idea but wonder if resolution follows.

This.

Can't wait to hear results.

I think I'm going to get this update sooner than I thought...

[dwilliams]

Started demo. First thing I checked is does it still hang-up crash on bounce to disk. It does.

[tommymandel]

... it's not the cost, but updates for the sake of updates ... if you're sticking with DP 10 why does it have to be run in OS 11? What's wrong with 10.14?

Maybe I'm out of step with the world here, but it seems to me we should pick the software we want to run, then look for the hardware and OS that runs it -- not buy a computer because it's new and then wonder why the software we want doesn't run on it. There will alway be a few people who are forced to buy a new computer that won't run software that's more than six weeks old but that's life.

Maybe we need more complaints to Apple about why they'd make a computer that abandons existing software?

I agree (with everybody) but... with DP10 running very well here, and me not needing MPE support and having real concerns about some of my older third party plug-ins dying, I am still deciding whether I need DP11. I would have to take my 5,1 up to 10.13 from 10.12, (or maybe to 10.14 to match my 2015 laptop.) But that's as high as i want to go, Apple. Thanks for, as bayswater put it so well, denying us the ability to: pick the software we want to run, then look for the hardware and OS that runs it -- not buy a computer because it's new and then wonder why the software we want doesn't run on it.

[cuttime]

Just to be clear, as I see some confusion here and elsewhere, that DP 11 runs on Intel machines just fine (at least for me). I get the impresson that some people think they need to upgrade to an M1 Mac to run DP 11. Not so.

[tommymandel]

thanks, cuttime...yes, my post sounded like I thought that, sorry, didn't mean to.

[toodamnhip]

I still havent seen any sign of a big fix list, anyone seen one? Also, I applaud MOTU for improving articulation mapping. But does anyone here wish for a fader bank dedicated to continuous controllers? For me, dealing with controller data in VIs will never be convenient until they are translated into a fader bank so one can touch, trim and do all the automation necessary to comfortable edit CC data. That would be a fantatsic "next project" for MOTU! I never hear others speak of such a feature, but it seems to make so much sense.