Pausing progress if it was playing and the stating again #526
Conversation
* master: Added flag for background mode (TheWidlarzGroup#563) issue 310 - Added a new property, ignoreSilentSwitch. (TheWidlarzGroup#403) Add progressUpdateInterval to android-exoplayer (TheWidlarzGroup#540) Initial WPF Support (TheWidlarzGroup#385) added progressUpdateInterval to Android (TheWidlarzGroup#512) load new source if it is different (TheWidlarzGroup#502) Pausing progress if it was playing and the stating again (TheWidlarzGroup#526) bump android dependencies (TheWidlarzGroup#524) Update ExoPlayer to r2.2.0 (TheWidlarzGroup#505) Update readme (TheWidlarzGroup#497) [Android] App crash when unmounting video (TheWidlarzGroup#533) Fix/494 (TheWidlarzGroup#537) fix(RCTVideo.m): Fixed status bar disappearing issue
|
@deshiknaves can you please explain why this was added and what the intended behaviour is? This introduced a regression for us where the 'paused' and 'rate' properties are being ignored as a result of this change. It looks like the paused and rate props are being ignored when setting the video to playing with this change. Reproduced by seeking a video to 0 then setting the paused and rate props to pause the video. Video will autoplay from 0. |
|
When you scrub a track, and it doesn't have it buffered already, then it continues to play until it has enough to play. Normal behavior is for it to stop and then start up when it can play. This was to make it stop if it is playing if it's playing and then restart it when there is enough to play. Maybe it needs to check more flags? |
When loading a network resource, when seeking the player has really weird behavior of it continuing to play till it has buffered enough to play. Also when it is buffering, it doesn't notify that it is buffering. At least this way, some logic can be added to
onProgressto track when the audio is not actually playing.