Jump to content

Using XTeVe with Emby


EODCrafter
Go to solution Solved by EODCrafter,

Recommended Posts

EODCrafter

Marmei already said to have multiple instances for different providers. Then set the limit per instance. You can look about three weeks ago for the answer in this thread

Not really practical...Just get rid of Providers that Ban you so easily. IPTV is Dime a Dozen

Edited by EODCrafter
Link to comment
Share on other sites

Tony B.

Not really practical...Just get rid of Providers that Ban you so easily.

Well, I would say that if I had one provider that allowed 4 streams and one that only allowed two, then consistently using 4 from both of them would cause problems. It's needed in some cases

Link to comment
Share on other sites

EODCrafter

Well, I would say that if I had one provider that allowed 4 streams and one that only allowed two, then consistently using 4 from both of them would cause problems. It's needed in some cases

Service I sell just kicks you for over-limit...Nothing as Harsh as a all out Ban...This is just over-kill.

  • Like 1
Link to comment
Share on other sites

marmei

The problem is that xTeVe can merge multiple provider files.

Provider 1 could support 5 streams

Provider 2 could support only 1 stream

 

Now feed this file into Emby and what do you set this setting to?

 

 

Not tried yet, but would have to work:

 
Both providers set up in xTeVe
 
Provider 1 = 5 streams
Provider 2 = 1 stream
 
In the mapping, you create a separate group title for each provider.
Provider 1: Group-title = 5 streams
Provider 2: Group-title = 1 stream
 
xTeVe can also filter the M3U list!
 
In Emby, you set up two M3U tuners
M3U Tuner 1:
M3U URL = http: //xteve.ip: port?group-title = 5 streams
Tuner Limit = 5
 
M3U Tuner 2
M3U URL = http: //xteve.ip: port?group-title = 1 stream
Tuner Limit = 1
  • Like 4
Link to comment
Share on other sites

Yea, that would likely work for now since Emby doesn't support Groups.  But if//when they support groups, then this would not be very elegant.  A BETTER way would be to export by PROVIDER vs group title.  This info is there already.

 

I've got a custom solution that does exactly this.  I can import everything in a DB, manipulate it how ever is needed then export back out to separate files just for this purpose (Emby stream limit per provider).

 

However, Emby throws another monkey wrench into things as it seems to use the tvg-id field as some sort of key which it shouldn't.  It should use it strictly to match a corresponding EPG.  Each M3U files SHOULD allow the same tvg-id used multiple times.  You could for example have an SD and HD channel or Backup channel or two of the same channel but all using the same tvg-id for EPG purposes.

 

If you load 4 or 5 M3U files it's also likely that there will be overlaps of tvg-id as well between files which SHOULD NOT MATTER EITHER as each will likely have a corresponding xmltv file for EPG that could be different.

 

Right now for example if 5 M3U files had a tvg-id field of "xyz tv.us" then only 1 of these channels would make it into Emby as 4 would get over written.

 

@@Luke can you fix this?

  • Like 1
Link to comment
Share on other sites

dcol

 

 
The xTeVe M3U export can now also be selected by group title. This makes it possible in Emby to create multiple M3U tuner from xTeVe.
The group titles can be changed in xTeVe (mapping).
 
Example:
 
M3U tuner 1: 
http://xteve.ip:port/m3u/xteve.m3u?group-title=group1,group2
M3U tuner 2: 
http://xteve.ip:port/m3u/xteve.m3u?group-title=group3

 

When I use the group feature this is the response from Emby

5cc1ff3a15b26_xteve1.jpg

Edited by dcol
Link to comment
Share on other sites

EODCrafter

When I use the group feature this is the response from Emby

5cc1ff3a15b26_xteve1.jpg

 

 

Syntax Probably wrong...Can you share so we can Help you or do you want us to guess what you typed wrong?

 

Here's a Example that Works with mine.....

http://192.168.1.114:8080/m3u/xteve.m3u?group-title=Sports
Edited by EODCrafter
Link to comment
Share on other sites

EODCrafter

I know why it doesn't work. I have to use a URL.

Uhhh, Where was that ever not explained? If something starts with http:// (The Protocol) 100% of the time it's gonna be a URL.

Edited by EODCrafter
Link to comment
Share on other sites

dcol

So what would be the URL if xteve is on the same computer. I tried the IP and localserv. That is my problem. I know you need a URL, just can't get it to work locally.

Edited by dcol
Link to comment
Share on other sites

EODCrafter

So what would be the URL if xteve is on the same computer. I tried the IP and localserv. That is my problem. I know you need a URL, just can't get it to work locally.

It's in the xTeVe Web User Interface Mr Dcol......Please Take this discussion to Discord xTeVe...I really don't like this format for Forum.

 

5cc21de975543_Capture.png

Edited by EODCrafter
Link to comment
Share on other sites

EODCrafter

The Link you are posting is to a .xml file which is EPG.

http://192.168.100.94:34400/xmltv/xteve.xml
Edited by EODCrafter
Link to comment
Share on other sites

dcol

So what does Emby do when the simultaneous # streams is reached? Does it continue to wait, or abandon the stream?

Link to comment
Share on other sites

hshah

Just caught up on the last few posts and I have to be honest, I did wonder what the **** was going on lol  :D

 

As @@EODCrafter has quite rightly said, all http / https references are URLs.  If you have xTeVe on the same machine as Emby then you could use:

 

http://localhost:port/

http://127.0.0.1:port/

 

And if it is elsewhere on your network then:

 

http://[ipaddress]:port/

 

 

@@dcol, the URL you were mentioning was the EPG one so if you were using that for the tuner then it would never have worked :)

 

 

If XTeVe is on the same machine then alternative options are file paths, which is what I current have set up in my Emby:

 

C:\Users\hshah\xteve\data\xteve.m3u

C:\Users\hshah\xteve\data\xteve.xml

 
Link to comment
Share on other sites

EODCrafter

Just caught up on the last few posts and I have to be honest, I did wonder what the **** was going on lol  :D

 

As @@EODCrafter has quite rightly said, all http / https references are URLs.  If you have xTeVe on the same machine as Emby then you could use:

 

http://localhost:port/

http://127.0.0.1:port/

 

And if it is elsewhere on your network then:

 

http://[ipaddress]:port/

 

 

@@dcol, the URL you were mentioning was the EPG one so if you were using that for the tuner then it would never have worked :)

 

 

If XTeVe is on the same machine then alternative options are file paths, which is what I current have set up in my Emby:

 

C:\Users\hshah\xteve\data\xteve.m3u

C:\Users\hshah\xteve\data\xteve.xml

We finished this on Discord...too hard to discuss a issue here....

Link to comment
Share on other sites

EODCrafter

So what does Emby do when the simultaneous # streams is reached? Does it continue to wait, or abandon the stream?

It's just a constant loading wheel loop....

 

@@Luke It would be nice if it output a simple Message "Max Stream Usage has been Reached"

Link to comment
Share on other sites

Tony B.

It's just a constant loading wheel loop....

 

@@Luke It would be nice if it output a simple Message "Max Stream Usage has been Reached"

I will second that! It's a pain in the ass when I get a never ending loop. It forces me to figure out why; gotta go to TVMosaic's site to see if the tuners are stuck or restarting the services.

Link to comment
Share on other sites

CBers

We finished this on Discord...too hard to discuss a issue here....

To be fair, if the issue started here, it would be nice to finish it here.

 

Saves people having to jump to another platform when all of the evidence is here.

 

Just saying.

Link to comment
Share on other sites

EODCrafter

It's like jumping thru hoops to discuss anything here...He needed real time support...Sry.

Link to comment
Share on other sites

dcol

Problem is we needed to get on the same page. I, obviously, wasn't explaining the issue properly because I wasn't getting help about what I was seeing.

 

Here is my take on the discord conversation.

First off, I was having issues getting the URL to work because of my firewall. I resolved that by enabling reflection.

Then the issue with group-title. Still don't completely understand the logic here.

Apparently the group-title field that shows in xTeVe is NOT the actual group-title used when you specify the group-title in the Emby m3u field.

Rather it uses the group-title field from the original m3u providers m3u. This is what confused me.

I edited all the group titles in xTeVe to reflect what I wanted to be used in Emby using the group-title field and it didn't work.

Then I wanted to know why, so I asked.

I was told the edited group-title field was not used with the xTeVe m3u in Emby even though all my edited group-title fields were there in the xTeVe m3u.

This is when the conversation got confusing.

 

Here are the details of what I did.

I have 3 providers in xTeVe using 3 m3u's and 3 xml's

I used the filters to narrow the listing, then disabled all the unwanted shows.

This left me with about 50 channels in the xTeVe listing.

I ported that to Emby using 'http://192.168.100.94:34400/m3u/xteve.m3u'

Everything works as expected.

Then I wanted to separate the three providers in Emby so I could set different Simultaneous stream limits for the three providers.

This is when I thought that group titles would solve this.

I edited the group titles in xTeve to reflect the providers name, let call them pvr1,pvr2, and pvr3.

I set each providers channel to reflect the group title name.

Next I inspected the xTeVe m3u in notepad and all the newly edited group titles were correct.

Then I tried to use this m3u in Emby using - http://192.168.100.94:34400/m3u/xteve.m3u?group-title=pvr1

It did not work. I still got all the channels for all providers in Emby.

This is when I started asking questions, and got this answer - The edited group titles in xTeVe are not used in the group-title field in the xTeVe m3u rather the original group-title fields from the original providers m3u are used.

 

So this is where I am and why this seemed so confusing. I figured if I detailed what I did, I could get answers that make sense to me.

Edited by dcol
  • Like 1
Link to comment
Share on other sites

Senna

Then I tried to use this m3u in Emby using - http://192.168.100.94:34400/xmltv/xteve.m3u?group-title=pvr1

It did not work.

Why is your m3u URL you load into Emby for your TV Channels not this:

http://192.168.100.94:34400/m3u/xteve.m3u?group-title=pvr1

 

Instead of this what you are using now:

http://192.168.100.94:34400/xmltv/xteve.m3u?group-title=pvr1

See also post #188 :rolleyes:

Edit: removed quote

Edited by Senna
Link to comment
Share on other sites

Senna

Sorry, I was using the m3u. typo

No problem, so have you checked your TV channels in Notepad++, when you use file open and paste that XteVe link with group title , if everything is correct, that it only shows your channels that have group-title PVR1 ?

http://192.168.100.94:34400/m3u/xteve.m3u?group-title=pvr1
Link to comment
Share on other sites

dcol

Yes shows the correct group titles. I just tried it again and it seems to be somewhat working now, but some of the channels not showing up. Will rebuild and try again.

I think I just have a mess from all the edits and filters. Going to start clean.

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...