4 ms·
Regardless of how much of an "abomination" RTMP is, Apple's system is a huge hack: 1. It's taking a transport stream format based around a buffering model...
by DarkShikari 16y ago
Regardless of how much of an "abomination" RTMP is, Apple's system is a huge hack:
1. It's taking a transport stream format based around a buffering model... but as far as I can tell, completely ignoring the actual buffering model itself. Instead of working within the MPEG buffering model, it simply makes some arbitrary restrictions on the size of each chunk, which doesn't make any sense.
2. Aggravated by 1), the latency of the system is horrible. Good luck using "HTTP live streaming" for anything that needs less than 5 seconds of latency, let alone 0.05 seconds.
I can implement a videoconferencing system in RTMP. I sure as heck can't do it with "HTTP live streaming".
Now, does it work well for some use-cases? Sure, but it's definitely not a replacement for all aspects of RTMP.
(Also, obviously as you mentioned the link is biased, but it's actually not even relevant to your post: it's comparing Adobe's software to Microsoft's software, not comparing protocols. Talking about Adobe's software is very silly when nearly everyone actually uses Red5, Wowza, etc. For example, it mentions that the latency is ~6 seconds, but the company I work for has that down to ~100 times less.)
- Terretta 16y agoAbsolutely love your work, btw. Not a huge fan of HLS for our customers even with libraries of tens of thousands of full length movies serving to iOS. Latency is the number one complaint. Meanwhile, to your point, we churn out video broadcasting sites for clients on RTMP. EDIT:(We support server side PPM on RTSP, RTMP, and both Apple and Microsoft adaptive HTTP, from WMS, IIS Media Services, Wowza, DSS, and FMS. This makes us pretty familiar with the buffering approaches, and agree with you, Apple's is essentially broken. That said, the value of being able to leverage a more "commodity" HTTP infrastructure is huge.) Been meaning to talk to you some time about x264 in the near real time mode. Drop me contact info to my user name at gmail? PS. We use both Red5 and Wowza, but usually Wowza for these kinds of projects, which we have deployed CDN-wide.
- DarkShikari 16y agoAdded my email to my profile.
- kierank 16y ago1. It's taking a transport stream format based around a buffering model... but as far as I can tell, completely ignoring the actual buffering model itself. Instead of working within the MPEG buffering model, it simply makes some arbitrary restrictions on the size of each chunk, which doesn't make any sense. Yes, it totally ignores the MPEG buffering model. Perfectly valid streams don't play on Apple devices.