-
Notifications
You must be signed in to change notification settings - Fork 91
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
RFC 4175: Uncompressed RTP Payload Support #7
Comments
Hello and thank you for your interest in uvgRTP! Unfortunately at this point in time, we (Ultravideogroup) do not need this feature meaning I cannot use my working hours to implement it. I can, however, take a look at this later when my personal schedule clears up a bit. In the mean time, I would like to remind you that uvgRTP supports generic payload types that can be used to stream raw video. I will leave this issue open for now. |
I wanted to leave this here as a reference. This is the only fully functional example I've found. If this could be useful to add in the feature. I'm currently looking at implementing this library as a solution so we will see if I get to the feature first. http://www.live555.com/liveMedia/doxygen/html/RawVideoRTPSource_8hh_source.html |
Thanks for the source I took a quick look at the specification and it looked quite simple but unfortunately I don't have the time to implement and test it at the moment. Start of April is the earliest I can take a closer look at it. |
Sounds fine, I figured it would be useful to see. |
Hey noticed you added the enhancement tag, hope this gets included! |
I added the tag only to categorize this. Sadly we don't have anyone currently implementing any new features to uvgRTP. I try to maintain this repo the best I can, but I'm not familiar with the code itself. Our group deals with transporting compressed video since we have our own HEVC encoder Kvazaar that we use in almost all of our projects. |
Would it be possible to get support for RFC 4175 aka SMPTE 2110 as a feature of this library?
The text was updated successfully, but these errors were encountered: