-
Notifications
You must be signed in to change notification settings - Fork 58
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
no audio? #10
Comments
|
Yeah, audio streams are not implemented unfortunately, just video. Supporting audio streams would not be particularly difficult to add I think. It just hasn't been a priority. Some code from https://github.com/horgh/audiostreamer could potentially be used at least as inspiration. I'd probably accept a PR! |
When this project was running under Windows, FFmpeg output Pipe protocol failed all the time, the prompt: Bad file descriptor. Is it related to the operating system? I use Windows 10. Can you help me? |
Can you paste the output? And what flags are you running it with? I've never tried it on Windows and don't have it available to try. It might be doable, I'm not sure. |
Thank you for your reply. Below is my input log. I checked Windows and Linux, and there are differences in pipe usage. The failed return message is failed when the call to avformat_write_header is failed: Bad file descriptor returns a value of -9. I'm trying to use this project in Linux PS C:\Gopath\src\github.com\horgh\videostreamer> .\videostreamer.exe -host 127.0.0.1 -port 8080 -format mp4 -input 6.6.mp4 -verbose true -fcgi false |
Does the same input file work on Linux? It looks like you modified it to print out the error reported by You could try testing your input using the program in the I don't know what's going on. It does look like there's something questionable with the pipe. I wonder if using named pipes would be better for Windows. Using the examples from http://trac.ffmpeg.org/ticket/986 with https://github.com/natefinch/npipe. |
Thanks for the replay. I'm still trying to use the same input file for Linux. Next I'll try to use a named pipe, and I need to make sure I can enter a pipe name that FFmpeg can use. I looked at the FFmpeg source code and found no way to export video content into memory. I tried to modify the pipe protocol into a file protocol, and as a result, I could output mp4 files normally. Then try to write a service that puts the mp4 file directly into the browser. Chrome decoded incorrectly because of audio. I'll write it down here if I get a result. Thank you for your advice |
I will keep you on watch until "AUDIO" is implemented. Thanks! |
Hi @horgh, Nice work. Any chance for you to revisit the code and improve it with audio any time soon? BR |
I recommend anyone looking for a complete solution with audio to check out https://github.com/pion/webrtc and https://github.com/deepch/RTSPtoWebRTC |
Thanks for the links but i really like his clean solution, it works very smoothly. I hope he gets motivated and can have a look at it again, I have a generic camera with sound and I can help debug and test the code if necessary. Cheers |
I tried to add support for audio but hit a wall, my rtsp looks like this:
The funny thing is the title: h264.mp4 :) |
Muxed to mkv and now i have video and audio, unfortunately mkv is about 10% bigger in size than mp4. (without the audio and same condition). If anyone interested I can push the changes to my github, but I changed the C code only, I am not a go programmer. |
Great project!
I'm not getting any audio with my stream. Is that to be expected?
The text was updated successfully, but these errors were encountered: