{"_id":"576d42354bcd290e00428953","createdAt":"2016-02-11T16:39:04.926Z","isReference":false,"link_external":false,"order":0,"slug":"introduction-to-chirp","user":"56bc6af27c91881900089bac","__v":3,"body":"[block:html]\n{\n  \"html\": \"<style>\\np a {\\n\\tdisplay: inline-block;\\n \\tbackground: #288fba;\\n  color: white !important;\\n  font-weight: bold;\\n  padding: 10px 20px;\\n}\\np a:hover {\\n  background: #7bbe5f;\\n}\\n</style>\"\n}\n[/block]\nChirp is a suite of technologies to send and receive information using sound. A chirp encodes an array of integers as an audio signal, which can be transmitted by any device with a speaker. This can then be received by any device with a microphone running a Chirp SDK. It is designed to be robust over distances of several metres, in noisy, everyday environments.\n\nAs the transmission takes place purely via audio signals, no internet connection or prior pairing is required, and any device within hearing range can receive the chirp. \n\nChirps can be generated on-device with dynamic data, or recorded as an audio file for later playback - like a sonic barcode. \n\n[Read more about Chirp's technology.](chirp-technology-overview)\n\n## Audio Types and Data Rates\n\nIn our basic SDKs, we offer two different Chirp audio protocols. Each protocol is tailored for a specific environment or use case, with distinct data capacities and audible properties.\n\nThe **standard** protocol is capable of sending 50 bits of data as an audible melody, comprised of a 10-character alphanumeric string. \n\nThe **ultrasonic** protocol sends 32 bits of data in the ultrasonic part of the acoustic spectrum, inaudible to human ears.\n\n[Read more about Chirp protocols.](chirp-protocols)\n\nIf you want to send larger or more complex payloads, the Chirp REST API allows you to associate an arbitrary JSON object to a chirp, which can be seamlessly retrieved when the chirp is heard. (Note that this functionality is not yet available in ultrasonic mode.)\n\n[Read more about the Chirp API.](chirp-api-overview)\n\n## SDKs\n\nChirp SDKs are provided for multiple different platforms, from web applications to embedded electronic devices. Our developer kits in scripting languages (Python, JavaScript) are provided under open-source licenses. Note that these are only capable of sending chirps, and cannot currently receive.\n\nWe've included the following SDKs within this package:\n\n* iOS (iPhone, iPad)\n* Android\n* JavaScript (send only; requires internet connection)\n* Python (send only; requires internet connection)\n\n[Read more: Chirp SDKs Overview.](our-sdks)\n\n## Downloads\n\nTo start exploring the Chirp SDKs, you'll need to sign up for Chirp credentials at the Chirp Admin Centre.  From here, you can download developer resources, and view analytics on how your users are using your Chirp-enabled applications.\n\n[Registration and Downloads](https://admin.chirp.io/sign-up)","hidden":false,"link_url":"","project":"56a526d4e7a1622b0024fae4","type":"basic","excerpt":"","githubsync":"","next":{"description":"","pages":[]},"parentDoc":null,"version":"576d42354bcd290e00428941","api":{"auth":"required","params":[],"results":{"codes":[]},"settings":"","url":""},"category":"576d42354bcd290e00428942","sync_unique":"","title":"Introduction to Chirp","updates":[],"childrenPages":[]}

Introduction to Chirp


[block:html] { "html": "<style>\np a {\n\tdisplay: inline-block;\n \tbackground: #288fba;\n color: white !important;\n font-weight: bold;\n padding: 10px 20px;\n}\np a:hover {\n background: #7bbe5f;\n}\n</style>" } [/block] Chirp is a suite of technologies to send and receive information using sound. A chirp encodes an array of integers as an audio signal, which can be transmitted by any device with a speaker. This can then be received by any device with a microphone running a Chirp SDK. It is designed to be robust over distances of several metres, in noisy, everyday environments. As the transmission takes place purely via audio signals, no internet connection or prior pairing is required, and any device within hearing range can receive the chirp. Chirps can be generated on-device with dynamic data, or recorded as an audio file for later playback - like a sonic barcode. [Read more about Chirp's technology.](chirp-technology-overview) ## Audio Types and Data Rates In our basic SDKs, we offer two different Chirp audio protocols. Each protocol is tailored for a specific environment or use case, with distinct data capacities and audible properties. The **standard** protocol is capable of sending 50 bits of data as an audible melody, comprised of a 10-character alphanumeric string. The **ultrasonic** protocol sends 32 bits of data in the ultrasonic part of the acoustic spectrum, inaudible to human ears. [Read more about Chirp protocols.](chirp-protocols) If you want to send larger or more complex payloads, the Chirp REST API allows you to associate an arbitrary JSON object to a chirp, which can be seamlessly retrieved when the chirp is heard. (Note that this functionality is not yet available in ultrasonic mode.) [Read more about the Chirp API.](chirp-api-overview) ## SDKs Chirp SDKs are provided for multiple different platforms, from web applications to embedded electronic devices. Our developer kits in scripting languages (Python, JavaScript) are provided under open-source licenses. Note that these are only capable of sending chirps, and cannot currently receive. We've included the following SDKs within this package: * iOS (iPhone, iPad) * Android * JavaScript (send only; requires internet connection) * Python (send only; requires internet connection) [Read more: Chirp SDKs Overview.](our-sdks) ## Downloads To start exploring the Chirp SDKs, you'll need to sign up for Chirp credentials at the Chirp Admin Centre. From here, you can download developer resources, and view analytics on how your users are using your Chirp-enabled applications. [Registration and Downloads](https://admin.chirp.io/sign-up)