\n
![](\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEi3xfaeSVwhItxPTRdI2vEUu6t8ZSJWKMYB6xWkb9inI8ab1GltWuCExl29Z8SAQ1Fo2A4moEQLykBdkjIZ_IqikrD-QrmkwWKCOaKALh5fMiV5SRRUM7JRmjavEZ64horigEBxNK5RtW_NI88_LjbqTa69Os3a-ADQbrNp7R5e78dXmkc7rsYyx3cRYdo\/s1600\/AndroidSpotlight_Camera&Media_Blog_Media3%201.5.0_Card%20%281%29.png\")
<\/p>\nPosted by Kristina Simakova \u2013 Engineering Manager<\/em><\/p>\n This article is cross-published on Medium<\/a><\/em><\/p>\n Transformer now supports motion photos and faster image encoding. We\u2019ve also simplified the setup for DefaultPreloadManager<\/span> and ExoPlayer<\/span>, making it easier to use. But that\u2019s not all! We\u2019ve included a new IAMF decoder, a Kotlin listener extension, and easier Player optimization through delegation.<\/p>\n To learn more about all new APIs and bug fixes, check out the full release notes<\/a>.<\/p>\n Transformer<\/span> now supports exporting motion photos. The motion photo\u2019s image is exported if the corresponding MediaItem<\/span>\u2019s image duration is set (see MediaItem.Builder().setImageDurationMs()<\/span>) Otherwise, the motion photo\u2019s video is exported. Note that the EditedMediaItem<\/span>\u2019s duration should not be set in either case as it will automatically be set to the corresponding MediaItem\u2019s image duration.<\/p>\n This release accelerates image-to-video encoding, thanks to optimizations in DefaultVideoFrameProcessor.queueInputBitmap()<\/span>. DefaultVideoFrameProcessor<\/span> now treats the Bitmap given to queueInputBitmap()<\/span> as immutable. The GL pipeline will resample and color-convert the input Bitmap only once. As a result, Transformer operations that take large (e.g. 12 megapixels) images as input execute faster.<\/p>\n Similar to VideoEncoderSettings<\/a><\/span>, Transformer now supports AudioEncoderSettings<\/span> which can be used to set the desired encoding profile and bitrate.<\/p>\n Transformer<\/span> now shifts the first video frame to start from 0. This fixes A\/V sync issues in some files where an edit list is present.<\/p>\n This release includes improved logging for unsupported track types, providing more detailed information for troubleshooting and debugging.<\/p>\n In one of the previous releases we added a new muxer library<\/a> which can be used to create MP4 container files. The media3 muxer offers support for a wide range of audio and video codecs<\/a>, enabling seamless handling of diverse media formats. This new library also brings advanced features including:<\/p>\n The muxer library can be included as a gradle dependency:<\/p>\n To use the media3 muxer with Transformer, set an InAppMuxer.Factory (which internally wraps media3 muxer) as the muxer factory when creating a Transformer:<\/p>\n With Media3 1.5.0, we added DefaultPreloadManager.Builder<\/span>, which makes it much easier to build the preload components and the player. Previously we asked you to instantiate several required components (RenderersFactory<\/span>, TrackSelectorFactory<\/span>, LoadControl<\/span>, BandwidthMeter<\/span> and preload \/ playback Looper<\/span>) first, and be super cautious on correctly sharing those components when injecting them into the DefaultPreloadManager<\/span> constructor and the ExoPlayer.Builder<\/span>. With the new DefaultPreloadManager.Builder<\/span> this becomes a lot simpler:<\/p>\n <\/p>\n <\/p>\n <\/p>\n We\u2019ve added the ability to preload the next item in the playlist of ExoPlayer<\/span>. By default, playlist preloading is disabled but can be enabled by setting the duration which should be preloaded to memory:<\/p>\n With the PreloadConfiguration<\/span> above, the player tries to preload five seconds of media for the next item in the playlist. Preloading is only started when no media is being loaded that is required for the ongoing playback. This way preloading doesn\u2019t compete for bandwidth with the primary playback.<\/p>\n When enabled, preloading can help minimize join latency when a user skips to the next item before the playback buffer reaches the next item. The first period of the next window is prepared and video, audio and text samples are preloaded into its sample queues. The preloaded period is later queued into the player with preloaded samples immediately available and ready to be fed to the codec for rendering.<\/p>\n Once opted-in, playlist preloading can be turned off again by using PreloadConfiguration.DEFAULT<\/span> to disable playlist preloading:<\/p>\n The 1.5.0 release includes a new media3-decoder-iamf<\/span> module, which allows playback of IAMF<\/a> immersive audio tracks in MP4 files. Apps wanting to try this out will need to build the libiamf<\/span> decoder locally. See the media3 README<\/a> for full instructions.<\/p>\n This release also includes a new media3-common-ktx<\/span> module, a home for Kotlin-specific functionality. The first version of this module contains a suspend function that lets the caller listen to Player.Listener.onEvents<\/span>. This is a building block that\u2019s used by the upcoming media3-ui-compose<\/span> module (launching with media3 1.6.0) to power a Jetpack Compose playback UI.<\/p>\n Media3 has provided a ForwardingPlayer<\/span> implementation since version 1.0.0, and we have previously suggested that apps should use it when they want to customize the way certain Player<\/span> operations work, by using the decorator pattern<\/a>. One very common use-case is to allow or disallow certain player commands (in order to show\/hide certain buttons in a UI). Unfortunately, doing this correctly with ForwardingPlayer<\/span> is surprisingly hard and error-prone, because you have to consistently override multiple methods, and handle the listener as well. The example code to demonstrate how fiddly this is too long for this blog, so we\u2019ve put it in a gist instead<\/a>.<\/p>\n In order to make these sorts of customizations easier, 1.5.0 includes a new ForwardingSimpleBasePlayer<\/span>, which builds on the consistency guarantees provided by SimpleBasePlayer<\/span> to make it easier to create consistent Player implementations following the decorator pattern. The same command-modifying Player<\/span> is now much simpler to implement:<\/p>\n Command buttons for media items allow a session app to declare commands supported by certain media items that then can be conveniently displayed and executed by a MediaController or MediaBrowser:<\/p>\n You’ll find the detailed documentation on android.developer.com<\/a>.<\/p>\n This is the Media3 equivalent of the legacy \u201ccustom browse actions\u201d API, with which Media3 is fully interoperable. Unlike the legacy API, command buttons for media items do not require a MediaLibraryService<\/span> but are a feature of the Media3 MediaSession<\/span> instead. Hence they are available for MediaController<\/span> and MediaBrowser<\/span> in the same way.<\/p>\n If you encounter any issues, have feature requests, or want to share feedback, please let us know using the Media3 issue tracker on GitHub<\/a>. We look forward to hearing from you!<\/p>\n <\/p>\n <\/p>\n This blog post is a part of Camera and Media Spotlight Week. We’re providing resources \u2013 blog posts, videos, sample code, and more \u2013 all designed to help you uplevel the media experiences in your app.<\/p>\n To learn more about what Spotlight Week has to offer and how it can benefit you, be sure to read our overview blog post<\/a>.<\/p>\n <\/em>\n<\/div>\n![](\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEh1PmhSCIphw3wGW7dJ9Yr7LLgG_6rqNwklO04UO6iZAsh6HjosgOn_SovJ8sEJvNYdeU08nMgnHQ3_L8F3pNU0Z72viRxqg8Ir0ceP-XVx45lkfImCbLnKywl7lho5CWJt0hBqt5dehuzLLpkrmkHdpTXRCzokmV4m3lswrsxAHWRHCstygUnK5PKCrO4\/s1600\/AndroidSpotlight_Camera&Media_Blog_Media3%201.5.0_Banner.png\")
<\/a><\/p>\nTransformer improvements<\/span><\/h2>\n
Motion photo support<\/span><\/h3>\n
Faster image encoding<\/span><\/h3>\n
AudioEncoderSettings<\/span><\/h3>\n
Edit list support<\/span><\/h3>\n
Unsupported track type logging<\/span><\/h3>\n
Media3 muxer<\/span><\/h2>\n
implementation (\"androidx.media3:media3-muxer:1.5.0\"<\/span>)\n<\/pre>\n<\/div>\nMedia3 muxer with Transformer<\/span><\/h3>\n
val<\/span> transformer = Transformer.Builder(context)\n .setMuxerFactory(InAppMuxer.Factory.Builder().build())\n .build()\n<\/pre>\n<\/div>\nSimpler setup for DefaultPreloadManager<\/span> and ExoPlayer<\/span><\/span><\/h2>\n
\n
\n
val<\/span> preloadManagerBuilder = DefaultPreloadManager.Builder()\nval<\/span> preloadManager = preloadManagerBuilder.build()\nval<\/span> player = preloadManagerBuilder.buildExoPlayer()\n<\/pre>\n<\/div>\n\n
\n
val<\/span> preloadManagerBuilder = DefaultPreloadManager.Builder().setRenderersFactory(customRenderersFactory)\n\/\/ The resulting preloadManager uses customRenderersFactory<\/span>\nval<\/span> preloadManager = preloadManagerBuilder.build()\n\/\/ The resulting player uses customRenderersFactory<\/span>\nval<\/span> player = preloadManagerBuilder.buildExoPlayer()\n<\/pre>\n<\/div>\n\n
\n
val<\/span> preloadManagerBuilder = DefaultPreloadManager.Builder()\nval<\/span> preloadManager = preloadManagerBuilder.build()\n\/\/ Tune the playback-only configurations<\/span>\nval<\/span> playerBuilder = ExoPlayer.Builder().setFooEnabled()\n\/\/ The resulting player will have playback feature \"Foo\" enabled<\/span>\nval<\/span> player = preloadManagerBuilder.buildExoPlayer(playerBuilder)\n<\/pre>\n<\/div>\nPreloading the next playlist item<\/span><\/h2>\n
player.preloadConfiguration =\n PreloadConfiguration(\/* targetPreloadDurationUs= *\/<\/span> 5<\/span>_000_000L)\n<\/pre>\n<\/div>\nplayer.preloadConfiguration = PreloadConfiguration.DEFAULT\n<\/pre>\n<\/div>\n
New IAMF decoder and Kotlin listener extension<\/span><\/h2>\n
implementation (\"androidx.media3:media3-decoder-iamf:1.5.0\"<\/span>)\n<\/pre>\n<\/div>\nimplementation (\"androidx.media3:media3-common-ktx:1.5.0\"<\/span>)\n<\/pre>\n<\/div>\nEasier Player customization via delegation<\/span><\/h2>\n
class<\/span> PlayerWithoutSeekToNext<\/span>(player: Player) : ForwardingSimpleBasePlayer(player) {\n override<\/span> fun<\/span> getState<\/span>(): State {\n val<\/span> state = super.getState()\n return<\/span> state\n .buildUpon()\n .setAvailableCommands(\n state.availableCommands.buildUpon().remove(COMMAND_SEEK_TO_NEXT).build()\n )\n .build()\n }\n\n \/\/ We don't need to override handleSeek, because it is guaranteed not to be called for<\/span>\n \/\/ COMMAND_SEEK_TO_NEXT since we've marked that command unavailable.<\/span>\n}\n<\/pre>\n<\/div>\nMediaSession: Command button for media items<\/span><\/h2>\n
<\/div>\n