#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by richardpl): * priority: normal => wish * resolution: wontfix => * status: closed => reopened * component: avcodec => undetermined -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by wriede): * cc: wrb2c@… (added) Comment: ATSC3.0 Broadcast video uses AC-4 sound. Support for AC-4 in ffmpeg appears to be required for Plex TV to be used to play such video streams. I would like to see renewed urgency for this feature. Unfortunately I don't have enough knowledge on the subject to program something like this but I would be happy to help testing if that's of use. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:4> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by talkenrain): * cc: talkenrain@… (added) Comment: There is a growing need for Dolby AC4 support within ffmpeg. As ATSC 3.0 broadcast becomes mainstream across the US many applications (like PLEX) depend on ffmpegs support of AC4 to be compatible with this growing format. Hardware that requires support has already hit the market. Please add me to the list of willing beta testers as the lack of AC4 support is now the only obstacle to full support with PLEX. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:6> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * priority: important => wish -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:8> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * priority: important => wish -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:10> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by richardpl): Post short samples of various configurations. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:12> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by richardpl): Looks like nobody cares about AC-4, because if they care they would actually provide AC-4 samples here. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:14> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by kyl416): Replying to [comment:14 richardpl]:

Looks like nobody cares about AC-4, because if they care they would actually provide AC-4 samples here. siryurian just posted a sample for ATSC 3.0, but links to multiple AC-4 samples were already provided via the DASH IF link in the bug report. Just click "Accept" on their TOS popup and refresh the page to get a dozen different samples.

-- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:15> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by CBme): Replying to [comment:14 richardpl]:

Looks like nobody cares about AC-4, because if they care they would actually provide AC-4 samples here.

That is false and absurd statement for a number of reasons. Here are 100 comments and rising of people starting to realize this show stopping problem. https://forum.silicondust.com/forum/viewtopic.php?f=133&t=74323 To any interested devs, please let us non devs know what is needed. How many clips? Does the video content matter (HD, standard def, progressive/interlaced). Do you want it where it transitions into commercials? etc. Here is two longer HD clips from a progressive and borked interlaced stream (due to bug 4141) for anyone who can use them. https://1drv.ms/u/s!Ap22nCAxKBS7j-Jr9Q8eX45gp2Uh7w?e=3miW5h -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:17> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Nomis101): Ah, sorry, the "0 channel" thing was just because of AV_CODEC_CAP_CHANNEL_CONF. If I add that to ac4dec.c I have sound with the sample files from above. So, it seems with this patch we are on a good way... ffplay /Users/Nomis101/Downloads/ABC\ Stream\ -\ FFmpeg\ bug\ \#8349.ts ffplay version N-100421-g1eb751955e Copyright (c) 2003-2020 the FFmpeg developers built with Apple clang version 12.0.0 (clang-1200.0.32.28) configuration: --pkg-config-flags=--static --enable-swscale --enable- avfilter --enable-fontconfig --enable-gpl --enable-version3 --enable- libass --enable-libbluray --enable-libfreetype --enable-libsoxr --enable- libaom --enable-libmp3lame --enable-librav1e --enable-encoder=librav1e --enable-libtheora --enable-libvorbis --enable-libvpx --disable-debug --enable-libmysofa --enable-libx264 --enable-libx265 --enable-libxvid --enable-nonfree --enable-libfdk-aac --enable-muxer=mov --enable-muxer=mp4 --enable-muxer=ipod --enable-encoder=eac3 --enable-encoder=ac3 --enable- encoder=flac --enable-ffplay --enable-librtmp --enable-libsmbclient --enable-opencl --enable-libssh --enable-openssl --enable-encoder=truehd --enable-bsf=aac_adtstoasc --enable-encoder=h264_videotoolbox --enable- encoder=hevc_videotoolbox --enable-sdl --extra-ldflags=-L/opt/local/lib libavutil 56. 62.100 / 56. 62.100 libavcodec 58.115.102 / 58.115.102 libavformat 58. 65.100 / 58. 65.100 libavdevice 58. 11.103 / 58. 11.103 libavfilter 7. 93.100 / 7. 93.100 libswscale 5. 8.100 / 5. 8.100 libswresample 3. 8.100 / 3. 8.100 libpostproc 55. 8.100 / 55. 8.100 [mpegts @ 0x7fd2f082ac00] stream 3 : no PTS found at end of file, duration not set Input #0, mpegts, from '/Users/Nomis101/Downloads/ABC Stream - FFmpeg bug #8349.ts': Duration: 00:01:15.34, start: 12951.873511, bitrate: 3690 kb/s Program 3 Stream #0:0[0x31]: Video: hevc (Main 10) ([36][0][0][0] / 0x0024), yuv420p10le(tv), 1280x720 [SAR 1:1 DAR 16:9], 59.94 fps, 59.94 tbr, 90k tbn, 59.94 tbc Stream #0:1[0x32](eng): Audio: ac4 (AC-4 / 0x342D4341), 48000 Hz, 5.1(side), fltp Stream #0:2[0x33](spa): Audio: ac4 (AC-4 / 0x342D4341), 48000 Hz, stereo, fltp Stream #0:3[0x3a](ee`): Audio: ac4 (STPP / 0x50505453), 48000 Hz, 3.0, fltp [hevc @ 0x7fd308885c00] Could not find ref with POC 56 13030.02 A-V: 0.019 fd= 174 aq= 0KB vq= 0KB sq= 0B f=0/0 -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:19> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by richardpl): Do you have samples to reproduce this, as that patch contradicts with specifications. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:21> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by georgeP): All i know is all the main stations in seattle have switched to ATSC 3.0 so I upgraded to a new HDHomeRun 4k for my Plex DVR. All I can see is really clear video with no audio stream found. So no football for me or anyone else in the same situation. Happy to help however I can and willing to chip in if needed. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:23> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Balling): Another sample is here https://github.com/yaronzz/Tidal-Media- Downloader/files/4746747/01.-.Believer.feat.Lil.Wayne.mp4.zip -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:25> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by vogateer): I've uploaded a TS file from an OKC OTA station with AC-4 audio here: https://drive.google.com/file/d/1xpEyd59cD4NgLtfYsWuBOrMjovzCO7xj/view?usp=s... Unfortunately I can't figure out how to demux the TS file and just upload the audio portion. If anyone has instructions for that, please let me know. I could record multiple samples. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:27> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by mooninite): Replying to [comment:22 richardpl]:

This is latest AC4 WIP code: https://github.com/richardpl/FFmpeg/tree/ac4

I tested these patches against a 4.3 branch (Fedora/RPMFusion) and could successfully play live streaming data in the Dallas, TX market from a SiliconDust CONNECT 4K and Kodi. Audio is working. Thanks! -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:29> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by csdesigns): * Attachment "atsc3.ts" added. ATSC 3.0 OTA 5.1 -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: reopened Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by LostDog): I compiled the ac4 branch at https://github.com/richardpl/FFmpeg/tree/ac4 using Linux Mint 20.1. It built successfully and I was able to play the atsc3.ts samples with AC-4 audio using ffplay. I've not been able to compile VLC or Kodi against this branch but I'm suspecting it's due to my own lack of understanding rather than the branch code. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:32> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

Let us know if you're successful. I'd really like to have a PVR that records and plays ATSC3.0 streams without using a bunch of scripts and hacks. Over at the NextPVR forums there's a guy who has written some

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by LostDog): Replying to [comment:33 ferrellsl]: python scripts that use the binaries from this tree to transcode the ATSC3.0/AC4 audio stream into AC3 on-the-fly but I'm hoping for a cleaner solution.

For now, I can still record my ATSC3.0 channels using NextPVR and use

the binaries from this tree for playback of those ATSC3.0 recordings without transcoding, and of course all the 4K channels in the Phoenix area are mirrored in 1080p/ATSC1.0 channels. I'm quite pleased with richardpl's progress. I was expecting things to move much slower than they have, or not at all. At least now I have a poor-man's PVR using scripts for playback. Having AC4 integrated natively into VLC, Kodi, or NextPVR would be very welcome from my standpoint.

I have successfully built Kodi v18.9 against the AC-4 branch of ffmpeg. ATSC3.0 captures work seemingly flawlessly with audio. I cannot verify if it's 5.1 and the channels are correct but on my computer with stereo headphones the audio sounds great. Tuning live ATSC3.0 is really buggy using the HDHomerun plugins but it will occasionally play and when it does there is audio. I don't think this has anything to do with ffmpeg but rather the plugins themselves. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:34> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by ferrellsl): I decided to build an AC-4 capable video player based on the code found here: https://github.com/itisyang/playerdemo It only has 3 dependencies, SDL2, QT, and ffmpeg so I set about updating it to support richardpl's ffmpeg/AC4 branch. I normally avoid github projects that depend on QT for several reasons but this project is very well-written and modular so it was very easy to compile it against the ffmpeg/AC4 branch. The majority of my time was spent Anglicizing all the dialogs and menus because the author is Chinese and had hardcoded most of the menus and dialogs. I also added the ability to read mpeg TS files directly as that was missing. I've tested it on MKV files and TS files containing AC-4 audio streams and it works great so I suspect it will read any format supported by ffmpeg. My build environment is Visual Studio 2015 and QT5.6 and the binary is 64-bit. My apologies to those who want 32-bit builds but I have no desire to re-tool my developer system which is entirely 64-bit. I'm an applications developer, not a video (encode/decode) - (mux/demux) developer, so I will only be able to help you squash bugs in the UI and possibly add more file types. You can download the Player here: https://www.dropbox.com/s/uuf16gxqs2s4bqk/Player-AC4.zip?dl=1 Just unzip the files to the folder of your choice and run the playerdemo.exe file. If you want to test it, here's a 40MB TS file with HEVC video encoding and AC-4 audio: https://www.dropbox.com/s/vzv66pz54phfskl/v161.1.ts?dl=1 Anyway, I hope somebody will get some use out of this player. It was actually a pleasure to update and build, unlike VLC which is a total dumpster fire. The keyboard shortcuts can be found under the About dialog, just right- click on the screen to bring up the context menu. If want to use this player to view your SiliconDust tuner's media streams, you can do so with the ffmpeg.exe in the archive here: https://www.dropbox.com/s/bze1a5nrhq63u20/ffmpeg-ac4-msys2-shared.zip?dl=1 For example, to stream channel 161.1 here in Phoenix which uses HEVC and AC4 audio, open a command prompt and type: ffmpeg -i http://x.x.x.x:5004/auto/v161.1 -b 900k -vcodec copy -r 60 -y test.mkv Just change the X's to your tuner's IP address. This will create an ever growing video file named test.mkv in the same folder as your ffmpeg.exe file. Now just run the playerdemo.exe and open the test.mkv file. You can also just use wget to get the raw TS stream: wget -O test.ts http://x.x.x.x:5004/auto/v161.1 Then use the player to open the TS file. This also works for RTSP camera streams as well. For password protected cameras substitute your user ID and password, your camera's IP address and stream path I.e: ffmpeg -i rtsp://admin:password@x.x.x.x:554/x -b 900k -vcodec copy -r 60 -y test.mkv For cameras not using a password: ffmpeg -i rtsp://x.x.x.x:554/x -b 900k -vcodec copy -r 60 -y test.mkv -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:36> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: open Priority: important | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by ferrellsl): Replying to [comment:37 Moe247]:

So I'm new to this. I'm on Plex installed on Ubuntu. I cloned this: https://github.com/richardpl/FFmpeg/tree/ac4. Configured it, but I'm unsure how to get plex use it. I appreciate any advice.

If you've already ran the ./configure command, then all you should need to do is run make, and then run make install. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:38> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Moe247): Replying to [comment:39 cehoyos]: I did as you said. Unfortunately, no luck. I even tried both copying the binary to the PMS folder and creating a symbolic link, with no success. I'm a noob, sorry. Thank you for your time. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:40> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:40 Moe247]:

Replying to [comment:39 cehoyos]:

I'm a noob, sorry.

I don't know your exact task, but in this case, you should probably wait for a package made by somebody else. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:42> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by tmm1): Replying to [comment:21 richardpl]:

Do you have samples to reproduce this, as that patch contradicts with specifications.

The sample in comment:27 reproduces, as does this one: https://tmm1.s3.amazonaws.com/atsc3-aspx-num-env.ts Where in the spec does it state that aspx_num_env is capped at 5? -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:44> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by ferrellsl): Replying to [comment:45 ferrellsl]:

Here's an updated player with streaming support so there's no longer a need for ffmpeg, wget or other app to capture HEVC/AC-4 streams to a file before playback. I've tested this player with http:// streams from my HDHomeRun tuner as well as an rtsp:// security camera at my home. It still supports AC-4 and HEVC.

To play an HEVC/AC-4 stream, or any other type of stream from your HDHomeRun tuner or web server, enter the channel's URL as found in your channel lineup (Ex: http://x.x.x.x:5004/auto/v161.1 ) into the video selection dialog box or select a local file for videos stored locally.

Download link: https://www.dropbox.com/s/eft7u6d0ajp2twu/Videoplayer- AC4-streaming%20support.zip?dl=1

This player is based on code found here: https://github.com/yundiantech/VideoPlayer

It took me several hours to track down an annoying audio bug/crackle but it works great now.

I squashed a few more bugs and moved the source code as well as the 64-bit Windows installer over to github. The earlier version experienced a strange video buffer underrun after several minutes of streaming from my tuner that caused the video to become choppy. This has been fixed. You can get the latest release here: https://github.com/ferrellsl/VideoPlayer/releases/download/v1.0 /VideoPlayer-AC4-setup.exe -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:46> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by ferrellsl): Replying to [comment:47 richardpl]:

Is this open source or what kind of endorsement is this at all?

I'm not an expert on all the licensing issues and I'm not sure what you mean by endorsement so I just chose "Unlicense" when github asked which license I wanted to use when I created the repository for the video player. It's open source as I understand it and I don't care what anyone wants to do with the code. The other dependencies (SDL2, QT, and your experimental ffmpeg branch) weren't modified in any way so whatever terms those dependencies were released under still apply to those dependencies. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:48> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by dotjoel): I just wanted to point out that there is a bounty on this feature. https://www.bountysource.com/issues/83125729-dolby-ac-4-support -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:50> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by Jim Scarborough): * cc: Jim Scarborough (added) -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:52> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

Looks like nobody cares about AC-4, because if they care they would actually provide AC-4 samples here. I realize this post is quite dated now; but I wanted to highlight that for

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Nicholas S Jenkins): Replying to [comment:14 Elon Musk]: people with HDHomeRun Connect 4K devices (and I assume successor Flex devices) that there is a trivially easy way for people in ATSC3.0 broadcast areas to capture raw feeds for testing with: https://info.hdhomerun.com/info/troubleshooting:creating_a_sample remember that ATSC3.0 stations are presented by HDHR as 100+channel number, so for me (picking up Cincinnati), 105.1, 109.1, 112.1, etc. Example curl command: curl http://192.168.0.37:5004/auto/v112.1?duration=120 > ../test_capture_of_112_1.ts This capture avoids automatic transcoding by ffmpeg/ffmpeg-derived tools that will otherwise try to demux/remux and decode/encode broadcast formats (e.g. HEVC/AC-4) into assumed-preferred formats (e.g. MP2/H.264). Since I'm now able to record off-air, I hope to help in testing + probably code integration into head branch of ffmpeg. On a related note... do you know why?: 1) The Richardpl fork indicates it's from an ffmpeg branch 3 years old, and that can't be readily updated to current ffmpeg version (no big deal, only ~dozen sources look related to AC-4, but just curious) 2) but this thread would suggest the code is only 10 months old? ... and is there a separate discussion / real effort underway to integrate the code into ffmpeg head? (I wouldn't want to duplicate effort, but rather assist) -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:54> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by kenmac999): * Attachment "capture5003.ts" added. recorded from OKC Physical Channel atsc3:503000000:2 -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Bo Xu): Replying to [comment:29 mooninite]:

Replying to [comment:22 richardpl]:

...

This is latest AC4 WIP code: https://github.com/richardpl/FFmpeg/tree/ac4

I tested these patches against a 4.3 branch (Fedora/RPMFusion) and could successfully play live streaming data in the Dallas, TX market from a SiliconDust CONNECT 4K and Kodi. Audio is working. Thanks!

Thanks for the ac4-branch! I cloned it (https://github.com/richardpl/FFmpeg/tree/ac4) and also checkout ac4-branch, but after I built it (in macOS with M1-cpu), I can replay atsc3.ts and got the video, but cannot hear audio. could you let me know how do you configure ac4-branch when building it or could you copy your configure-parameters to me? Thanks! (the following is my configure parameters): ./configure --prefix=/Users/boxu/Desktop/boxu/LIBs/ffmpeg_ORIG/ffmpeg- ac4/FFmpeg/build --enable-swscale --enable-libmp3lame --enable-libvorbis --enable-libopus --enable-librsvg --enable-libtheora --enable-libopenjpeg --enable-libmodplug --enable-libsoxr --enable-libspeex --enable-libass --enable-libbluray --enable-lzma --enable-gnutls --enable-fontconfig --enable-libfreetype --enable-libfribidi --disable-libjack --disable- libopencore-amrnb --disable-libopencore-amrwb --disable-libxcb --disable- libxcb-shm --disable-libxcb-xfixes --disable-indev=jack --enable-opencl --disable-outdev=xv --enable-audiotoolbox --enable-videotoolbox --enable- sdl2 --disable-securetransport --mandir=/opt/local/share/man --enable- static --enable-pthreads --cc=/usr/bin/clang --enable-libx265 --enable-gpl --enable-postproc --enable-libx264 --enable-libxvid --enable-nonfree --enable-libfdk-aac --extra-ldflags=-L/opt/local/lib --disable-x86asm --enable-shared --enable-static --enable-encoder=eac3 --enable-encoder=ac3 --enable-decoder=ac4 --disable-avfilter -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:57> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by skyler): What I would like to know is whether there is a static build of ffmpeg similar to John VanSickle's build at https://johnvansickle.com/ffmpeg/ that include the AC4 support. In case anyone wonders why people are wanting this, I refer you to the thread at https://forum.silicondust.com/forum/viewtopic.php?t=77067&sid=0446c9341c1db6d3f24a2db24a5dd059 which in a series of posts pretty much explains the current situation. But the short version is that if you purchase a HDHomeRun tuner capable of receiving ATSC3 signals, by default you probably won't get a usable audio signal unless all your equipment is very new (basically it must have Dolby Atmos support, as I understand it). This also means you don't get audio on things like computer desktop systems or HTPC's, since none of them that I'm aware of have AC4 audio support. Silicon Dust's current solution is to have their devices send the AC4 audio to a cloud server where the audio is turned around and sent back to the device as a two channel STEREO stream. So instead of getting 5.1 audio as is usual with current ATSC1, you get 1970's era stereo. And there are other disadvantages as well - if you lose your internet connection or it gets very congested (as might happen when hundreds of users are all sending streams to be decoded during prime time), you would lose the audio and possibly would not be able to view or record live TV. If you record a show using backend software (Tvheadend, MythTV, etc.) you will either record the AC4 audio (which still can't be played on most devices) or the stereo from the cloud server, depending I suppose on how you have configured the HDHomeRun device. And also, for those who care about such things, it gives Silicon Dust a way to track what you are watching (which is a big NOPE as far as I'm concerned, although some people don't seem to care if their viewing habits are tracked). A version of ffmpeg with AC4 support, on the other hand, should be able to convert the AC4 audio to AC3 or AAC or even MP2, whatever would be compatible with a user's receiver or computer or HTPC in almost real time, or on a previously recorded program if that is desired. And this would not be in any way dependent on Silicon Dust's servers, nor would it limit you to only two audio channels. I might have purchased a new HDHomeRun device with ATSC3 support almost a year ago, when stations in my area first started offering ATSC3 programming, if it weren't for the stupid way they are handling the audio. Now, I think the U.S. FCC made a big mistake by allowing the use of AC4 in the first place, but that's another discussion for another forum. In the meantime, it would be really helpful if support for AC4 decoding could be included in either the main ffmpeg distribution, or failing that, in a static build that will run on Linux systems so it can be used with server- based backends like Tvheadend or MythTV or similar software (similar to the John Van Sickle build). Really, I would think that only AC4 decoding is needed at the present time; I can't think of a single situation where anyone would want to encode using AC4 and would not already have access to a hardware-based encoder. I know some of you guys are conversant enough in Linux to be able to build your own custom builds of ffmpeg and that is great, but I haven't the foggiest idea how to do something like that and unless someone publishes "cookbook" type instructions (or better yet, a video walkthough of how to do it) on a Linux system, that will probably forever be beyond my skill set. That's why I would really like to see this in the main ffmpeg distribution, or at least in a separate static build at some point in the not too distant future. Right now all ATSC3 signals are still available as ATSC1 (though not always with the exact same coverage areas) but that will not be the case forever. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:59> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by Carl Eugen Hoyos): * priority: important => wish -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:61> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

Thank you for your work! I was able to build and run ffplay via your branch. I took the commits, made some minor changes to pass fate, and rebased to be merged without conflict. Code has been published on my

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by skyler): Replying to [comment:58 Mark Bumiller]: personal fork https://github.com/makrsmark/FFmpeg/tree/ac4 Thank you for posting that. After a lot of trial and error we were able to get it to compile but for some reason it still is not putting audio in the output file. When I run it using "ffmpeg -i raw.ts -c copy -c:a ac3 -map 0:0 -map 0:2 atsc3test.ts" I see this: {{{ Input #0, mpegts, from 'raw.ts': Duration: 00:00:59.44, start: 43533.303533, bitrate: 1369 kb/s Program 3 Stream #0:0[0x31]: Video: hevc (Main 10) ([36][0][0][0] / 0x0024), yuv420p10le(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], Closed Captions, 59.94 fps, 59.94 tbr, 90k tbn Stream #0:1[0x32](spa): Data: bin_data (AC-4 / 0x342D4341) Stream #0:2[0x33](eng): Data: bin_data (AC-4 / 0x342D4341) Stream #0:3[0x39](eng): Data: bin_data (STPP / 0x50505453) Output #0, mpegts, to 'atsc3test.ts': Metadata: encoder : Lavf59.30.101 Stream #0:0: Video: hevc (Main 10) ([36][0][0][0] / 0x0024), yuv420p10le(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 59.94 fps, 59.94 tbr, 90k tbn Stream #0:1(eng): Data: bin_data (AC-4 / 0x342D4341) Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:2 -> #0:1 (copy) Press [q] to stop, [?] for help [mpegts @ 0x55eed5f66600] Stream 1, codec bin_data, is muxed as a private data stream and may not be recognized upon reading. frame= 3557 fps=0.0 q=-1.0 Lsize= 8910kB time=00:00:59.44 bitrate=1227.9kbits/s speed= 403x video:7145kB audio:0kB subtitle:0kB other streams:701kB global headers:0kB muxing overhead: 13.561085% }}} As you can see it identifies stream 0:2 as the English language stream, which is why I am using the map options, but if I don't use them I still get no sound. I have tried converting the audio to ac3, eac3, and aac with no luck. I always see the error message "Stream 1, codec bin_data, is muxed as a private data stream and may not be recognized upon reading." But, I have no idea what that means or if it is relevant. Are there different options I should be using? -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:63> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: open Priority: wish | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by videotranscoder): * cc: videotranscoder (added) -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:65> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------- Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: open Priority: critical | Component: | undetermined Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by Nik): * keywords: => ac4 -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:67> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+----------------------------------- Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: closed Priority: critical | Component: avcodec Version: git-master | Resolution: fixed Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by Nomis101): * status: open => closed * resolution: => fixed Comment: I think this can be closed now that we have support for muxing and demuxing of Dolby AC-4 audio in FFmpeg. https://github.com/FFmpeg/FFmpeg/commit/2bc65003e2861eeeeae4db828890df33d2fc... https://github.com/FFmpeg/FFmpeg/commit/9c6538d4c2d045cc55674adde7a758fd24e7... https://github.com/FFmpeg/FFmpeg/commit/293e353460856f5f0f8c122a1d2b406fa398... https://github.com/FFmpeg/FFmpeg/commit/961b17eace0eb36f201df97fe9067f3f5764... https://github.com/FFmpeg/FFmpeg/commit/2cac3fd744ea7f1a8bd0f507718c3323e754... https://github.com/FFmpeg/FFmpeg/commit/98cae37e23ed4c48116d5e7d8ad5131df2e1... Thanks for that! -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:69> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: critical | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by Nomis101): * status: closed => reopened * resolution: fixed => Comment: Replying to [comment:70 Balling]:

I think decoding should be merged.

Yes, you are right. I guess I spoke too soon. It still does not work. It now detects the AC-4 steam properly, but FFmpeg is unable to decode or recode it. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:71> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: critical | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by Robert Houghton): Replying to [comment:72 Balling]:

The bug is only about muxing though.

I tried to open #10450 to specifically address decoding of AC-4 audio and was shut down for being a duplicate ticket. Is there any current progress or effort on decoding? -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:73> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: critical | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by Romualds Cirsis): * cc: Romualds Cirsis (added) -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:75> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by Leo Izen): Stop changing the priority to critical. It won't make anything happen faster. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:77> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by thovo): * cc: thovo (added) -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:79> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by davygrvy): * cc: davygrvy (added) -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:81> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by P Liu): I was able to make it work by rebasing the patches and fixing a few issues. https://github.com/pliu6/FFmpeg I can play "atsc3.ts" with my local build. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:83> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by Hoof): Also here because because I cannot hear ATSC 3.0 audio. Any chance this gets supported? -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:85> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by Elliot Lee): I have taken @pliu6 's git repository and merged it with what's in the latest FFmpeg github. It now compiles and basically works but has split-second audio drop-outs every few seconds, so I think there is more work to do from someone who knows how AC-4 decoding is supposed to work. Pull requests are welcome. https://github.com/elliotclee/FFmpeg -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:87> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by digitpan): anybody who could make the decoded audio channel mapping in the correct order then I could provide the hardware as the renderer. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:89> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by Brad Isbell): * cc: Brad Isbell (added) Comment: Hello all. I saw that AC-4 had been partially added to FFmpeg, but doesn't support any decoding or encoding at this time. Along the lines of Reuben's question, is there any blocker (legal, technical, or otherwise) that prevents merging in a patch for AC-4 decoder support? I also wonder if there's a way we can use platform codecs, such as Media Foundation Transform (MFT), for which AC-4 is available to OEMs. If so, then we wouldn't have to worry about licensing issues, as far as I understand it. {{{ ffplay -loglevel debug http://192.0.2.3:5004/auto/v104.1 ffplay version 2024-12-11-git-a518b5540d-full_build-www.gyan.dev Copyright (c) 2003-2024 the FFmpeg developers built with gcc 14.2.0 (Rev1, Built by MSYS2 project) configuration: --enable-gpl --enable-version3 --enable-static --disable- w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libaribb24 --enable-libaribcaption --enable-libdav1d --enable-libdavs2 --enable-libopenjpeg --enable-libquirc --enable-libuavs3d --enable-libxevd --enable-libzvbi --enable-libqrencode --enable-librav1e --enable-libsvtav1 --enable-libvvenc --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxeve --enable-libxvid --enable-libaom --enable-libjxl --enable-libvpx --enable- mediafoundation --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libharfbuzz --enable-liblensfun --enable- libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda- llvm --enable-cuvid --enable-dxva2 --enable-d3d11va --enable-d3d12va --enable-ffnvcodec --enable-libvpl --enable-nvdec --enable-nvenc --enable- vaapi --enable-libshaderc --enable-vulkan --enable-libplacebo --enable- opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable- libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable- libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libcodec2 --enable-libilbc --enable-libgsm --enable-liblc3 --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable- libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable- libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint libavutil 59. 49.100 / 59. 49.100 libavcodec 61. 26.100 / 61. 26.100 libavformat 61. 9.100 / 61. 9.100 libavdevice 61. 4.100 / 61. 4.100 libavfilter 10. 6.101 / 10. 6.101 libswscale 8. 12.100 / 8. 12.100 libswresample 5. 4.100 / 5. 4.100 libpostproc 58. 4.100 / 58. 4.100 Initialized direct3d renderer. [AVFormatContext @ 000001cd6a82d440] Opening 'http://192.0.2.3:5004/auto/v104.1' for reading [http @ 000001cd6a82da40] Setting default whitelist 'http,https,tls,rtp,tcp,udp,crypto,httpproxy,data' [tcp @ 000001cd6a82db40] Original list of addresses: [tcp @ 000001cd6a82db40] Address 192.0.2.3 port 5004 [tcp @ 000001cd6a82db40] Interleaved list of addresses: [tcp @ 000001cd6a82db40] Address 192.0.2.3 port 5004 [tcp @ 000001cd6a82db40] Starting connection attempt to 192.0.2.3 port 5004 [tcp @ 000001cd6a82db40] Successfully connected to 192.0.2.3 port 5004 [http @ 000001cd6a82da40] request: GET /auto/v104.1 HTTP/1.1 User-Agent: Lavf/61.9.100 Accept: */* Range: bytes=0- Connection: close Host: 192.0.2.3:5004 Icy-MetaData: 1 [mpegts @ 000001cd6a82d440] Format mpegts probed with size=2048 and score=50 [mpegts @ 000001cd6a82d440] stream=0 stream_type=24 pid=31 prog_reg_desc= [mpegts @ 000001cd6a82d440] stream=1 stream_type=6 pid=32 prog_reg_desc= [mpegts @ 000001cd6a82d440] stream=2 stream_type=6 pid=39 prog_reg_desc= [mpegts @ 000001cd6a82d440] stream=3 stream_type=6 pid=33 prog_reg_desc= [mpegts @ 000001cd6a82d440] Before avformat_find_stream_info() pos: 0 bytes read:6204 seeks:0 nb_streams:4 [mpegts @ 000001cd6a82d440] parser not found for codec ac4, packets or times may be invalid. Last message repeated 1 times [mpegts @ 000001cd6a82d440] probing stream 2 pp:2500 [mpegts @ 000001cd6a82d440] probing stream 2 pp:2499= 0B [mpegts @ 000001cd6a82d440] probing stream 2 pp:2498= 0B [mpegts @ 000001cd6a82d440] probing stream 2 pp:2497= 0B [mpegts @ 000001cd6a82d440] probing stream 2 pp:2496= 0B [mpegts @ 000001cd6a82d440] probing stream 2 pp:2495= 0B [mpegts @ 000001cd6a82d440] probed stream 2 [mpegts @ 000001cd6a82d440] parser not found for codec bin_data, packets or times may be invalid. [mpegts @ 000001cd6a82d440] parser not found for codec ac4, packets or times may be invalid. Last message repeated 1 times … (various HEVC debugging messages) … [mpegts @ 000001cd6a82d440] max_analyze_duration 7000000 reached at 7007000 microseconds st:1 [mpegts @ 000001cd6a82d440] rfps: 60.000000 0.014560 [mpegts @ 000001cd6a82d440] rfps: 59.940060 0.000000 Last message repeated 1 times [mpegts @ 000001cd6a82d440] Could not find codec parameters for stream 1 (Audio: ac4 (AC-4 / 0x342D4341), 0 channels): unspecified sample rate Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options [mpegts @ 000001cd6a82d440] Could not find codec parameters for stream 3 (Audio: ac4 (AC-4 / 0x342D4341), 0 channels): unspecified sample rate Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options [mpegts @ 000001cd6a82d440] After avformat_find_stream_info() pos: 5270956 bytes read:5272104 seeks:0 frames:846 Input #0, mpegts, from 'http://192.0.2.3:5004/auto/v104.1': Duration: N/A, start: 66559.780100, bitrate: N/A Program 3 Stream #0:0[0x31], 419, 1/90000: Video: hevc (Main 10), 1 reference frame ([36][0][0][0] / 0x0024), yuv420p10le(tv, bt709, left), 1920x1080 [SAR 1:1 DAR 16:9], 0/1, 59.94 fps, 59.94 tbr, 90k tbn Stream #0:1[0x32](eng), 212, 1/90000: Audio: ac4 (AC-4 / 0x342D4341), 0 channels Stream #0:2[0x39](eng), 4, 1/90000: Data: bin_data (STPP / 0x50505453), 0/1 Stream #0:3[0x33](spa), 211, 1/90000: Audio: ac4 (AC-4 / 0x342D4341), 0 channels }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:91> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by Jim Scarborough): This ticket is about ffmpeg support for Dolby AC-4. The primary motivation for ever so many people to be interested in this ticket is that ATSC 3.0 mandates Dolby AC-4. To that end, I suggest a policy workaround for people experiencing this issue: It is deeply problematic that **ATSC 3.0 mandates a proprietary codec** (Dolby AC-4) for audio on **free over-the-air (OTA) television** in the U.S. and other regions adopting the standard. This effectively **locks out open-source software** like FFmpeg, VLC, Plex, and Kodi, preventing the public from fully accessing broadcasts that are supposed to be free. == Why This Matters * Public airwaves should not be encumbered by proprietary restrictions. * FFmpeg and other open-source projects cannot legally implement AC-4 support, limiting users' ability to watch ATSC 3.0 content. * The FCC approved ATSC 3.0 with no open alternative to AC-4, forcing consumers to buy Dolby-licensed hardware just to hear broadcasts. * If ATSC 1.0 is fully phased out, thousands (if not millions) of viewers may lose access to free OTA TV. == What Can We Do? This is not just a technical issue—it is a policy issue that affects media accessibility for everyone. If you believe that publicly available TV should not require proprietary codecs, consider: * Filing a complaint with the FCC (File here: https://consumercomplaints.fcc.gov/hc/en-us) * Contacting your local broadcasters to urge them to advocate for an open alternative to AC-4 * Pressuring ATSC and the National Association of Broadcasters (NAB) to reconsider the forced use of proprietary codecs * ATSC: https://www.atsc.org/contact-us/ * NAB: https://www.nab.org/about/contactus.asp * Spreading awareness on forums, tech news sites, and social media * AVS Forum: https://www.avsforum.com/threads/atsc-3-0-nextgen- tv.3125888/ * r/Plex: * https://www.reddit.com/r/PleX/comments/jkx007/atsc_30_and_ac4_audio_support/ * https://www.reddit.com/r/PleX/comments/11fmzcr/ac4_support_for_atsc_30/ * r/HDHR: https://www.reddit.com/r/HDHR/comments/zqrr2o/atsc_30_compatability/ * Silicondust: * ATSC 3.0 streams https://forum.silicondust.com/forum/viewtopic.php?start=45&t=79256 * HDHomeRun 4k is Nextgen TV Certified: https://forum.silicondust.com/forum/viewtopic.php?start=165&t=78419 == Thank you! 🚀 **FFmpeg devs have done incredible work** supporting open media formats, and even coming up with an experimental solution here. But without an open AC-4 alternative, ATSC 3.0 will remain inaccessible to a large portion of its intended audience. Advocating for open standards isn’t just about software—it’s about **ensuring that publicly owned airwaves remain truly public**. I'd love to hear from you directly or in one of the online groups mentioned above. If anyone has legal, regulatory, or technical insights, let’s work together to **push for an open alternative**. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:93> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by pross): fyi: the ac-4 decoder is now merged into [https://github.com/librempeg/librempeg librempeg] (Paul's ffmpeg fork) -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:95> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by compn): i collected a few samples from this ticket and put them here: https://samples.ffmpeg.org/A-codecs/ac-4/ to answer questions: nothing is really holding up the patch besides a lack of motivation. the code has to be submitted to ffmpeg-devel list and reviewed and fixed (by the person who sends the patch) and then possibly resubmitted with fixes + reviewed again or applied. which is the process for almost all new code in ffmpeg. if you are interested in sponsoring the ac4 decoder in ffmpeg, you could contact paul and offer to pay him to submit the code to ffmpeg , paul's ac-4 decoder is in his ffmpeg fork on github https://github.com/librempeg/librempeg/blob/master/libavcodec/ac4dec.c and looks like its being actively developed. if you are interested in sponsoring codec work , feel free to send a mail to the ffmpeg-devel mailing list. something like 'we are interested in sponsoring work on ffmpeg (insert what you want worked on), please contact us for more information'. we also have an ffmpeg consulting page where available developers can offer their services. https://ffmpeg.org/consulting.html -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:97> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

#8349: Dolby AC-4 Support -------------------------------------+------------------------------------ Reporter: Nomis101 | Owner: (none) Type: enhancement | Status: reopened Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: ac4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by v0lt): Another sample with three AC-4 audio tracks (2, 10, 8 channels) http://lcba.free.fr/UHD_FR/test_UHD_C24_210328_1.ts (247 Mb) -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349#comment:99> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker