ActiveX version (asrecmms.ocx and asrecmms64.dll) 7.0.2.0 (March 26, 2015)
Multimedia engine version (AdjMmsEng.dll and AdjMmsEng64.dll) 11.2.0.9 (August 2, 2015)

PRODUCT HISTORY

Full product history available inside the online documentation.

Fixed builds can be downloaded using the same link, username and password received after purchasing the product: if you should have lost them or if they shouldn't work anymore, please, contact our Technical support.

VERY IMPORTANT: Before proceeding with the installation of updated versions, don't forget to close all of the running applications and to UNINSTALL the existing version: missing this step could prevent the new version to run correctly on your development PC.

Fixed Bugs (since version 7.0)

• Loading certain types of sound files in WMA format may cause the application to hang.
• The call to the StartFromWasapiLoopbackDevice always returns a ERR_INVALID_DRIVER error.
• When starting a recording session through the StartFromWasapiMixer method, the embedded Spectrum object reports value peaks lower than normal.
• When a recording session is paused, a call to the Spectrum.Resize method has no effect.
• The SpectrumEnh object may report wrong values when the recording is being performed from an ASIO or a Wasapi device.
• When calling the RecordedSound.TrimSilence method on the same sound file twice, the resulting sound may appear empty.
• When the InitDriversType method of Audio DJ Studio or Audio Sound Recorder enables the usage of both DirectSound and ASIO devices, the waveform scroller may not display the current position correctly.
• When no output device is installed or all output devices have been disabled, exiting the application may raise an exception.
• The MixerVolumeGet and MixerMuteGet methods don't return the requested value inside the provided parameter but inside the return value which should instead contain an eventual error code.
• The LoadSoundFromRecordingSession method may not work correctly if the recording system was stored inside a memory buffer instead of an output file on disk.
• Visual feedbacks may sometime not work and the VUMeterValueChange event could sometime be missing.