Integration | Voice SDK
Please Note

We are only able to provide this service for Europe. For customers in the US, please visit:

www.olympusamerica.com

Voice SDK

 

This SDK is designed to develop an application to play DSS and DSS Pro files and read/write a header. The SDK consists of two components:

  • DSS/DSS Pro Decoder Filter API. DSS File Playback with the OLYMPUS DSS/DSS Pro SDK. This can be used to play DSS and DSS Pro files as well as an encrypted DSS Pro file. DSS and DSS Pro decoders use DirectShow Filter. Using an interface provided by DirectShow allows for a playback, filter chaining, and conversion into other formats. 
  • DSS Format API. DSS File Editing with the OLYMPUS DSS/DSS Pro SDK (Header Editing). The header part of a DSS file contains the following information related to Dictation and Transcription. This API can be used to obtain and update this data:
    • Readable information: Recording mode, recording date and time, end date and time, job number, etc.
    • Readable / Writeable information: Author ID, Typist ID, Process Word, Status Word, file attributes, priority level, priority, Index Mark, etc. The DSS Pro file can be encrypted and decrypted.

 

The Voice SDK consists of documentation for the functions exported by the DLLs included with the DSS Player Pro and DSS Player Standard software. Sample Visual C++ programs are included to demonstrate how to call these functions from your own application.

 

Operating Environment

  • Windows 2000
  • XP
  • Vista (32 and 64-bit editions are supported)
  • Windows 7


Development Environment

  • Visual Basic.NET
  • Visual C++
  • Visual C#
  • DirectX SDK

 


 

Who can apply for the SDK?  

Anyone can apply. We will however validate all retuned NDA's and the companies behind them. We will not typically issue SDK's to individuals or e-mail addresses such as generic pop accounts such as hotmail / gmail etc.  

How can I apply for the SDK?  

  • Simply visit www.opdsupport.com/integration
  • Complete the form
  • Follow the instructions to download the NDA
  • Return the completed NDA to Olympus as per the instructions on the website.

What if I need technical support with the Olympus SDK and my application?  

Due to the nature of SDK's, it is not always possible to provide in-depth support. If you feel there is an error or omission in the Olympus SDK, please contact us we will research the issue. If you require technical assistance relating to the SDK and your application, Olympus may request or require a copy of your application and elements of your source code. Unless this can be provided it unlikely Olympus can provide assistance. Olympus cannot provide technical support for queries derived from lack of knowledge and / or development experience.

Which development environments are supported?  

  • Microsoft Visual Studio 2005
  • Microsoft Visual Studio 2010  

Which programming languages are supported?

  • C++
  • C#
  • VB.NET 

How do I know if my version of the IRP is current?  

The current version is 2.1

How do I get updates if my version is out of date?

If you originally registered at this website then updates will automatically be delivered to you.

Is the DSS file specification included in the SDK?  

No. The DSS file is a proprietary format and the specification is not available. The SDK includes functions for converting DSS files to WAV and for retrieving information from the DSS file header.  

Can I control the voice recorder using the SDK?

Yes. The SDK includes functions for controlling the voice recorders including start and stop recording, erase files and upload/download files.

Can I open DSS files from other vendors?  

Yes. The SDK can open and convert DSS files from other vendors. However, vendor specific header information cannot be displayed.

What if we wish to support legacy devices which are not HID compliant?  

Unfortunately due to the age of these devices Olympus no longer supports these products (please see the device table for support information). However should you wish to support these devices the Device SDK should contain all the components required.

What is a merge module and why is it used?

Merge modules are basically a standard package to deliver Windows installer components (code, files and other resources); in one compound file. For example our Directrec merge module contains the following:

This greatly benefits the integrators as the can simply import the merge module into their installer. During their software installation our merge module will install the required components to use our devices.