Jump to content

Live TV hangs at 33%


user60

Recommended Posts

user60

I'm having an issue with live TV to Roku devices where it will stop playing and go to a spinning circle at 33%.  Sometime this will last a few minutes but most of the time it just hangs there, I've waited up to 1/2 hour, until you exit the channel and go back in then the issue will happen again after playing for a while.  It's a fairly random occurrence and can happen every 10 minutes or may not happen for an hour but almost always happens.  This also causes issues with recordings of live TV at about the same rate.  This happens on 3 different Roku devices.  I've attached the embyserver and ffmpeg logs from the last occurrence.  In the Emby app settings there are a couple of notes about Roku devices and I've tried yes and no for each with no change.

System

AMD Ryzen 5 3400g with radeon vega graphics

32 GB RAM

Emby 4.6.7.0

Fedora 35 workstation

Roku 11.00 build 4184-CU

Emby app 4.0.46

Homerun HDHR5-4US firmware 20210624

Thanks

ffmpeg-transcode-55f3c12c-76ff-497f-a0c9-ad850f66ff5d_1.txt ffmpeg-directstream-6e274c09-912d-4bfe-8e29-db0a8f0c51ea_1.txt ffmpeg-directstream-40bd00db-8176-44d7-aa56-e9143eb2d736_1.txt embyserver (1).txt

Link to comment
Share on other sites

user60

I had never used the web app so I just ran it along with 2 Roku's and the web app had a couple of times that it hung for less then 10 seconds at about the same time the Roku's both went to the 33% spin.  The first time the Roku's came back but the second they are still at it after 20 minutes.  I personally don't watch recordings so the web app will have to wait until later to test them if it would be useful.

Right after I posted this I went back to check the web app and it is solidly hung and not coming back.

 

Edited by user60
Link to comment
Share on other sites

  • 2 weeks later...
user60

I am still having this issue.  I noticed if I boot the computer it takes longer to see the issue but it still happens and gets worse with time.

Link to comment
Share on other sites

Hi. Your ffmpeg logs are full of what looks like errors in the source:

10:48:07.727 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875471, current: 19132132; changing to 297875472. This may result in incorrect timestamps in the output file.
10:48:07.727 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875472, current: 19133634; changing to 297875473. This may result in incorrect timestamps in the output file.
10:48:07.727 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875473, current: 19135135; changing to 297875474. This may result in incorrect timestamps in the output file.
10:48:07.727 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875474, current: 19136637; changing to 297875475. This may result in incorrect timestamps in the output file.
10:48:07.727 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875475, current: 19138138; changing to 297875476. This may result in incorrect timestamps in the output file.
10:48:07.727 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875476, current: 19139640; changing to 297875477. This may result in incorrect timestamps in the output file.
10:48:07.826 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875477, current: 19141141; changing to 297875478. This may result in incorrect timestamps in the output file.
10:48:07.827 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875478, current: 19142643; changing to 297875479. This may result in incorrect timestamps in the output file.
10:48:07.827 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875479, current: 19144144; changing to 297875480. This may result in incorrect timestamps in the output file.
10:48:07.827 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875480, current: 19145646; changing to 297875481. This may result in incorrect timestamps in the output file.
10:48:07.827 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875481, current: 19147147; changing to 297875482. This may result in incorrect timestamps in the output file.
10:48:07.926 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875482, current: 19148649; changing to 297875483. This may result in incorrect timestamps in the output file.
10:48:07.927 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875483, current: 19150150; changing to 297875484. This may result in incorrect timestamps in the output file.
10:48:07.927 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875484, current: 19151652; changing to 297875485. This may result in incorrect timestamps in the output file.
10:48:07.927 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875485, current: 19153153; changing to 297875486. This may result in incorrect timestamps in the output file.
10:48:07.927 [segment @ 0x2050380] Non-monotonous DTS in output stream 0:0; previous: 297875486, current: 19154655; changing to 297875487. This may result in incorrect timestamps in the output file.

It is possible the upcoming 4.7 release will deal with this better.

Link to comment
Share on other sites

  • 1 month later...
  • 3 weeks later...

Hi, have you updated to Emby Server 4.7.5? Are you still running into this?

Link to comment
Share on other sites

user60

Sorry for the delay, was out of town and then found when I had rebuilt to Ubuntu I hadn't enabled debug in the logs.  Yes I am still having this issue.  I'm at Emby server 4.7.5 and it seems to be better, in the attached log we saw the issue at 06:12 and 12:15.  Also because of other issues I have changed to a HomeRun FLEX 4K.

 

 

ffmpeg-directstream-cf9a0085-835c-4345-8338-e6c3b5a221a9_1.txt 1722598979_embyserver(1).txt

Link to comment
Share on other sites

Happy2Play
37 minutes ago, user60 said:

Sorry for the delay, was out of town and then found when I had rebuilt to Ubuntu I hadn't enabled debug in the logs.  Yes I am still having this issue.  I'm at Emby server 4.7.5 and it seems to be better, in the attached log we saw the issue at 06:12 and 12:15.  Also because of other issues I have changed to a HomeRun FLEX 4K.

 

 

ffmpeg-directstream-cf9a0085-835c-4345-8338-e6c3b5a221a9_1.txt 8.14 MB · 0 downloads 1722598979_embyserver(1).txt 144.53 MB · 0 downloads

I am confused as LibraryMonitor is monitoring cache and transcode-temp folders and your backups.

2022-07-05 00:00:00.002 Info App: Cache path: /emby/video/cache
2022-07-05 00:00:00.002 Info App: Transcoding temporary files path: /emby/video/transcoding-temp

2022-07-05 00:10:00.002 Debug LibraryMonitor: New file refresher created for /emby/video/Emby Backup - 2022-07-05 00.10.0 - Auto

2022-07-05 07:11:00.699 Debug LibraryMonitor: New file refresher created for /emby/video/transcoding-temp/F6FC62/F6FC62_1109.ts
2022-07-05 07:11:00.699 Debug LibraryMonitor: New file refresher created for /emby/video/transcoding-temp/F6FC62/F6FC62_1110.ts.tmp

So your library pointing to /emby/video is breaking everything.

Backups, Cache and Transcode-temp cannot exist in your media library.

 

Link to comment
Share on other sites

Yea you can keep the library at emby/video, but move all of those settings paths that you configured out of them.

like for example you could do emby/data, and put transcoding temp under there, cache path under there, backups under there, etc.

we should add some safeguards into the server to not even allow this to situation to happen.

Link to comment
Share on other sites

user60

Those are changes I made when having issues with space but this issue started before that (but with the old server version).  I've created a new folder and set transcoding etc to point there.  Should be able to see if it corrects it tomorrow.

 

Thanks for the time on this.

  • Thanks 1
Link to comment
Share on other sites

  • 2 weeks later...
On 7/19/2022 at 11:58 AM, user60 said:

Made the changes requested but still seeing the issue.  It is much better after changing the paths and I've attached new logs.  Did I miss a path to change?

 

 

embyserver (2).txt 11.92 MB · 0 downloads ffmpeg-directstream-e508caea-d44a-43c5-8fb9-177c68cf943c_1.txt 4.51 MB · 1 download

HI, this log contains timeouts trying to communicate with your HDHR:

2022-07-19 06:51:16.762 Error HttpClient: Error getting response from http://10.0.0.16/discover.json
	*** Error Report ***
	Version: 4.7.5.0
	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
	Operating system: Linux version 5.15.0-41-generic (buildd@lcy02-amd64-065) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #44-Ubuntu SMP
	Framework: .NET 6.0.2
	OS/Process: x64/x64
	Runtime: opt/emby-server/system/System.Private.CoreLib.dll
	Processor count: 8
	Data path: /var/lib/emby
	Application path: /opt/emby-server/system
	System.Net.Http.HttpRequestException: System.Net.Http.HttpRequestException: No route to host (10.0.0.16:80)

So maybe it was offline?

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