Studio Support Gnome wrote:I am pondering what will happen if I go to using a later OS, and a thunderbolt Hub to connect both a new interface and the screen ?? any clues oh Obi_wan??
So, the thunderbolt port carries multiple streams of data - let's ignore USB-C for now, but on 2011-2015 machines, the thunderbolt port carries both thunderbolt data, and displayport data as separate things.
When you plugin a thunderbolt device, the thunderbolt stuff will work - for instance, I can plugin in a thunderbolt dock thing, which has FW, USB3 ports and other things. This works fine. I also have a UAD2 card I can plugin into the thunderbolt port too - again, works fine.
What won't work is external displays. These generally use the displayport connection (over thunderbolt, or over their own displayport port), and external displays are *only* handled by the dGPU - as soon as you plugin an external display in, the machine (when it works!) will switch to the dGPU. No dGPU, no external display.
Even if you plugin a display into the thunderbolt port on my working TB dock, the display won't work - there's no dGPU to power it.
On later machines, I'm not sure, but later machines don't have the same GPU failure issues so it's likely not an issue anyway.
Now, there *are* some external display options that don't set themselves up as an external display, as far as the OS is concerned. You can get some monitors that use the thunderbolt connection, and proprietry handling, to provide external displays for things like FCPX. These work apparently, but I think are quite expensive. Also, there are some USB display systems that should work, but aren't very good.
But anything that OSX thinks is a proper external monitor won't work, as these are hard tied to the dGPU in 2011 machines, at least.
Now - I'm not 100% sure of the exact behaviour on the 2012 machines, because I'm invested in the 2011 and most of my experience and knowledge is around that, so it's worth double-checking (I'll have a nose around...)