webrtcbin: is h264parse (opusparse, etc) really needed?
filesrc location=media.mkv ! matroskademux name=demux webrtcbin bundle-policy=max-bundle name=webrtcbin stun-server=stun://stun.l.google.com:19302 \
demux.audio_0 ! opusparse ! rtpopuspay ! queue ! application/x-rtp,media=audio,encoding-name=OPUS,payload=96 ! webrtcbin. \
demux.video_0 ! h264parse ! rtph264pay aggregate-mode=zero-latency ! queue ! application/x-rtp,media=video,encoding-name=H264,payload=97 ! webrtcbin.'
Though not investigated thoroughly, I didn't get noticeable difference on receiving side when h264parse
and opusparse
are omitted. What's the real reason behind them and is it fine not to use them?
The question arose from library dependencies which are needed for h264parse
and opusparse
and consume precious flash memory space on embedded device.