[Bug 793765] rtpopuspay doesn't support clock-rate=16000
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Fri Feb 23 21:13:34 UTC 2018
https://bugzilla.gnome.org/show_bug.cgi?id=793765
--- Comment #2 from David Woodhouse <dwmw2 at infradead.org> ---
I'm not quite sure why that is relevant to the clock-rate of the 'timestamp'
field in the RTP packets.
The wire protocol I'm working with needs a timestamp field, equivalent to the
timestamp in RTP packets, which works at a frequency of 16000HZ.
With the patch above, I can simply convert the RTP into my own wire protocol
and the timestamps can be copied between the two as-is.
Without the patch, I end up having to regenerate timestamps somehow for the
outbound traffic.
(In fact what I have right now is my *own* subclass of rtpbasepay, because that
way I can deal with bug 793763 too, *and* interoperate with FarStream 0.2.7 by
only having a single encoding-name instead of a list. But I'd *like* to get
everything working without such hacks, of course.)
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list