Replies: 2 comments
-
You have to let Origin do the encoding. Since one origin and multiple edges are usually used, encoding is performed only in the origin. So, usually, Origin uses a powerful machine, and Edge uses several less powerful machines. OVT has the ability to synchronize everything in Origin to Edge, and streams input through OVT cannot be re-encoded. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Your issue has been moved from the Issue board to the Discussion board. If you need another discussion, please write in this thread. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
First of all: you're doing a great software, thank you very much for it!
ABR doesn't seem to work with LLHLS.
I have tried to setup transcoding for my home streaming server.
The overall stream flow was supposed to be:
OBS via RTMP -> OME (origin) -> OME (Edge+transcoding) via OVT -> OvenPlayer via LLHLS.
To Reproduce
Steps to reproduce the behavior on the Edge+transcoding server:
curl https://edgeserver/app/streamname/qweqwe.m3u8 -v Waits couple of seconds (gets the stream from the OVT upstream), then gives 404
Expected behavior
Its expected that connect to the m3u8 playlist will trigger the transcoding process and will return the playlist.
Logs
The full log of the OME running on the edge+transcoding server:
Server (please complete the following information):
Player (please complete the following information):
Not applicable, the error happens during HTTP GET phase.
Additional context
For some reason, I was able to fetch the playlist https://example.com/app/stas/llhls.m3u8 even though it wasn't defined under the statement. Perhaps it is a default hard-coded playlist.
Feel free to reach me with questions or if I need to test anything.
Beta Was this translation helpful? Give feedback.
All reactions