Embed your mobile app or device with NeoSpeech’s natural sounding text-to-speech voices.
This blog is part 3 of a 7-part blog series highlighting each of NeoSpeech’s text-to-speech solutions
Giving your smart phone application or mobile device a voice shouldn’t be difficult, which is why we made it easy.
NeoSpeech’s VoiceText Embedded SDK package was specifically designed with embedded operating systems in mind. Mobile apps and embedded devices run on very specific operating systems, have limited storage space, and can have a low amount of processing power. Finding a high quality text-to-speech engine that can be compatible with an embedded product’s specifications has long been a challenge for developers.
Fortunately, our Embedded SDK package is the solution that easily overcomes this challenge.
So who is this solution for? What does it come with? And how does it work? Let’s take a look at everything you should know about our VoiceText Embedded SDK package.
What is it?
In terms of what the package is composed it, our Embedded package is nearly identical to our Engine package. When you purchase our VoiceText Embedded SDK, we send you the complete text-to-speech engine and SDK.
Text-to-Speech Engine
This is what makes the magic happen! It’s what gives your product a voice! The text-to-speech engine, or TTS engine for short, is able to analyze inputted text and convert it into speech. The method of how it puts together the speech depends on the type of engine you get.
Either way, with the TTS engine in hand, you’ll be able to convert any amount of text into high quality speech instantly!
SDK
The software development kit (SDK) is what will enable you to easily integrate the TTS engine into your custom application or device. An SDK is defined as a set of tools that a software developer uses to help build applications.
So if integrating a powerful TTS engine into an embedded device sounds daunting, don’t sweat it. Our SDK (which includes a very informative manual on how to use it) makes the whole process simple and straight forward.
Who is this solution for?
If we had to sum it up in one sentence, we’d say that the VoiceText Embedded SDK package is for people wanting to give their embedded device or application a voice by hosting the TTS engine locally.
First, let’s define what an embedded device and an application are.
An embedded device is a device that contains a special computing system for a dedicated purpose. These aren’t general-purpose computers like your laptop that can do anything. Instead, embedded devices usually have one or a few specific purposes.
An example is a blood glucose monitor. This is a device that tests the levels of glucose in your blood. People suffering from diabetes often use blood glucose monitors to make sure their blood-sugar levels aren’t too low or too high.
Blood glucose monitors have a specific purpose. They test blood samples and display back the results. They aren’t general-purpose computers that can perform most common tasks. They are embedded devices. Other examples include ATMs, DVD players, smart home devices, and a GPS device.
An application, at least in this context, refers to an application for a mobile device. If you have a smartphone, then you probably have dozens of apps downloaded onto your device. Our VoiceText Embedded SDK is perfect for integrating text-to-speech into smartphone apps.
Now that you know what we mean by “embedded device or application”, you should have a pretty good idea if the Embedded SDK package is right for you. Is the product you’re developing going to be an embedded device? Or is it going to be an app for a smartphone? If you answered yes to either of these two questions, then our Embedded SDK package is probably right for you.
Note that in our one sentence summary of who the Embedded SDK package is for, we mentioned that it’s for those who want to host their TTS engine locally. Hosting the TTS engine locally means that the engine is located and stored within the device or app itself. The other option would be host your TTS engine either in your own server or through NeoSpeech’s cloud.
How does NeoSpeech optimize it for my needs?
As mentioned above, embedded devices and applications have very unique operating systems, specifications, and storage space limitations. Therefore, we at NeoSpeech make sure to optimize our Embedded SDK package to fit your needs.
Our Embedded SDK package works with several operating systems, including iOS, Android, Embedded Linux, WinCE, and Windows Mobile. We can also custom port our engine to your specific operating system if we don’t already support it.
You can also choose your desired sampling rate (which affects sound quality) and footprint size. Our embedded TTS engines can range anywhere from 8MB to 900MB. Which footprint size and sampling rate you need depends on your device specifications and the application for which the TTS engine is being used for.
How does it work?
Here is a look at how you can use our VoiceText Embedded SDK package to integrate text-to-speech into your embedded device or app.
Purchasing process
There are no mind-bending hoops you have to jump through to get your hands on our Embedded SDK package. Just get in touch with our Sales Team. We’ll take it from there and make sure we get all the information we need so we optimize the package to your needs.
Installation
After purchasing the package, we’ll send you the complete TTS engine and SDK for download. You or your developer will need to download these files on the computer you’re using to develop your product.
Verification
Before you can do anything, you have to verify your software. In the same email we send you with the download files, we’ll send you a license key that’ll activate and unlock your TTS engine.
Integration
Here’s where the fun begins. At this point it’s time to integrate the TTS engine into your custom application or device.
To get started, just take a look at the SDK manual that comes with the SDK package. In there you’ll find clear, easy to follow, step-by-step directions on what to do.
Basically, you’ll just need to copy the TTS engine and a few files from the SDK into your device or application. Then, all you need to do is write out the commands that’ll be the blueprint that tells your product how and when to use the TTS engine to create speech. That’s it!
Our SDK manual will go over all the commands you could use and how they work. With that in hand, you’ll give your embedded product an engaging, natural sounding voice in no time.
See? We told you it was easy.
That’s the overview of NeoSpeech’s VoiceText Embedded SDK solution! If you’ve decided that this is the solution for you, click the button below to get started!
I want the VoiceText Embedded package!
Be sure to check out the other blogs in this series to learn more about our other solutions. And if you need help figuring out which solution is right for you, read our free eBook on the matter.
Here’s the list of blogs in this series covering NeoSpeech’s solutions:
- VoiceText TTS Engine SDK
- VoiceText TTS Server SDK
- VoiceText Embedded SDK
- VoiceText Editor (VT Editor)
- VoiceText SAPI
- Web Service (cloud-based solution)
- TTS On Demand (cloud-based solution)
Learn more about NeoSpeech’s text-to-speech
Want to learn more about all the ways Text-to-Speech can be used? Visit our Text-to-Speech Areas of Application page. And check out our Text-to-Speech Products page to find the right package for any device or application.
If you’re interested in integrating Text-to-Speech technology into your product, please fill out our short Sales Inquiry form and we’ll get you all the information and tools you need.
Related Articles
New eBook, “Which Text-to-Speech Product Is Right For You?” released
Check out NeoSpeech’s Interactive Online Text-to-Speech Demo!
What is Text-to-Speech and How Does It Work?
Don’t forget to follow us on LinkedIn, Facebook, Google+, and Twitter!
The post NeoSpeech’s Text-to-Speech Embedded SDK Overview appeared first on Text2Speech Blog.