Hi, thanks for maintaining RootEncoder.
We are using the RTMP module and noticed that the library already sends the standard @setDataFrame/onMetaData message when publishing starts.
For some RTMP ingest/analytics workflows, it would be useful to add custom fields to the onMetaData object, such as an encoder string.
Currently, RtmpClient exposes setCustomAmfObject(), but that appears to add fields to the RTMP connect command object, not to the stream-level onMetaData message.
Would it be possible to expose an API to add custom onMetaData fields, for example:
rtmpClient.setCustomMetadata(customMetadata)
or a similar method on RtmpStreamClient?
Expected behavior:
- Keep the existing standard metadata fields unchanged
- Append the custom fields to the
@setDataFrame/onMetaData AMF object
- Send them whenever the library sends
onMetaData, including the initial publish and full reconnects
- Logic should be consistent across both
AMF0 and AMF3
Thank you again for all the work you put into the project.
Hi, thanks for maintaining RootEncoder.
We are using the
RTMPmodule and noticed that the library already sends the standard@setDataFrame/onMetaDatamessage when publishing starts.For some
RTMPingest/analytics workflows, it would be useful to add custom fields to theonMetaDataobject, such as an encoder string.Currently,
RtmpClientexposessetCustomAmfObject(), but that appears to add fields to theRTMPconnect command object, not to the stream-levelonMetaDatamessage.Would it be possible to expose an API to add custom
onMetaDatafields, for example:or a similar method on
RtmpStreamClient?Expected behavior:
@setDataFrame/onMetaData AMFobjectonMetaData, including the initial publish and full reconnectsAMF0andAMF3Thank you again for all the work you put into the project.