Projector does not work as soon as I plug in my Kinect
I have a problem that really kinda sucks. So here's my setup:
I am currently working with a trial version of Millumin2 on a MacBook Pro 15" (mid 2012) with OSX El Capitan 10.11.1 installed. My projector is an Acer P1173. It is connected to my MacBook via an HDMI --> Thunderbolt cable. With Millumin2, this setup works perfectly fine. I am planning to make an interactive projection mapping project. So I got myself a Kinect (the old one, version 1). I installed the dependencies as Millumin suggested and played around with the Kinect mask a little - while the projector was unplugged. Worked fine as well. So I wanted to see it "in action" and plugged in my projector. Unfortunately that was the moment when things didn't work out so well anymore. The output of my projector did not appear - all I could see was a text that said that the signal was being processed but except for that nothing happened. The moment I unplugged my Kinect, the projector output returned. As soon as I plugged in my Kinect again, the output was gone once again... So apparently I cannot use my Kinect and my projector simultaneously which totally sucks. :-(
I think it is definitely not a Millumin problem because even if I have Millumin closed, the projector output does not show up as long as the Kinect is connected to my MacBook. I started several solution approaches by restarting everything and plugging in the Kinect first and then the projector. But nothing of that has worked so far.
My roomie has Windows 10 installed as a partition on his MacBook so we thought we'll try to see if it is a software/driver problem since the Kinect is a Microsoft device. Surprisingly, the projector output worked fine while the Kinect was plugged in, but this time the Kinect didn't (the green lamp wasn't on). This might be because we didn't have any drivers installed for the Kinect on Windows, but we thought the Kinect's lamp should at least be on, right?
Well, now I wonder if it might be a hardware problem or a software problem. Could it have something to do with my MacBook's graphics card? Are there any projection mapping experts hanging out here who might have an idea what is wrong? Maybe the solution is really simple. I have a pretty cheap HDMI to Thunderbolt/mini displayport cable which was like 10 Euro on Amazon. Since the projector output returns a message that the signal is being processed, do you think it might have to do sth with that? I'd prefer not to invest in a super expensive cable yet, not as long as I don't know what is causing these issues.
Thank you guys in advance for any help!