Jump to content

Single OTA HD channel not working DLNA, all others OK


viziofire

Recommended Posts

viziofire

@Luke:   Having a problem with a single OTA channel via DLNA with MB using ServerWMC as backend.     As all the other channels work, Krustyreturns does not believe it is ServerWMC issue.     Basically, the channel will start up streaming as normal and then freeze after about 8-10 seconds.    Can you assist?

Edited by viziofire
Link to comment
Share on other sites

viziofire

Media Browser Server Version 3.0.5490.2

Media Browser for Android Version  2.1.38

Backend ServerWMC build 1175

Tuner Silicondust HDTC-2US

Included is server log and 3 transcode logs.    First 2 transcode logs are channel 2 and 4 which stream normally.   Last transcode log is channel 11 which streams ~8-10 seconds then freezes and app goes back to prior menu or occasionally app crashes.    

 

Thanks 

server-63558036071.txt

transcode-788a1942-84b1-42d3-ba1c-a290ca832503.txt

transcode-7657950e-f817-4204-8c27-67fbaa5e95a5.txt

transcode-e1c3bc38-0dd5-4dd1-a659-87318dce5e06.txt

Link to comment
Share on other sites

Unfortunately, this is a really difficult one. i will have to think about this one. only thing i would do is try taking the command line at the top of the transcode file and run it outside of MBS. Since it's a live tv stream, it should continue on forever.

Link to comment
Share on other sites

viziofire

I'm stumped but thanks for considering to think about it.   As its the only channel that seems to be problematic with MB, there must be something different about ATSC feed that can't be transcoded as well by MB?    I'd like to be able to test out this theory by turning off the transcoding from MB and sending an h.264 stream from HDTC-2US to be streamed directly from MB to the client.  Is there a way to turning off MB transcoding to test this theory out?     The client has no problem playing back h.264 streams from tuner using Silicondust app.   Its hard to believe the bit rate of the problematic channel is too high for my server to handle but that seems to be how it is behaving.   

Edited by viziofire
Link to comment
Share on other sites

No i would start with my above test and take MBS out of the equation. We don't decode or transcode. Other tools do it for us. Sometimes there's an obvious answer where we're sending the wrong command but this isn't one of those cases.

Link to comment
Share on other sites

viziofire

OK, I've run the ffmpeg command line (with options) from first line of transcode code, lots of errors.   Do you want to see?

Link to comment
Share on other sites

viziofire

its pretty maddening as I can watch the same channel without issue in Silicondust app.   For some reason ffmpeg doesn't like the DLNA stream for this channel?  Even its just for a test, would it be possible to skip the ffmpeg transcoding step?

Edited by viziofire
Link to comment
Share on other sites

viziofire

Just thought I'd pass on a couple more findings in case it might assist in solving the issue.

 

With ServerWMC not using DLNA mode, channel 11 streams normally to client as do all the other channels.

With ServerWMC using DLNA mode, channel 11 freezes after ~8 seconds whereas all other channels stream fine.

I have also tried modifying the ServerWMC config file to sending h.264 streams to Media Browser which has same result as mpeg2 source.

 

What does it mean if  a channel fails in DLNA mode whereas it streams fine in non-DLNA mode?

 

Just trying to look at this another way but is it possible to use another backend in DLNA mode to eliminate the possiblity of this somehow relating to ServerWMC?

Edited by viziofire
Link to comment
Share on other sites

i'm not sure what you're asking up there, although i'm surprised that the h264 stream from hdhr is having the same result. since your model supports dlna, you definitely want to stay with that despite the issue with this channel. as a whole it's going to be considerably more reliable than turning dlna mode off.
 

does your hdhr support h264 transcoding? maybe it doesn't so the server wmc setting is having no effect.

Link to comment
Share on other sites

viziofire

I'm using an HDTC-2US which can definitely transcode to h.264 and my experience with its transcoding has been pretty good.    I too was surprised/disappointed that sending h.264 Live TV stream to MB resulted in the same issue with this single channel.     I've sent a note to krustyreturns as is it possibly still a serverWMC issue?     I do prefer DLNA as its a little quicker than non-DLNA and I think the image looks a little better as well.   

 

@Luke:  Is there another backend or method for me to try DLNA for this channel?  

Link to comment
Share on other sites

No, and I doubt it's a server wmc issue. if you can reproduce the stoppage using ffmpeg all by itself, then it has nothing to do with server wmc or MBS.

Link to comment
Share on other sites

viziofire

First let me say thank you for trying to solve this mystery.   I understand that it may not directly have to do with MB however MB does require using ffmpeg.   Is there a way to tell MB to send the DLNA stream directly without running it through ffmpeg?   I am able to DLNA stream the same channel directly from the HDTC tuner to a smart TV (Panasonic Viera) and to Kodi without any issue so I know the HDTC-2US tuner has no issues with DLNA.    Am I correct that the issue appears to be ffmpeg?   It just doesn't seem to make sense.   Is it possible there is an error in the command line options for ffmpeg in the log?

Edited by viziofire
Link to comment
Share on other sites

viziofire

Let me throw this out there.    If I configure Kodi to act as PVR client with ServerWMC as the backend streaming DLNA, that would be removing ffmpeg from the equation, correct?    If I set this up and channel 11 streams without issue, that would support that the issue is ffmpeg.   If however Channel 11 fails upon DLNA streaming,  would it be reasonable to conclude this is a serverWMC issue?

Edited by viziofire
Link to comment
Share on other sites

No because the only thing server wmc does is give the dlna url to MBS. Nothing more than that. And Kodi is using the stream in a different way so it's not a true comparison. Kodi's requirements are much lower because it's video player can handle just about anything. Some MBS clients have specific requirements and we have to ask ffmpeg to do some complicated things in order to achieve that.

Link to comment
Share on other sites

viziofire

I understand everything you are saying but unless there is a command line glitch in ffmpeg, it just doesn't seem like it makes sense for ffmpeg not to be able process the stream.   I read a post from krustyreturns that he did find an issue with caused DLNA to fail in serverWMC   Whether this issue is related I do not know but I will probably try setting up a quick Kodi PVR client with ServerWMC to see if the same issue exists for DLNA streaming with this channel.   If the same issue persists with this channel, the common denominator is serverWMC.

Edited by viziofire
Link to comment
Share on other sites

That issue was server wmc producing the wrong url leading to the HDHR throwing a 404 error. And in that case, obviously playback never started at all. So it's not the same thing. ffmpeg is man-made software and as a wise man once told me, anything man-made can fail. 

Link to comment
Share on other sites

viziofire

You're probably correct as everything is pointing to ffmpeg.    As this is such an obscure issue, is it even worth conveying to them?    How often have you switched ffmpeg versions used with MB? 

Link to comment
Share on other sites

viziofire

@Luke:  Krustyretruns has figured out a novel way to work around this issue but I'm still perplexed.   Is it possible try a different version of ffmpeg with MB? 

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...