home *** CD-ROM | disk | FTP | other *** search
-
- Ozapell Music Studio 2
- Software Development Kit
-
- Programmers are free to develop and distribute their own filter plug-ins
- for use with Ozapell Music Studio 2.
-
- The steps needed to develop a filter plug-in include:
-
- 1. Create the DLL (the framework of which is given in Filter.dpr).
-
- 2. Package the DLL using OMFilter.exe. This will prompt you for a
- destination for your filter (OMF file) and it should go in the
- \filters\ directory under the directory where OMS2 was installed.
- The new file will be visible to OMS2 and it will provide it with the basic
- information it needs to use it.
-
- Notes about OMFilter.exe:
-
- 1. DLL Location - Use the Browse button to find the DLL to package.
-
- 2. Output Location - Set this to the path of the Filters directory used
- by Ozapell Music Studio 2.
-
- 3. 8 Character Name - This name needs to be unique from other filters.
- It will be used as the file name of the *.omf file as well as the
- identifier used by the program for each filter.
-
- 4. 64 Character Name - Name displayed in the Filters Available box that
- the user will see.
-
- 5. 12 Character Version - The version will be displayed in the Filters
- Available box and will also be used in the update program to determine
- if a filter should be overwritten with a newer filter.
-
- 6. Page Filter, Track Filter, Beat Filter - Click the boxes to allow the
- program to use the filter for the appropriate components. Most filters
- can be used for all three.
-
- Important things to keep in mind:
-
- 1. Any subroutine that does nothing should not be exported in the DLL.
-
- 2. Data and DataDefault should be used to store user data. These are
- 256 byte blocks of memory and the filter should not attempt to
- exceed that limit.
-
- 3. Buffer points to an array defined as array[1..1764000,1..2] of LongInt
- in the main program. Although other compilers may reference this
- data differently (0..1763999, for example), filters should not exceed
- this limit. Also, remember that 1 is the left channel and 2 is the
- right channel.
-
- 4. The Buffer data is stored as a 32-bit signed integer instead
- of the standard 16-bit signed integer. This is useful when the amplitude
- of the wave being altered exceeds the 16-bit limit (-32768 or 32767).
- The Ozapell Page Volume Control or the Ozapell Basic Volume Control
- will normalize the amplitude after all other filters have been used.
-
- 5. The contents of the OMF file should not be modified as internal
- checking may indicate that the filter is corrupt.
-
- 6. Data is filled with 0's before having DataDefault copied to it. This
- important to keep in mind if new entries in Data are added later --
- the end user's projects will have the Data block as defined by the
- original version of your filter and you may need to check and handle
- the 0's that the new version will encounter.
-
- 7. If CPU intensive loops are used, be sure to occasionally allow Windows
- to handle messages. In Delphi, this is done with the routine
- Application.ProcessMessages.
-
- 8. To save the current user settings as the new default settings, simply
- copy the data in Data to DataDefault (in Delphi, DataDefault^:=Data^).
-
- Web site --> www.ozapell.com
-
- Further questions can be sent to --> support@ozapell.com
-
- An expanded SDK is planned for the future if enough people register
- the current version of OMS2.
-