MOTUnation.com

Been messing around with it, from my experience it's not as stable as 8 yet, but not too bad.
I can crash DP9 doing things while the sequence is running, which normally in 8 would just cause a small audio hiccup at most. Mostly though it's pretty stable and once the checks clear I'll drop the $ down.
Love the 30 day demo, and since it's looking like no huge manual is coming out at least for upgrades, it's not a big deal to demo for a week or so.

With the nex MX4 version, I try to load banks from a previous version of the MX4 (I have the license and I love this Instrument) and it quits DP 9 after Import command _

bayswater wrote: I don't know if the manual has not been updated. That's what I'm asking. I suspect that particular page does not show what we are all seeing on the screen. It might be just this one thing. The Undo/Redo thing is updated, but I haven't checked any other updates.

On that note, I once asked about compiling an errata list for the manual, thinking it might be useful to new users, if not MOTU. The V7 manual had a few dozen errors, ranging from minor typos to a few total mysteries. But all I heard back was crickets.

I would LOVE to see a manual errata list. I suspect there is more than just this one thing wrong or missing from the manual. I suspect that whoever wrote the manual didn't submit for critical review by those who actually use the program. Always good to have a separate set of eyes to look over things (like having a mastering engineer do his thing instead of doing it yourself).

MIDI Life Crisis wrote:The word "bug" always appears a lot but is often misused in place of the phrases "user error" and "software conflict."

Indeed. So often "bugs" are a case of someone not understanding how to do it.

Unfortunately, doesn't always apply since the DP 9 manual is a rehash of the 8 manual with new features shoehorned in. One really needs to go to the Getting Started Guide where things are often more accurate when the manual doesn't seem to be correct. Somehow, RTFGSG doesn't have the same ring.

I do hope that MOTU has commissioned a tech writer to do a ground up rewrite of the manual for DP 9. Probably wishful thinking.

They seem to have fixed an issue I've had where full value controller events couldn't be selected by dragging with the standard cursor in the MIDI editor. YEAH!

musicman691 wrote:

bayswater wrote:I would LOVE to see a manual errata list. I suspect there is more than just this one thing wrong or missing from the manual.

Well, I'll offer again to compile one if people are interested in sending errors they see, and there is a place to post it on Motunation.

Another oddity: in the DP8 manual, the page numbers in the contents pages acted as links you could click on to go to that page. That is not working in the DP 9 manual.

MIDI Life Crisis wrote:The word "bug" always appears a lot but is often misused in place of the phrases "user error" and "software conflict."

Well, amen, preacher.

A bug is reproducible. If it's only happening to you and three other guys, it ain't a bug.

It's a rash.

Well bug, user error, sunspots, whatever you want to call it - I've downloaded the demo and can confirm that the drum editor crashes DP9 frequently (as mentioned in another thread). I'll wait for the sunspots to pass and try again.

On a positive note, my projects are loading faster in 9 and some graphic issues I had in 8 seem to have been resolved.

Still a lot more testing to be done.

Phil

MIDI Life Crisis wrote:

monkey man wrote:

James Steele wrote:Bunch of nonsense deleted. Carry on.

Doh!

I missed all the fun, it seems...

PM me and I'll catch you up... or knot [sic]

... says he who disabled PMs long ago...

Smarty-pants Gorilla!

Question:

I'm tempted to upgrade, but since I have a show on Friday and an album 70% done I obviously don't want to put it on my primary machine. Now, will activating 9 affect 8 activations, since it's an upgrade? We get two activations, I think. If install 9 on my test machine and run it through paces will it deactivate, or mark for deactivation the next time it checks, one or both of the 8 installs? Will we be able to activate an 8 install once we upgrade? I ask mainly because some of us like to keep important stuff in the previous version until we know the early bugs are squashed, even if they are few and far between. The upgrade to 6 still weighs heavily on me.

I was able to activate the demo on two Macs without losing either DP 8 activation. Activating 8 didn't remove 7, and there are many who bought 9 and can use it and 8 on the same partition, so you'd have to assume you can have both going at once. But 9.00 has to be risky if you depend on DP for a show.

bayswater wrote:I was able to activate the demo on two Macs without losing either DP 8 activation. Activating 8 didn't remove 7, and there are many who bought 9 and can use it and 8 on the same partition, so you'd have to assume you can have both going at once. But 9.00 has to be risky if you depend on DP for a show.

Yeah, that's why I wanted to install on my beater machine for a test drive. Live machine doesn't get touched unless there's at least a month window to run something new through it's paces as a part of rehearsal.

corbo-billy wrote:With the nex MX4 version, I try to load banks from a previous version of the MX4 (I have the license and I love this Instrument) and it quits DP 9 after Import command _

I can't offer any reason for your problem but I can say I was able to launch DP7 on my old G5, load MX4 and export all my patches. I was then able to import into MX4 in DP9 without any issues. All my old projects containing MX4 loaded just fine.