varix 4 Posted June 17, 2025 Posted June 17, 2025 I'm trying to use Emby to access ATSC 3.0 channels from an HDHomeRun Flex 4K. I can receive four non-DRM channels on the HDHR, which all play OK on the HDHR app. Via Emby using an Android phone, I can watch all four of them live, with Emby showing it is using direct play for both audio and video. This also works with recordings made on Emby (the server is running on a Windows 10 computer). However, using the Emby app on an nVidia Shield, I can watch only two of the channels (both PBS--video and audio work, although the stream shows as being converted to a compatible container and the audio shows as being transcoded). FOX and CBS do not play; I get a blank screen with a spinning circle. Emby shows it is using direct play for audio and video. If I make a recording from FOX or CBS and choose to use an external player (VLC or MX player), the video plays but with no audio--I assume due to a lack of AC4 support on the Shield. [The behavior is mostly the same with a Windows web browser--Firefox, Chrome, or Edge--except instead of an endless spinning circle, I get "no compatible streams are currently available".] I assume the behavior reflects a difference between the Emby apps for Android vs. AndroidTV, along with the AC4 issue. Is there anything to be done to get the player working on the Shield--perhaps make it transcode for all channels the way it's doing for PBS? embyserver.txtembyserver.txt
Luke 42077 Posted June 17, 2025 Posted June 17, 2025 Hi. Can you try searching for our standard android app (Just "Emby" on Amazon and "Emby for Android on Google) on the same device's app store and see how that compares? Thanks.
varix 4 Posted June 17, 2025 Author Posted June 17, 2025 Using the generic Android app on the Shield, the video plays for CBS and FOX, but no audio. Interestingly, PBS still plays fine (audio and video), but now shows direct play for both, including AC4 audio.
Luke 42077 Posted June 17, 2025 Posted June 17, 2025 OK we'll take a look at the no audio issue. Thanks.
Luke 42077 Posted September 10, 2025 Posted September 10, 2025 @varixThis is the cause of the issue and we are following it: https://github.com/librempeg/librempeg/issues/95 Thanks.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now