Indigo Domotics

Indigo 6.1.11 (and maybe earlier versions) causes Macs with both discrete and integrated graphics to switch to the discrete GPU. This can have a detrimental impact on systems on battery. I can't fathom what Indigo might actually need the discrete GPU for, so please don't do that

See https://developer.apple.com/library/con ... tes/tn2229

Are you running your Indigo server on battery?

Indigo doesn't use Open GL at all (never creates a GL context), and makes no explicit API calls to change the GPU mode. I haven't any clue as what Indigo might be doing to cause this. Indigo only uses straight Cocoa API calls for its UI.

Are you sure this is Indigo related?

If this is because of the SDK Indigo is linked against, then try the Indigo 7 trial. It is linked against a newer SDK.

No, this isn't impacting my server. I have a remote client on my laptop, and it always switches to the discrete GPU when I launch Indigo. Yes, I'm positive it is Indigo related as gfxCardStatus has a very nice menu extra that shows which process is holding the assertion on the GPU.

I'll give Indigo 7 a try, thanks.

Oh, BTW, the issue persists in Indigo 7 (at least as of 7.0.2)

This has info on what the Indigo devs need to do: http://supermegaultragroovy.com/2016/12/10/auto-graphics-switching/

Thanks for the info. We'll try adding the flag to the plist.

SuperMegaUltraGroovy Blog wrote:

... many years after this feature was introduced, it still doesn’t appear by default in the Info.plist. It doesn’t even show up in the default Info.plist generated for new apps by Xcode.

Sometimes I wonder about Apple...

Indigo v7.0.3 is now available and now sets the flag to have Indigo use the integrated GPU on newer MacBooks (which might help conserve battery usage).