Set starting number for channelID tags?

[hcurtiss]

I use a pair of xteve-vpn containers to manage two different sources for my PVR. xteve injects channelID tags in my m3u and, unfortunately, my PVR software (channels DVR) requires each source to have unique channelID tags for certain functionality to work. Both m3u files start at channelID="x-ID.0" and count up, creating overlap between the two. Is there any way I can have the second instance/container start at channelID="x-ID.1000" and count up from there, kind of like you do in settings.json for the starting channel number? I do not see anything relevant to channelID.

[hcurtiss]

Alternatively, is there a way to prevent xteve from injecting the channelID tags?

[alphalneo]

Sorry I don't use the docker to run xteve, however, check the file settings.json for mapping.first.channel