DP and Mavericks

[mikehalloran]

Working well for me. Mavericks fixed the big issue I had with DP 8.05 so I'm a happy camper. Liking everything else I see.

[dado]

Installed this morning. Less cpu usage!!!

[magicd]

Installed this morning. Less cpu usage!!!

Does this mean that DP under Mavericks is... snappier?

Dave

[nick danger]

It appears to me that Mavericks is designed to encourage use of iCloud. How many out there are currently using iCloud to any significant degree? Is it of benefit while using DP? Can a DP project be manipulated on two different computers simultaneously?

[MIDI Life Crisis]

Come for the DAW. Stay for the snap.

Or is it the other way around?

[dado]

Installed this morning. Less cpu usage!!!

Does this mean that DP under Mavericks is... snappier?

Dave

It needs less ram and less stress on the processor

[mikeka]

From MOTU: DP 8 is Mavericks ready and has been tested with the new OS. I'm in the middle of a mix but will install after completion.

Mike, just wondering where you saw this? I've just checked MOTU's website for the 8.05 release
http://www.motu.com/newsitems/dp-805-is-now-shipping
and there's no mention at all about Maverick that I can find?

I called them. Tech support assured me all is well.

[Drumwizard]

DP's Delay and Modulation effects do not work correctly with Tempo Lock to Beats or Note Value.

[dave pine]

that's not good, have you tried any third party plugs synched to bpm?

[Drumwizard]

that's not good, have you tried any third party plugs synched to bpm?

Yep. Waves SuperTap Delay works as it should in sync mode.

[Drumwizard]

When I click on '+' or '-' (under knob) it's step =2 instead of 1. For example, to increase gain I click on '+' several times and it grows like 2, 4, 6, 8 etc.

[Phil O]

I haven't tried the Delay plug yet, but everything I've tried so far is working great. DP8/Mavericks may just be a winning combination.

Phil

[amadeus_d]

I'm curious if anyone is running DP 7 with Mavericks?

[Dark Goob]

From MOTU: DP 8 is Mavericks ready and has been tested with the new OS. I'm in the middle of a mix but will install after completion.

MOTU is always ready in advance!
That continues to impress me, more so now than ever before.

I can almost guarantee you that's because they're competent developers who follow best practices. I.e., they RTFM and don't do weird hacks that rely on deprecated code, etc.

Meanwhile Avid/Digidesign... cough... I've had more *****ing problems with their **** drivers over the ******* years than any other piece of ******* I've ever ********* owned. And I *just* got my Digi 002 Rack to *kind of* play nice with Mountain Lion, by having two versions of the driver simultaneously installed, and using terminal commands to selectively load/unload the version of the driver I need at any given time... sigh... I have to say when it works, it works well, but it's been such a pain.

MOTU on the other hand is a godsend when it comes to drivers.

[Dark Goob]

It appears to me that Mavericks is designed to encourage use of iCloud. How many out there are currently using iCloud to any significant degree? Is it of benefit while using DP? Can a DP project be manipulated on two different computers simultaneously?

I use iCloud a little bit, mostly for Notes syncing. As an iOS developer, I can tell you there have been a host of issues with certain aspects of iCloud in the past, when it comes to a certain kind of fine-grained, database-level syncing that Apple offers. iOS 7 was supposed to address that and I'm sure Mavericks includes these improvements as well, since the core-level stuff tends to be pretty similar if not identical between the two OS's (and is becoming more so).

What *has* worked well for third-party developers and iCloud is the ability to have your app simply save a document to iCloud that will be accessible from elsewhere. I'm not sure how it handles two people simultaneously working on the same file, but given that iOS is designed as a single-user system, I don't think they are worried about you editing a document on your iPad with one hand, WHILE you edit it on your Mac with the other.

However when it comes to something like Digital Performer, I kind of don't see what the usefulness of iCloud would be. My average DP projects are in the range of ~5-10GB. I suppose that could be backed up to iCloud simply for backup purposes but I don't see how multiple people editing that iCloud project simultaneously would even be desirable, let alone possible.

You have to look at something like Github to get an idea of what a major project being edited by multiple people simultaneously might look like. You start to realize that even in the case of a large set of text documents full of computer code, synchronizing changes between multiple different versions and branches can become incredibly complex.

It would be very difficult indeed to create a revision tracking system like Git for something like a DP project, with all its tracks data, plug-ins assignment data, automation data, mix data, MIDI data, take data, etc. How would you compare two versions of a DP project? In programming every program is broken up into many different source files. It would be like if each individual track, automation control, MIDI track, etc. in your project had its own separate file for each take. As it stands, audio is kept in separate files but most everything else is all inside the DP project file itself. I have no idea what method of storage MOTU uses inside these files. If it's CoreData, then theoretically there might be a way to merge the changes between two different versions of a project file, rather than simply choosing one or the other.

However from what I do know about CoreData, I am quite sure that to attempt such a feature would be a monumental undertaking, and to get it to work with iCloud would be something no sane developer would dare even consider, let alone attempt, unless the success or failure of the product depended entirely on that feature alone. Even then they would probably have cold sweats at night.

GIven DP's support for the branching undo's however, I do think if any developer were to be capable of doing this, MOTU would be the one, because the same underpinnings that allow an undo history to be possible are also what allows document revision tracking and change syncing to be possible (in a general, categorical sense).