MOTUnation.com

Started to install only to find that it requires 10.5.8 or above.

I've been happily dragging my feet with Tiger but push is rapidly coming to shove.

DP 7.2 looks great.

Tobor

10.5.8?! Whoa, I'm just under the wire! Didn't notice that but I bet that will help stability as some legacy code may have gone bye bye. Since PPCs are history anyway, there's real;ly not too many who will be lower than that except a few die hards.

AH I"M STUCK AT WORK THE REST OF THE DAY!

When I saw contextual menus i may have pee'd a little. I'm so stoked to get home.

Those of you using Audio Hijack Pro, or any other application that might cause a previous version of DP to load... BE CAUTIOUS.

Make sure you that you change the application being captured from DP 7.12 to DP 7.2 so that it doesn't open the previous version of DP while you are running the current one. I just did this and experienced a system failure with DP 7.12 at the forefront of the issue, with the window window flickering like mad and requesting a plugin set. I had to force shutdown the computer in order to get out of the loop.

This is probably not to suggest that opening up two versions of DP is necessarily a problem (although I'd say it is ill advised). My system failure likely was connected with the fact that Audio Hijack was trying Hijack from DP 7.12 which I had forced quit when it started to load. So this is probably NOT a bug or suggestive of DP stability issues. It is just a reminder for those of you who use these third party tools.

AND ANOTHER REMINDER... if you use custom folders for your MAS plugins, as I do, remember that the DP install will have duplicated all of those plugins again on the main level of the MAS folder. You will probably want to drag the new copies to replace those in the folders, although I think I am just going to delete all the new copies myself.

It would be great if MOTU could let us know if any of the MAS plugins have been modified. If they haven't, deleting the new ones is the simplest solution. FWIW, the plugins in my folders are still the only ones showing up in my projects, so DP seems to be ignoring the new plugins anyway.

A quick check of the new "Themes" folder shows that the themes are in bundle format. WIthin those bundles are simple .png files. Really looks like it's going to be easy for Amplidood and iPerformer to port over their existing themes and make them accessible from the GUI!

Another huge win for MOTU is their adding OSC support! This is going to be big for insuring compatibility with all of the innovative new control surfaces that are coming out and for custom iPhone/iPad controllers as well. Very cool!

KEVORKIAN wrote:A quick check of the new "Themes" folder shows that the themes are in bundle format. WIthin those bundles are simple .png files. Really looks like it's going to be easy for Amplidood and iPerformer to port over their existing themes and make them accessible from the GUI!

It should be no problem to do this. I've already started hacking his Sharp theme to work under the new Themes format.

James Steele wrote:

KEVORKIAN wrote:A quick check of the new "Themes" folder shows that the themes are in bundle format. WIthin those bundles are simple .png files. Really looks like it's going to be easy for Amplidood and iPerformer to port over their existing themes and make them accessible from the GUI!

It should be no problem to do this. I've already started hacking his Sharp theme to work under the new Themes format.

Not quite as easy as you might imagine. I was just trying to do a modified theme myself, and some of the image elements are not stored in the themes bundles (even though they can be changed by the themes). Some of the images are still contained in the main DP application bundle, but which I assume are selected according to information in the theme bundle TEXT files. The pan knobs are an example of this. I haven't figured out how to do it yet, and it may not be that difficult if images in the themes automatically override the similar images in the main DP bundle. I will have to find the file for the pan knobs, drag it into a theme and see if it works.

But this will potentially be great for all of us wanting to try out Amplidood and iPerformer mods at the click of a button, and more easily create our own custom mods. Cool stuff!

I just found a minor issue regarding the new Contextual Menus feature:

I have my mighty mouse set up as a single button mouse. Meaning, When I need right-click functionality, I "control-click" and hold down the control key on the keyboard, while clicking on an item to get a contextual menu. Pretty old-school, I know.

Unfortunately in DP 7.2 that doesn't work. I am only able to call up a Contextual Menu when setting my mighty mouse to have a "secondary button" in system prefs.

This is not the end of the world, but it does make DP the only Mac application that behaves this way that I have ever come across!

In any case, I'l off to submit a technote. Can anyone else replicate this behavior?

MIDI Life Crisis wrote:10.5.8?! Whoa, I'm just under the wire! Didn't notice that but I bet that will help stability as some legacy code may have gone bye bye. Since PPCs are history anyway, there's real;ly not too many who will be lower than that except a few die hards.

Bummer...this means that 7.12 is the end of the line for me, unless I buy
a new Mac Pro and subsequently a new UAD card - unfeasible at this time.

Oh well, I knew this day would eventually come.

.

I just installed it in my laptop.
I LOVE the themes, especially the Plasma and Carbon Fiber Red one!

I'm playing with it as we speak.

Thank you, MOTU!

zed wrote:

James Steele wrote:

KEVORKIAN wrote:A quick check of the new "Themes" folder shows that the themes are in bundle format. WIthin those bundles are simple .png files. Really looks like it's going to be easy for Amplidood and iPerformer to port over their existing themes and make them accessible from the GUI!

It should be no problem to do this. I've already started hacking his Sharp theme to work under the new Themes format.

Not quite as easy as you might imagine. I was just trying to do a modified theme myself, and some of the image elements are not stored in the themes bundles (even though they can be changed by the themes). Some of the images are still contained in the main DP application bundle, but which I assume are selected according to information in the theme bundle TEXT files. The pan knobs are an example of this. I haven't figured out how to do it yet, and it may not be that difficult if images in the themes automatically override the similar images in the main DP bundle. I will have to find the file for the pan knobs, drag it into a theme and see if it works.

But this will potentially be great for all of us wanting to try out Amplidood and iPerformer mods at the click of a button, and more easily create our own custom mods. Cool stuff!

No... I know about that. It will only override if it is present. If you look at the listing of the theme bundles when you open the Themes folder from the Themes preference pane, you will see that "2 Medium Light (Default).bundle" is only about 16K. Much smaller than the others. This is because the graphics making up that theme are largely contained in the DP 7.2 app itself. Other themes have new graphics that will override it.

One way to get in the ball park with one of the earlier 7.12 "mods" like Amplidoods, is to duplicate a theme in the Finder, then empty it's contents and replace it with the contents of the "Supplemental" folder. There will still be issues if you do this though... certain graphics won't line up properly, and MOTU seems to have added new capabilities. From what I can see there are new states for the Mixing Board faders, so it should be possible to have one fader for Record, another for Mute, etc.

It will take a while for Amplidood to take a look at this, but it should be do-able. In fact, it really looks like MOTU opened this up to make it easier for folks like Amplidood. There's even a graphic inside the bundle that is the theme preview that appears in the Themes preference panel in DP 7.2! Cool stuff! I'm liking Alloy myself right now, but can't wait for Amplidood to port Sharp over. My hack is not quite there!

KEVORKIAN wrote:I just found a minor issue regarding the new Contextual Menus feature:

I have my mighty mouse set up as a single button mouse. Meaning, When I need right-click functionality, I "control-click" and hold down the control key on the keyboard, while clicking on an item to get a contextual menu. Pretty old-school, I know.

Unfortunately in DP 7.2 that doesn't work. I am only able to call up a Contextual Menu when setting my mighty mouse to have a "secondary button" in system prefs.

I use a single button Mac mouse (using that old-school method you speak of) and the contextual menus seem to work fine with that. But I know nothing about the mighty mouse, aside from the cartoon character...

KEVORKIAN wrote:Unfortunately in DP 7.2 that doesn't work. I am only able to call up a Contextual Menu when setting my mighty mouse to have a "secondary button" in system prefs.

Apparently in the read me MOTU built it that way in case you use control-click for another function:

Existing behaviors which utilize clicking while holding
the Control key take precedence over the contextual menu.
That is, when Control-click is already used in a particular
context for a different function, you must use right-click to
access the contextual menu.

KEVORKIAN wrote:I just found a minor issue regarding the new Contextual Menus feature:

I have my mighty mouse set up as a single button mouse. Meaning, When I need right-click functionality, I "control-click" and hold down the control key on the keyboard, while clicking on an item to get a contextual menu. Pretty old-school, I know.

Unfortunately in DP 7.2 that doesn't work. I am only able to call up a Contextual Menu when setting my mighty mouse to have a "secondary button" in system prefs.

This is not the end of the world, but it does make DP the only Mac application that behaves this way that I have ever come across!

In any case, I'l off to submit a technote. Can anyone else replicate this behavior?

From the 7.2 PDF:

Existing behaviors which utilize clicking while holding the Control key take precedence over the contextual menu. That is, when Control-click is already used in a particular context for a different function, you must use right-click to access the contextual menu.