Republishing from Nimble Streamer to Cloudflare Streams

If we push a live feed from OBS to Cloudflare Streams directly, we have no issue.

However if we push from OBS to Nimble Streamer to Cloudflare Streams, we can’t seem to make a connection. We’ve confirmed we have no issue pushing out to another RTMPS endpoint from Nimble Streamer such as Facebook.

I know there had been a few issues with Larix Broadcaster so I was wondering if this might be a similar issue.

Logs from our Nimble Streamer show the following:

[2021-10-25 12:53:53 P927-T961] [rtmppublisher] E: failed to recv buffer from client: 42
[2021-10-25 12:53:55 P927-T961] [rtmppublisher] E: failed to recv buffer from client: 42
[2021-10-25 12:53:57 P927-T961] [rtmppublisher] E: failed to recv buffer from client: 42
[2021-10-25 12:53:59 P927-T961] [rtmppublisher] E: failed to recv buffer from client: 42
[2021-10-25 12:54:01 P927-T961] [rtmppublisher] E: failed to recv buffer from client: 42
[2021-10-25 12:54:03 P927-T961] [rtmppublisher] E: failed to recv buffer from client: 42
[2021-10-25 12:54:05 P927-T961] [rtmppublisher] E: failed to recv buffer from client: 43
[2021-10-25 12:54:07 P927-T961] [rtmppublisher] E: failed to recv buffer from client: 43
[2021-10-25 12:54:09 P927-T961] [rtmppublisher] E: failed to recv buffer from client: 42
[2021-10-25 12:54:11 P927-T961] [rtmppublisher] E: failed to recv buffer from client: 42

Cheers,
Michael

To be clear, Larix Broadcaster has no problems now.

Cool! We’re happy to check this out and try to identify this issue.

Hi @SenselessData, we’ve taken a look at Nimble Streamer and believe we’ve found the pair of issues that would cause this. We’re working on a fix.

We’ll update this thread once we’ve deployed the fix and confirmed it works. One of the issues may require a configuration change in your Nimble setup.

Hi, Softvelum Nimble Streamer team here.

Please feel free to share what was the reason for the failure and let us know if you need any assistance in resolving this issue.

1 Like

Hey! Sorry for the late reply here, I was on vacation.

Few threads of progress on our end:

  1. The way Nimble Streamer sends client version makes Stream Connect think the incoming connection is using RTMPE, which is not supported. We’re working on ways to solve this, but in the meanwhile disabling the RTMPS handshake client version in nimble.conf should solve the issue with sending RTMPS to your live input.
...
rtmp_handshake_client_version_disabled = true
...
  1. We also tested using Nimble Streamer in conjunction with OBS and Stream Live. This setup caused significant audio/video synchronization issues. We think this is related to how Nimble Streamer may be modifying the presentation timestamp on audio tracks. We’re investigating this more.