Search the Community

Hi, I want to warn you that the last stable version of the client for Android TV 2.0.83g was released by you in October 2022, a stable version that became obsolete almost immediately because it contained a very old and obsolete version of ExoPlayer as an internal player due to the inconvenience with many files containing DV - HDR10. Then just on January 26, 2023 they released an unstable Beta version 2.0.87g with the solution in the reproduction of many files that contain DV - HDR10 with the change of the internal ExoPlayer version. But since January 26, 2023 you abandoned the development of new stable versions of the client for Android TV with the latest unstable version 2.0.87g. I also want to warn you that the unstable version 2.0.87g has some problems, sometimes when watching several episodes of series one episode after another in a row, sometimes randomly when an episode ends and jumps to the next episode by mistake instead of starting from it. beginning at minute zero, erroneously starts playing in the middle of the episode, or near the end of the episode, when this error happens there is also a small popup legend of a few seconds, from the client for Android TV 2.0.87g that reports that various errors has happened, with the reproduction of movies the same error occurs much less frequently. Most likely you will tell me that instead of using the client for Android TV, that I use the other client for Android smartphones and tablets, but at this moment I have two drawbacks to use the client for smartphones and tablets, the first The problem is that the client Android 3.3.07 and earlier versions produces jumps and jerks in the images when the subtitles appear on the TV screen, with any subtitle format, be it SRT or PGS, just at the moment they appear on the screen. they produce jumps and jerks. The second problem is that the client for smartphones and tablets is for exclusive use with a PREMIERE subscription, and unfortunately, due to the tightening of the block and restrictions on transactions with foreign money imposed by the Argentine government, it is completely impossible to use dollars to buy a subscription PREMIERE. For these reasons, I need you guys to continue to release stable, bug-free versions of the client for Android TV. ¿For everything I have explained to you, I ask if you continue to develop new 100% stable versions without any playback errors in the client for Android TV?

I want to suggest you guys, please add LibVLC player as an alternative internal player to ExoPlayer. It's just a matter of adding a configuration option in the client for Android TV, in which I can choose between the different options ExoPlayer, or LibVLC, or an external player. An Emby competitor's Android TV client already has the configuration options ExoPlayer, or LibVLC, or automatic, or an external player. It is that if Emby's competitor already has two internal players, the official Emby clients would also have to have the internal LibVLC. Since the problem of playing MKV files, which contain Dolby Vision and HDR10, is unique to the Emby's ExoPlayer player, but if I had the option to choose LibVLC, right now I could play absolutely all my files that have DV and HDR10 with LibVLC, if you were as an internal player in the Emby client for Android TV. Although VLC a few years ago has problems with small jerks or jumps in the image when playing SRT text subtitle lines, I only use forced subtitles with a few lines of text in movies or TV series episodes. I leave you an attached image with the configuration options that should be added to the client for Android TV: Thanks. Greeting.

first ones the video themes. It seems that it plays the actual video instead of playing it in the background example:- Screen_Recording_20210412-033132_Emby.mp4 next ones the subtitles. For some reason, when you initially start a video, the subtitles tend to look very oddly generated but a quick restart of the app fixes it examples initially starting a video (the opening/intro subtitles gets jumbled up too) after a quick restart of the app This ones again with the subtitles. Sometimes, the complex styled subtitles tend to glitch out and never show up (the dialogues do show up after this specific opening) example Screen Recording 20210412-035313 Emby-1.mp4 sample video https://mega.nz/file/wkAwBJSQ#9XZtCTDzdnsxnC0baqmBHfMnn7jVV3ya7wBvNsYyQJY (skip by 10 seconds) I ran all the videos listed above in galaxy s10

Hi, I have a Minix NEO U9-H media player hub for Android connected to a Panasonic TV. I have installed Emby on the Minix device. The Emby App is great. My videos are in the m2ts format from a Sony Handycam. The Exoplayer transcodes these m2ts files which the video becomes shaky and jerky when viewing. I presume Exoplayer does not support direct play (of m2ts files) hence the need for transcode? Question: 1) Can you recommend any tweaks I can try to improve the quality of the transcode? 2) Will Exoplayer support direct play of m2ts files in the future? 3) Is there an android media player that supports m2ts directly and doesn't transcode? Thanks in Advance Regards Shane

Hello, Yesterday ExoPlayer released a new version that fixes SSA overlapping texts and supports positions. https://github.com/google/ExoPlayer/blob/release-v2/RELEASENOTES.md#2110-2019-12-11 Just wondering if we the android tv app will get updated soon with this version. If this feature works correctly there will be no reason to transcode this kind of subtitle. Regards

Hello, I can not seek/resume videos which require remuxing on my NVIDIA Shield using the Emby for Android TV's internal Player (exoplayer?). Whenever I try to resume, rewind or fast forward a video that is being remuxed, the video skips to the correct frame it is supposed to continue from but then stays there. According to ffmpeg logs and watching the size of the created tmp directory file transcoding works fine. If I play the video from beginning to end it works just fine. Also videos that are "direct play" or transcoded work fine including seek and resume - only "direct stream" is a problem. Workarounds are switching to use external player (vlc) or setting max bitrate low to force transcoding. What I have tried: - switching audio to "direct" and "downmix to stereo" - accessing emby server directly (8920 and 8096) - accessing emby server via nginx reverse proxy (ssl and unencrypted) - nginx: with and without http2 enabled - access emby server by hostname or ip - switching ffmpeg versions (3.1.4, 3.1.5, ffmpeg-git-20160215-64bit-static) - move transcoding temp folder to local or nfs storage This has been happening across several emby-server and emby for android tv versions. Possibly related: https://emby.media/community/index.php?/topic/43008-on-remux-android-tv-times-out-too-many-errors/ though I do not receive any errors on the client. Interestingly enough while trying various settings/configurations fast forwarding worked on one occasion yesterday though not repeatable. There is nothing in the server or ffmpeg logs which is different from attempts where it fails. I attached the logs of the attempt where the first fast forward worked (ffmpeg -ss 00:05:26.589 ...) while the second attempt on the same video with the same settings about 30 seconds later failed (ffmpeg -ss 00:11:21.392 ...). ffmpeg1.txt ffmpeg2_fast_forward_success.txt ffmpeg3_fast_forward_fail.txt server.txt