Closed basemkhirat closed 1 year ago
This issue is related to the HTTP callback bug.
As a workaround, you can manage the FFmpeg process independently, since the transcoder is essentially an FFmpeg process. By managing FFmpeg yourself, you can bypass this bug.
You can add [param]
after the output
as follows, and try again.
transcode {
enabled on;
ffmpeg /usr/local/bin/ffmpeg;
engine 360p {
enabled on;
... ...
output rtmp://127.0.0.1:[port]/[app]/[stream][param];
}
}
I am transcoding to 360p and sending the output to another vhost which named by the engine name.
I am using on_connect and but It's firing twice.
One when connecting the origin vhost and the other when SRS connected internally to the quality host.
To authenticate, I send a secret with the stream_key like stream_key?secret=09mY6AsPSeSF and check it using on_connect hook. like what implemented in srs-cloud.
The data sent from SRS to the first
on_connect
request:And the data sent from SRS to the second
on_connect
request:And the last one not having the secret, so it will fail to connect.
SRS Version: 5.0 SRS Config:
Is there a method to allow firing on_connect once? or a method to forward the secret to the other vhost to be authenticated also, or recommned another authentication method to do this.