You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when we use RTMP.SourceBin, some metadata information that might be present in the RTMP stream is lost.
An example might be framerate, send as a part of OnMetaData message or SetDataFrame message. We don't pass it any further from the RTMP.Source.
FLV stream produced by the RTMP.Source is then demuxed with FLV.Demuxer and the H264 format generated by the latter element is missing framerate field as information about the framerate might not be available in the FLV stream.
To solve this problem, we need to be able to pass out-of-band metadata of RTMP stream to the FLV demuxer. The following options are available:
we could add RTMPPayload stream format (with additional metadata fields), send it from RTMP.Source instead of Membrane.RemoteStream and accept it within FLV.Demuxer - the problem is, that this solution "doesn't scale well": if we were to deliver FLV stream unwrapped from yet another protocol, we would need to make FLV.Demuxer accept yet another stream format
we could pass metadata as options to FLV.Demuxer - however a problem would occur if metadata would change throughout the stream
we could make FLV.Demuxer accept some FLV stream format, which could contain some optional metadata map
The text was updated successfully, but these errors were encountered:
Currently, when we use
RTMP.SourceBin
, some metadata information that might be present in the RTMP stream is lost.An example might be
framerate
, send as a part ofOnMetaData
message orSetDataFrame
message. We don't pass it any further from theRTMP.Source
.FLV stream produced by the
RTMP.Source
is then demuxed withFLV.Demuxer
and theH264
format generated by the latter element is missingframerate
field as information about theframerate
might not be available in the FLV stream.To solve this problem, we need to be able to pass out-of-band metadata of RTMP stream to the FLV demuxer. The following options are available:
RTMPPayload
stream format (with additional metadata fields), send it fromRTMP.Source
instead ofMembrane.RemoteStream
and accept it withinFLV.Demuxer
- the problem is, that this solution "doesn't scale well": if we were to deliver FLV stream unwrapped from yet another protocol, we would need to makeFLV.Demuxer
accept yet another stream formatFLV.Demuxer
- however a problem would occur if metadata would change throughout the streamFLV.Demuxer
accept someFLV
stream format, which could contain some optionalmetadata
mapThe text was updated successfully, but these errors were encountered: