The Race for Digital Music Standardization and Adoption
The music industry is at a technological crossroad. One of the biggest challenges for the music industry is accurate tracking of songs that are streamed or downloaded; streamlining the distribution of the music; and improving how musicians, writers, and owners are compensated.
What if artists, record companies, producers, and publishers had the ability to read minds? Well, social listening and social intelligence technology have made it easier to discern and track what people are thinking and saying than any other time in history. Now that almost everyone posts almost everything on social media, review sites, forums, and blogs, those opinions can be analyzed and tracked. The ability to extract insights from social data is a practice that is being widely adopted by organizations across the world, and the music industry is ready for innovation in this important growing category.
The digital evolution has had a massive and continuing influence on the new music technology ecosystem, including the plethora of startups entering the space. But let’s face it, just like music artists, not every new company will make it big - and rarely is there only one reason for a startup’s failure. So what do music technology startups need to know to increase their chances of success?
Greg Abbott, Senior VP of Travel and Hospitality at the global technology consultancy DataArt, was invited to participate in the travel survey for Travel Expert Index organized by Sabre.
Streaming, downloading, publishing, copyright laws, piracy, commissions, royalties, breakage, indie labels – the diverging complexities of the current music industry ecosystem and where the money is going continues to be the hot topic of conversation these days. The big question on everyone’s mind is what can be done to instill trust, confidence and ensure that music payments make it to their rightful owners?
What is RE?
Requirements Engineering (RE) can be summarized as a set of activities that ensures a team is building the right product. In the field of Software Engineering, hence, it seeks the correct and suitablesoftware deliverable.
Now, what do correct and adequate mean? Correct is a deliverable that meets stakeholder expectations, i.e. that it realizes their vision of the product, while suitable relates to whether it is fit for purpose.
IoT technologies have become a natural part of our life. And therefore the number of IoT protocols has grown exponentially. Device manufacturers (e.g. wearables, sensors, or temperature / light / environment controllers) use their own protocols for communication and cloud enablement. The cloud infrastructure can also use custom protocols of a higher level to receive device state updates and management information.
Some platforms use low-level protocols (e.g. COAP) to interact with devices and MQTT to communicate with a central hub. Others use their own standards, built upon HTTP or WebSockets. Central hubs in turn can use a variety of protocols and methods for marshalling data. And imagine the mashup of all those protocols to connect to external services.
The DeviceHive project development team has explored the possibility of integrating the DeviceHive data platform with SAP Hana DB. DeviceHive allows third party IoT device developers to concentrate on business tasks and the distinctive features of a project by shifting the data and device management to the platform. SAP Hana DB provides analytical tools integrated with data storage.
This approach can be used as a reference architecture solution based on devices that use Ubuntu Core. In our example, the devices collect data from the sensors and transmit it to the cloud for further analysis.
The DeviceHive platform allows us to collect data sent by devices in various ways. One of the most convenient ways that is available immediately after server installation is to use the data stream in an Apache Kafka server. The data flow available from Kafka topics contains device notifications. Aggregation and data analysis received from the sensors on the fly makes it possible to create a real-time monitoring system.
The DeviceHive team has released a new version of their gateway for Android N. DeviceHive Android Gateway for Bluetooth Low Energy devices makes it possible to connect multiple Bluetooth Low Energy devices to DeviceHive IoT clouds through a single Android device. Now it’s possible to connect sensors, buttons, indicators, wearables, and any other BLE devices to prototype solutions even faster.
All that’s needed is to start the gateway, connect it to the device, and send a command (or subscribe to sensor data notifications).
Here is a presentation showing common use cases for the DeviceHive Gateway on Android.
This quick tutorial will help to start prototyping the solutions faster.