How do I push RTMP Stream to another RTMP Server with curl or php? #1176

zapf2000 · 2023-04-06T17:03:47Z

zapf2000
Apr 6, 2023

I'm a bit confused using the REST API. I like to push a RTMP Stream (in my case it's an ABR stream transcoded on OME) to another server.
Let's say my video is called "1080p" and my audio is called "320k" and the app is called "app" and stream key is "live" on the origin.
So the push url to OME is rtmp://origin.url:1935/app/live.
The edge server listens on rtmp://edge.url:1935/0 (no app name, just the stream key 0).
How can I do this using php together with curl?

Backgroud: I like to stream to commercial end-user IPTV devices (Set-Top Boxes, TV's, Satellite TV receivers). They don't support LL-HLS or WebRTC. Most only support RTMP or RTSP. That makes OME to a show stopper. So I like to use MediaMTX Server as an edge to stream in RTSP and RTMP directly to devices, which do not support LL-HLS or WebRTC as a compromise for users that don't have capability for WebRTC or LLHLS, but can have a latency less than 5 seconds. Traditional HLS or DASH has much more latency.

Answered by Keukhan

Apr 11, 2023

@zapf2000

I committed the patched code to the master branch.
Thanks to you, I was able to find and solve the problem. 👍

5e3edad

View full answer

getroot · 2023-04-10T03:48:34Z

getroot
Apr 10, 2023
Maintainer Sponsor

Have you checked the API docs?

https://airensoft.gitbook.io/ovenmediaengine/rest-api/v1/virtualhost/application/push

Put rtmp://edge.url:1935/ in "url" and "0" in "streamKey" of Json body

0 replies

zapf2000 · 2023-04-11T06:41:55Z

zapf2000
Apr 11, 2023
Author

Yes, I checked the API docs. The problem was the variant names.
{ "id": "{unique_push_id}", "stream": { "name": "{output_stream_name}", "variantNames": [ "h264_fhd", "aac" ] },

I can put in anything there, but it won't work. If i use "trackIds" instead, it works fine but it is not documented in the API docs. I came across this in one of the issue posts here. Now everything works fine with a reasonable end-to-end latency of 1...1.5s.
OBS -> OME (Origin with ABR transcoding) -> OME (Edges with RTMP Push only pushed the 1080p RTMP stream) -> SRS (restream in HLS, RTMP and FLV) -> Enigma2 Satellite Receiver and/or Smart TV.

For those who may have the same problem, this is the curl syntax:

Start push:
curl -X POST -H "Content-Type: application/json" -H "Authorization: Basic XXXXXXXXXXXXXXXXXX" -d '{"id": "1", "stream": {
"name": "live", "tracks":[0,2]}, "protocol": "rtmp", "url": "rtmp://XXXXXXXXXXX/live", "streamKey": "livestream"}' http://XXXXXXXXXXXX.XXX/v1/vhosts/default/apps/app:startPush

Stop push:
curl -X POST -H "Content-Type: application/json" -H "Authorization: Basic XXXXXXXXXXXXXXXX" -d '{"id": "1"}' http://XXXXXXXXXXXX.XXX/v1/vhosts/default/apps/app:stopPush

6 replies

Keukhan Apr 11, 2023
Maintainer Sponsor

It seems that it is possible to accurately determine whether the variantNames parameter is working or not by analyzing your log. I'll look at the application named 'app' in your configuration file and tell you what I predicted.

there are no encodes names such as h264_fhd and aac in the 'app' application. values of variantNames you can use are bypass_audio, bypass_video, opus, aac48, opus_low, 720p.

<Encodes>
	<Audio>
		<Name>bypass_audio</Name>
		<Bypass>true</Bypass>
	</Audio>
	<Video>
		<Name>bypass_video</Name>
		<Bypass>true</Bypass>
	</Video>
	<Audio>
		<Name>opus</Name>
		<Codec>opus</Codec>
		<Bitrate>192000</Bitrate>
		<Samplerate>48000</Samplerate>
		<Channel>2</Channel>
	</Audio>
	<Audio>
		<Name>aac48</Name>
		<Codec>aac</Codec>
		<Bitrate>48000</Bitrate>
		<Samplerate>48000</Samplerate>
		<Channel>2</Channel>
	</Audio>
	<Audio>
		<Name>opus_low</Name>
		<Codec>opus</Codec>
		<Bitrate>48000</Bitrate>
		<Samplerate>48000</Samplerate>
		<Channel>2</Channel>
	</Audio>
	<Video>
		<Name>720p</Name>
		<Codec>h264</Codec>
		<Bitrate>2000000</Bitrate>
		<Framerate>30</Framerate>
		<Width>1280</Width>
		<Height>720</Height>
		<Preset>fast</Preset>
		<ThreadCount>1</ThreadCount>
	</Video>
</Encodes>

Please check again.
Thanks.

zapf2000 Apr 11, 2023
Author

No, it doesn't work with variantNames.

curl -X POST -H "Content-Type: application/json" -H "Authorization: Basic XXXXXXXXXXXX" -d '{"id": "1", "stream": {
"name": "live", "variantNames": [ "bypass_video", "bypass_audio" ]}, "protocol": "rtmp", "url": "rtmp://XXXXX:1935/live", "streamKey": "livestream"}' http://XXXXXXX:8081/v1/vhosts/default/apps/app:startPush
{"message":"OK","response":[{"app":"app","createdTime":"2023-04-11T13:32:40.341+02:00","finishTime":"1970-01-01T01:00:00.000+01:00","id":"1","protocol":"rtmp","sentBytes":0,"sentTime":0,"sequence":0,"startTime":"2023-04-11T13:32:40.341+02:00","state":"error","stream":{"name":"live","trackIds":[],"variantNames":[]},"streamKey":"livestream","totalsentBytes":0,"totalsentTime":0,"url":"rtmp://XXXX:1935/live","vhost":"default"}],"statusCode":201}

OME log:

[2023-04-11 13:34:53.769] W [AW-RTMPPush0:5725] RTMPPush | rtmppush_session.cpp:92 | Could not supported codec. track_id:3, codec_id: 8
[2023-04-11 13:34:53.769] W [AW-RTMPPush0:5725] RTMPPush | rtmppush_session.cpp:92 | Could not supported codec. track_id:5, codec_id: 8
[2023-04-11 13:34:53.769] W [AW-RTMPPush0:5725] RTMPPush | rtmppush_session.cpp:92 | Could not supported codec. track_id:6, codec_id: 0
[2023-04-11 13:34:53.952] E [AW-RTMPPush0:5725] FFmpeg | third_parties.cpp:111 | [AVFormatContext: 0x7fd2cd226c00] at most one video stream is supported in flv
[2023-04-11 13:34:53.953] E [AW-RTMPPush0:5725] RTMPWriter | rtmp_writer.cpp:150 | Could not create header

I think he tries to push all variants.

When using trackId's the log looks fine and everything is working.

OME log:

[2023-04-11 13:37:54.224] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 | Output #0, flv, to 'rtmp://XXXXXXX:1935/live/livestream':
[2023-04-11 13:37:54.224] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 | Metadata:
[2023-04-11 13:37:54.224] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 | encoder :
[2023-04-11 13:37:54.224] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 | Lavf59.16.100
[2023-04-11 13:37:54.224] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 |
[2023-04-11 13:37:54.225] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 | Stream #0:0
[2023-04-11 13:37:54.225] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 | : Video: h264, 1 reference frame ([7][0][0][0] / 0x0007), yuv420p, 1920x1080 (0x0) [SAR 1:1 DAR 16:9], 0/1, q=2-31, 6$
[2023-04-11 13:37:54.225] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 | ,
[2023-04-11 13:37:54.225] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 | 1k tbn
[2023-04-11 13:37:54.225] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 |
[2023-04-11 13:37:54.225] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 | Stream #0:1
[2023-04-11 13:37:54.225] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 | : Audio: aac ([10][0][0][0] / 0x000A), 48000 Hz, stereo, 4 kb/s
[2023-04-11 13:37:54.225] I [SPAPISvr-t8081:5762] FFmpeg | third_parties.cpp:119 |
[2023-04-11 13:37:54.229] I [SPAPISvr-t8081:5762] Orchestrator | orchestrator.cpp:832 | Trying to pull stream [#default#app/live] from provider using origin map: PullProvider
[2023-04-11 13:37:54.229] I [SPAPISvr-t8081:5762] Provider | provider.cpp:144 | The inbound stream already exists: #default#app/live

This is the encoding setting in OBS:

info: ---------------------------------
info: [FFmpeg NVENC encoder: 'advanced_video_stream'] settings:
encoder: NVIDIA NVENC H.264 (FFmpeg)
rate_control: CBR
bitrate: 6000
cqp: 0
keyint: 60
preset: p5
tuning: hq
multipass: qres
profile: high
width: 1920
height: 1080
b-frames: 0
psycho-aq: 1
GPU: 0

info: ---------------------------------
info: [FFmpeg aac encoder: 'adv_stream_audio'] bitrate: 192, channels: 2, channel_layout: 3

info: [rtmp stream: 'adv_stream'] Connecting to RTMP URL rtmp://127.0.0.1:1935/app...
info: [rtmp stream: 'adv_stream'] Connection to rtmp://127.0.0.1:1935/app successful
info: ==== Streaming Start ===============================================

Keukhan Apr 11, 2023
Maintainer Sponsor

thanks. 👍 I will figure out the cause of the problem and patch it as soon as possible.

Keukhan Apr 11, 2023
Maintainer Sponsor

@zapf2000

I committed the patched code to the master branch.
Thanks to you, I was able to find and solve the problem. 👍

5e3edad

Answer selected by getroot

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

How do I push RTMP Stream to another RTMP Server with curl or php? #1176

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 6 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

How do I push RTMP Stream to another RTMP Server with curl or php? #1176

zapf2000 Apr 6, 2023

Replies: 2 comments · 6 replies

getroot Apr 10, 2023 Maintainer Sponsor

zapf2000 Apr 11, 2023 Author

Keukhan Apr 11, 2023 Maintainer Sponsor

zapf2000 Apr 11, 2023 Author

Keukhan Apr 11, 2023 Maintainer Sponsor

Keukhan Apr 11, 2023 Maintainer Sponsor

zapf2000
Apr 6, 2023

Replies: 2 comments 6 replies

getroot
Apr 10, 2023
Maintainer Sponsor

zapf2000
Apr 11, 2023
Author

Keukhan Apr 11, 2023
Maintainer Sponsor

zapf2000 Apr 11, 2023
Author

Keukhan Apr 11, 2023
Maintainer Sponsor

Keukhan Apr 11, 2023
Maintainer Sponsor