DP 8 feels sluggish compared to 7.24

[Shooshie]

When DP quits recognizing clicks or keys, go to a track and try Select All (Command-A). Then open a panel window (smaller title bar than a regular window) such as the Commands Window, then see if it will close with Command-W. There is a keyboard focus issue with DP8 whereby it selectively forgets keyboard commands (while remembering others). The same thing may be happening in regard to clicks, right-click, and so on. They seem related. Just give it a try when it happens, test the keyboard commands, and if they turn out to be related, please let us know.

Thanks,
Shooshie

[delcosmos]

Have you noticed that the insert buttons effectively cut in half? the right side is used for loading/changing the inserts, and the left side is for opening the plugin window and moving/copying the plugins. Thankfully, the cursor changes to indicate what zone of the button you are on. It's possible the right-click-and-hold old dropdown menu only works on one side (probably the left side, which never brings up the plugin management window). This will take some getting used to, but I'm confident that I will learn to use it effectively. I actually really like the new plugin management window.

However, contrary to all other statements, DP8 doesn't feel sluggish at all, in fact, it feels noticeably snappier than DP7. I'm working on an old DP7 project, and I haven't encountered any of the slowdowns that everyone else is talking about. In DP7, I had some terrible scrolling problems at certain zoom levels, and DP8 clears that up, so I'm happy.

I am however having keyboard shortcut problems

Are you using 32 or 64bits version?

First of all, I'm a big DP fan, really, I'm not against DP8, I really want to make this work.

I started a clean project from zero in DP at 32 bits. It started very good, everything was working great, but in the middle of the production, it started to feel sluggish, every time I opened a new plug in, you had to wait. I had to "pitch correct" a vocal track, everything was good but at some point, the beach ball appeared and I simply can't move a note at all, every time the beach ball stopped and I tried to move a note, the beach ball came back. I quitted, re opened and the behavior was the same, beach ball and impossible to move the note in the pitch editor.

Then I close DP8, opened the same session in DP7.24 and everything was perfect, everything worked fast without a problem.

That's my story, I'm using DP8 with a MAC PRO Dual Eight Core Intel Xeon 2.93, Memory: 16gb ram.

Best regards.

delcosmos.

[blue]

Looks like they recoded the "close all plugin windows" command to close ALL windows. So now, when I hit "option-close window" on a plugin to close multiple plugin windows, all my other windows close too. Bummer.

[James Steele]

Looks like they recoded the "close all plugin windows" command to close ALL windows. So now, when I hit "option-close window" on a plugin to close multiple plugin windows, all my other windows close too. Bummer.

That's unfortunate. You'll probably have to just use the keyboard shortcut instead unless MOTU changes this.

[David Polich]

I've spent a couple of hours tonight trying to determine whether DP8 is
more sluggish than DP7.24.

Tested on a couple of very track and plug-in heavy projects, went back and forth between 7.24 and DP8 (32 bit). I have to say, on both my Macs (2009 Macbook and 2010 Quadcore MacPro, both running 10.6., DP8 32 bit is NOT slower or less responsive than 7.24. Scrolling is the same for both versions of DP as well. In fact, DP8 appears to run a bit faster than 7.24, on both of my systems, and it certainly loads a project MUCH quicker than 7.24 does.

The key commands issue - I only use 9 -
Shift+A (to get the audio input meter), option+A (to change inputs and outputs), command+A (to select all), Shift+B (to get the soundbites window), command+S (to Save), Shift+C (to get the chunks window), Shift+K (to get the markers window), Shift+E (to see an event list on a track) and Shift+M (to get the mixing board). All those keycommands are working fine
for me.

I should say, I never have more than one VI instantiated at a time, ever,
and I always immediately record the VI's output as audio and then remove it. So I'm no authority on VI-heavy projects.

[blue]

Looks like they recoded the "close all plugin windows" command to close ALL windows. So now, when I hit "option-close window" on a plugin to close multiple plugin windows, all my other windows close too. Bummer.

That's unfortunate. You'll probably have to just use the keyboard shortcut instead unless MOTU changes this.

I'm not sure if "option-command W" ever worked on just plugins before DP8. I'll have to check. I know it doesn't work now in DP8. For now I'll just have to close plugin windows one at a time. I'm hoping this was just on oversight and not deliberate.

[dewdman42]

Interesting thread. Given the number of people complaining about sluggishness, we have to acknowledge it is happening to a significant number of people. The fact that its not happening to everyone indicates hope for everyone, but Motu will have to track down these bugs and fix them. Spinning beach balls, etc. This does seem to me from all the comments like not one of the best releases MOTU has made. I'm sure it will all get resolved eventually.

Its not a big surprise to me that DP8 is suffering these kinds of problems initially. They made a big leap to cocoa, cross-platform and 64bit all in one release. All of those things can easily cause all kinds of hidden little problems and reduce stability of the software until they can slowly but surely find all the bugs and stabilize the software more. Perhaps they needed a bigger Beta program this time then was anticipated.

In any case, I will definitely hold off on DP8. I was excited to get it, but thanks to all of you for beta testing it for me!

[James Steele]

Looks like they recoded the "close all plugin windows" command to close ALL windows. So now, when I hit "option-close window" on a plugin to close multiple plugin windows, all my other windows close too. Bummer.

That's unfortunate. You'll probably have to just use the keyboard shortcut instead unless MOTU changes this.

I'm not sure if "option-command W" ever worked on just plugins before DP8. I'll have to check. I know it doesn't work now in DP8. For now I'll just have to close plugin windows one at a time. I'm hoping this was just on oversight and not deliberate.

That's not the correct shortcut to close just effects windows.

[Gravity Jim]

I am not experiencing any kind of sluggishness on my system, for what it's worth. Running in 64-bit mode under OS X 10.7.5, it feels very snappy, with controls responding instantly and no lag in screen redraws or, well, anything really. On my machine, it's cruising.

[tommypenngotti]

It's definitely more sluggish ! Only time it looks good is when I minimize the entire left side , then my right side (mixer) snaps to life. Buffer size does nothing .

Help Motu!!??

[red1]

I'm running 64bit, it's sluggish for me. Plug-in windows seem to jitter and lag a little and it's really obvious when using Expose. It's pretty annoying.

Makes me wonder what's going on under the hood and if audio is being affected, too.

I'm running OS 10.6.8, 2x3 Ghz Quad Intel, 10 Gig ram.

[Dan Worley]

Looks like they recoded the "close all plugin windows" command to close ALL windows. So now, when I hit "option-close window" on a plugin to close multiple plugin windows, all my other windows close too. Bummer.

I know, right?

http://www.motunation.com/forum/viewtop ... 51#p435701

[tommypenngotti]

how do you toggle between 64 bit and 32bit or is it auto?

[blue]

That's not the correct shortcut to close just effects windows.

Ah, now I know why I never used a key command to close ALL plugin windows. Because I never realized there was one. Thanks for the heads up.

For those who want to know, the command is "shift-control-command w." A bit of a handful, but certainly better than closing plugs one at a time.

[James Steele]

That's not the correct shortcut to close just effects windows.

Ah, now I know why I never used a key command to close ALL plugin windows. Because I never realized there was one. Thanks for the heads up.

For those who want to know, the command is "shift-control-command w." A bit of a handful, but certainly better than closing plugs one at a time.

It IS reassignable. If you find yourself using it a lot, maybe you have a spare F key on your keyboard. I have one of those keyboards that goes up to F19, so I have some frequently used shortcuts set up on those upper F keys.