MOTUnation.com

Two clearly related problems I'm hitting with DP9.1 and the Apollo Quad:

1. On song load, the Apollo will click and stop playing audio. Fix: Go to Hardware setup and reselect the Apollo, click ok, audio comes back.
2. In one particular song, every time I hit a specific spot in the song the same thing will happen: Apollo will click, and audio will stop. Go to Hardware setup, click OK (the Apollo is already selected), and audio comes back. But if you try to play through that spot again, it craps out again, so there's no way to play the entire song end to end.

Any ideas? Workarounds? Indications as to why this might happen...specific plugins, automation, etc.? I can state it isn't number of tracks or something about the mac that's the issue, it's clearly a DP bug. Other songs load and play fine, including songs that use UAD plugins.

Have you tried creating a copy of the session and try that one? Something could be wrong with the writing of a file and by it rewriting the session is may correct it? Worth a try.

I'm on 9.1 with a Quad and a Twin via Thunderbolt and have not experienced that issue...not that that helps you.

Try loading the problem project into a new project. See LOAD under FILE Menu.

Something in 9.1 is causing DP to lose the hardware connection - I have it with an HD192. Clicking in hardware has brought it back. But certain things trigger it to lose communication. When I open Reason or load a sound it's been losing communication. I wonder if at the point in the song where this happens you have something happening - a new patch, VI entrance. Anything going on there that you can point to?

If you can find a way to reproduce reliably let us know. It would likely be a big help to MOTU to find the problem.

From what I remember, I believe UAD does no testing with DP.

I had the stuttering / glitching, processor spike problem in a project a while back. Always at the same spot in the track. I eventually solved it by disabling the stock Motu DP sampler.

If it is a firewire Apollo quad there may lie your problem. I had those kind of problems and so did scores of others with the firewire version of this hardware. Check the UAD forum I am sue you’ll find the thread that is severals years running!!

Yes I too recently moved from my trusty pci-424 based MOTU interfaces to Apollo FireWire and its proven to really slow down DP. I'm also experiencing dropped UAD plugs during playback and recording. Very unpleasant. At this point I'm considering going back to my HD192, but I really like the UAD2 plugs. Maybe I can use both. Probably won't solve the issues though unless I unplug the Apollo. Ugh. I paid $3k for the thing -and 10 plugs.
Greg


Sent from my iPod touch using Tapatalk

The Sonnet Allegro PCIe/firewire card completely fixed Apollo issues for me. No more error messages!
https://www.newegg.com/Product/Product. ... lsrc=aw.ds

Interesting. Is the PCI FW800 somehow superior to the front panel FW800 connector on a MacPro. Not sure I see the advantage of going PCI plus I'm out of card slots...?
Greg


Sent from my iPod touch using Tapatalk

By the way, the latest UA and Mac Sierra updates seemed to have really helped responsiveness in my system. See my earlier post in this thread.
Greg


Sent from my iPod touch using Tapatalk

I don't have the technical acumen to tell you why a PCIe to Firewire 800 card is superior to the built-in FW ports on the MacPro. My tech, however does, and he is insistent that the FW ports on the MacPro (silver towers) are junk.
As I said in previous post, I was having incessant Error -38, -50, -51, etc. UAD messages until I installed the Sonnet card. After installation they were 99.9% gone. Every once in a while I'll get the "one or more UAD Plug-Ins have been disabled" message. But a DP re-boot usually fixes that. Wouldn't it nice if they told us which plug-in was disabled? I've spoken with UA about this annoyance, but I feel my words have fallen upon deaf ears.

I was early to the Apollo platform. With all of the error messages, as well as a few other issues, I was able to convince UA to let me be a Beta tester (they also suggested it!). The UA team was great, and committed to fixing the teething problems of the Apollo. They even replaced my original Apollo in an effort to remedy the issues. They suspected the MacPro FW ports may have been the culprit, but were having inconsistent results using the PCIe/FW cards. They simply couldn't endorse the Sonnet or any other card for that reason.

I did find out that UA tests only ProTools, Logic, Cubase (PC), and Ableton.
Despite the fact that some former MOTU people work or worked at UA, and that DP has such a large base among composers, they said that the numbers of DP users weren't sufficient to include it for testing. They figure that with Logic representing the Audio Units DAW there's enough carry-over. Of course I disagreed, saying that we're a small but mighty group. Maybe if enough DP users petitioned UA things could change.