Tvheadend

Mass edit of grid entries has been added to 4.1.xxxx (dev) - I'm not sure 4.0.x has it though.

The config has changed a lot since 3.x. I can't check as to the actual contents of a 4.0.x config right now as I use 4.1.xxxx mainly.

But it shouldn't be too hard to use sed and replace certain values in the config files.

... thanks for your prompt answer.

But it shouldn't be too hard to use sed and replace certain values in the config files.

this is not an issue for me, at all.

What I need is the the name(s) of file(s) and the fields I have to modify. Maybe someone on version 4.0 can provide the names.

The config has changed a lot since 3.x. I can't check as to the actual contents of a 4.0.x config right now as I use 4.1.xxxx mainly.

is the version 4.1 so different from 4.0?

best regards
Beny

After browsing my file hierarchy, it looks like the muxes (and their services) live in .hts/tvheadend/input/[input_type]/networks/[random_networkid_string]/muxes/ . The problem is, while most other files seem to be JSON, the files for each mux look like they're binary dumps of the mux objects.

The channel configs live in .hts/tvheadend/channel/config/ , and those are just plain JSON. Here is one of my channels:

{
        "enabled": true,
        "name": "PBS SoCal",
        "number": 50,
        "icon": "file:///media/tv/channels/PBS%20SoCal.png",
        "epgauto": false,
        "dvr_pre_time": 0,
        "dvr_pst_time": 0,
        "epg_running": 0,
        "services": [
                "1af48663c487bb36ca9c6945d3dd91bb",
                "870a2c2022f60cab7dcde93dddc26af2",
                "9715059cfbcfd5b782e95514871a7abf" 
        ],
        "tags": [
                "66277c335712651c9a3ddaa9b1058b78",
                "dec0faeb1f4c91553f9d49a4a0e69e1f" 
        ],
        "bouquet": "" 
}

I am uncertain about "dvb_eit_enable", since my inputs are IPTV.

Also, since these files are JSON, you may find better luck with jq⁰ than with sed.

[0]: https://stedolan.github.io/jq/

Robert,

again thank you for taking care of my inquire - I do appreciate it!

Reading your feedback I understood that the TVH file structures are similar (if not the same).
My "muxes" are also not a plain text in 4.0.x

I will change just few channel files from .hts/tvheadend/channel/config/ and see if the system does what I want.
This is a good hint, pointing to the JSON format. I'm tending to create a python script (with a few lines) to do the job, as soon as the test will be successful. [edit:] jq works perfectly and is available out of the box i will give it try.

Maybe someone can put more light to the dvb_eit_enable field successor.

best regards
Beny

Evening's update:
I found the service config files to be modified. The files are stored in: ~/.hts/tvheadend/input/dvb/networks/<network-ID>/muxes/<transponders>/
The script has to go transponder by transponder folder and modify all files the sub-folders.
In each file there are to fields:
"enabled" to be set to false in order to disable the service and
"dvb_ignore_eit" to be set to true in order to ignore epg data.

To disable the channels I used following bash script:

#!/bin/sh
for file in ls -1 -r ~/.hts/tvheadend/channel/config/* ; do
    #[[ ! -e $file ]] && continue  
    echo "$file" 
    cat "$file" | jq '.enabled |= false | .epgauto |= false' | sponge "$file" 
done

The script has to be started from the hts user (relative path ~ to chanel files)