-
-
Notifications
You must be signed in to change notification settings - Fork 791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SRT Streaming issue #1330
Comments
Hello, SRT is using version 1.4.4: I will test it and report you back |
Thanks for your quick reply! Awesome. |
How are you doing to reproduce the stream using a player? I'm using ffmpeg as encoder to test (it is used by OBS so it should be the same) It is not working for me using docker from quick start guide: |
We deployed OvenMediaEngine on a Ubuntu 22.04 VPS running docker and using their OME Docker Launcher: After deployment one has to manually enable SRT in the OME config file (located at /opt/ovenmediaengine/bin/origin_conf/Server.xml) The input stream URL that works by default after enabling SRT is: The playback URL that works by default is: Using OBS, we found no problem using both H265 and H264 over SRT. We we're able to view the output stream via OME's demo player (be sure to use HTTP, not HTTPS, when visiting the website) |
Thank you, I will try that way |
Using RootEncoder, we intermittently get adaptation header parsing errors on our OME logs:
RootEncoder doesn't seem to give any errors, but the stream can not be played on OME. |
For now, I can reproduce the case and I'm working to find the reason. |
After investigate it and some changes I was able to stream only audio. |
Hello, Finally it is working using the code in the branch: But only H264 is working. Using H265 you will have a black screen. I will fix tests and merge changes |
Thanks for the quick fixes, they are much appreciated. |
I see, I will try to fix it. For now, you can use this gradle to test using H264 (this is the last commit of the fix branch): implementation 'com.github.pedroSG94:RootEncoder:2981a93caf' |
Which version of OBS and SO did you use to test? It is not available on Linux version: |
Thanks for the fixes, Pedro! The H.264 SRT stream works; I just tested the fix branch. The H.265 still does not work, the bytes are sent but nothing is shown on the player side. The encoding depends on your hardware, whether you have an encoder which supports H.265, I think unless it can do CPU encoding. I've used a Macbook Pro with the ARM M1 Pro chip, which supports H.265 encoding. FYI, maybe this will be useful: https://obsproject.com/forum/threads/obs-28-no-hevc-streaming-encoder-option.160539/ |
Hello, Thank you, I will try with my mac mini with M1 chip and OBS. |
Hello Pedro, @robinwesterik and me, we did some more testing. It turns out, to avoid the black screen on OME with H.265 you have to use LLHLS as the decoder. We tested SRT H.265 with OBS and LLHLS on the player side and it worked. (You have to use HTTP instead of HTTPS). When streaming using the RootEncoder library with SRT and H.265, the OME logs are as follows:
Let us know in case of any questions. |
Hello, I was testing with OBS with my MacMini M1 and I have exactly the same problem that with my library. Black screen video but audio working using wss source and never load using HLS LL source. I let you a video here: video.mp4As you can see in the video you have wireshark to make sure that streaming is working where you can see the server IP in destination that is the same that the used in OBS and player. I also tested using SRT url encoded as suggested in the tutorial but with the same result. I tested using H264 and it is working fine: Tested using: |
Closing as inactive. |
Hello Pedro,
I have a question about the SRT client. Which version does the current implementation support?
I am trying to setup a connection to a OvenMediaEngine. The situation is as follows:
However, on the player side, there is no video coming. When I test the server with OBS studio as explained in this link (srt://ip:port?streamid=srt%3A%2F%2F{domain or IP address}[%3APort]%2F{App name}%2F{Stream name}) the stream is coming through. I noticed that in your library you expect the URL to be in the following form: srt://ip:port/streamid. Thus, I supply the link as follows: srt://ip:port/srt%3A%2F%2F{domain or IP address}[%3APort]%2F{App name}%2F{Stream name}.
My hypothesis is that the SRT socket connects successfully but the streamid is perhaps incorrectly supplied.
Any idea what could be the issue here?
Thank you for your response in advanced.
Regrads,
Andrej
The text was updated successfully, but these errors were encountered: