@rainlake with Plex Tuner 0 won’t tune, but if I do two shows at once Tuner 1 works. Not sure what the deal is. (Detroit here also)
is it related to this? https://forum.silicondust.com/forum/viewtopic.php?f=133&t=74215
It looks like one of the commenters on the ffmpeg ticket has managed to get ffmpeg to play audio. Now the question is how long for the ffmpeg devs to finish a patch, release, and then plex to also update/release it.
I saw the recent comments in ffmpeg, this is starting to look promising!
Lets just hope Plex is willing to integrate the patches in their current version for people to use versus waiting for a major release of ffmpeg.
Have SiliconDust HDHome Run $K ATSC 3.0 tuner. Plex scanned and found ATSC 3.0 channels but would not show up in guide. Unable to watch except for SiliconDust
HD software.
Silicon Dust’s temporary solution to move the 3.0 channels to have guide numbers in the 100’s isn’t going to work in Plex guide. You can have them play in Plex by unchecking the ATSC 1.0 version of the channel and assigning the 3.0 version.
However there is no point to that as AC-4 audio won’t play from Plex (or any other FFMpeg app).
I am not sure I understand your response. There are two things needed (I believe) to use this tuner with plex
- Map the HEVC Channels to the right guide data - which is easy
- Plex needs to integrate the ffmpeg patches to support AC-4
I am obviously hoping plex does this sooner than later even if it is experimental.
-
You cannot map a single guide channel to two different virtual channels in Plex. So if NBC on the HDHR is 5.1 for the atsc 1.0 channel and 105.1 on the atsc 3.0 channel they are both really 5.1. Silicon Dust only made the 105.1 as a temporary solution until some of the support issue gets worked out and it goes back to 5.1. So if you want to use the ATSC 3.0 channel in Plex, you can you just, uncheck the 5.1 channel so it isn’t assigned to NBC and check the 105.1 and assign it to NBC. Plex is very unlikely to take the time to figure out how do deal with guide mapping and recording data of having two virtual channels map to the same guide channel, especially as Silicon Dust stated this change was a temporary fix. If you think it is “easy”, you need to offer your coding skills to Plex team to do it.
-
Yes, they would need to integrate ffmpeg version that supports ac4 once one exists in the supported branch. While I wouldn’t complain if they wanted to try to add richardpl’s code to what they are doing, it would add complications to their support path and they would just have to revert it. There are so few of us that have atsc3 tuners, and there is currently little to no benefit to even using atsc3 channels over the 1.0 versions, so I don’t see them feeling a need to rush to hack something into their builds.
1 Like
Just purchased the Silcondust NextGen 4k…I need to demo the local DFW 4K Channel in a Cut the Cable Preso for my community…when I mapped the 104.1 in Plex I also do not receive any sound SO I am assuming the same issue as in this tread has not been resolved…it appears that this is a Silcondust issue no Plex…is this a correct assumption?
That is incorrect. The open source module ffmpeg that Plex uses does not yet support AC-4 audio.
jeobrossard…Thank You for Confirming!
Here in the Seattle area I expect that ATSC 3.0’s improved multipath reception will be a huge benefit immediately. I’ll buy a tuner as soon as the AC-4 codec is implemented.
2 Likes
It is possible it could be beneficial to your reception but of course, only if those issues are specifically affecting your reception quality now. For those of us that don’t have those issues, the reception is the same as for 1.0 (from the same tower/area). It doesn’t seem to affect any other aspects such as reception strength/quality at specific distances.
A few people in the Seattle thread have noted improvement where, with 1.0, they were affected by things like some swaying trees in their path. ATSC 3.0 Forum - Silicondust
I, for one, am seeing weaker reception for some ATSC 3.0 channels in the Phoenix area.
Well add me to the list of people that went out and bought the HDHomerun Connect 4K ATSC 3.0 tuner and expected it to work with Plex using ATSC 3.0. For the time being I have my existing Extend tuner and Connect 4K tuner configured in Plex. From reading this thread I understand I won’t be watching ATSC 3.0 streams any time soon but I am wondering if Plex will be able to use all 4 tuners in ATSC 1.0 mode as well as my existing 2 tuners in the original HDHomerun Extend. (Not that I would ever need 6 tuners at one time mind you, just curious.) I am in the Mobile/Pensacola market.
Yes. I have 8 between this and my quad 1.0 tuner.
1 Like
With the latest firmware the Connect 4K will tune the ATSC 3.0 channels to a higher number and you can select the ATSC 1.0 channels. This allows you to use the tuners as a workaround for the time being
1 Like
Will there be any response, or post by PLEX admins on getting this function working correctly? I too also have the new HDHomeRun 4K tuner. I supported it and got a early model off of Kickstarter. Plex can see the channels, but it has no audio, or the image is stretched out weird. In Ohio at least!
OSUIndie07, the video is the same on the HDHomeRun app on my Shield TV. The broadcaster is the root cause. I get the same issue on the two WTTE stations. AC4, the audio format is not supported in ffmpeg, yet, which Plex uses for some of its transcoding. Roku doesn’t support AC4 natively.
