Forums » Tutorial and setups »
Missing ATSC-T Pre-defined Muxes?
Added by Anonymous over 8 years ago
Hello - I have a fresh install of 4.1-1931 and I am setting up my ATSC-T network I only see 3 pre-defined muxes.
Canada: ca-AB-Calgary
United States: us-ID-Boise
United States: us-MA-Boston
I typically select: United States: us-ATSC-center-frequencies-8VSB.
Is there a way I can manually configure this network?
network.png (43.3 KB) network.png |
Replies (6)
RE: Missing ATSC-T Pre-defined Muxes? - Added by edit4ever ! over 8 years ago
I'm having the same issue - my list only shows United States: us-CA-SF-Bay-Area and United States: us-CO-Denver -- missing the United States: us-ATSC-center-frequencies-8VSB - which is the only one that matters!
I've created a new bug ticket. I checked previous builds and this started after 4.1.1892 (last working version)
RE: Missing ATSC-T Pre-defined Muxes? - Added by Anonymous over 8 years ago
So it looks like all the files are in the /usr/share/tvheadend/data/dvb-scan/atsc folder. So I made a copy of the us-ATSC-center-frequencies-8VSB, removed the frequencies I didn't want, saved it, restarted, and it showed up. I am good to go now.
RE: Missing ATSC-T Pre-defined Muxes? - Added by edit4ever ! over 8 years ago
That folder doesn't seem to exist on Rapberry Pi running LibreELEC...but I notified the LE team to check their compiler.
RE: Missing ATSC-T Pre-defined Muxes? - Added by Salo cink over 8 years ago
Any news about this issue ?
RE: Missing ATSC-T Pre-defined Muxes? - Added by edit4ever ! about 8 years ago
I believe I may have found a cause for this...but am not in a position to test it.
At commit f02851ab9c60bdd326fdba9afee4255b7b07a06c the ATSC network was split to atsc-t and atsc-c. However, the dvb-scan git was never updated to the new naming system. I believe the issue is being caused by the fact that there are no dvb-scan files with the atsc-t and atsc-c networks.
Hopefully someone can test the theory.
RE: Missing ATSC-T Pre-defined Muxes? - Added by edit4ever ! about 8 years ago
I have tested this and the dvb-scan folder/files update is the solution. I have submitted the pull request for updating dvb-scan. I've also added the information to issue #3745.