Once any apps remove all of their assertions, the system IDLE timer will count down to whatever setting you've set in the OS power settings and the Mac will go to sleep as designed. That way, XBMC would allow any OS activities that might need to keep the OS awake to do so. Once neither of these activities is going on, remove the sleep assertion from the OS and allow the OS to take over with managing the sleep setting. Instead of forcing the Mac to go to sleep, I'm requesting that you instead use a sleep assertion to prevent the mac from sleeping while XBMC is playing back content, or you are actively working in XBMC via the GUI. What I'm suggesting would be to make the sleep timer a bit more OS friendly. It will literally go to sleep right in the middle of the copy. It also causes lost network connections when copying a large number of files because of this idle timer configuration. I also have scheduled backups which have begun failing as well. For example, I use iTunes to stream video to various rooms in the house to Apple TV's while using XBMC as my primary HTPC media player. This overrides any background processes which have assertions into the OS X power settings to prevent sleep. Any processes currently running when the XBMC idle timer runs out are ignored and the PC is put to sleep. If you enable the Sleep Timer within XBMC, you can get some sleep functionality (while still ignoring the OS sleep setting), but it does so without any awareness or politeness around what processes are currently running on the host Mac. Currently XBMC ignores the OS settings for energy saver/sleep modes and prevents any sleep for a Mac at all with the 'sleep' timer disabled in XBMC.
0 Comments
Leave a Reply. |