OVT between origin and edge fails #248
Labels
bug
Confirmed as bug
Comments
This is what you request edge to play with ovt (this doesn't work. ovt is the protocol edge asks for origin). To play with HLS, you need to request play to "http://edge_host/app/stream/playlist.m3u8". Then, if it does not have the corresponding stream, edge requests the stream to the origin server as ovt according to the setting. And the part you wrote OBS->rtsp->origin is the rtmp protocol, not rtsp. |
|
@getroot please read the log, not just the log-excerpt which apparently was misleading. |
|
Oh, sorry. I haven't looked closely at the log. |
|
This problem has been resolved and committed to the Master branch. |
|
@getroot I can confirm Here some logs: |
|
nope, the current master branch is not usable at all. Constantly getting buffer underruns, even in local network setup. |
|
lldash isn't stable yet. It is in progress at #182 . This is not an ovt problem. And since our edge is not an http reverse proxy, dash and hls need some time to create chunks. If you need an http reverse proxy, use ome as origin and nginx as edge. I am verifying the stability of the origin-edge behavior you reported in this task. Do HLS and WebRTC work well? |
|
My test setup does not include WebRTC. The HLS stream from edge can't be played. |
|
With the most recent changes, LL-DASH stream is unusable in chrome and unplayable in firefox even directly from origin. This use case worked fine with master until 3 days ago. Thus I don't think OVT is to blame for these issues. |
|
Did you wait until all the chunks are made when playing hls? First in your log, edge returned 202 to the player. This means ome is making chunks. |
|
We are working on multiple patches at the same time, so don't try to find the cause of the problem by date. Maybe there is a patch on the lldash side. Right now I want to check only the stability of ovt's behavior in this issue. At the same time, it is difficult to solve the problem if you put many issues on one table. |
|
Sorry, I can't help testing OVT because I can't get any stable video playback over HLS, DASH or LL-DASH with current master branch. So I have no idea how to determine if it is working properly or not. I can however confirm that some audio and frame data gets transferred successfully, and Chrome/Chromium seems to be able to playback these sometimes. |
|
Please provide your full log (not the edited log) when you can't play hls from edge. |
|
I rebuilt all of the docker with the latest master branch to reproduce your problem and tested it several times. But I couldn't reproduce.
I used http://demo.ovenplayer.com and HLS is playing normally. When Edge receives packets through Origin, it starts creating chunks for HLS and DASH. Edge returns http 202 while chunks are being created, and passes data along with http 200 when all chunks are created. Playback starts from this point. |
|
@getroot please test using hls.js and Firefox as webbrowser. |
|
https://hls-js-dev.netlify.app/demo/ http://demo.ovenplayer.com Test it here. The OvenPlayer is also using hls.js when playing HLS.
|
|
@getroot see configuration linked in the issue description. Of course it contains the TLS configuration. |
|
In my environment, it plays well with firefox as well. OvenPlayer is also using hls.js. https://gist.github.com/basisbit/96e09409dbcb313ac30f029a1364a449#file-error-log-L47 As I've mentioned above many times, this log means that Edge started creating chunks. And when all the chunks have been made, playback begins. Can you check if it plays well with OvenPlayer? OvenPlayer automatically retries when a 202 response is received. But the player above won't. This is the difference. Try playing hls again after the chunks are made. And I want to see the full log, not your truncated log. Can you provide a full log? |
|
The problem you have is judged to be not OVT's problem. If the issue continues to reproduce, please create a new issue related to it. I close this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
OVT between origin and edge server seems to be broken. Edge server does not send any video data to client. Also, the documentation is missing minimal working full configuration sample for origin and edge for a typical Origin -> edge setup.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
OVT should be successfully used by the edge server to get video data with low latency so the edge server can then be used to stream using HLS / DASH / LL-DASH.
Logs
See https://gist.github.com/basisbit/96e09409dbcb313ac30f029a1364a449
Server (please complete the following information):
Additional context
OBS 26.0.2 was used to stream screen to the origin server using rtsp and B-Frames was set to
0.The text was updated successfully, but these errors were encountered: