2012-09-01, 23:45
Glad to hear you are able to reproduce it and working on it!
THX for that and your time you're spending!
THX for that and your time you're spending!
(2012-09-01, 23:45)sw4y Wrote: Glad to hear you are able to reproduce it and working on it!
THX for that and your time you're spending!
(2012-09-01, 23:31)DDDamian Wrote:(2012-09-01, 23:23)Voyager-xbmc Wrote:(2012-09-01, 18:14)WiSo Wrote: A brief look reviled nothing but I could miss something.
@WiSo - as said, I have reverted the commit and everything works great. Just to test the theory a bit further, I commented out the call to SDL_Init in CApplication::CreateGUI (around line 800, inside #ifdef HAS_SDL block) plus the associated if block... and voila, the problem is back!
So this proves that the removal of SDL (and implicitly the call to SDL_Init) has caused all this.
So even though SDL_Init is called with no flags (0), somehow, stuff gets initialized that influences the stability of video playback.
I checked out SDL source code here, and all I see is threading initialization, and timer ticks initialization. All other subsystems are not started because of the "0" parameter. Back to the timer ticker. On Windows SDL calls QueryPerformanceCounter(). That's as far as my analysis goes, everything else would be speculation.
The WASAPI sink also uses QueryPerformanceCounter frequently - although it should be a thread-safe call I wonder if that's locking things up briefly. You can test using a debug build - the calls from the sink to the performance counter are ifdef'd out in debug mode. If this stabilizes it we may be closer to an answer.
(2012-09-02, 04:45)DDDamian Wrote:(2012-09-01, 23:45)sw4y Wrote: Glad to hear you are able to reproduce it and working on it!
THX for that and your time you're spending!
Patched up - please let me know (anybody) if the issue is resolved with tmo's nightly. Thx.
(2012-09-02, 17:26)jpsdr Wrote: @voyager-xbmc : Thanks. Apparently it fixes also the ticket 13277 i've opened.
(2012-09-02, 18:36)maruchan Wrote: Running the latest nightly, I'm still seeing some FPS oddities on my setup, unfortunately I'll post some logs later tonight. I'm using an old budget receiver that only supports AC3 and while overall it's MUCH improved, a quick test converting 5.1 DTS to 5.1 AC3 is causing stutters every 5 seconds or so. Enabling "Output sound to all speakers" makes the stutter much more pronounced. CPU usage is sitting in the low single digits, so I don't think it's that.
(2012-09-02, 18:02)DDDamian Wrote:(2012-09-02, 17:26)jpsdr Wrote: @voyager-xbmc : Thanks. Apparently it fixes also the ticket 13277 i've opened.
Very nice - marked ticket as resolved and closed it. Great work Voyager.
(2012-09-03, 05:01)maruchan Wrote: Just had a chance to build a binary from head and the problem still persists Here's a log file:
http://xbmclogs.com/show.php?id=7827&hash=46641207
Let me know if I can provide any other information.
<advancedsettings>
<loglevelrem>1</loglevelrem>
<audio>
<audiosinkbufferdurationmsec>200</audiosinkbufferdurationmsec>
</audio>
</advancedsettings>