<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by James Nesfield on Medium]]></title>
        <description><![CDATA[Stories by James Nesfield on Medium]]></description>
        <link>https://medium.com/@jamesnesfield?source=rss-3403c7c9e640------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*j8ME3TRoiCjQmW4wGyzPtg.jpeg</url>
            <title>Stories by James Nesfield on Medium</title>
            <link>https://medium.com/@jamesnesfield?source=rss-3403c7c9e640------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 05:57:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jamesnesfield/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Abbey Road Hackathon]]></title>
            <link>https://medium.com/chirp-io/abbey-road-hackathon-627d16e9dad6?source=rss-3403c7c9e640------2</link>
            <guid isPermaLink="false">https://medium.com/p/627d16e9dad6</guid>
            <category><![CDATA[london]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[music]]></category>
            <category><![CDATA[dsp]]></category>
            <category><![CDATA[audio]]></category>
            <dc:creator><![CDATA[James Nesfield]]></dc:creator>
            <pubDate>Tue, 23 Oct 2018 13:05:36 GMT</pubDate>
            <atom:updated>2018-10-23T13:05:36.897Z</atom:updated>
            <content:encoded><![CDATA[<h3>Chirp + Abbey Road Hackathon</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OldD9gXRG8U3z4-BSD7xcw.jpeg" /></figure><p>Chirp is really happy to partner with Universal Music Group, Microsoft, JUCE and others to support the first <a href="https://www.abbeyroad.com/hackathon">Abbey Road Studio Hackathon</a> at their historic Studio One.</p><p>We will be providing SDKs, our data-over-audio hardware and engineering support on the day to make sure that London’s best developers interested in audio and DSP have an interesting and productive event.</p><p>We are especially happy to be able to provide <a href="https://medium.com/u/2e9fb4b6ff3b">Arduino</a>-compatible <a href="https://mailchi.mp/chirp/explorer-board/">Chirp Explorer Board</a> units which make physical prototyping easy for audio and data-over-sound purposes.</p><p>From Abbey Road:</p><blockquote>The Hackathon will explore music information retrieval, machine learning, IOT or embedded systems and experiment with new frameworks and hottest AI and audio API’s, delivered by the key players in this field. Whether you are an audio developer, MatLab or MX MSP or C++ hero or Python guru, design thinker or tech minded producer we want to hear from you.</blockquote><p>We can’t wait to see what folk build with our SDKs and hardware — this is truly an opportunity to teach the machines to sing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=627d16e9dad6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chirp-io/abbey-road-hackathon-627d16e9dad6">Abbey Road Hackathon</a> was originally published in <a href="https://medium.com/chirp-io">Chirp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quality tools matter.]]></title>
            <link>https://medium.com/chirp-io/quality-tools-matter-ce1d92aa10c1?source=rss-3403c7c9e640------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce1d92aa10c1</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[audio]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[sound]]></category>
            <dc:creator><![CDATA[James Nesfield]]></dc:creator>
            <pubDate>Thu, 04 Oct 2018 16:13:28 GMT</pubDate>
            <atom:updated>2018-10-04T16:13:28.133Z</atom:updated>
            <content:encoded><![CDATA[<p>Sound is a simple and frictionless method for nearby devices to exchange data. We believe that our data-over-sound tools should be equally easy to access and simple to use.</p><p>Since 2011 Chirp has been at the forefront of the effort to develop and productise data over audio tools. We started way back then with our own consumer-facing app for iOS and Android so we know what it is like to rely first-hand on our data over sound tech to facilitate in-app functionality. We also gained experience with operating the technology in general real world, with real users. at scale. This history has made us acutely aware of the responsibility to create well-engineered software products which perform in complex, chaotic real world environments. It also guides us in design decisions towards making these products as simple and straightforward to integrate as possible – after a all we are developers too.</p><p>Our latest releases represent the most straightforward way to add reliable, performant data transmission via sound to your app or product. We have made it as simple as possible for developers and engineers to integrate our SDKs and in doing so in many cases, add additional connectivity capabilities to their service with no additional effort or expense.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OXg8uULFSmqEmAKAWxf3Xw.png" /></figure><p>To get setup, an account can be setup at <a href="http://developers.chirp.io/">developers.chirp.io</a> – it takes 2 minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*KnRIqVkFtyy0qzxLdGwi2w.gif" /></figure><p>Installing the SDK is just as quick – here is Python going from a completely uninstalled state to sending data using sound in 10 seconds.</p><p>Chirp’s SDKs represent the fastest and most reliable sonic data transmission SDKs available, with a range of different protocols to suit different demands, data rates and acoustic environments.</p><p>Importantly, they work completely offline and do not record or store any audio at all. For developers, they have a simple set of. functions to setup, send and receive data – and they accept data in it’s existing format without imposing restrictions on the type or schema being broadcast.</p><p>Whether you are interested in adding proximity, nearby data exchange or presence detection or simply want to experiment – download our SDKs for your preferred platform today and together we can teach the machines to sing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9NhiGuijGVPmeGqJkXpKCg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce1d92aa10c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chirp-io/quality-tools-matter-ce1d92aa10c1">Quality tools matter.</a> was originally published in <a href="https://medium.com/chirp-io">Chirp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chirp + Microsoft: Effortless provisioning for Azure IoT devices]]></title>
            <link>https://medium.com/chirp-io/chirp-microsoft-effortless-provisioning-for-azure-iot-devices-814e690f602e?source=rss-3403c7c9e640------2</link>
            <guid isPermaLink="false">https://medium.com/p/814e690f602e</guid>
            <category><![CDATA[wifi-provisioning]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[data-over-sound]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[James Nesfield]]></dc:creator>
            <pubDate>Tue, 14 Aug 2018 15:31:12 GMT</pubDate>
            <atom:updated>2018-08-14T18:36:27.800Z</atom:updated>
            <content:encoded><![CDATA[<p>Anyone who has tried to connect a smart device to a new Wi-Fi network can testify that it’s an awkward and often painful process.</p><p>That’s why we’re delighted to announce that we’ve been working with Microsoft on a system to seamlessly provision new IoT devices to the Azure Cloud with nothing more than a single Chirp tone.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F1oCyJe7WS7o%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D1oCyJe7WS7o&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F1oCyJe7WS7o%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e35b542deece3ed89ead009314db6b09/href">https://medium.com/media/e35b542deece3ed89ead009314db6b09/href</a></iframe><blockquote><a href="https://channel9.msdn.com/Shows/Internet-of-Things-Show/Chirp-your-device-into-Azure-IoT-Central">https://channel9.msdn.com/Shows/Internet-of-Things-Show/Chirp-your-device-into-Azure-IoT-Central</a></blockquote><p>Provisioning these IoT devices has traditionally demanded that users spend several minutes turning the device into a WiFi hotspot, connecting to that using a laptop or smartphone, and setting the credentials — a complex and labour-intensive manual process that many customers have long struggled with.</p><p>That all changes with Microsoft adoption of Chirp for Azure MXChip onboarding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/295/1*Pf8OUJyj2vOhOIbPHK70kQ.png" /><figcaption>The Microsoft Azure MXChip</figcaption></figure><h4>Here’s how Microsoft’s provisioning for IoT devices using Chirp works:</h4><ol><li>Credentials are converted into sound and broadcast from a phone or laptop’s loudspeaker.</li><li>A nearby offline device running the Chirp Arm SDK receive the data over audio and use the credentials to connect and authenticate with the network.</li><li>That’s it.</li></ol><p>Now, leveraging Chirp’s leading data-over-sound technology, users can provision IoT devices, including MXChip, frictionlessly and in seconds rather than minutes.</p><h3>The new Chirp Arm C SDK</h3><p>Following the announcement of the collaboration between our two companies, Chirp has released for the first time its free C SDK for the MXChip board adding new possibilities for the board to interact with the environment.</p><p><strong>The SDK is available for developers to try for free today : </strong><a href="http://developers.chirp.io/"><strong>developers.chirp.io</strong></a><strong>.</strong></p><p>This is a big milestone for data-over-sound, as it marks the first public release of the Chirp SDK for Arm processors. We’ve harnessed the power of Arm’s CMSIS optimised DSP library to enable low-power real-time Chirp encoding and decoding on the Cortex-M4 and Cortex-M7 chips — which means you can add data-over-sound capabilities to your embedded devices at a sub-dollar cost per unit.</p><p>And if you already have an M4- or M7-based device with audio I/O, then your system is already Chirp-ready with no addition to your BOM. It works with any consumer MEMS microphone and speaker and is extremely robust to environmental noise and interference.</p><p>Chirp enables data to be transferred via sound, using a device’s existing speaker and microphone. It can use audible or ultrasonic frequencies, works in the most challenging acoustic environments, and does not need a network connection.</p><p>To learn more visit <a href="http://chirp.io/">https://chirp.io</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=814e690f602e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chirp-io/chirp-microsoft-effortless-provisioning-for-azure-iot-devices-814e690f602e">Chirp + Microsoft: Effortless provisioning for Azure IoT devices</a> was originally published in <a href="https://medium.com/chirp-io">Chirp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data over audio for Windows .NET]]></title>
            <link>https://medium.com/chirp-io/data-over-audio-for-windows-net-6a90ca282ddd?source=rss-3403c7c9e640------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a90ca282ddd</guid>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[windows-7]]></category>
            <category><![CDATA[audio]]></category>
            <category><![CDATA[dsp]]></category>
            <category><![CDATA[windows-10]]></category>
            <dc:creator><![CDATA[James Nesfield]]></dc:creator>
            <pubDate>Fri, 03 Aug 2018 15:31:27 GMT</pubDate>
            <atom:updated>2018-08-03T15:31:58.498Z</atom:updated>
            <content:encoded><![CDATA[<p>Data over sound is a flexible technology because it spans not just device form-factors and platforms, but also device generations. We work hard to make sure that we provide developer-friendly native SDKs for a wide range of platforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Fprz8A7kDyic26Oee3mqQ.png" /></figure><p>Starting with our iOS and Android SDKs, our suite has grown to support Python, macOS, JavaScript, Linux and prebuilt packages for embedded applications running Arm Mx chipsets, including the Raspberry Pi. Up until now, our Windows offering was limited to Windows 10 Universal Window Platform (UWP) applications.</p><p>We are happy to announce today that we have released .NET compatible assemblies which extend support back to Windows 7 SP1 to our beta users. .NET framework /C# assemblies have often been requested by our larger corporate customers due to their clients’ support of legacy systems. Chirp’s data over sound technology can now be used to bridge devices new and old — the only requirements are a loudspeaker and/or a microphone.</p><p>Getting started with this framework is as straightforward as with our other SDKs: Set your credentials, set your callbacks and start!</p><pre>// Create instance<br>chirpConnect = new ChirpConnectNet.ChirpConnect(<br>                                       &quot;YOUR_APP_KEY&quot;,                              <br>                                       &quot;YOUR_APP_SECRET&quot;<br>                                      );<br>                <br>// Set your licence<br>ChirpError err = chirpConnect.SetLicence(&quot;YOUR_CHIRP_LICENCE&quot;);</pre><pre>// Wire up information events<br>chirpConnect.Sent         += ChirpConnect_Sent;<br>chirpConnect.Sending      += ChirpConnect_Sending;<br>chirpConnect.Receiving    += ChirpConnect_Receiving;<br>chirpConnect.Received     += ChirpConnect_Received;</pre><pre>// Start the instance<br>var startErr = chirpConnect.Start();</pre><p>We are proud to support a wide range of ultrasonic and audible data over audio technologies, and will continue to ensure that any device capable of making sound can also send data.</p><p>Our .NET data over sound SDK can be downloaded now from <a href="http://developers.chirp.io/">developers.chirp.io</a>. Each product sends data using audible sound by default, but each is also easily configurable by the developer for ultrasonic data transfer. Like all our SDKs, they are available to use for free for students, startups, academics and charities.</p><p>We look forward to seeing what you build — together we will teach the machines to sing!</p><p>Chirp is a wireless communication technology that enables data to be transferred via sound, using a device’s existing speaker and microphone. It can use audible or inaudible ultrasonic frequencies, works in the most challenging acoustic environments, and requires no network connection. To learn more about the benefits of data-over-sound, visit <a href="http://chirp.io/">https://chirp.io</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a90ca282ddd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chirp-io/data-over-audio-for-windows-net-6a90ca282ddd">Data over audio for Windows .NET</a> was originally published in <a href="https://medium.com/chirp-io">Chirp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data over sound and other data connectivity technologies]]></title>
            <link>https://medium.com/chirp-io/data-over-sound-and-other-data-connectivity-technologies-41150139b3e4?source=rss-3403c7c9e640------2</link>
            <guid isPermaLink="false">https://medium.com/p/41150139b3e4</guid>
            <category><![CDATA[connectivity]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[signal-processing]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[digital-signal-processing]]></category>
            <dc:creator><![CDATA[James Nesfield]]></dc:creator>
            <pubDate>Wed, 18 Jul 2018 17:06:31 GMT</pubDate>
            <atom:updated>2018-08-15T13:24:01.744Z</atom:updated>
            <content:encoded><![CDATA[<p>Chirp is often asked why data transmission via sound a better connectivity solution than technology X, Y or Z.</p><p>The short answer is that, just as with the alternatives, the affordances of data transmission via audio often align well with a specific product’s requirements. It is <em>the pairing</em> of product requirements and the features of data transmission through audio which represent an optimum solution when combined. Just as with each of the alternatives, data-over-sound is sometimes <em>not</em> the best solution to a particular connectivity problem — though often it is.</p><p>Data-over-sound sits amongst a wide array of other data transport technologies such as Bluetooth, Wi-Fi, NFC, QR codes and GSM/LTE. Adding to this established collection of connectivity options, the growth of IoT is driving a new generation of WLAN technologies such as Zigbee, LoRa and NB-IoT.</p><p>Each of these channels are, at their most simple, ways of getting bytes from A to B. But they also have a unique set of capabilities and features — range, power requirements, hardware ubiquity, data rate and payload size to name a few. For a designer assessing this connectivity landscape for his or her product, this combination of features and benefits must be compared and assessed individually — not an easy task with so many options and combinations. The task gets harder still when multiple technologies are present and working together in concert.</p><p>That said, it is possible to extract a few key affordances where audio data transfer is often preferable. These scenarios often occur when product demands include a combination of :</p><ul><li>Requiring to support a very wide range of mobile handsets, new and old</li><li>Requiring to share data to multiple devices quickly and simply</li><li>Requiring to ensure that receiving devices are proximal</li><li>Requiring completely offline functionality</li><li>Requiring a simple, frictionless user experience</li><li>Requiring no prior setup, configuration or login</li><li>Requiring a connectivity standard to be very cross-platform, and device agnostic</li></ul><p>Chirp is at the forefront of audible and inaudible ultrasonic data transmission. Our mission is to promote this technology’s use and bring its benefits to as wide an application space as possible where we are able to add value. And although we have replaced other technologies in some products and services, we do not position data transmission via audio as a direct replacement for other connectivity solutions in most scenarios. Rather we look forward to a future when devices interact seamlessly from an end user perspective — where the technology doesn’t matter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fbKzCJYNB40z0Nt8X5NIsg.png" /></figure><p>For example, a users’s mobile device receives an image url encoded as an ultrasonic data transmission which allows it to download over GSM/LTE and display. An IoT sensor device having no user interface receives Wi-Fi credentials from a nearby laptop’s loudspeaker. Or devices broadcasting their Bluetooth MAC address within the same room are connected automatically, without being confused with those Bluetooth peripherals which may be interfering from outside of the room.</p><p>At scale this represents a point where total, frictionless connectivity is achieved by multiple solutions working collaboratively together — each bringing their own unique set of capabilities and benefits.</p><p>We look forward to the challenge and incredible opportunity to do our bit for the future of effortless device to device communications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41150139b3e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chirp-io/data-over-sound-and-other-data-connectivity-technologies-41150139b3e4">Data over sound and other data connectivity technologies</a> was originally published in <a href="https://medium.com/chirp-io">Chirp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The hardware and software of sound]]></title>
            <link>https://medium.com/chirp-io/https-medium-com-jamesnesfield-chirp-is-bullish-on-sound-41f3931642e5?source=rss-3403c7c9e640------2</link>
            <guid isPermaLink="false">https://medium.com/p/41f3931642e5</guid>
            <category><![CDATA[dsp]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[audio]]></category>
            <category><![CDATA[sound]]></category>
            <category><![CDATA[voice-assistant]]></category>
            <dc:creator><![CDATA[James Nesfield]]></dc:creator>
            <pubDate>Wed, 02 May 2018 17:42:15 GMT</pubDate>
            <atom:updated>2018-05-03T08:45:41.695Z</atom:updated>
            <content:encoded><![CDATA[<p>Advances in signal processing and a growing abundance of loudspeakers and microphones in everyday devices means there has never been a more interesting time to be in the business of making air molecules vibrate in interesting and useful ways.</p><p>Audio focussed software, and its associated hardware, are combining to foster an amazingly fertile time for sound based technologies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*-jLGrfZoNp1DHcz1_53ghw.png" /></figure><h3>Software</h3><p>Signal processing for audio has a long and successful history of major advancements. From Morse-code to DTMF, the dial-up modem, the mp3 file format — the echo cancellation that attenuates the sound of your own voice on a Skype call.</p><p>The innovation continues: pushing the envelop of what is possible using sound through digital manipulation, are companies creating <a href="https://www.ultrahaptics.com/products-programs/touch-development-kit/">the sensation of touch in midair</a> using ultrasound, providing immersive VR experiences by digitally modelling <a href="https://developers.google.com/resonance-audio/">acoustic and psychoacoustic phenomena</a>, and listening for illegal logging in the amazon <a href="https://www.youtube.com/watch?v=Lbn6kVlFaSQ">using machine learning</a> running on smartphones.</p><p>The capabilities and value that sound based technologies can deliver via new methods of signal processing continues to expand.</p><p>Chirp’s own technology has consistently pushed forward the state of the art for reliable data transmission via sound. In the last year we have increased our data rate in a wide array of acoustic conditions by 8X whilst maintaining our industry leading reliability.</p><p>Through software the decades-old loudspeaker and microphone continue to be given new superpowers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2iGrQuMVMcwNkop_bKTzIw.jpeg" /></figure><h3>Hardware</h3><p>As well as new capabilities, we also see the fundamental infrastructure needed to create, control and analyse sound becoming ever more ubiquitous and capable. At some point sound based technologies always have to interact with the real world though a transducer: a loudspeaker or a microphone.</p><p>We need three things to manipulate, listen for, and understand sound: A loudspeaker, a microphone and a processor. With each of these components capabilities continue to expand, driven by the combination of material advances, faster more efficient processors. More recent innovations in each of these spaces include <a href="http://vespermems.com/">zero power microphones</a>, ultrasonic loudspeakers used for <a href="http://www.pnas.org/content/pnas/early/2013/07/10/1301860110.full.pdf">physical levitation of objects</a>, and <a href="http://www.aspinity.com/technology.html">ultra low power processing units</a>.</p><p>When combined with DSP software, hardware’s sophistication and raw computing capability is unlocking new possibilities. For example, what happens when you combine 64 microphones with a super efficient custom processor? You get an incredibly accurate, but still battery operated and handheld ‘<a href="https://www.cae-systems.de/en/products/acoustic-camera-sound-source-localization/bionic-xs-56.html">sound camera’</a> capable of detecting the precise location of any sound source in the environment around you.</p><p>Then there is ubiquity of the hardware components themselves. Over the last decades the advent of the smartphone combined these three items and placed them in everyones pocket — over the next decade voice assistants will make them truly ubiquitous within our everyday environments.</p><p>The history of interacting with computers is an effort to seek increasingly natural means to communicate and interact with our machines. Beginning with punch-cards, through to the cryptic command line, to the graphical user interface, the mouse and then the direct manipulation of on screen objects via the touchscreen — the history of interacting with these devices has been a slow but steady swing away from talking to them on their terms, towards a arrangement where we can talk to them on our terms.</p><p>This is in part why we believe that voice based user interaction is a not momentary trend — it is here not only to stay, but to become a constant presence to the point of being taken for granted in our domestic and urban environments. The strangeness once felt listening to a lone, early adopter, mobile phone user walk down the street taking a personal call will give way to general public acceptance and then of course reliance on the benefits that these new technologies bring. It will become a social norm around being able to access information and control your environment by speaking to it.</p><p>We believe voice interaction with devices <a href="https://www.theverge.com/2018/3/13/17109782/ecobee-switch-plus-alexa-review">will be everywhere</a>. Their increasing ubiquity will usher in a set of opportunities by rolling out the hardware infrastructure that is a prerequisite for software audio technologies such as Chirp.</p><p>New software processes, more capable hardware and audio infrastructure that is evermore present in our environment.</p><p>Chirp is very pleased to be in a field with such an abundance of innovation and opportunity. The cooperation of hardware and software continues a long history of progress within audio. Our team is motivated every day to push forward the state of the art for data over sound and do our part to add to the innovation within an incredibly exciting, innovative wider field.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41f3931642e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chirp-io/https-medium-com-jamesnesfield-chirp-is-bullish-on-sound-41f3931642e5">The hardware and software of sound</a> was originally published in <a href="https://medium.com/chirp-io">Chirp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A new standard for Data Over Sound]]></title>
            <link>https://medium.com/chirp-io/a-new-standard-for-data-over-sound-50da1ef6e8da?source=rss-3403c7c9e640------2</link>
            <guid isPermaLink="false">https://medium.com/p/50da1ef6e8da</guid>
            <dc:creator><![CDATA[James Nesfield]]></dc:creator>
            <pubDate>Tue, 06 Mar 2018 19:29:35 GMT</pubDate>
            <atom:updated>2018-03-06T21:20:32.297Z</atom:updated>
            <content:encoded><![CDATA[<h3>A new standard for Data-Over-Sound SDKs</h3><p>Myself and the whole Chirp team are super excited to announce the launch of our Version 3 Connect SDKs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*ADkpMDcpQN6KBLskdPLYsg.png" /></figure><p>This is our ‘<a href="https://twitter.com/fijiaaron/status/494864581265604609">Goldilocks release</a>’. The third version — the version that puts into place all of the learnings, improvements, optimisations and polish gleaned over the course of the last 2 years through building our previous generation SDKs. If the first version was our ‘<em>too basic</em>’, the second our ‘<em>too complicated</em>’ — Version 3 is absolutely ‘<em>just right</em>’. Our v3 SDKs represent a new standard and a firm foundation for developers to integrate Data-Over-Sound into their own applications with ease and confidence.</p><p>The v3 SDKs were developed with a single priority in mind:</p><blockquote>Make it trivially quick &amp; simple to integrate Data-Over-Sound capabilities which are reliable in even the most acoustically complex, difficult environments.</blockquote><p>As such, we have made improvements across the board, but they boil down into two categories : Performance, and Developer Experience.</p><h4>Performance 📈</h4><p>The new SDKs represent a new state-of-the art for reliable data-over-sound. Depending on acoustic conditions, the v3 SDKs represent an 8X improvement in data rate over our v2 SDKs. They achieve significantly faster data transfer in all conditions, while maintaining Chirp’s best in class standard for reliability in even the <a href="https://www.theregister.co.uk/2017/01/24/chirp_nuclear_power_station_iot_audio_sensors/">loudest and most challenging</a> acoustic environments.</p><p>The performance increase is not an incremental improvement over existing data-over-sound technologies — it represents a step change in what is possible. For many applications, what used to take seconds, now takes milliseconds — the difference in user experience is transformed completely.</p><h4>Developer Experience</h4><p>Creating the v3 SDKs was an opportunity to go back to the drawing board and start from scratch. The new SDKs benefit from starting with a blank sheet of paper: we reimagined what a developer-first experience should look like for a Data Over Sound SDK.</p><p>The biggest difference here is the removal of the translation step required by version 2 SDKs. The previous generation relied on developers translating their data into an esoteric ‘Chirp Identifier’ which could then be passed to the SDK. The v3 SDKs talk about sending and receiving data in bytes — no more strange identifiers, alphabets or encoding transformations.</p><p>The result is a suite of SDKs which are trivial to integrate in minutes, and which accept data in the format you are familiar with and likely already using in your application.</p><p>For sending, the v3 SDKs have an incredibly simple interface:</p><pre>// Pseudocode send</pre><pre>Byte[] bytesToSend = {}<br>Chirp.send(bytesToSend)</pre><p>… and it is just as simple to receive data:</p><pre>// Pseudocode receive</pre><pre>Chirp.receivedData(Byte[] bytesReceived){<br>   Byte[] myData =  bytesReceived<br>}</pre><p>For developers already on our v2 SDKs, transitions guides are available via our <a href="http://developers.chirp.io/">Developer Centre</a>. The Centre has been upgraded and developer support (powered by <a href="https://www.zendesk.co.uk/">Zendesk</a>) put within easier reach.</p><h3>Chirp Version 3 is available now.</h3><p>You can download a free trial of our version 3 SDK for Android, iOS, JavaScript and Python right now from <a href="http://admin.chirp.io/"><strong>admin.chirp.io</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50da1ef6e8da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chirp-io/a-new-standard-for-data-over-sound-50da1ef6e8da">A new standard for Data Over Sound</a> was originally published in <a href="https://medium.com/chirp-io">Chirp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sure, it’s fast — but…]]></title>
            <link>https://medium.com/chirp-io/sure-its-fast-but-acc00a78ddf?source=rss-3403c7c9e640------2</link>
            <guid isPermaLink="false">https://medium.com/p/acc00a78ddf</guid>
            <category><![CDATA[sound]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[audio]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[James Nesfield]]></dc:creator>
            <pubDate>Thu, 26 Oct 2017 19:29:30 GMT</pubDate>
            <atom:updated>2017-10-26T19:45:57.717Z</atom:updated>
            <content:encoded><![CDATA[<h3>Sure, it’s fast — but…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/474/1*nuFNKYRRMWC4tUsRZo-1XQ.jpeg" /><figcaption>Fast, but somewhat compromised in other areas</figcaption></figure><p>We put together a quick video below demonstrating the world’s first 1000<strong>+</strong> bits per second data over audio solution. We picked a random number, 1111.1 bits per second in this instance, because our technology has always had the capability of doing so. But for us, when developing customised solutions, it’s really all about understanding our clientele’s specific needs.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F240038812&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F240038812&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F663214482_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/07fe24af56e69665f0747969c8b29cce/href">https://medium.com/media/07fe24af56e69665f0747969c8b29cce/href</a></iframe><p>Chirp’s world class specialists are ready to tailor a solution to your product’s specific requirements whether it’s for payments, transport or nuclear reactors.</p><p>This is not a test. We are not in beta. Our technology is already live at mass global scale with partners you know. Activision, Creata, Netflix and EDF Nuclear Energy trust Chirp to reliably send data in their most demanding applications.</p><p>After all, there’s more to a successful product than speed alone.</p><p>Find out more at <a href="http://dataoversound.com/">dataoversound.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acc00a78ddf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chirp-io/sure-its-fast-but-acc00a78ddf">Sure, it’s fast — but…</a> was originally published in <a href="https://medium.com/chirp-io">Chirp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[String Theory]]></title>
            <link>https://medium.com/chirp-io/papercups-and-protocols-727f6197e8e8?source=rss-3403c7c9e640------2</link>
            <guid isPermaLink="false">https://medium.com/p/727f6197e8e8</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[sound]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[James Nesfield]]></dc:creator>
            <pubDate>Tue, 28 Mar 2017 17:46:37 GMT</pubDate>
            <atom:updated>2017-04-24T09:56:43.374Z</atom:updated>
            <content:encoded><![CDATA[<p>Chirp produces a suite of software products dedicated to sending data acoustically, broadcast over the air.</p><p>Our standard ‘off-the-shelf’ products all adhere to the same <em>protocols</em>— the set of acoustic and data encoding parameters which define a chirp and allow devices to both send and receive data in an interoperable way. The data encoding parameters include properties such as the amount of data and error correction that should be included in each transmission, while the acoustic parameters describe properties such as the constituent pitches and duration of the chirp.</p><h4>Our standard audio protocols…</h4><p>Here is an example of a standard chirp — the sound you hear represents an identifier which tells the listening iPhone which picture to display.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F173647519&amp;src_secure=1&amp;url=https%3A%2F%2Fvimeo.com%2F173647519&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F580080773_1280x720.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/b6c21fe49b0f9923c74adf64ab33c753/href">https://medium.com/media/b6c21fe49b0f9923c74adf64ab33c753/href</a></iframe><p>The sound you hear in the video above can be interpreted by any device or application which has Chirp technology embedded. It contains 50 bits of information and is incredibly robust against background noise. Whilst the protocol in the above video is audible, we also offer an inaudible ultrasonic protocol which sends 32 bits of information.</p><p>Our standard audible protocol contains frequencies in the range of about 2kHz and 11kHz — this range was chosen because it works particularly well being broadcast and received by consumer electronic audio hardware, such as the transducers we have in our mobile phones — as these are optimised for the transmission of music and the human voice which occupy the same frequency ranges. Positioning our standard audible protocol in the centre of this range allows us to take advantage of these broad performance gains and optimisations for free.</p><p>These two ‘standard’ protocols, audible and inaudible, allow our partners to quickly develop products or services which take advantage of their interoperability and broad interaction capabilities. The data encoding and acoustic parameters for our standard protocols were chosen to maximise the flexibility of their use across a very wide range of use cases, so we chose configurations which suit many different applications.</p><h4>Cup &amp; String Telco International</h4><p>Typically, once a product has integrated the standard protocol and proved the use case using our technology, there remains an opportunity to optimise the protocol characteristics to better fit specific requirements of a particular project.</p><p>This is the point at which we work alongside a partner to develop data payload and acoustic characteristics which are tailored to their product’s unique demands. For example, we have worked with partners who needed to send much more than the 50 bit payload capability of our standard SDKs, as well as those whose use case prioritised the shortest overall chirp duration — some almost 10 times shorter than our standard protocol.</p><p>To illustrate our capabilities in this area of customising protocol to fit extreme use cases, we set ourselves a challenge via an imagined partner: ‘Cup &amp; String Telco International’ - producers of the world’s most lightweight communication equipment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eWR9BOU2sbuJEmEnzb13Lg.jpeg" /><figcaption>Our ‘test’ equipment — the Cup &amp; String Telco International v1.0</figcaption></figure><p>However, the Cup &amp; String use case is no normal scenario for audio transmission — it represents a very restricted channel in terms of its frequency bandwidth and signal-to-noise ratio. As you might be able to remember from playing with a similar setup at some point, the audio coming from the cup at the receiver’s end sounds very ‘muffled’ or ‘dull’ — i.e. it sounds like the person on the other end is talking through a barrier such as a pillow or similar.</p><p>This dullness is caused directly by the loss of high frequencies during transmission — they are less efficient when traveling down the string, and also lose significantly more energy during the transition between air and solid at each end of the apparatus.</p><p>So, how can we optimise our protocol for transmission down the Cup &amp; String Telco International v1.0? The first thing we do is design a protocol which does not include any higher frequencies. Our standard audio protocol’s lowest frequency is 1760Hz — the Cup Audio Protocol’s <em>highest</em> frequency is around 1000Hz.</p><p>We also lengthened the duration of each note to help with note detection in such a noisy channel, and reduced the amount of data in each chirp in order to keep the overall length of the chirp sensible.</p><p>The spectrogram below shows both protocols side by side— the standard protocol is above (with its higher frequencies), the Cup Audio Protocol underneath (with its lower frequencies and longer notes).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cGtVCzC1xhT0h1nyFouZPQ.png" /></figure><h4>Did it work?</h4><p>It worked exceedingly well, even with these basic initial customisations (lower frequencies, longer notes).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*69ukoOtPVHzSS6dVLFgxOw.gif" /></figure><p>As a quick test, we took the equipment outside with a simple listening app which flashed the screen green when it heard a chirp using the Cup Audio Protocol.</p><p>We started at a modest volume that could be heard by the person clearly at the sending position (it’s likely that at this initial level there was some significant ‘bleed’ — a direct path to the receiver without going through the string). Then we started turning down the volume…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/301/1*4Ws6DKkOf-LEvHG_N5cwFw.gif" /><figcaption>green flash means ‘received!’</figcaption></figure><p>In the end, we successfully got to the point where data could be transmitted reliably at volume levels low enough that the people holding the cups could not hear any of the audio being broadcast from the sending device.</p><p>We also got quite a lot of strange looks from passersby.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F208360214&amp;src_secure=1&amp;url=https%3A%2F%2Fvimeo.com%2F208360214&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F623656335_1280x720.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/fa60827575a30d5cc4b086eb86552f8b/href">https://medium.com/media/fa60827575a30d5cc4b086eb86552f8b/href</a></iframe><h4>Beyond cups &amp; string</h4><p>This test was obviously a fun experiment for us, but it illustrates the process of optimisation that we regularly go through with our partners as they integrate Chirp’s technology across a wide variety of use cases. The adaptations mentioned here for this particular experiment are only the beginning of a very sophisticated set of tools which allows us to optimise precisely in even the most challenging acoustic environments.</p><p>Because of the diversity of application areas where our technology is being applied, we often work with our partners to design custom audio protocols bespoke to their product’s requirements.</p><p>Often our standard protocols allow engineers to develop proof-of-concept Chirp integrations using our ‘off-the-shelf’ SDKs, which then illustrates the opportunity for further performance improvements. These gains are then achieved working in collaboration with each partner to develop a custom protocol with its acoustics and data encoding parameters tuned precisely for their particular application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DzCmnOVsanRFdfDCCxLZQA.jpeg" /></figure><p>If you’d like more information about our standard products, or the possibilities with respect to custom Chirp audio protocols for your application, product or service — please <a href="https://www.chirp.io/?utm_medium=referral&amp;utm_source=medium.com&amp;utm_campaign=stringtheory-blog-post">get in touch with us</a>.</p><p>You can also follow <a href="http://blog.chirp.io/">our blog</a> to hear more about Chirp and sound technology.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=727f6197e8e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chirp-io/papercups-and-protocols-727f6197e8e8">String Theory</a> was originally published in <a href="https://medium.com/chirp-io">Chirp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What we mean by ‘audible’, ‘inaudible’ and ‘ultrasonic’]]></title>
            <link>https://medium.com/chirp-io/what-we-mean-by-audible-inaudible-and-ultrasonic-36c59560d7fc?source=rss-3403c7c9e640------2</link>
            <guid isPermaLink="false">https://medium.com/p/36c59560d7fc</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ultrasound]]></category>
            <category><![CDATA[sound]]></category>
            <category><![CDATA[science]]></category>
            <dc:creator><![CDATA[James Nesfield]]></dc:creator>
            <pubDate>Thu, 02 Feb 2017 14:36:39 GMT</pubDate>
            <atom:updated>2017-02-02T14:38:54.506Z</atom:updated>
            <content:encoded><![CDATA[<p>There is a lot of misinformation around about what the terms ‘audible’, ‘inaudible’ and ‘ultrasound’ mean. This post aims to give readers a better understanding of each, the reasons behind some of the confusion, and why the differences here matter.</p><h4>‘Audible’</h4><p>Simply put, the term ‘audible’ means ‘able to be heard’. This may seem blindingly obvious, but as we’ll see — it sets the scene for more subtle distinctions later in this discussion.</p><p>When we say that we are ‘able to hear’ something, we are making a statement about several different characteristics of a particular sound and its acoustic context. Each of these qualities must be within certain ranges in order for the human auditory system to detect a sound.</p><p>A couple of the most significant qualities affecting human hearing of particular sounds :</p><ul><li>The type and amount of any other sounds playing which are competing to be heard</li><li>How loud it is</li><li>The frequencies it contains (is it very high or very low pitch?)</li></ul><p>Let’s assume here that the first one is controlled by us — that we have quiet conditions for listening, so that the main remaining 2 factors become a sound’s loudness and its frequency composition.</p><p>In terms of frequencies, the common definition for the human audible frequency range is 20Hz and 20kHz [1] — however our ear’s sensitivity to sound varies dramatically over this range.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/881/1*s_33i7CFjc-4Q7_Da9ST2Q.png" /><figcaption><a href="https://en.wikipedia.org/wiki/File:Lindos1.svg">https://en.wikipedia.org/wiki/File:Lindos1.svg</a></figcaption></figure><p>Our ear is most sensitive between the ranges of ~2kHz and ~5kHz (see the dip in the graph above). This range of particular sensitivity corresponds directly to the main frequency components of human speech.</p><p>In our most sensitive frequency regions we are able to perceive sound pressure levels of under 20μPa — this corresponds to the vibrating air molecules <a href="https://blog.chirp.io/what-is-sound-130a93d6955f#.5y5csues5">which together constitute audible sounds</a> over incredibly small distances, on the order of 1/100 <em>of a millionth </em>of a centimetre, or 1/10th the diameter of a hydrogen molecule [2].</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*hHhPACitWanPQhL0tv7-Pg.png" /><figcaption><a href="https://en.wikipedia.org/wiki/File:Ath-byage.png">https://en.wikipedia.org/wiki/File:Ath-byage.png</a></figcaption></figure><p>This sensitivity changes not only with frequency of the sound, but with the age of the listener — with younger folk having a much greater sensitivity to higher frequency sounds. There are many different ways a person can lose hearing sensitivity, most commonly this happens as a natural process of ageing as we (unlike frogs &amp; fish[3]) gradually loose the tiny hair cells in the inner ear (<a href="https://en.wikipedia.org/wiki/Presbycusis">presbycusis</a>) which translate vibration to electrical impulses finally interpreted by the brain.</p><h4>‘Inaudible’</h4><p>Inaudible then — ‘unable to be heard’.</p><p>There may be multiple potential reasons for this — a sound could be inaudible over the background noise level (i.e. ‘masked’), could be outside the human audible frequency range, or be too quiet to be heard even in ideal listening conditions.</p><p>Again we must be careful to differentiate between academic, general definitions of whether a sound is audible or not, and the ability of single individuals to detect these sounds- the definition of frequencies inside the 20Hz-20kHz range being ‘audible’ does not mean that all frequencies within this range are accessible to everyone.</p><h4>‘Ultrasound’</h4><p>When we say that a sound is ultrasonic, or lies in the ultrasonic range, we generally mean that it contains only frequencies which are above the upper limit of the human audible frequency range - defined generally as frequencies above 20kHz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*ACT780YNFKJLenUuPMbJ2Q.png" /></figure><p>‘Ultrasonic’ then, is a sound rendered inaudible specifically due to its frequency content.</p><p>Although the definition of ultrasound covers the majority of the population, there are those (especially younger people) who will be able to hear frequencies at or above the textbook definition of 20kHz.</p><p><em>For some individuals</em> then ‘ultrasonic’ (as most standardly defined) does not <em>necessarily</em> mean ‘inaudible’.</p><p>Equally, for many (especially older) individuals, higher frequency sounds will be ‘inaudible’ though they lie well <em>below</em> the 20kHz limit.</p><h3>Audibility and data-over-sound</h3><p>Chirp and most other companies offering ‘inaudible’ data over sound technologies use a frequency range at the very upper limit of human hearing, but below the standard 20kHz definition of ‘ultrasound’, typically in the 18–19kHz range.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*XcQBUnFoAYLJh1OwVbpiTw.png" /></figure><p>Whilst this lies above the audible range for most of us individual — especially if you are older — it is not, with respect to standardised definitions, <em>ultrasonic.</em></p><p>In the next post of this series, we will look at the various affordances and appropriate use cases for both audible and inaudible sound as a means of transmitting data.</p><ol><li>Rosen, Stuart (2011). <em>Signals and Systems for Speech and Hearing</em> (2nd ed.). BRILL. p. 163</li><li>Everest, F. Alton. <em>The Master Handbook Of Acoustics</em>. 1st ed. New York: McGraw-Hill, 2001. Print.</li><li>Horowitz, Seth S. <em>The Universal Sense</em>. 1st ed. New York: Bloomsbury, 2012. Print. p.91</li></ol><p>For more information on Chirp’s data-over-sound technology solutions, please visit <a href="http://www.chirp.io/">Chirp.io</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36c59560d7fc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chirp-io/what-we-mean-by-audible-inaudible-and-ultrasonic-36c59560d7fc">What we mean by ‘audible’, ‘inaudible’ and ‘ultrasonic’</a> was originally published in <a href="https://medium.com/chirp-io">Chirp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>