2014-10-01, 15:08
Thanks both, I've only just had a chance to start testing it today.
I built a version of 13.2 with my suggested change of features to 0xF7 and the three patches suggested above. They did apply cleanly over 13.2 by cherry-picking:
https://github.com/DBMandrake/xbmc/commi...rplay_fix2
So far I've given it some testing on Windows 7 and it looks promising - as yet I have not been able to get airtunes (audio only) connections failing while using Amber, including having it automatically start full screen visualisation. As it was intermittent before it hasn't had enough testing yet to be conclusive about it.
I'll build the same version for my Mac at home and make it my default XBMC install for a few days and see how it behaves.
Any idea why only some skins were affected ? Is it just that the different skin triggers the race condition due to small differences in execution timing ? (So small that even turning debugging on and off had an effect...)
I built a version of 13.2 with my suggested change of features to 0xF7 and the three patches suggested above. They did apply cleanly over 13.2 by cherry-picking:
https://github.com/DBMandrake/xbmc/commi...rplay_fix2
So far I've given it some testing on Windows 7 and it looks promising - as yet I have not been able to get airtunes (audio only) connections failing while using Amber, including having it automatically start full screen visualisation. As it was intermittent before it hasn't had enough testing yet to be conclusive about it.
I'll build the same version for my Mac at home and make it my default XBMC install for a few days and see how it behaves.
Any idea why only some skins were affected ? Is it just that the different skin triggers the race condition due to small differences in execution timing ? (So small that even turning debugging on and off had an effect...)
