Install a DLNA app on your smartphone and see if you can find xTeVe with it.
If there xTeVe is not found, you have a network problem with broadcast requests.
ok i Will try
Hi!
Thanks for the beta key.
Is there a way to use filters to exclude channels (e.g. I want to exclude +1 channels or whatever matches a given string)?
Thanks!
No that does not work, but you can deselect the unwanted channels in the Pex DVR settings
Not sure if itās just me, but I am trying to download the macOS version from the website, but it appears to download as an Amiga DMS archive.
Tried a few apps, such as The Unarchiver, but it will not open.
Is the macOS version actually a DMS file?
I also have a Mac, do not take the Safari browser. Safari think you have an Amiga ![]()
thanks itās working nowā¦
if i put two m3u from two different account with the same channels⦠can i use 2 tuners?
thanks!
How do you want to know which channels are played by which account?
The number of tuners tells Plex only how many concurrent streams can be played.
Right. But it means I have the limit of 420.
Good job, anyway - works very well!
If I may suggest improvements:
- Make the filters able to add or exclude channels
- Make the filters apply per specific M3U list (when one has more m3u lists)
- run different instances so that Plex sees them as different tuners, and one can pick different Plex guide sources
How many streams do you have with filters?
I also wanted to extend the filters.
If you can filter more, you do not need this feature anymore ![]()
Please explain why you didnāt make this open source ?
I have not made that decision yet. Maybe it will be an open source, but first it will be closed source.
Hi!
Iām testing it and when I run the command in a Windows 10 CMD, it starts in a rare IP that is not in my range. It should be in the local machine IP not?
I have 2 real NICs a some virtual NICs.
Can you send me some screenshots?
169.254.xxx.xxx is a link local address. xTeVe displays the IP address of the first network card. You still have to go through http://192.168.0.5:34400/web/
Normally this is a sign that this will not be free to use going forward, as not making it open source prevents collaboration and obviously leaves control with the dev. Thatās of course his/her choice but itās why for now Iāll stick with using tvhproxy.
Yep my thoughts exactly. Also not comfortable in putting credentials in a closed source application that is actually phoning home.
This looks very promising, I wouldnāt mind trying it out.
Cheers
With the 0.1.39 BETA version, it sows an other IP address but it works in that IP, the web interface and the DVR service. The IP still out of my range of IPs
