erobertc 0 Posted July 4, 2017 Share Posted July 4, 2017 Hi folks, I'm using Emby v. 3.2.22.0 with MPExtended v. 0.6.0.4-Emby and the MediaPortal plugin for Emby v. 1.5.4.0. I've set up a username and password with MPExtended and I can access http://192.168.1.229:4322/MPExtended/TVAccessService/json/GetServiceDescription successfully with these credentials. I entered these credentials in the settings for the MediaPortal Emby plugin, and on the Emby Live TV tab it shows a successful connection to MPExtended (Status: Ok). The problem is that most of the time when I attempt to stream live TV via the Emby web portal, on the client I just get the spinning wheel, and in the server logs, the ffmpeg-transcode log contains the line http://192.168.1.229:4322/MPExtended/StreamingService/stream/DoStream?type=TV&provider=0&itemId=37&clientDescription=TV-37-20170704040238&profileName=Direct&startPosition=0&idleTimeout=30&identifier=TV-37-20170704040238:Server returned 401 Unauthorized (authorization failed). I'm attaching the ffmpeg-transcode logs from a successful streaming session and a this type of failure. Keep in mind I haven't changed any settings between the two attempts -- just different combinations of restarting my PC (the server) and Emby server. I have been unable to find any pattern in when it does or does not work, but most of the time, it doesn't. Any help would be greatly appreciated. Log_fail.txt Log_successful.txt Link to comment Share on other sites More sharing options...
pünktchen 1251 Posted July 4, 2017 Share Posted July 4, 2017 Oh, that is completely new. I can only guess that's because of the different subnetwork Anyway, can you also please attach the Emby server log and the MPExtended log of those two sessions?! Link to comment Share on other sites More sharing options...
erobertc 0 Posted July 4, 2017 Author Share Posted July 4, 2017 Here you go. (These aren't from the same instance as the logs I posted above, but it's the same problem.) There doesn't seem to be any difference between whether I'm on the same network as the server or streaming externally. Also, once it works, it continues to behave completely normally until I restart the server. On, and one other thing -- if I do get it working, I often see multiple ffmpeg.exe processes spawn in Task Manager, I guess corresponding to the number of times it had failed previously. logs-fail.zip logs-success.zip Link to comment Share on other sites More sharing options...
pünktchen 1251 Posted July 4, 2017 Share Posted July 4, 2017 Please try the attached plugin. Link to comment Share on other sites More sharing options...
erobertc 0 Posted July 5, 2017 Author Share Posted July 5, 2017 Thanks! So far so good. I'll post here again if I run into any problems. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now