Releases: veeplay/android-media-player
Releases · veeplay/android-media-player
2.0.5b
2.0.5
- Stability improvements / bugfixes
2.0.0
- added support for the Google Cast plugin
- added build.gradle file
2.0.0RC2
- updated Youtube API adding support for Lollipop
- updated supported color formats for Controls and Text overlays (RGBA, RGB, #RGBA and #RGB)
- minor bugfixes and API improvements in preparation of 2.0.0 final
2.0.0 RC1
- bugfix - cloning a unit did not also copy over the unit manager
- added support for multiple renderers. By default, VeePlay ships with two default renderers, MediaPlayerRenderer (used automatically for 4.0.x devices) and ExoPlayerRenderer(used automatically for 4.1+ devices)
- APSMediaUnit objects now hold a renderer string property. In order to explicitly set a renderer, use the static rendererIdentifier string of the renderer class.
- bugfix - transitioning to full screen and then changing orientation could cause an exception
- this version is a release candidate. Altough it was extensively tested over the past few weeks, it should be tested with each implementation before deploying into production
1.9.23
- bugfix - finishing the player during playback might cause a crash
1.9.22
- major internal player refactoring to allow multiple renderers, in preparation for ExoPlayer support
- bugfix: events with a high number of VAST sources might time out prematurely, causing them to be skipped
- bugfix: calling getCurrentPosition during a unit transition might have caused a crash
- increased default preload time to 10 seconds
1.9.21
- bugfix: calling resumePlay() before the VeePlay surface view was created would trigger an error and skipping to the next unit.
1.9.20
- improved stability and support for surface view state changes
1.9.19
-bugfix: setting an adbreak offset larger than 1 hour caused the offset to be marked as null.