Files to be included with your application

Important note about installed version

This section of the documentation applies to the full purchased version only: the trial version of the component comes with an internal protection schema against fraudulent uses which will block most functionalities when the component is redistributed outside of the development machine where the trial version was originally installed through the provided setup program.

Files that you need to redistribute with your application depend upon the platform target:

•	If compiling for "Any CPU"

- the x86 version of the the control's binary ASOEDMMS.OCX

- the x86 version of the multimedia engine AdjMmsEng.dll

- the x64 version of the the control's binary ASOEDMMS64.OCX

- the x64 version of the multimedia engine AdjMmsEng64.dll

•	If compiling specifically for x86

- the x86 version of the the control's binary ASOEDMMS.OCX

- the x86 version of the multimedia engine AdjMmsEng.dll

•	If compiling specifically for x64

- the x64 version of the the control's binary ASOEDMMS64.OCX

- the x64 version of the multimedia engine AdjMmsEng64.dll

You can find redistributable files mentioned above inside the folder in which you installed Active Sound Editor (default "\Program files\MultiMedia Soft\Active Sound Editor\Redist").

Important note about the folder chosen for installing our files

In order to avoid the "DLL Hell" problem, it's strongly recommended that you install the mentioned files into the same folder in which you will install the EXE of your container application on the target system and not inside the Windows\System32 or Windows\SysWOW64 folders.

In order for the control to register and work correctly on the target system, the following is a summary of the Microsoft Windows libraries that must be available on the target system:

WINMM.DLL

MSACM32.DLL

OLEAUT32.DLL

OLEPRO32.DLL

DirectX version 9.0c or higher should be available as well. DirectX redistributable modules can be obtained from the Microsoft web site.

Special notes

•

If you need dealing with Windows Media Audio files (WMA, ASF, WMV, etc.), the Microsoft Windows Media Format modules must already be installed on the target PC: for Windows XP and previous versions the Windows Media Format modules can be installed using the redistribution setup package (wmfdist.exe) provided by Microsoft. For Windows Vista and later versions there is the need to install the Microsoft's Windows Media Player application (which is usually installed by default).

•

For encoding of MP3 files, the Lame encoder (Lame.exe) must be available on the target system: starting from version 8 of the component this requirement is no more needed until you make use of the default internal MP3 encoder. See the EnableInternalEncoders method for details about disabling the default internal encoders and continue to rely upon external encoders.

•

For encoding of , OGG Vorbis filesthe OggEnc encoder (OggEnc.exe) must be available on the target system: starting from version 8 of the component this requirement is no more needed until you make use of the default internal OGG Vorbis encoder. See the EnableInternalEncoders method for details about disabling the default internal encoders and continue to rely upon external encoders.

•

For encoding of OPUS files, the OPUS encoder (OpusEnc.exe) must be available on the target system: starting from version 8 of the component this requirement is no more needed until you make use of the default internal Opus encoder. See the EnableInternalEncoders method for details about disabling the default internal encoders and continue to rely upon external encoders.

•	For encoding of MP2 files, the TwoLame encoder (TwoLame.exe) must be available on the target system.

•	For encoding of AAC and MP4 files, the Faac encoder (Faac.exe) must be available on the target system.

•	For encoding of AAC+ files, the FdkAac encoder (FdkAac.exe) must be available on the target system.

•

If you are using the Microsoft Visual Studio "Package and Deployment Wizard" for packaging your applications, be sure that Oleaut32.dll and Olepro32.dll libraries are taken from your Windows\System32 directory: by default this wizard makes use of an outdated version of the mentioned libraries that could cause failures while registering any ActiveX control on the target system.