summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCara Salter <cara@devcara.com>2022-06-26 09:14:49 -0400
committerCara Salter <cara@devcara.com>2022-06-26 09:14:49 -0400
commitf05eb9e87ce3f8f72126e82299f32b940e3b29f0 (patch)
treeb3f927a55cd49c3d76e5bda24d20f85ae80f894f
parent8bd904670f0e7acea40d0f7f34fac0df502a74c1 (diff)
downloadsite-f05eb9e87ce3f8f72126e82299f32b940e3b29f0.tar.gz
site-f05eb9e87ce3f8f72126e82299f32b940e3b29f0.zip
post: Update Custom RTMP
-rw-r--r--blog/custom-rtmp.md14
1 files changed, 13 insertions, 1 deletions
diff --git a/blog/custom-rtmp.md b/blog/custom-rtmp.md
index e1a89fb..5e2d1a8 100644
--- a/blog/custom-rtmp.md
+++ b/blog/custom-rtmp.md
@@ -83,9 +83,21 @@ To recap, the general steps I took were:
I hope this was able to help! I plan on looking into this more, especially the
access control bits, so I'll be sure to update this post with anything I find.
+Update 2022-06-19:
+
+I should've known this was too good to be true. RTMP does *not* do well with
+cross-continent streaming. The last act was delayed 30 minutes by technical
+audio difficulties from the extreme delay.
+
+A better alternative would be SRT[^3], via [nginx-srt-module](https://github.com/kaltura/nginx-srt-module).
+It uses UDP as the underlying protocol, so it's more error-resistant. Part of
+the issue was a delay in tech checks and the network quality of the remote
+talent, but this was an issue that could have also been prevented by not using a
+protocol that's not designed for cross-continent use.
+
[^1]: Which, if you didn't know, is a really wonderful tool that can do
basically anything related to A/V including transcoding and streaming.
[^2]: Dynamic Adaptive Streaming over HTTP
-
+[^3]: Secure Reliable Transport
[ome]: https://ovenmediaengine.com
[ddevault]: https://drewdevault.com/2018/08/26/Self-hosted-livestreaming.html