RTSP pull problems establishing stream #1433
Unanswered
rebound-software
asked this question in
Help
Replies: 3 comments 2 replies
-
Did you get anywhere with this Mark? I have similar/same problem. I have OME all working fine when I use wss send from the ovneplayer app, but when using the API to pull from RTSP, I just get [SPRtcSig-t3334:12] Orchestrator | orchestrator.cpp:740 | Could not find Origin for the stream: [#default#app/stream5] even though it says the stream creates fine. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I found it was intermittent so gave up and reverted to an older version of OME that is stable. I haven’t tried with the latest version for a while so will try again next week as I’m back working on my project involving OME for the next few weeks.
On 12 Jan 2024, at 19:09, Adam D ***@***.***> wrote:
Did you get anywhere with this Mark? I have similar/same problem. I have OME all working fine when I use wss send from the ovneplayer app, but when using the API to pull from RTSP, I just get [SPRtcSig-t3334:12] Orchestrator | orchestrator.cpp:740 | Could not find Origin for the stream: [#default#app/stream5] even though it says the stream creates fine.
—
Reply to this email directly, view it on GitHub<#1433 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AI3XBIMFCMDXMMQWOIS7EQDYOGC6BAVCNFSM6AAAAAA67ZELYGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DCMJTGQ4DI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
2 replies
-
This is the version reported at OME startup for what I’m using:
OvenMediaEngine v0.14.18 (v0.14.15-43-g06553b97)
I’ve also reverted the version of ffmpeg to 4.4.1 due to a high CPU load issue with v5 using GPU acceleration (fixed in later versions of OME but couldn’t then get stable RTSP stream establishment). I built it locally on my media server (i.e. not docker).
On 14 Jan 2024, at 19:48, Adam D ***@***.***> wrote:
thanks for letting me know, what version please? so i can test that version too and confirm. thanks.
—
Reply to this email directly, view it on GitHub<#1433 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AI3XBIPPK6SDXEH4ABQ43DLYOQZA7AVCNFSM6AAAAAA67ZELYGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DCMRVHA4TS>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
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
-
I am looking to bring my OME server up to a more recent version (v0.16.0 release tag) but am experiencing issues with RTSP feeds again. My current version is based on v0.14 (-version reports v0.14.18 (v0.14.15-43-g06553b97)) with ffmpeg v4.4.1 which was needed to workaround an issue with high CPU usage when using v5.0.1 at the time. I have an Nvidia GPU and HW acceleration enabled in both builds. NB I noticed HW accel seems to be broken in the latest code on master and doesn't recognise the GPU (recent commits elude to some changes in this area)
Initial establishment of the RTSP stream to a WebRTC client seems to fail, but after a few retries, I then get a stream flowing and picture in the browser ovenplayer client. Dropping and re-establishing the WebRTC stream works fine until the unused stream timeout causes the RTSP pull feed be dropped. Re-establishment of the feed again after this is then problematic and can end up in a state where it seems the RTSP Pull is flowing, but I can't get a WebRTC session playing at all without restarting OME.
Here's the log output from a clean start of OME and then trying to view an RTSP camera feed (there are 3 separate cameras in this log):
My config file is:
@getroot Previously, I have shared access to my RTSP camera feed to debug/diagnose problems so if this would be helpful then happy to do again.
Thanks, Mark.
Beta Was this translation helpful? Give feedback.
All reactions