Jump to content

Search the Community

Showing results for tags 'exoplayer'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 3 results

  1. Foxbat008

    Emby App & m2ts file format.

    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
  2. 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
  3. 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
×
×
  • Create New...