Response buffer was null after encoding and bad audio quality #155

andreslorek opened this Issue Feb 16, 2016 · 2 comments


None yet

2 participants


I'm getting this warning sometimes:
[WARN] 2016-02-15 14:25:48,634 [RTMPConnectionExecutor-8] - Response buffer was null after encoding

I don't know if this is related with the warning, but at the same moment that we get many of these logs, the audio loses quality (the transmission has some gaps or little jumps).

I'm using Red5 1.0.6 and my file is

I don't have a known scenario where this happens, but when I noticed the problem CPU and memory were at normal values.

mondain commented Feb 17, 2016

Do you experience the same issue when using RTMP instead of RTMPT?


How should the error look like for RTMP connections?
Is it ok to look for "BaseRTMPConnection - Response buffer was null after encoding" in my logs?

I noticed the bad audio quality using RTMP, but maybe some client was connected using RTMPT during the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment