# \[Announce\] node-red-contrib-voice2json (beta)

**URL:** <https://discourse.nodered.org/t/announce-node-red-contrib-voice2json-beta/29066>\
**Category:** Share Your Nodes\
**Created:** [27 June 2020 13:43 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-voice2json-beta/29066 "2020-06-27T13:43:57Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![JGKK](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jgkk/32/18515_2.png) [@JGKK](https://discourse.nodered.org/u/JGKK)\
**Post date:** [6 July 2020 05:55 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-voice2json-beta/29066/31 "2020-07-06T05:55:28Z")

</div>

> [@sepia-assistant](#):
>
> Sorry, but I didn't quite get the argument here. Are you saying the "wav buffer" is different from the raw audio stream (=another buffer)?

Yes a raw stream from a microphone is just buffers of pcm audio which have no information attached to them like length or encoding. So any program you pass it too wouldn’t know what to do with it. Wav data on the other side has riff headers embedded in it which will provide all that information. That’s why when you want to convert or play raw audio in any tool you actually will have to enter that information manually. The question is if sepia is streaming the raw data from the microphone or if it is actually streaming wav chunks that have headers?

> [@sepia-assistant](#):
>
> I'll try to read a bit more about voice2json and its interfaces.

I really recommend you read the white paper about the voice2json pipeline by mike the developer:

> **[How voice2json Works](http://voice2json.org/whitepaper.html)**
>
> Command-line tools for speech and intent recognition on Linux

---

_[View the full topic](https://discourse.nodered.org/t/announce-node-red-contrib-voice2json-beta/29066)._