jajh2204

Q: Strange Screen Sharing Issue

Hi All,

 

So i have a 2012 mac mini running the latest osx and its connected to my samsung TV in the lounge.

 

I run Kodi on the mac mini and usuall connect to the mac mini via my macbook and the "share screen" feature.

 

For some reason whilst we are watching something on the mac mini (i.e. on the tv) and I close the share screen function on the macbook, the picture on the tv goes off? this is also the case if I shut down the laptop whilst watching something being played on the TV.

 

I assume this is a setting issue somewhere but I cant for the life of me figure out why the TV screen is linked to the macbook? I thought the mac mini was running independently and I only use the macbook share screen so I dont have to have a trackpad/mouse/keyboard on the go to control the mac mini.

 

Hope this makes sense!! Help?

MacBook Pro (13-inch Mid 2009)

Posted on Nov 5, 2015 11:11 AM

Close

Q: Strange Screen Sharing Issue

  • All replies
  • Helpful answers

  • by jajh2204,Solvedanswer

    jajh2204 jajh2204 Nov 6, 2015 3:46 PM in response to jajh2204
    Level 1 (1 points)
    Nov 6, 2015 3:46 PM in response to jajh2204

    So just an update,

     

    If i shut the macbook with share screen still running then the picture on the tv stays?

  • by Drew Reece,

    Drew Reece Drew Reece Nov 6, 2015 3:56 PM in response to jajh2204
    Level 5 (7,552 points)
    Notebooks
    Nov 6, 2015 3:56 PM in response to jajh2204

    This sounds like you are doing something wrong.

     

    Screen sharing does need to be running to work across machines, so the first issue seems to be correct - you can't turn off screen sharing & expect it to keep running for a remote Mac.

     

    I also suspect you need to use Kodi differently. It should be a possible to run Kodi on one Mac (as a server) & then view the contents on another Mac via the Kodi app. It may require some settings to achieve this. That is how other video applications generally work, a server shares the files & a client then views them. I don't have experience with Kodi (just XMBC before it was renamed), so I'd suggest you review the setup or help on the Kodi site.

     

    Plex may be another option if you cannot setup Kodi, I found it was simpler to run & use, but maybe Kodi is better than the older XMBC.

  • by olivierfromchicago,

    olivierfromchicago olivierfromchicago Mar 9, 2016 6:55 AM in response to jajh2204
    Level 1 (0 points)
    Mar 9, 2016 6:55 AM in response to jajh2204

    Is this truly solved? If so, how?

     

    I don't use Kodi but I experienced the same symptoms otherwise. I have a Mac Mini connected to my A/V receiver. I use screen sharing on a MacBook Air to control the Mac Mini. For example, I'll start a video stream. Or I'll rip a CD.

    When I close the lid on the MacBook Air, it will go to sleep, as expected.

     

    What I don't understand, and would like to fix, is why this would have any impact on what is happening on the Mac Mini. Why, as it seems, it is going to sleep mode.

  • by ctujack,

    ctujack ctujack May 20, 2016 10:03 PM in response to olivierfromchicago
    Level 1 (4 points)
    Mac OS X
    May 20, 2016 10:03 PM in response to olivierfromchicago

    I don't see a solution here to the similar problem I'm having since I upgraded from 10.10 to 10.11.4 last week.

     

    I have a Mac mini connected to my TV. I control it through Screen Sharing from my MBPro. If I close the Screen Sharing window on my MBPro, the TV loses the video signal from the Mac mini. To be clear, it does not go into screen saving, it does not go to a login screen, I just get a black screen on the TV with "no signal" on it, as if the video cable was unplugged. It does not matter what is active on the Mac mini. It can just be in a Finder window, or browser, or watching a movie. If I close Screen Sharing on the laptop, the video signal from the Mac mini to the TV is gone. But as soon as I start Screen Sharing on the laptop again, the video signal from the Mac mini to the TV returns.

     

    This problem never happened before 10.11.4.

    Is there a setting that can fix this, or is this a bug waiting to be fixed in the next update? Thanks.