davidmarshalljr 1 Posted March 11, 2019 Share Posted March 11, 2019 Howdy! I'm broadcasting a stream using Wowza media player, and I want user devices to access the Wowza encoder directly. I'm wondering how I can prevent direct streaming from happening. I've attached the ffmpeg log. Is it possible to have it come directly from the server without direct streaming? What format do I need to use to accomplish this? The dashboard says that direct streaming is happening because the container isn't compatible, but the stream is. Thanks! =DDavid Link to comment Share on other sites More sharing options...
Luke 37065 Posted March 12, 2019 Share Posted March 12, 2019 Hi there, did you forget to attach the ffmpeg log ?thanks. Link to comment Share on other sites More sharing options...
davidmarshalljr 1 Posted March 12, 2019 Author Share Posted March 12, 2019 Sorry about— here it is Log.txt Link to comment Share on other sites More sharing options...
Luke 37065 Posted March 12, 2019 Share Posted March 12, 2019 Hi, can you attach the emby server log as well please? thanks. Link to comment Share on other sites More sharing options...
davidmarshalljr 1 Posted March 12, 2019 Author Share Posted March 12, 2019 Here you go! Thanks for your help. embyserver 20190312-02.txt embyserver 20190312.txt Link to comment Share on other sites More sharing options...
Luke 37065 Posted March 12, 2019 Share Posted March 12, 2019 So the wowza server is not on your local network? Link to comment Share on other sites More sharing options...
davidmarshalljr 1 Posted March 12, 2019 Author Share Posted March 12, 2019 It’s not, but I also have an encoder that is on the local network, on the same switch as Emby that also does the direct streaming thing. Does it matter that it’s saying that the container is the wrong format? Link to comment Share on other sites More sharing options...
Luke 37065 Posted March 12, 2019 Share Posted March 12, 2019 At this time we will not allow our store apps to direct play to remote urls because we cannot verify the legality of the content. In order to avoid potential violations of app store policies, that is why we run it through your Emby Server and direct stream it. There is no way around this. the container transcoding reason is probably erroneous. I'll double check, but since we don't currently have a reason string for the above scenario, it probably just ends up using that one generically. Link to comment Share on other sites More sharing options...
davidmarshalljr 1 Posted March 12, 2019 Author Share Posted March 12, 2019 Gotcha. And now that I think about it, the local encoder is on another subnet on that switch, so that's why it isn't playing direct to that URL either. I'm thinking that if I add the subnet to the "local URL" list, it will stream directly from the encoder. I'll update with these new findings when I get back to the office. Thanks for your help! Link to comment Share on other sites More sharing options...
Luke 37065 Posted March 13, 2019 Share Posted March 13, 2019 Thanks for the feedback. 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