Jump to content

Search the Community

Showing results for tags 'distorted'.

  • 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 2 results

  1. I have two MKV files that I stream from a Windows emby server to a Raspberry Pi HTML5 client. One of them has perfectly fine audio, while the other has highly distorted audio (like if it was amplified 10 times, then compressed). The audio is distorted only on the Raspberry Pi client. If I read the same video on another client (Android app, or windows web client) the audio is perfect on both files. The Raspberry Pi client uses Chromium 65.0.3325.181 Built on Raspbian , running on Raspbian 9.8. Here are the specs of the file that does not distort the sound Here are the specs
  2. Hello, Sorry to dig this one up from the grave, as another thread indicated this issue was solved, but I'm afraid the answer given doesn't address the underlying issue. Essentially, it seems that the Roku app defaults to the primary image when browsing unset (mixed content), but uses the proportions for a thumb image. Unfortunately, as this thread below indicates, I don't think this is simply a matter of unset (mixed content) view vs. content type view. https://emby.media/community/index.php?/topic/55693-thumbs-as-primary-photo/ This actually seems like a bug and here's why: When
×
×
  • Create New...