rdhardi 27 Posted June 4 Posted June 4 It’s been a while (over a year or more) since I tried the standard/universal Android app. I decided to try out the lastest version so I just installed it from the Play Store on my nVidia Shield 2019 (ver 11). The first thing I checked was Live TV, specifically my HEVC channels. I was very impressed with how fast they tuned in (much faster than on ATV). The picture quality is good. Then…I realized there was no sound! All the regular HD channels have sound, so the audio issue specific to ATSC 3.0 channels. I don't have this issue in the AndroidTV app. Is this a known issue in the beta or is it a user issue on my end? The log starts throwing errors as soon as an HEVC channel starts playing. I can provide logs if requested. Here’s a snip that I captured from the log: *** Error Report *** Version: 4.8.11.0 Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb Operating system: Linux version 5.15.0-139-generic (buildd@lcy02-amd64-067) (gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #149~20.0 Framework: .NET 6.0.36 OS/Process: x64/x64 Runtime: opt/emby-server/system/System.Private.CoreLib.dll Processor count: 8 Data path: /var/lib/emby Application path: /opt/emby-server/system Emby.Server.MediaEncoding.Unified.Ffmpeg.FfRunException: Emby.Server.MediaEncoding.Unified.Ffmpeg.FfRunException: Error running ffprobe: -analyzeduration 3000000 -i file:"/var/lib/emby/transcoding-temp/8687aeb8dd234eb09a631a45f3798d2c/0000000.ts" -threads 0 -v info -print_format json -show_streams -show_format -show_data ffprobe version 5.1-emby_2023_06_25 Copyright (c) 2007-2022 the FFmpeg developers and softworkz for Emby LLC built with gcc 10.3.0 (crosstool-NG 1.25.0) Assertion 0 failed at libavcodec/ac4dec.c:4186 at Emby.Server.MediaEncoding.Probing.MediaProbeManager.GetMediaInfoInternal(String inputPath, String primaryPath, MediaProtocol protocol, String userAgent, Boolean extractChapters, String probeSizeArgument, Boolean isAudio, Boolean hasMixedProtocols, CancellationToken cancellationToken) at Emby.Server.Implementations.Library.MediaSourceManager.AddMediaInfoWithProbe(MediaSourceInfo mediaSource, Boolean isAudio, Boolean addProbeDelay, CancellationToken cancellationToken) at Emby.Server.Implementations.Library.MediaSourceManager.AddMediaInfoWithProbeSafe(MediaSourceInfo mediaSource, Boolean isAudio, Boolean addProbeDelay, CancellationToken cancellationToken) Source: Emby.Server.MediaEncoding TargetSite: Void MoveNext()
Luke 40018 Posted June 4 Posted June 4 Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!
rdhardi 27 Posted June 4 Author Posted June 4 (edited) Logs attached. Rebooted Emby, started HEVC channel WLOS 113.1 at 19:20:07.818. Played for 5 minutes. Good picture quality, but NO sound. ETA: I tried to send logs from the app, but I don't see "Debug Options" as described in the link you posted. embyserver.txt hardware_detection-63884661008.txt Edited June 5 by rdhardi Add info 1
rdhardi 27 Posted June 5 Author Posted June 5 Uninstalled 3.4.70 and sideloaded 3.4.72. Still no sound.
CharlieMurphy 88 Posted June 8 Posted June 8 I'm getting this same error on two of my three atsc3 locals. "Assertion 0 failed at libavcodec/ac4dec.c:4186" Would it help to take sample files of the streams, @Luke?
CharlieMurphy 88 Posted June 8 Posted June 8 (edited) On 6/4/2025 at 3:15 PM, rdhardi said: I don't have this issue in the AndroidTV app. Are you sure of this? I haven't tried it in the AndroidTV app yet since I noticed the issue, but the error is coming from ffmpeg on the server when it tries to transcode the AC4 audio, for me. I assume it's the stations that have changed their broadcast and not the difference in the Emby apps. Edit to add: Working atsc3 channel ffprobe http://hdhr:5004/tuner1/v111.1 ffprobe version 5.1-emby_2023_06_25 Copyright (c) 2007-2022 the FFmpeg developers and softworkz for Emby LLC built with gcc 10.3.0 (crosstool-NG 1.25.0) Input #0, mpegts, from 'http://hdhr:5004/tuner1/v111.1': Duration: N/A, start: 25073.790356, bitrate: N/A Program 3 Stream #0:0[0x31]: Video: hevc (Main 10) ([36][0][0][0] / 0x0024), yuv420p10le(tv, bt709), 1280x720 [SAR 1:1 DAR 16:9], Level 120, 59.94 fps, 59.94 tbr, 90k tbn, Start-Time 25073.807s Stream #0:1[0x32](eng): Audio: ac4 (AC-4 / 0x342D4341), 46034 Hz, 5.1(side), fltp, Start-Time 25073.790s Stream #0:2[0x39]: Data: bin_data (STPP / 0x50505453), Start-Time 25079.796s Stream #0:3[0x33](spa): Audio: ac4 (AC-4 / 0x342D4341), 46034 Hz, stereo, fltp, Start-Time 25073.790s Unsupported codec with id 98314 for input stream 2 Not working channel: ffprobe http://hdhr:5004/tuner1/v144.1 ffprobe version 5.1-emby_2023_06_25 Copyright (c) 2007-2022 the FFmpeg developers and softworkz for Emby LLC built with gcc 10.3.0 (crosstool-NG 1.25.0) Assertion 0 failed at libavcodec/ac4dec.c:4186 Aborted (core dumped) sample.ts is taken from the not-working channel. sample.ts Edited June 8 by CharlieMurphy 1
rdhardi 27 Posted June 8 Author Posted June 8 5 hours ago, CharlieMurphy said: Are you sure of this? I haven't tried it in the AndroidTV app yet since I noticed the issue Now that you mention it, I realize it’s been a while (2-3 months, mabye more) since I watched ATSC3 channels on AndroidTV. They always played well with good picture quality AND sound - whenever they decided to play. Getting them to play sometimes required several attempts and lots of clicking. I got impatient and just gave up and started using the HDHomeRun app. I’ll check my AndroidTV when I get home. Thanks! 2
CharlieMurphy 88 Posted June 9 Posted June 9 I noticed in my testing that the stubbornness in playing a channel may be because the HDHR Flex 4k returns a 503 error about half of the time when you ask it for an atsc3 channel. Not sure why, I'm on the recently released firmware and the channels for that tower have excellent signal quality. 1
CharlieMurphy 88 Posted June 9 Posted June 9 That's the version I've been testing with and I'm not sure if the last firmware was doing the same because I updated it as I started my little mission. It all started with me moving my antenna away from trees, so the timing of me discovering this error so close to the start of this thread is pure coincidence.
rdhardi 27 Posted June 9 Author Posted June 9 23 hours ago, CharlieMurphy said: Are you sure of this? I haven't tried it in the AndroidTV app yet Just tested on AndroidTV v2.1.26g and my ATSC3 channels are NO longer working. As I mentioned, they’ve always been finicky but they eventually played. Not today…just the spinning circle. It shows up as "Now Playing" in the dashboard and shows stats in the HDHR Flex 4k Tuner Status, but no playback. So at this point, +1 for ATSC3 playback in Android for Emby. Although it doesn’t have sound (yet), it starts playing video almost immediately and the picture quality is excellent! 2
CharlieMurphy 88 Posted June 10 Posted June 10 Maybe what happened is that these locals enabled Atmos over AC4? 12 channels?!? DANG. Hopefully a fix is simple but I truly have no idea how decoders work. lol Stream #0:1[0x32](eng): Audio: ac4 (AC-4 / 0x342D4341), 46034 Hz, 12 channels (FL+FR+FC+LFE+FLC+FRC+SL+SR+TFL+TFR+T BL+TBR), fltp 1
rdhardi 27 Posted June 10 Author Posted June 10 (edited) 9 hours ago, CharlieMurphy said: Maybe what happened is that these locals enabled Atmos over AC4? 12 channels?!? DANG. Hopefully a fix is simple but I truly have no idea how decoders work. lol Lol, yeah I have no clue what's going on! You're defintely not alone, I have no idea how decoders work either. I've tried researching to understand...but my eyes start glazing over, and I'm like, huh?! Now I understand the "deer in headlights" look my users used to give me when I worked in IT support. Where did you see this...in the Emby logs? Stream #0:1[0x32](eng): Audio: ac4 (AC-4 / 0x342D4341), 46034 Hz, 12 channels (FL+FR+FC+LFE+FLC+FRC+SL+SR+TFL+TFR+T BL+TBR), fltp Edited June 10 by rdhardi corrections 1
CharlieMurphy 88 Posted June 11 Posted June 11 I used ffprobe from an ffmpeg build that is at least ac4 aware even if it still can't decode it. I think the main branch of ffmpeg at some point got the ability to remux it but not decode. 1
Luke 40018 Posted June 11 Posted June 11 In the near future we'll have an updated ffmpeg build on the server beta channel, just FYI. 1 1
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