Jump to content

Live TV (M3U Tuner) not playing or massive intermittant delay


jakrigg
Go to solution Solved by softworkz,

Recommended Posts

jakrigg

Version 4.2.0.26-beta

 

Hi there, currently having an issue with playing Live TV m3u sources.

 

Having either:

-"no compatible streams"

-"spinning wheel"

-"eventualy play 'some' streams after massive delay

 

Opening the M3U streams via VLC works flawless.

 

So far I have:-

-removed and re-added source m3u and xml

-restarted server

-updated to latest beta

-confirmed there are no outgoing dns resolution issues from the server

 

Attached is the server log from a restart - failing to play a couple. If there are any clues there, please let me know.

 

embyserver.txt

 

Kind regards,

 

Jonny

 

 

Link to comment
Share on other sites

Ok, i'm going to have to add logging, so please try the next beta build and then let's compare. thanks.

Link to comment
Share on other sites

jakrigg

Hi Luke, I have done some more testing.

 

On beta 28, still the same.

- some live tv streams work fine

- some do not - just sit there. In the attached server log, i finished on a live radio stream which would not play

embyserver4.2.0.28.txt

 

I then downgraded to 4.1.1.0 and ran the same tests

- i experienced no issues and the streams on all (including the live radio stream) performed as expected

embyserver4.1.1.0.txt

 

Hope the attached can provide some info

 

Cheers,

 

Jonny

 

 

 

Link to comment
Share on other sites

jakrigg

I did try this also, however here is the log with this step.

 

Steps:-

-reboot

-refresh guide (twice)

-play 7mate stream (success)

-play radio stream (fail - error report in log) just spinning wheel on ui, no error

 

Note on 4.1.1.0 or using vlc the radio stream works fine

 

 

embyserver.txt

Link to comment
Share on other sites

@@jakrigg, try removing all tuners and guide sources from emby server, then run the guide refresh to clear out the database, then add them back. thanks.

Link to comment
Share on other sites

Your provider is sending back a response header saying this stream requires winamp. I have no idea what that means, sorry. You'll have to ask them. Maybe you can play with customizing the m3u tuner settings to make emby server appear like it is winamp.

Link to comment
Share on other sites

Unfortunately I can't make a direct comparison because your 4.1.1 log shows an m3u8 url whereas your 4.2 logs are different.

 

It's two different inputs that get handled differently. My guess is if you tried the exact same thing on 4.2 it would still work.

Link to comment
Share on other sites

jakrigg

I can re-do the test when I get home and I'll upload the logs. I am only ever using the same raw playlist and XML provider so not sure why you are seeing a difference

Link to comment
Share on other sites

jakrigg

Hi Luke, no worries - done.

 

Steps:-

-delete m3u and xml sources

-downgrade to 4.1.1.0

-reboot

-refresh guide data (sources empty)

-add sources back in

-let auto refresh happen & also manual refresh guide data

-tested playing triplej station - successful straight away.

embyserver-4.1.1.0.txt

post-319049-0-54456500-1563259524_thumb.png

 

Next:

-delete m3u and xml sources

-upgrade to 4.2.0.30

-reboot

-add sources back in

-let auto refresh happen & also manual refresh guide data

-tested playing triplej station - fails -  just spinning wheel

embyserver-4.2.0.30.txt

post-319049-0-06578100-1563259586_thumb.png

 

Cheers, Jonny

Link to comment
Share on other sites

  • Solution

@@jakrigg - thanks for supplying the stream details.

 

After adding the m3u tuner there were the following channels added:

 

  • triplej
  • triplej
  • triplej unearthed

All three channels played fine. Could you please retry with the latest beta?

  • Like 1
Link to comment
Share on other sites

jakrigg

Hi mate, yes now working again with beta 33 not with previous 4.2.0.x betas

 

Was the issue to do with how ffmpeg was handling the streams?

 

Thanks for your help, jonny

Link to comment
Share on other sites

We did not do anything specifically for this, so i guess we'll have to keep an eye on it. Could be a result of changes in the remote stream.

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