-
Notifications
You must be signed in to change notification settings - Fork 53
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
How do I output the srt stream? #60
Comments
Saving it to disk could be done in the same way you'd copy from any other As for go-ffmpeg, I cannot find a library by that name. |
thanks for the quick response and yes it's ffmpeg-go. guessing my two options would either be to relay the stream to an srt port that I can read using ffmpeg or alternatively write to stdout and use the pipe: method then? |
Is it possible to publish the srt stream to localhost? Then I could simply ffmpeg -i srt://localhost:1234 and get the stream I need to transform and send |
You could use this library to open a listener, and write to every client that it accepts, and then it should work in ffmpeg with the address in your comment. I don't think I understand your use case, though, or if you are at the stage of your work where the issue you have is with this Go binding. You should start with a manual setup that uses srt-live-transmit and/or ffmpeg to do what you want, then start work on automating it with Go. |
I have to send an srt stream h.265 to rtmp for distribution in h.264. Currently I can trasnmit to srtgo listener and send the srt stream but struggling to input the stream to ffmpeg to do the transcoding to h.265 and send to rtmp endpoint. with another service the stream gets published to localhost and ffmpeg can receive input from localhost. hope that makes sense |
What is failing when you try to input the stream to ffmpeg, and does it work if you do |
I can start the server and stream video to it and log the bytes but how do I get the stream to something like go-ffmpeg to convert and restream? or even just save to disk?
The text was updated successfully, but these errors were encountered: