-
Notifications
You must be signed in to change notification settings - Fork 63
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
Add tools to support RTP stream saving/playback #252
Comments
RTPDump is a widely-implemented file format for saving RTP packet dumps without the overhead of UDP and IP headers found in pcap dumps. libWebRTC, Wireshark, and RTPTools all have an implementation. For more information see: https://www.cs.columbia.edu/irt/software/rtptools Relates to #549
RTPDump is a widely-implemented file format for saving RTP packet dumps without the overhead of UDP and IP headers found in pcap dumps. libWebRTC, Wireshark, and RTPTools all have an implementation. For more information see: https://www.cs.columbia.edu/irt/software/rtptools Relates to #549
RTPDump is a widely-implemented file format for saving RTP packet dumps without the overhead of UDP and IP headers found in pcap dumps. libWebRTC, Wireshark, and RTPTools all have an implementation. For more information see: https://www.cs.columbia.edu/irt/software/rtptools Relates to #549
RTPDump is a widely-implemented file format for saving RTP packet dumps without the overhead of UDP and IP headers found in pcap dumps. libWebRTC, Wireshark, and RTPTools all have an implementation. For more information see: https://www.cs.columbia.edu/irt/software/rtptools Relates to #549
RTPDump is a widely-implemented file format for saving RTP packet dumps without the overhead of UDP and IP headers found in pcap dumps. libWebRTC, Wireshark, and RTPTools all have an implementation. For more information see: https://www.cs.columbia.edu/irt/software/rtptools Relates to #549
RTPDump is a widely-implemented file format for saving RTP packet dumps without the overhead of UDP and IP headers found in pcap dumps. libWebRTC, Wireshark, and RTPTools all have an implementation. For more information see: https://www.cs.columbia.edu/irt/software/rtptools Relates to #549
RTPDump is a widely-implemented file format for saving RTP packet dumps without the overhead of UDP and IP headers found in pcap dumps. libWebRTC, Wireshark, and RTPTools all have an implementation. For more information see: https://www.cs.columbia.edu/irt/software/rtptools Relates to #549
RTPDump is a widely-implemented file format for saving RTP packet dumps without the overhead of UDP and IP headers found in pcap dumps. libWebRTC, Wireshark, and RTPTools all have an implementation. For more information see: https://www.cs.columbia.edu/irt/software/rtptools Relates to #549
@maxhawkins This all landed right? It would be cool to have an example for this, currently we don't have a way to do easy 'playback'. I think this could be it though! also maybe taking in a webm or something easy for users to play with. |
I'm leaving this open to remind myself to add a Player/Recorder to rtpdump. I merged the reader/writer for the file format but I haven't done playback/time tracking. |
One nice thing the rtpdump utility does is provide a way to pipe in RTP streams and save as a file. You can hook it up to gstreamer, for instance. rtpdump -Fdump -o example.rtpdump 0.0.0.0/5000 gst-launch filesrc location=example.wav ! decodebin \
! audioconvert ! audioresample ! opusenc ! rtpopuspay \
! application/x-rtp,media=audio,encoding-name=OPUS,payload=111 \
! udpsink host=0.0.0.0 port=5000 Maybe we could add a gstreamer-based utility for converting input audio/video into output opus/webm streams saved as rtpdump files. |
Summary
Add libraries that make it easier to play and record RTP streams.
Motivation
It's useful to play pre-recorded streams directly to a PeerConnection to support playback of audio/video files without transcoding.
The text was updated successfully, but these errors were encountered: