DP 7.2 is out ! !

[HCMarkus]

I am a big pill, and am thus terribly insulted by your comment.

Love DP 7.2 though.

[wylie1]

Thank you MOTU.
Looks like we've got some new smiles as well.
Thanx James.

[toodamnhip]

Boom!

Loaded 7.2 today and have not been able to bring it up unless I skip loading Ethno.

This is on a Mac recently upgraded to 10.6.4. Just noticed that Ethno and SL have some issues...

Before I upgrade I have to see if Ethno 2 is going to not be compatible. Are you talking about Ethno 1 or 2? Ethno 1 doesn't work with Snow Leopard, Ethno 2 works fine. I have various projects "in progress" that have Ethno tracks in them and I can't afford to lose them. Can anyone else tell me if Ethno 2 is causing a hiccup in DP 7.2? Thanks

Ethno 2 working fine here too. MOTU would be rather inept if the managed to break their own VI by updating their own DAW from 7.12 to 7.2.

Though I agree with that statement, I would remind you that in making DP5, MOTU "broke" Sys Ex.....LOL..which just blew my mind., Murphy, the "lawmaker" is no stranger to MOTU

[James Steele]

Though I agree with that statement, I would remind you that in making DP5, MOTU "broke" Sys Ex.....LOL..which just blew my mind., Murphy, the "lawmaker" is no stranger to MOTU

How is it broken? Do you mean in Custom Consoles somewhere? I'm not very familiar with this issue.

[toodamnhip]

Though I agree with that statement, I would remind you that in making DP5, MOTU "broke" Sys Ex.....LOL..which just blew my mind., Murphy, the "lawmaker" is no stranger to MOTU

How is it broken? Do you mean in Custom Consoles somewhere? I'm not very familiar with this issue.

In earlier versions of DP 5, (5.0?)- the sys ex broke. You could record the sys ex into a DP track, for ex, from a JV1080 synth.

If you played it back into the 1080, the 1080 would load fine.
But, when you saved the DP file, something corrupted the sys ex. Upon next trying to load sys ex into any MIDI device, you'd get an error. the sys ex became unusable by the act of saving the DP file.

I brought this to the attention of all here at MOTUNATION, and by the next update, this trouble was fixed.
I wondered how many people got hung up badly by this un announced, major bug. I for one, depended heavily on being able to load and re load synths on a variety of projects. it was highly disturbing that MOTU made no official announcement of such a terrible bug, neither here at this site or online, leaving members to hang in the wind if so unlucky as to have saved sys ex in DP 5.0
I believe. Though this issue is a thing of the past, that it shows 2 PAST negative aspects, 1) that MOTU has broke solid, basic code in an update, and 2), that MOTU's closed-lipped nature can be of great harm to users unfortunate enough to rely on the product when there's a bug that doesn't show up right away, such as sys ex corrupting upon saves. This bug was verified consistently by users here once I brought it up.

It seems today's DP has no such major problems. But, every update is in my mind at least, is a "look before you leap" scenario. Fortunately, I only screwed up one or two recording sessions worth of MIDI, but those one or two were paid sessions and all the more fortunately, the clients were cool about it and I went back to the MIDI set up of a session before the bad sys ex and worked my way back free of charge for those unfortunate clients.

I hope the new DP 7 is different, but, though I do not agree with saying DP is a semi-pro product, there have been several amateur problems over the yrs, another being Dp's move to OSx which made previous effects set ups non transferrable, making supposed "Masters" "break" so to speak. I have a computer that I have had to save, loaded with OS9 songs from the past that I will need to transfer to OSx by a very tedious method of fixing each effect that broke in the transfer from OS9 to OSx

the lesson for me is never assume anything, check everything, if you have master DP files you intend to archive.
I don't apply any negativity to DP 7.2 per se, it looks like a nice update. But always keep your eyes open. The moment we all start feeling comfortable that MOTU or any company won;t ever again screw up an update, is the moment we could get caught.
We all share a responsibly to observe and report with a critical eye. Our clients deserve this for they are paying us.
On the positive side-well done MOTU for a nice looking DP 7.2 and well done listening to users and making skins for DP. That was impressive.

[beautypill]

Loving the new themes. Haven't played with a lot of them, but I will say right of the bat i like the new Default.

Default is great!

Much improved over the old DP6/7 look.

This makes my workday so much more pleasant, it's ridiculous.

Thank you, MOTU for putting an emphasis on the value of aesthetics. I'm ecstatic about it.

My envy of the stylishness of Ableton Live and Pro Tools is gone. I can do everything I want to do and enjoy "the world of the screen" while doing it!

- c

[James Steele]

Though I agree with that statement, I would remind you that in making DP5, MOTU "broke" Sys Ex.....LOL..which just blew my mind., Murphy, the "lawmaker" is no stranger to MOTU

How is it broken? Do you mean in Custom Consoles somewhere? I'm not very familiar with this issue.

In earlier versions of DP 5, (5.0?)- the sys ex broke. You could record the sys ex into a DP track, for ex, from a JV1080 synth.

If you played it back into the 1080, the 1080 would load fine.
But, when you saved the DP file, something corrupted the sys ex. Upon next trying to load sys ex into any MIDI device, you'd get an error. the sys ex became unusable by the act of saving the DP file.

I brought this to the attention of all here at MOTUNATION, and by the next update, this trouble was fixed.

Well that's good then. I thought it had still not been addressed.

I wondered how many people got hung up badly by this un announced, major bug. I for one, depended heavily on being able to load and re load synths on a variety of projects. it was highly disturbing that MOTU made no official announcement of such a terrible bug, neither here at this site or online, leaving members to hang in the wind if so unlucky as to have saved sys ex in DP 5.0
I believe. Though this issue is a thing of the past, that it shows 2 PAST negative aspects, 1) that MOTU has broke solid, basic code in an update, and 2), that MOTU's closed-lipped nature can be of great harm to users unfortunate enough to rely on the product when there's a bug that doesn't show up right away, such as sys ex corrupting upon saves. This bug was verified consistently by users here once I brought it up.

Got it. So MOTU messed up. Obviously they are not perfect. Bad MOTU.

It seems today's DP has no such major problems. But, every update is in my mind at least, is a "look before you leap" scenario. Fortunately, I only screwed up one or two recording sessions worth of MIDI, but those one or two were paid sessions and all the more fortunately, the clients were cool about it and I went back to the MIDI set up of a session before the bad sys ex and worked my way back free of charge for those unfortunate clients.

So you weren't harmed by it. Good thing. And these things do happen and they addressed it. I don't know what sort of mechanism they should use to alert everyone to a bug like this. Perhaps issue a news release to all the major audio sites? I suppose if they kept an email database they could email everyone about it.

The reason I said what I did, is because I can't remember MOTU breaking one of their own VI's from one *incremental* release to the next, like 7.12 to 7.2. Still I realize some people like to be especially cautious and would have us sound off and say "Sonic Modulator STILL WORKING HERE!" "Delay Plug-in STILL WORKING here!" Please everyone kick in. This is to assume these things are the norm rather than the exception. Just back up before you install and try it for yourself to make sure. It seems a little paranoid and alarmist to me. DP goes from 7.12 to 7.2. "Omigosh, does Ethno 2 STILL WORK????" Huh? Again, hey... just my opinion. Closest thing I can remember to MOTU breaking one of their own VIs, with an update to their own DAW, was graphic issues with MachFive. I think they still need to do that, but the VI is not compromised functionally. A sysex issue is something that is unfortunate, but something I can see as more likely to slip through the cracks, since I'd wager not as many people work with it much these days.

I don't apply any negativity to DP 7.2 per se, it looks like a nice update. But always keep your eyes open. The moment we all start feeling comfortable that MOTU or any company won;t ever again screw up an update, is the moment we could get caught.

Of course every company can "screw up an update" or to say it another way, introduce a bug in one particular feature of an update. That's why, as you detailed, you back things up and archive things, etc. It seems though some operate on the assumption of a screw up, when I submit that overall MOTU's track record is pretty good. However, we have a large number of users, and each user as different things that are important to them. So one users's great update is another users total piece of garbage... at least in the often black/white world of forum rhetoric.

On the positive side-well done MOTU for a nice looking DP 7.2 and well done listening to users and making skins for DP. That was impressive.

The contextual menus and various other optimizations and fixes they made along the way are nice as well. Built-in support for OSC and their impending iPhone remote control app shouldn't be overlooked as well. Themes is the most obvious improvement, but there's quite a bit more as well.

[KEVORKIAN]

Built-in support for OSC and their impending iPhone remote control app shouldn't be overlooked as well.

OSC support is huuuge... I don't think many realize how cool this is for DP to be out in front regarding this.

I don't believe that there is another major DAW aside from Live that has this yet. Pro Tools, Cubase and Logic certainly do not and neither does Reaper I believe.

[bayswater]

I don't know what sort of mechanism they should use to alert everyone to a bug like this. Perhaps issue a news release to all the major audio sites? I suppose if they kept an email database they could email everyone about it.

Would be very easy. They could put it in a subdirectory here:
http://www.motu.com/news" onclick="window.open(this.href);return false;
and those interested in receiving updates of this type could subscribe to the RSS feed.
Or, since DP now phones home, an option to see reports of this type could be implemented.

But very few companies like to publish their bug list. Steinberg used to publish a bug list with workarounds, but I think they ran out of server space.

[James Steele]

I don't know what sort of mechanism they should use to alert everyone to a bug like this. Perhaps issue a news release to all the major audio sites? I suppose if they kept an email database they could email everyone about it.

Would be very easy. They could put it in a subdirectory here:
http://www.motu.com/news" onclick="window.open(this.href);return false;
and those interested in receiving updates of this type could subscribe to the RSS feed.
Or, since DP now phones home, an option to see reports of this type could be implemented.

But very few companies like to publish their bug list. Steinberg used to publish a bug list with workarounds, but I think they ran out of server space.

They already have an RSS feed which I'm already subscribed to. Just click this link in Safari:

feed://www.motu.com/newsitems/RSS2" onclick="window.open(this.href);return false;

They also have a twitter account too.

http://twitter.com/motutech" onclick="window.open(this.href);return false;

[bayswater]

Would be very easy. They could put it in a subdirectory here:
http://www.motu.com/news" onclick="window.open(this.href);return false;
and those interested in receiving updates of this type could subscribe to the RSS feed.
Or, since DP now phones home, an option to see reports of this type could be implemented.

But very few companies like to publish their bug list. Steinberg used to publish a bug list with workarounds, but I think they ran out of server space.

They already have an RSS feed which I'm already subscribed to. Just click this link in Safari:

feed://www.motu.com/newsitems/RSS2" onclick="window.open(this.href);return false;

They also have a twitter account too.

http://twitter.com/motutech" onclick="window.open(this.href);return false;

Yes, I know they do. I'm subscribed too. That's why I suggested they could use it to issue alerts on known bugs that might cause the sort of problem under discussion.

[bOing]

Hi folks. I'm still keeping my eye on DP, despite having switched for various reasons to Reaper. I've always liked DP but sort of got mentally shut down over it with certain issues around the release of 6.0.

I find it interesting (and not to stir an ants nest) that the new 7.2 update has what Reaper offered at its inception years ago, namely themes, right click, unique search features (not to name its other strengths). Where it still needs to gather steam is where DP has always been strong, which is with its groove quantize and perhaps a score editor (although I don't miss these features very much).

I'm sure all the DAW people are eye-balling each other constantly and so there will be a lot of cross pollination. I just found it interesting that this update was so Reaperish.

Hope you're all well.
All the best,
Roland K.

[James Steele]

Yeah-- but I wouldn't want to use Reaper just to get those things. What DP should focus on is often different to every user.

[bOing]

Yeah-- but I wouldn't want to use Reaper just to get those things. What DP should focus on is often different to every user.

Hey James.

My point was that for such a well developed and enduring DAW as DP is, it also seems to be taking some direction from a relatively new kid on the block, as are some other DAWs. It's not that anyone would switch to Reaper for the skins. That was not my point. I know you know that I know that.

[James Steele]

Yeah-- but I wouldn't want to use Reaper just to get those things. What DP should focus on is often different to every user.

Hey James.

My point was that for such a well developed and enduring DAW as DP is, it also seems to be taking some direction from a relatively new kid on the block, as are some other DAWs. It's not that anyone would switch to Reaper for the skins. That was not my point. I know you know that I know that.

Well, right. That's one of the drawbacks to an app that traces its lineage to the earliest days of MIDI. Writing a new app lets you come up with some of these new ideas. DP is the first such "old school" MAC DAW to be fully "skinnable" AFAIK. (I'm thinking DP, Pro Tools, Logic, Cubase).

My point was you seemed to be saying that Reaper already had this, so this was nothing new. Almost like DP should have focused on another feature, but I *want* the option of different themes in DP, so it doesn't matter to me if Reaper did this already. It's something that's a good addition to DP.