2018 MacMini experiment on ProTools HDX

[khoop2112]

This weekend I decided to try an experiment:

I currently have a 2013 MP with a TB --> PCI expansion chassis for HDX, with an S3 and a Dock. I run 2 4k monitors off it, plus a 3rd at a much lower resolution. When the new Mac Mini came out I was really curious to see if it would be a viable replacement for my 2013 MP. So my trial setup was:

2018 MacMini 3.2ghz i7, 32 GB RAM, 1TB SSD
Blackmagic eGPU (Radeon RX580)

Now, I KNOW ProTools 2018.10 is not yet ready for Mojave or the later versions of High Sierra, but most of the reported issues seemed to focus around lower buffer sizes, and since I run HDX and keep my buffer at 512 I thought it was worth a try.

After installing all my plugs, opening relatively high track count sessions, I noticed more CPU power in Pro Tools from the Mini over my 3.5ghz 6 core 2013 MP. The Mini felt more responsive, and I felt like the eGPU helped my screen redraw on my 4k monitor over the old MP.

I loaded a couple sessions, one 44.1k and one 88.2khz. I could loop the 44.1k session and it would play forever without interruption, but the 88.2k session would give me a 9173 error within 10 minutes of looping, but on the 2013 MP it looped for over an hour before I stopped the test.

I'm hoping that the 9173's I'm getting are tied to the known issue with PT and Mojave. Even more hopeful that there will be a new version of PT soon to deal with this. Gonna call Avid tomorrow to see if I can get a timeline. If it's not for awhile, I'll return the new MacMini.

For my overdub session tomorrow I'll go back to my 2013, but might try the Mini on a vocal session Wednesday that is less crucial. I'll report back what I discover.

- Kent

[LDS]

Sounds like a neat little setup! Hopefully the incoming 2018.11 update has Mojave support and bug fixes. Would it be worthwhile watching the CPU and system temperatures when looping through the 88.2khz session?

[khoop2112]

I've got all my computers in a separate machine room right now, but didn't notice the computer getting too loud or too hot to the touch...

[ramonetl]

I am curious if you did a total clean install after flattening the MP if that responsiveness you felt from the mini would be the same. My MP has slowed down over time though its not enough to make me wipe it and start fresh. I did upgrade to Mojave and its been pretty smooth sailing but I had a few CPU errors which is new for me in a long time and seems related to the buffer as you mentioned bc I keep mine low since I have 64gb of ram.

[LDS]

Originally Posted by khoop2112

I've got all my computers in a separate machine room right now, but didn't notice the computer getting too loud or too hot to the touch...

The only real way to tell what is going on is to run something like Intel's Power Management Gadget. It will graph the temperature and CPU clock speeds over time, which would be ideal for narrowing down what is causing the 9173 CPU errors when you are running the 88.2khz session.

[khoop2112]

Downloading now.

Anything particular I should pay attention to from your experience?

[LDS]

Originally Posted by khoop2112

Downloading now.

Anything particular I should pay attention to from your experience?

The App is pretty straight forward. It will draw three graphs - Power, Frequency and Temperature. Load the app, then run your 88.2khz test session. Ideally you want to see the frequency line being drawn as straight as possible. What you don't really want to see is the frequency line going down when the power and heat lines go up.

If you run it with the 88.2khz test session of both your Mac Pro and Mac Mini, it should show which system is handling the session in a more efficient manner. Feel free to post some screenshots if you like!

[A Chapman]

Hey Khoop - which chassis are you using? Thanks for the guinea-pigging

[khoop2112]

Sonnet echo express pro - TB1.

I've been doing many tests today trying to track down why I get the 9173/6101 error messages.

Last night I brought the session that had been stopping, and ran it headless on my MacMini with no eGPU, and no HDX/UAD cards. It looped for 45 minutes and never stopped.

Today I brought the mini back down to my studio, and tried the test without UAD or HDX, and it still stopped. Then tried with HDX/UAD but no eGPU, and it stopped.

Then I lowered my resolutions from 2560x1440 HiDPI on my 2 monitors to 1920x1080 HiDPI, and worked fine without stopping but no HDX or UAD. I'm a little perplexed to be honest.

Will keep testing but open to any thoughts on things to try...

[Ru_C]

Originally Posted by khoop2112

Sonnet echo express pro - TB1.

I've been doing many tests today trying to track down why I get the 9173/6101 error messages.

Last night I brought the session that had been stopping, and ran it headless on my MacMini with no eGPU, and no HDX/UAD cards. It looped for 45 minutes and never stopped.

Today I brought the mini back down to my studio, and tried the test without UAD or HDX, and it still stopped. Then tried with HDX/UAD but no eGPU, and it stopped.

Then I lowered my resolutions from 2560x1440 HiDPI on my 2 monitors to 1920x1080 HiDPI, and worked fine without stopping but no HDX or UAD. I'm a little perplexed to be honest.

Will keep testing but open to any thoughts on things to try...

Thanks for all this testing. Just to be sure, was there a combo above that included the HDX card but removed the eGPU?

I'm watching this thread carefully, as the 2018 Mac mini+eGPU is likely to be many folks Mac Pro replacement , but i'm uncertain if the eGPU running via thunderbolt3 will restrict the operation of HDX/HDN connected in the same way. cheers