You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It can be easily observed if DefaultBandwidthMeter is attached to DataSource. It notifies about bandwidth when transfer ends (when connection/socket is closed).
In my case:
UdpDataSource is used (multicast)
ExtractorSampleSource with TsExtractor
h264/mp2 stream
ExoPlayer from master (1.5.3)
It happens with ExtractorSampleSource.enable(int track, long positionUs) which calls restartFrom(long positionUs) which cancels Loadable which closes socket.
I've measured time between player goes to STATE_BUFFERING (and tracks info is available) and first video frame being rendered to surface
with loader reset: ~1.2sec
without reset: ~0.250sec
Checked 3 times for each situation on the same live stream.
With streams I'm using it drops ~300kb of data (collected in ~1.3sec).
The text was updated successfully, but these errors were encountered:
It can be easily observed if DefaultBandwidthMeter is attached to DataSource. It notifies about bandwidth when transfer ends (when connection/socket is closed).
In my case:
It happens with ExtractorSampleSource.enable(int track, long positionUs) which calls restartFrom(long positionUs) which cancels Loadable which closes socket.
I've measured time between player goes to STATE_BUFFERING (and tracks info is available) and first video frame being rendered to surface
Checked 3 times for each situation on the same live stream.
With streams I'm using it drops ~300kb of data (collected in ~1.3sec).
The text was updated successfully, but these errors were encountered: