Google i/o 2018 - ExoPlayer 2.8

• MediaPlayer for Android and across all different devices
• API Level >= 16
• Open source in Github
• Used in 200,000 apps
• advanced functionality
• caching and offline to their application 
• ExoPlayer's extension modules with Google API (MediaSession, Cast, Interactive Media Ads)
• 2.8.0
• https://github.com/google/ExoPlayer/releases
  
• Exo-Player-Core, Exo-Player-Ui
• 
• 
  
• extension-Ima
• 
• 
  
• Audio Player with Notification 
• 
• 
  
• extension-mediassesion - Audio Palyer with Android Framework 
• MediaSessionConnect syncs the player state with the state of  MediaSession and retrieves commands from the MediaSession of Android Framework.
• 
• 
• 
  
• download functions for offline playback

• when the MediaSource request some data, it’s going to ask the CacheDataSource to provide that information. The CacheDataSource is going to look in the cache. If it is present there, then we can get the data from the local storage. On the other hand, if the data is not present in the cache, we’ve got a cache miss, then the CacheDataSource needs to go to the DataSource that’s being used to load from the network, and requests the data from the network, and then it’s going to store in the cache when it arrives. The cache gradually gets populated with the data that’s loaded during playback.

  The CacheEvictor is responsible for making sure that our cache doesn’t grow indefinitely as we play more and more different media items. The NoCacheEvictor implements CacheEvictor. It is never going to remove(evict) data from the cache for the current video. This is for that we don’t want to the situation downloading the stream and we are getting rid of the stream. It is very annoying for the users.

  We can get the every cache data from the CacheDataSource, then there’s never a need to go to network.

  
  

• 
  

  

  
  

• 

  
  

sample - https://github.com/SeungwonLee/ExoPlayer2.8Test

refer - https://www.youtube.com/watch?v=svdq1BWl4r8