Closed nickottocode closed 4 months ago
It looks like the extra field comes back within the final metadata response but not in the per-message response
https://github.com/deepgram/deepgram-python-sdk/tree/main/examples/streaming/microphone
Using raw websockets the metadata includes the extra parameter. "extra" is included already in the final response.
"metadata": {"extra": {"example": "param"}, "request_id": "0bbe9f92-5b42-44bc-80cc-7c8f8c891e3f", "model_info": {"name": "general", "version": "2024-01-26.8851", "arch": "base"}, "model_uuid": "1ed36bac-f71c-4f3f-a31f-02fd6525c489"}
PR merged. Will be cutting a release shortly. Closing issue.
What is the current behavior?
It looks like the extra field comes back within the final metadata response but not in the per-message response
Steps to reproduce
https://github.com/deepgram/deepgram-python-sdk/tree/main/examples/streaming/microphone
Expected behavior
Using raw websockets the metadata includes the extra parameter. "extra" is included already in the final response.