Home

m3u-filter

Some of the m3u-filter features are:

• filter, raname, map entries of playlists with regular-expressions
• mimick XTREAM-Server or a M3U-Server with api-endpoints
• create files for Kodi
• process one/multiple source(s) and produce one/multiple playlist(s)
• use templates for filter to avoid repetitions
• define filter as statements
• schedule updates
• send telegram bot messages
• watch changes in groups and get messages

m3u-filter needs configurations for doing its job. There are three configuration files in yaml format.

• config.yml
• mapping.yml
• api-proxy.yml

config.yml

Is mandatory to run m3u-filter.
Detailled explanation is here.

mapping.yml

Is optional and used for advanced mapping functionality.
Detailled explanation is here.

api-proxy.yml

Is optional and used for api-endpoints for xtream and m3u server mimicking.
Detailled explanation is here.

Program Arguments

Extended M3U playlist filter

Usage: m3u-filter [OPTIONS]

Options:
  -c, --config <CONFIG>        The config file
  -t, --target <TARGET>        The target to process
  -m, --mapping <MAPPING>      The mapping file
  -a, --api-proxy <API_PROXY>  The user file
  -s, --server                 Run in server mode
  -l, --log-level <LOG_LEVEL>  log level
  -h, --help                   Print help
  -V, --version                Print version

m3u-filtersearches in the current directory for the configuration files.
If they are somewhere else you need to specifiy the locations with the arguments -c, -m and -a.

If you run m3u-filterin cli-mode (running from terminal and without the -s argument), you can define specific targets to update with the -t argument. You can write multiple -t arguments.

If you run with -s argument, the -t is ignored. This starts m3u-filterin server mode.
In Server mode the Web-UI is accesible through a browser. The port is defined in the config.yml file. The Url should look like http://<IP-Address>:<Port>. You need to replace <IP-Address> and <Port>