Errors: "Bitrate exceeds DirectStream limit" and "Process exited with code 137"

[EmYaj 25]

I'm getting an issue where some livetv channels are coming up as a black screen.  I've confirmed with VLC that the stream works fine, and it's not all channels - just some. 

I've attached the portion of the log that I thought was most relevant as well as the whole untouched log.

The two parts that jumped out at me were:

2025-01-30 11:58:22.003 Info App: Bitrate exceeds DirectStream limit: media bitrate: 8654824, max bitrate: 4000002

(my client was set to Auto but I tried setting it to the Maximum 4K bitrate and the problem persists)

and

2025-01-30 11:58:22.005 Info App: ProcessRun 'StreamTranscode e6d43b' Process exited with code 137 - Failed

which from a quick google might mean out of memory?  I don't believe that is the case but I am on a 8GB RAM server (it doesnt do much else) so I guess it's possible.  Usage shows 6GB/8GB (2GB free) in htop.

Any suggestions where I might start troubleshooting this?

embyserver-fulllog.txt relevant-portion.txt

Edited January 30, 2025 by EmYaj

[Luke 42077]

Quote

2025-01-30 11:58:22.003 Info App: Bitrate exceeds DirectStream limit: media bitrate: 8654824, max bitrate: 4000002

Hi, this is not an error.

[Luke 42077]

Was there an ffmpeg log? Please attach that as well. Thanks.

[EmYaj 25]

7 minutes ago, Luke said:

Hi, this is not an error.

OK good to know thank you.

 

6 minutes ago, Luke said:

Was there an ffmpeg log? Please attach that as well. Thanks.

Attached two, theyre both from the same similar timestamp and event but I'm not 100% sure which is the one you're looking for.  I believe first one (ending 734_1) is correct one.

ffmpeg-directstream-b52582b3-6b6e-4d61-ac63-7d8c7563e734_1.txt ffmpeg-directstream-1edd2c69-5514-42b7-91d8-102e27e78988_1.txt

[EmYaj 25]

Just following up here - I think this may have been a ram issue - I was having this issue a couple of times per day and restarting the server temporarily solved it.   I added an additional 8GB ram today (16GB total) and have not had the issue yet today which is much better than the last few days so I suspect the issue may be fixed.  I'll continue to monitor and update if this changes but for now if anyone else comes across this - consider adding RAM.