MOTUnation.com

Helicopter001 wrote:Same here - DP 10.11 and Mojave 10.14.6, project in 24/96: bouncing to disk takes like 25 minutes for a 4 minute song!!!
Now, on my other machine (DP 10.11 but running High Sierrra 10.13.6 and 24/48 projects) there is no problem at all with bouncing to disk...
The problem will be most likely related to Mojave then isn't it?
Where can one report this at MOTU? Thanks!

Perhaps my post is misleading, because the (originally 2009 but 5,1 upgraded) 64GB Tower machine where sometimes the bouncing takes a break, is running Mac OS 10.12.6 (The laptops run 10.14 Mojave.)
I don't have the Waves, so I don't think that's causing the very occasional issue here.
Does anyone here think it could be SSD related? Maybe related to TRIM operations? The issue would probably be way more widespread if it were TRIM related, but I thought I'd throw that out there anyway.

tommymandel wrote:Perhaps my post is misleading, because the (originally 2009 but 5,1 upgraded) 64GB Tower machine where sometimes the bouncing takes a break, is running Mac OS 10.12.6 (The laptops run 10.14 Mojave.)
I don't have the Waves, so I don't think that's causing the very occasional issue here.
Does anyone here think it could be SSD related? Maybe related to TRIM operations? The issue would probably be way more widespread if it were TRIM related, but I thought I'd throw that out there anyway.

I understand your issue of pausing randomly mid-bounce without any plugin issues. I have had that endlessly in DP 9.5 as well.

It's not an SSD thing. I use SSDs. When I was having bouncing in issues in DP9.5, I would simply quit DP9 and then open the session in DP8 and it would bounce perfectly without any pausing EVERY TIME.

-g

Does anyone here think it could be SSD related?

Only if defective or you’re running so-called “maintenance utilities” that interfere in the operation of the drive.

Maybe related to TRIM operations?

Only if the disk is too full or you’re running those crapware utilities and TRIM is not enabled. TRIM is part of the MacOS, Windows and UNIX. Apple disables it on 3rd party SSDs except NVMe over PCIe or TB3. To enable it over SATA III run sudo trimforce enable in Terminal — I had to do so to enable it on my SATA III SSDs sitting in a Thunderbolt 2 dock connected to my iMac Pro.

If you erase a full 2TB SATA III SSD with TRIM enabled, it takes about 24-28 hours before the drive is ready to accept 2TB of new data. Real world usage rarely works that way but if using it for storage, this is possible and I’ve measured it.

If TRIM s not enabled (such as connected via USB where TRIM is not supported) such a drive can take 36 or more hours if Garbage Collection is the only drive preparation utility available (built into the firmware of the SSD)

Thanks Mike!