 |
|
|
|
|
|
Yamaha realises the importance of computer based music production and recognises that the integration of its hardware products into this environment is the ultimate goal and dream for many users. To provide seamless integration requires a set of features including control surfaces, edit views (such as enhanced list views), and other MIDI processing tools.
“Wouldn’t it be great if the synth editors for your entire studio could run seamlessly inside your sequencer; so you don’t have to open up a second application, “ALT+TAB” between programs, or tie yourself in knots with multiclient MIDI links?”
“Imagine a world where the mind numbing MIDI event list, containing everything from automation data to synthesiser edit parameters could be translated from meaningless bytes into plain and simple language that you can understand”
“Imagine being able to take your favourite edit view, such as a drum or list editor, from one sequencer application to another. Or the capability to easily add new views or editors to applications that previously had none”. “Open Plug-In Technology” is designed to meet these needs. |
|
Whereas other plug in formats cater for audio processing and software synthesiser, “Open Plug-In Technology” is targeted at providing complete MIDI solutions in the computer environment. The architecture allows developers to provide custom plugins for direct support of new hardware and/or MIDI extensions; which will work in an integrated way with all participating software vendor products. This opens the possibility for a totally modular sequencer environment.
Yamaha are also developing a wide range of plug in tools to enhance the functionality of “Open Plug In Technology” enabled products. These will include many of Yamahas existing synthesisers, soundcards and tone generators, as well as pro audio equipment and also new and exciting computer related hardware products to come.
Yamaha have worked in cooperation with sequencer companies around the world, discussing the specification, and working to create a system that is beneficial to everyone concerned; from the hardware manufacturers, to the software companies, and most importantly to the end users - who just want things to work in a seamless manner.
For each new product, a single plugin can be developed which operates ‘out of the box’ in all “Open Plug-In technology” compatible sequencer environments. Thus reducing multiplicity of support and allowing a common interface to be presented throughout. Hardware companies will know exactly what their software front end will look like in all enabled applications. So no matter if the end user is working on a project in one application, and then moves to a studio where he is using another, the same level of functionality will be presented throughout. |
|
|
 |
|
|
|
|
 |
HOW IT WORKS |
|
|
|
|
|
|
“Open Plug-In Technology” is based upon the Microsoft Component Object Model (COM). This technology is well suited to plugins as it defines the interface at the binary level, avoiding problems of technology transfers and/or manufacturer specific libraries. The architecture supports specification/interface expansion whilst overcoming versioning problems. Thus allowing new features to be added without breaking old ones. COM is an established and proven technology, used within OLE, Active X and DirectX. |
|
Utilising “Open Plug-In Technology”, the client application exposes its sequencing features to MIDI plugins in a controlled manner. Such features may include: access to MIDI ports, track/event data, realtime/offline MIDI queues, timing information, transport features, UI hosting and file storage. Utilising these features, MIDI plugins can provide a wide variety of offline and realtime functions. The range of applications is only limited by the developers’ imagination. |
|
|
|
|
|
|
|
|
IMPLEMENTING "OPEN PLUG-IN TECHNOLOGY" |
|
|
|
OPEN PLUG-IN TECHNOLOGY PANELS |
|
|
|
|
Client application developers are free to implement as much or as little of the specification as meets their product requirements and timescales. However to simplify the users understanding of the clients capabilities, the following levels of “Open Plug-In Technology” integration have been defined. |
|
 |
|
|
|
Open Plug-In Technology Panels |
|
|
|
|
|
|
|
Provides support for running software control surfaces that transmit data via the clients MIDI ports. e.g. hardware synth editors. |
|
|
|
|
|
|
|
|
OPEN PLUG-IN TECHNOLOGY PROCESSORS |
|
|
|
OPEN PLUG-IN TECHNOLOGY VIEWS |
|
|
|
|
 |
|
 |
|
|
Open Plug-In Technology Processors |
|
Open Plug-In Technology Views |
|
|
|
Provides support for real-time and offline MIDI queues e.g. for the implementation of MIDI effect processors, arpeggiator functions, and realtime panel automation |
|
Provides support for client track/event access. Typically allows sophisticated MIDI edit views to be created (e.g. List editors, Auto Accompaniment etc). |
|
|
|
|
|
|
|
|
YAMAHA ARE PLEASED TO ANNOUNCE THE FOLLOWING COMPANIES ARE ALSO SUPPORTING OPT WITH CURRENT OR FUTURE PRODUCTS |
|
|
|
|
Cakewalk Music Software http://www.cakewalk.com
Sonic Foundry http://www.sonicfoundry.com
MusicLab http://www.musiclab.com
MusicLab is the manufacturer of wOPT compatible MIDI FX plug-ins
|
|
PDF version of the OPT specification
Please note: Redistribution or upload of all or a part of the PDF file is prohibited.
Acrobat PDF file (1,852KB)
Free SDK for OPT (Windows 9.x/ME/2K/XP version)
A full SDK containing all of the C++ components required to develop OPT compatible applications. This download also contains the full PDF document shown above.
SDK for OPT (1,882KB) |
|
