"How hard can it be?" I thought, so subscribed to an IPTV provider, got the M3u file/url....
...and then spent 3 days trying to figure out how to map the channels . Who knew doing a simple "leave these channels out and of the ones that are left this channel in emby = this channel in my m3u" was going to be sooooooo convoluted and such a pita?!
I have emby running on Unraid in a docker with xsteve also in a docker.
So far I have tried :-
xteve Homerun (no mapping in xsteve, but can at least filter)
xteve xmltv - has mapping and filterinf at least probably the closest to usable i have so far
xsteve is S-L-O-O-O-O-O-W-W-W to the point of being unusable and would take days to map all the channels.
My m3u has no channel numbers - is it channel numbers that emby needs to channel map? Where do i get channel numbers to add to the m3u file )using something like tantrum IPTV editor) - is that even what I should e doing?
I feel like what I want is simple but, man, am I wasting some time without getting anywhere and pretty much going round in circles.
Is there a definitive (step-by-step preferably) guide to this anywhere that you could point me to?
I feel your pain.
There are a few methods to accomplish what you are trying to do.
1. I would begin with editing that M3U and removing channels that you won't be using. You can do this with notepad ++ or any other editor. Just take care to not screw up the formatting of the file.
2. Channel numbers - here again there are couple methods to accomplish this. I think for ease of use and long term "not having to do anything" xTeve is the way you want to go. Initial setup takes
a bit of time, but once that is done your gold. Just make sure that when you are done setting everything up you point Emby to the files (M3U/XMLTV) that xTeve generates and not to the xTeve web/server.
If you are providing your own guide data through Schedules Direct you could use epg123 and using the custom lineup feature accomplish the same (channel management) as with xTeve.
3. From what I have read here Emby looks for a few different "things" for mapping the channels. And what it is looking at varies depending on the guide data type you are using. @Luke is that correct?
4. There is no definitive guide for setting this up. But the Emby FAQ/Wiki for this is pretty good - much better that in the past. Best bet is the FAQ/Wiki and asking here on the forums.