2014-07-27, 14:25
(2014-07-27, 07:14)wallstreet1 Wrote:(2014-07-21, 07:52)jsp1 Wrote:(2014-07-21, 01:52)Matt Devo Wrote: updated the wiki with some info on properly setting the color range, as well as a potential fix for those people having audio issues upon wake from suspend.
Still no problems with audio since fix here. Thank you!
Matt: I tried this and it did not work for me. Is there a way I can debug if autostart.sh is actually run when I resume from sleep? I added a line that writes the time to a log file, and I don't see that log after resuming from sleep.
jsp1: which fix are you referring to here? Is this something different than Matt's xrandr note on the wiki?
Thanks.
Afraid that was the fix I was referring to. I didn't post a follow up that I still ran into problems here and had just been especially lucky after applying the fix and had 8-10 resumes without an audio failure. Unfortunately, the fix doesn't seem to work in all cases. Sorry for not updating about that and getting hopes up. I have a feeling you are correct and that autostart.sh only works on a fresh start or reboot. I wonder if it could be scripted to somehow run on resume?
I did however, find that if you are using a harmony remote and you change up the CB power to last in the list and add a much longer delay 8-10k ms for example then you can mitigate the chances of dropping audio significantly. In my opinion the box simply resumes too fast for some AV receivers to be ready to receive a handshake properly. Since the audio device isn't something you can "keep alive" during a suspend state (especially if the AV receiver is down) then you need the script to wake it up on a delay in such a case, even if the autostart.sh is running on resume.