Fuggit. I'm going for 9.12

[Gravity Jim]

JSmith1234567: Because they're not buggy.

9.12 runs perfectly on my rig, as I'm sure it does on the Macs at MOTU. One guy or two guys or even 12 guys having a problem isn't a "bug."

Go for it, Babz. I agree that a start-up volume clone is always a good idea when updating the OS or your main software, but there are many more users having no trouble than users with problems.

[Robert Randolph]

If both of these updates are still buggy, why haven't we seen another rev. from MOTU yet?

It's been awhile!

Developer resources? Difficulty fixing the issues? Extra testing? Other features in the works to be included with the next update? Waiting for another minor release cycle?

There's plenty of sensible reasons.

I do know for a fact though that many (dare I say: most) of the reported issues with 9.12 have been replicated by Motu. This is both through my interactions with them and my interactions with other users that have relayed their experiences with Motu's team.

What is holding them up though, I don't know. It would be nice if there was some slightly better communication with the public.

[Babz]

If both of these updates are still buggy, why haven't we seen another rev. from MOTU yet?

It's been awhile!

Developer resources? Difficulty fixing the issues? Extra testing? Other features in the works to be included with the next update? Waiting for another minor release cycle?

There's plenty of sensible reasons.

I do know for a fact though that many (dare I say: most) of the reported issues with 9.12 have been replicated by Motu. This is both through my interactions with them and my interactions with other users that have relayed their experiences with Motu's team.

What is holding them up though, I don't know. It would be nice if there was some slightly better communication with the public.

Well, this may have nothing to do with anything, but it appears lead DP developer Michael Miller left the company sometime over the summer. I was sad to see him go, but wish him the best in his new adventures. He was so great at keeping us informed on all the fixes in DP, and I hope MOTU continues to post the detailed lists of bug fixes like we saw from Mr Miller.

Best,
Babz

[Robert Randolph]

If both of these updates are still buggy, why haven't we seen another rev. from MOTU yet?

It's been awhile!

Developer resources? Difficulty fixing the issues? Extra testing? Other features in the works to be included with the next update? Waiting for another minor release cycle?

There's plenty of sensible reasons.

I do know for a fact though that many (dare I say: most) of the reported issues with 9.12 have been replicated by Motu. This is both through my interactions with them and my interactions with other users that have relayed their experiences with Motu's team.

What is holding them up though, I don't know. It would be nice if there was some slightly better communication with the public.

Well, this may have nothing to do with anything, but it appears lead DP developer Michael Miller left the company sometime over the summer. I was sad to see him go, but wish him the best in his new adventures. He was so great at keeping us informed on all the fixes in DP, and I hope MOTU continues to post the detailed lists of bug fixes like we saw from Mr Miller.

Best,
Babz

Yeah, he appears to have left Motu in July. It was probably my fault



It is interesting that Motu does have job postings for software engineers, and the postings seem to indicate work on DP.

So maybe they are shorthanded? Maybe not. Just a bunch of speculation. They definitely have plenty of talented developers there still.

[waxman]

If BFD3 from FXpansion was working on Sierra I would upgrade. DP is working better then ever. I've had only 2 problems. One was a interim UAD update 8.7 and the other was a problem with a Soundtoys update. DP 9.12 is stable, elegant and works as advertised.

[JSmith1234567]

I made the move yesterday.

I was not upgrading before after all the troubles I had with 9.10 and had gone back to 9.02.

I did Sierra and DP 9.12 yesterday, as well as checked and updated to the latest versions of all my plug-ins.

All is working just fine, with WAY lower latency.

Cudos to you all @ MOTU if you are reading this!

[Armageddon]

No problems here -- I barely had v8 long enough to think about it before upgrading to v9.

[JSmith1234567]

I made the move yesterday.

I was not upgrading before after all the troubles I had with 9.10 and had gone back to 9.02.

I did Sierra and DP 9.12 yesterday, as well as checked and updated to the latest versions of all my plug-ins.

All is working just fine, with WAY lower latency.

Cudos to you all @ MOTU if you are reading this!

Well after a day working to picture, better latency, LOTS & LOTS of crashes.

I don't know...is this an improvement or not?

[Babz]

Well after a day working to picture, better latency, LOTS & LOTS of crashes.

I don't know...is this an improvement or not?

What kind of crashes? What steps create the crash?

[JSmith1234567]

Saving tracks to clippings (highlight a section of tracks you want saved, edit window; copy-to-clipping window) reliably crashes things 99% of the time.

Other things that I can't remember now...I remember that one because I wanted to save an aux-track setup that I use allot to the clippings window yesterday, and it would crash almost every time.

I did manage eventually to get it saved, but after a ton of crashes.

The movie window seemed to complicate things too.

I was getting great performance until I had to work with picture yesterday, and then my processor-performance window is peaking and then hanging around 75% all of the time now.

It was @ about 25% with 9.02 with the same template.

Other crashes also, but I'll try to remember what they were. I think using the audio edit window crashed me a couple of times, but that has ALWAYS been glitchy.

I've never understood why it has to unload and then reload all of your VI's and plugins every time you make an edit in that window?

[mikehalloran]

If you are getting constant crashes, there is a reason. What is it?

What do the crash reports say? It is generally contained in the first 20 lines.

What does a Console report say? Sometimes hard to read and difficult to interpret, Console always tells you what is happening with your Mac when a crash occurs.

In both cases, the answer is normally one of three issues: Something is trying to load that should but can't. Something is trying to load that shouldn't. The app or system is looking for something it can't find or the library it is loading is out of date.

It is always one of these. The culprit can be old code or an app that didn't follow the Apple Toolkit (or, again, is too old). It can be a corrupt installation (common) or bad preference file (rare).

It often happens that installing a plug will corrupt DP paths. There are certain Console logs that are a surefire tell when this happens. The solution is to just reinstall DP—always my first recommendation—and see if you still have a problem.

[JSmith1234567]

If you are getting constant crashes, there is a reason. What is it?

What do the crash reports say? It is generally contained in the first 20 lines.

What does a Console report say? Sometimes hard to read and difficult to interpret, Console always tells you what is happening with your Mac when a crash occurs.

In both cases, the answer is normally one of three issues: Something is trying to load that should but can't. Something is trying to load that shouldn't. The app or system is looking for something it can't find or the library it is loading is out of date.

It is always one of these. The culprit can be old code or an app that didn't follow the Apple Toolkit (or, again, is too old). It can be a corrupt installation (common) or bad preference file (rare).

It often happens that installing a plug will corrupt DP paths. There are certain Console logs that are a surefire tell when this happens. The solution is to just reinstall DP—always my first recommendation—and see if you still have a problem.

Thanks!

Will I lose my preferences if I re-install?

[doodles]

Other crashes also, but I'll try to remember what they were. I think using the audio edit window crashed me a couple of times, but that has ALWAYS been glitchy.

I've never understood why it has to unload and then reload all of your VI's and plugins every time you make an edit in that window?

I Always had the same issue, but there's a very simple reason/workaround. You'll have the waveform editor connected to main sequence. (haven't used it forever, so can't remember the terminology. It's when I used to use set beats, etc). Your big play button/triangle will be highlighted to link/sync it to track. Unclick it. Now it won't restart audio engine/reload plugs each time.

[mikehalloran]

Will I lose my preferences if I re-install?

No.

[JSmith1234567]

Will I lose my preferences if I re-install?

No.

Thanks! I'll try it.