Posts: 524
Joined: Dec 2012
Reputation:
10
2021-05-05, 01:57
(This post was last modified: 2021-05-05, 02:00 by oldtvwatcher.)
I am just wondering if any LINUX users in the land of ATSC 3.0 where you actually have stations on the air have been able to record programs in ATSC 3.0 using Tvheadend and then successfully play them using Kodi (with the Tvheadend PVR plugin). ATSC 3.0 has recently arrived in my area but those HDHomeRun devices are pretty pricey at $200 a pop, and although they have four tuners, only two of them will receive ATSC 3.0. But maybe it would be worth it IF they work okay with Tvheadend and Kodi, but I have been reading comments about it either not working at all, or that the video freezes and there is no sound (because they use AC-4 audio and apparently ffmpeg can't handle that yet?). But those comments were from about four months ago. So what I am asking is, are there any ATSC 3.0 viewers here that have recent experience using this combination (without having to futz around with it), and if so does it work well for you or not?
Also, just to be clear, if you were able to get it to work but only after jumping through all kinds of hoops that included compiling software from scratch, then the answer is no, and for me you could just leave it at that. I'm not a programmer or a developer or a Linux expert. I just run Kodi in Ubuntu Linux because in the past it has worked pretty well (other than the problems getting the remote to work after they came out with that godawful new version of lirc, until I found the article that shows how to revert to the old version), so anything that involves that extra level of expertise is beyond me. The last thing I need is any more problems, and my fear is that if I try to move to ATSC 3.0 too early that's exactly what I am going to get.
Posts: 5
Joined: Oct 2021
Reputation:
0
My experience with free-to-air satellite signals is that Tvheadend just records whatever transport stream it receives from the tuner, with minimal processing. So if the video is HEVC/h.265 and the audio is AC-4, that is exactly how Tvheadend will save it. It is then up to whatever player you use to decode it. I don't think the HEVC/h.265 will be a huge issue except on underpowered systems, for example I doubt that a Raspberry Pi will be able to deal with that. Also many GPUs won't decode those so in such cases the decoding has to be delegated to the CPU, which may or may not be a problem.
ffmpeg does many things well but there are some things it doesn't do well, or at all. Its support of USA/Canada style closed captioning is terrible - VLC displays closed captions just fine, but on some channels Kodi either doesn't display them at all, displayed a very garbled version, or displays them all in the same font with no distinction between text and music, and that's because ffmpeg's support of US-style closed captions is minimal at best. As for AC-4, the ffmpeg developers seem to act as if they couldn't care less if it ever gets added - all the action on AC-4 is coming from third parties that are making custom builds. Sometimes I wish Kodi would use whatever decoding engine VLC uses, although there could be drawbacks to doing that which I am not aware of.
Posts: 1,840
Joined: Jul 2012
Reputation:
68
There is nothing intrinsically "Windows" about the ffpeg patch for AC-4. I've applied it to Kodi and to ExoPlayer and it appears to decode audio ok. Also playing ATSC 3.0 with the cheapest ($20-30) ONN and TiVO 4k devices HEVC/AC-4 is not an issue. Not sure why it has to run on the RPi to considered relevant.
It seems like you are confusing the closed captioning decoding and rendering engine with ffmpeg which there is no doubt that it can be improved in Kodi.
Also note AFAIK nothing in the non-commercial realm decodes AC-4 xml subtitles
Martin
Posts: 1,840
Joined: Jul 2012
Reputation:
68
The NextPVR backend runs on most platform Linux, Docker, current CE/LE (using a package install) and MACOS not just Windows. There is no Kodi support for AC-4, since Team Kodi doesn't want to support it but you can build your own ffmpeg on linux from the PR. On any platform of course you can schedule and manage the recordings, you just won't have sound on the AC-4
So for now, if you don't want the HDHR app you are stuck with the Android NextPVR client which BTW via ExoPlayer has pretty good closed captioning however again no ATSC 3.0 captioning. I also haven't tested comskip on ATSC 3.0 since I don't live in the US but if the EDL file is good it will work.
Martin
Posts: 1,840
Joined: Jul 2012
Reputation:
68
The Silicon Dust ATSC 3.0 device is actually converting the ATSC 3.0 into an mpeg-ts http stream just like they do with ATSC 1.0, Cable Card and DVB.
Martin
Posts: 1,840
Joined: Jul 2012
Reputation:
68
2021-10-25, 00:21
(This post was last modified: 2021-10-25, 00:27 by emveepee.)
Transcoding firmware and licensing would cost more and you lose the future benefits of AC-4. No doubt some DVB users would benefit from AAC 5:1 transcoding to AC-3 too. 10-15 years ago users didn't want AC-3 and wanted 2:0 MPEG2 audio. Times change.
That discussion is better for the SiliconDust forum anyway. Maybe if other vendors enter the market you will get more choice.
Martin