DP 10.1 out

[wonder]

Pinch zoom on the trackpad will speed things up for those of us who gave up using a potato (I mean mouse - I meant potato) for a MTP2.

Yep, I can’t imagine ever using a mouse again. The Magic Trackpad 2 is an incredible piece of hardware.

are you still using the Raven?

[Helen]

Well, that's a drag.

My comp is saying 18% total processor usage, but DP is saying it's maxed out. About half the cores aren't even being utilized. I'll never understand the DP processor meter, or why it doesn't use all available cores.

And thus it has always been.

Yes, it’s been like this as long as there has been a cpu meter. I don’t understand why it’s not fixed.

We need to do the metering trick we used 40+ years ago. Just put tape over the stinking DP CPU meter so we cant see it. Anyone got any digital masking tape?

Isn’t it possible to hide the CPU meter as part of the Preferences?

[Phil O]

Hey there Phil. Are your templates created as DP templates, or just regular DP files you have built from scratch and are using as a template? Thanks

DP templates.

[bayswater]

“Pinch to zoom” on my Magic Trackpad (1st gen) isn’t working. It should, per page 331 of the User Guide.

Anyone getting this to work?

No. I spend ages getting a TrackPad working because of this, only to find it doesn't work in DP.

UPDATE: working now. I was mucking around with various setting, and must have done something to get it working. Don't know what it could be. (It's a Trackpad 2, btw)

AND: Shift Drag and Shift Alt Drag to move or copy an object with movement constrained to the direction of the initial movement is also working. I notice you have to press the modifier keys a fraction of a second before clicking on the object.

[MIDI Life Crisis]

Pinch zoom is working on my MTP2

[rawrooo]

It seems from a number of the posts here that processor usage is higher with 10.1, such as:

10.1 takes longer to load my (fairly big) template. Also moving tracks and folders takes longer as well, including spinning balls. None of that happened before in 10.01 and 9.52

Is anyone else seeing higher CPU usage on 10.1?

I just updated from 9.5x, and a tune I was working on is now choking, when it wasn't before. Nothing else has changed in the system or sequence.

Granted, this particular tune was close to maxing out at 2048 buffer size, but on 10.1, it just barfs unless I turn off the absurdly CPU spendy IK tape machines. It played fine before.

Anyone else seeing this?

Yes. Enabling MachFive3 maxed the CPU meter and made the cursor jerky.

Also there seems to be some plugin issues:

Since MAS plug-ins have been moved, how are they recognized by an earlier version of D.P. ?

I have what may be my first (and second) DP10.1 problem, 100% solved for me going back to 10.01 ( I renamed the old version before installing) I have a ton of UAD plugs on a project that are now getting disabled due to how they are allocated per DSP

1) Can anyone confirm that despite the attempts at speeding up the app 10.1 is more processor intensive than 10.01 overall?

2) Can anyone else confirm that UAD's aren't working well with 10.1? I'm using an Apollo Twin Duo Thunderbolt on a 2015 iMac, os 10.13.6

3) About the MAS plugins, i dont use them too often but they do get used. How will 10.1 respond when trying to open a 10.01 (or DP 8.07 I think it was? I never installed 9, went right from 8.07 to 10) file that uses MAS plugins?

[corbo-billy]

2) Can anyone else confirm that UAD's aren't working well with 10.1? I'm using an Apollo Twin Duo Thunderbolt on a 2015 iMac, os 10.13.6

I have just two PCI-express UAD_2 Quad & Duo cards and the UAD PLug-ins are working fine, at home .

[mrgkeys]

It seems from a number of the posts here that processor usage is higher with 10.1, such as:

10.1 takes longer to load my (fairly big) template. Also moving tracks and folders takes longer as well, including spinning balls. None of that happened before in 10.01 and 9.52

Is anyone else seeing higher CPU usage on 10.1?

I just updated from 9.5x, and a tune I was working on is now choking, when it wasn't before. Nothing else has changed in the system or sequence.

Granted, this particular tune was close to maxing out at 2048 buffer size, but on 10.1, it just barfs unless I turn off the absurdly CPU spendy IK tape machines. It played fine before.

Anyone else seeing this?

Yes. Enabling MachFive3 maxed the CPU meter and made the cursor jerky.

Also there seems to be some plugin issues:

Since MAS plug-ins have been moved, how are they recognized by an earlier version of D.P. ?

I have what may be my first (and second) DP10.1 problem, 100% solved for me going back to 10.01 ( I renamed the old version before installing) I have a ton of UAD plugs on a project that are now getting disabled due to how they are allocated per DSP

1) Can anyone confirm that despite the attempts at speeding up the app 10.1 is more processor intensive than 10.01 overall?

2) Can anyone else confirm that UAD's aren't working well with 10.1? I'm using an Apollo Twin Duo Thunderbolt on a 2015 iMac, os 10.13.6

3) About the MAS plugins, i dont use them too often but they do get used. How will 10.1 respond when trying to open a 10.01 (or DP 8.07 I think it was? I never installed 9, went right from 8.07 to 10) file that uses MAS plugins?

I can't see any overall processor usage increase at all, if anything, my PreGen instability seems to have gone away. I got that same project to load my UAD plugins by moving 2 instances of Capital Chambers all the way to the left in the mixer so that they loaded first and then had additional room to load smaller plugins on the same UAD chip. This is a problem from UAD, there's no way to manually configure which plugins go to which chip.. it's frustrating to have 20 DSP chips of UAD and having the meter max out at 31% because they won't do smart loading of their plugins. Why this just popped up on 10.1? I don't know. I popped back to 10.01 and it loaded fine. I worked there for a while and reinstalled 10.1 and now that project opens fine in 10.1. I'm staying there for the time being. Just having the TO bug fixed is enough when you're working with 60-100 tracks and 100 busses. And the scrolling!!!!! It's sooo good now.

[MIDI Life Crisis]

1) Can anyone confirm that despite the attempts at speeding up the app 10.1 is more processor intensive than 10.01 overall?

DP has long shown spikes in my system as long as there has been a CPU meter. It will stop things cold if you don't uncheck the preference in audio. The "workaround" is to disallow interrupting a process so you can continue to work. Not much of a workaround, but if you keep an eye on your output meters you shouldn't have any problems with delivery items. It would be nice to have a cpu clipping indicator that one could trust, but that is not something you'll find in DP. That's been a mystery to me for a long time, along with the cmd-f default key command that can send one into a tizzy. Yes, I said tizzy! lol

I won't be doing any serious work for a few weeks (when I get my piano back from the rebuilder). Around early January I'll be putting 10.1 through it's paces big time. As far as what I can see, there are some issues, but there are issues in every piece of software.

[mhschmieder]

I haven't had time to review so many pages, starting from scratch, but for some first page comments, want to help a bit by reporting that I experienced the lost plug-ins problem but it went away after a reboot of the computer. A bit of bootstrapping here and there, with some vendors not showing up initially but eventually being in the list.

Thanks for pointing out the mono-pressure bug, as I'll now know to re-track anything where I depend on that MIDI parameter for expression of any sort. That might take a bit of review as well as file rendering comparison dates vs. the previous update timeframe. I often convert it to something else anymore though, as I find most products no longer use it, so I switch it to something relevant on a per-library basis.

I've only launched DP 10.1 a few times so far, and have done a bit of rendering the past few nights, and it does seem faster to launch and more stable overall. No time yet to explore the new features; I'm playing the biggest gig of my life in a week, learning 60 songs for a sub gig that is super high-profile (that's all I'll say on the matter, in case the regular bassist becomes available and I lose the slot).

My overall impression though, is that 10.1 is what ordinarily would be a .5 release or even a major point release, with what appears to be some major infrastructure rewrites and even re-tooling of core technologies here and there as well as major upgrades to key stuff like time stretch and/or related features.

[labman]

We need to do the metering trick we used 40+ years ago. Just put tape over the stinking DP CPU meter so we cant see it. Anyone got any digital masking tape?

Isn’t it possible to hide the CPU meter as part of the Preferences?

It is ! but we need to see it for one thing..... when the dust has cleared upon loading the huge film template here. Things don't go well if we hit play prior to the huge red spike being gone. Oddly enough, in DP 10.x it usually only happens on first DP boot of the day.

[bayswater]

Anybody compare the efficiency between DP9.5 and DP10 yet?

More on this: The short answer is 10.1 is better than 10.01 is better than 9.

Using a large test project (description below), I was seeing CPU in the mid 40s with DP 10.01, and with the same project on the same system, I'm seeing mid 30s with DP 10.1. On a different system but with the same project with half the number of tracks, I saw drop in CPU from mid 60s to mid to low 50s between 9.52 and 10.01.

But this improvement seems to be mostly with the playback engine. I'm still finding a noticeable delay in the GUI updates when dragging window borders and panes around in the CW.

On CPU, it looks like DP has pretty much caught up with Logic. On the same project, Logic 10.4.8 runs in the low 30s (DP: 34%, Logic: 32%). But Logic screen updates are still faster with the same project to the point that you don't really notice them. It is a flatter colourless 2D GUI with few visual clues, so that may be the cost.

The advantages of Pre-Gen show up in this comparison. The project is on an external USB3 drive. In Logic it chokes halfway through because the disk cannot keep up. There is no such problem with DP. Copying the project to the internal SSD solves the Logic problem, and makes no difference to DP. Another Pre-Gen thing: the start times of the tracks in this project are staggered because Logic stalls if they all start at once, and playback cannot be started otherwise. DP sometimes glitches but soldiers on and gets stable quickly.

One think I didn't expect: running DP at buffers of 2048 versus 1024 made no difference to CPU. (Logic only goes up to 1024).

So: if there are flaws in DP stopping us from doing pretty much anything within reason, CPU efficiency is not one of them.

Project (this project was created to test out new Macs):
384 audio tracks playing 384 different audio files
128 MIDI tracks into 24 instances of Kontakt 5 in 2 V-Racks playing simple scales
Tracks bus through 18 Auxes to Main Out
All audio and VI tracks with one instance of 2 band EQ
Auxes with a simple compressor
Effects are the simplest versions of those packaged with the DAW

[HCMarkus]

Thanks Bays! Great news.

I just ordered a fresh SSD so I can keep my current working 9.52 system intact while paying around with 10.1.

[bayswater]

I can keep my current working 9.52 system intact while paying around with 10.1.

Always a good plan.

[HCMarkus]

I can keep my current working 9.52 system intact while playing around with 10.1.

Always a good plan.

Yes, I need to keep working, and this way, there are no concerns. Pop the old drive in and my known-good system will be back in service within seconds.