Active DJ Studio | MultiMedia Soft

Patches and Upgrades

ActiveX version (amp3dj.ocx) 6.1.1.1 (December 5, 2012)
Multimedia engine version (AdjMmsEng.dll) 9.2.3.4 (October 19, 2012)

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 6.0)

If both the DJ Studio and the Recorder components are instanced inside the same application, the ResetEngine method could not perform the correct sequence of operations resulting in some occasional instability.
If a VST effect is enabled through the VST.Enable method on a player having the loaded sound in paused or stopped state, the player starts playback in error.
In rare situations, after having loaded a VST effect and after having applied changes to parameters of the VST effect through provided methods of the VST object, when the VST editor is opened it doesn't reflect the changes on its user.
An exception may be raised if the VideoPlayer.Load or VideoPlayer.LoadForTempoChange methods are called passing an Internet URL which exceeds 256 characters.
In presence of a sound card driver developed by Realtek, after pausing playback through the PauseSound method and performing a rewind/forward operation through the RewindSound/ForwardSound methods, the call to the ResumeSound method will resume playback but no real sound could be heard from the speakers apart from a loud "click" at the beggining: although this is a bug inside Realtek drivers and not inside MultiMedia Soft code, we don't know when and if it will be fixed so we have internally developed a turnaround.
Video in WMV format are not recognized correctly.
The VideoPlayer.AudioDelaySet method doesn't work if no video clip is loaded.
When video files are loaded from a playlist, on certain systems there may be no audio output if the video player has not been set to work with an output window.
When loading files from a playlist, by default MP4 and WMV files should be loaded as video clips but, due to a bug, they are loaded as sound files so the related video track is not rendered.
DMO and equalizer settings are not maintained after calling the CloseSound method.
If a video clip fails to load through the VideoPlayer.LoadSync method because of an unsupported format, trying to load a new video clip of a supported format will in any case fail.
When the StopSound method is called after receiving the SoundDone event, playback may restart from the beginning.
In certain situations the PlayListAddItem method may return no error also if the insertion failed due to some external problem.
The call to the VideoPlayer.VideoWindowAdd method fails if the nUniqueID has the same value of a previous call to the same method in which the hWndTarget was related to a target window that has already been destroyed.
If the VideoPlayer.AudioRendererModeSet method has been called with nMode parameter set to AUDIO_RENDERER_MODE_DS_STANDARD and the player used for video playback has been attached to a VideoMixer, the loading of video clips may fail causing subsequent instabilities.
The VideoMixer.PlayerNormalizedRectSetIdeal method doesn't work correctly if no preview window has been added to the player.
If a video player is already attached to a video mixer, attempting to attach it to another video mixer without a detach to the previous one may result in a memory leak.
Calling the SeekSound method twice on a player attached to a stream mixer (or when ASIO drivers are enabled) and redirected to a DirectSound device, while the player is stopped, causes the next call to the PlaySound method to perform a playback of a few milliseconds then stop.
The default latency for players attached to a stream mixer (or when ASIO drivers are enabled) and redirected to a DirectSound device is 5000 ms instead of 500 ms.
No tag is detected with certain types of OGG vorbis files which don't have the header split in two Ogg pages.
When run inside the preview version of Windows 8 the multimedia engine may fail to load with the following error "Internal error, cannot load engine Number 2 due to error 50".
Certain MP3 files are not decoded till their end and report a shorter duration respect to the correct one.
Video in 16:9 are sometime not rendered with the correct aspect ratio
When the playback rate or tempo have been modified, in certain cases the component could miss firing the SoundDone event.
The automatic fader may not work with certain audio formats like FLAC, CAF and W64.
After calling the PlaySoundRange method, an eventual call to the SeekSound method which should bring the position out of the previous playback range will cause playback to stop.
The StreamOutputDeviceSet and the StreamOutputSpeakerSet methods don't work correctly with custom stream mixers.
Information retrieved with ReadSoundInfo and ReadSoundInfo2 methods for M4A, MP4 and WMA files may result incorrect under Windows 7.
The sound waveform is not positioned correctly on a scrolling waveform when the sound duration is smaller respects to the limits of the destination HDC.
When opening a video clip whose DirectShow graph requires the usage of the Haali splitter, after closing the video clip the icon of the Haali splitter may remain visible inside the tray notification area.
When opening certain types of video files (for example CDG), after closing the video the source file may stay in locked status.
When the ASIO.DeviceStart method is called with the nChannelMode parameter set to ASIO_CHANNEL_MODE_MIRROR_MONO the sound is played at half the normal speed.
The extraction in memory of the audio stream of a video clip through the VideoPlayer.AudioTrackExtract method may sometime raise a GPF.
When the InitDriversType has been called with paramater DRIVER_TYPE_BOTH_ASIO_FIRST, playback on a DirectSound device could fail.
When the InitDriversType has been called with paramater DRIVER_TYPE_BOTH_ASIO_FIRST, the StreamOutputDeviceGet method may return a wrong value when the selected current output device is of type DirectSound.
When using a volume automation procedure, the VU meters and the VUMeterValueChange event may report wrong peak values.
When playing a range of a DivX video clip using the VideoPlayer.Play method, if the nToPosition parameter is set to the same value reported by the VideoPlayer.GetDuration method, playback may stop far before the end of the clip.
While playback of a range of song is in loop, calling the SeekSound method may cause the loop to be interrupted also when the SeekSound doesn't bring the current song position outside of the playback range.
When starting playback of a range of the loaded song, the volume could be automatically set to 0.
When the video player is in paused state the GetCurrentPos and GetCurrentPosString methods may return invalid values.
When the components are instanced on a secondary container form (different from the main one) and the ResetEngine/ResetControl combination is called, the opening of another secondary form, instancing and initializing any of the components, may rise an unhandled exception.
If the Waveform.BitmapViewSaveToMemory method is called with the nStartPos parameter set to a value different from 0 and with the nEndPos parameter set to -1 the returned bitmap may be empty.
When playing a MP3 file which is still growing in size, the visual feedbacks may stop working after a few seconds when the InitDriversType method has been called with a value different from DRIVER_TYPE_DIRECT_SOUND.
When normalization has been enabled through the NormalizationEnable method, enabling MPX management as well, through the MPXEnable method, will cause the resulting sound to be distorted.
When the video player is loaded with a Sony MSV or DVF file, the GetCurrentPos and GetCurrentPosString methods may return invalid values.
A call to the StopSound method, performed after a call to the ForwardSound/RewindSound methods while the player was already in paused state due to a previous call to the PauseSound method, doesn't change the status of the player from "paused" to "stopped".
If a custom DSP is attached to the output of a custom stream mixer the CustomDSP.Enable method fails with error code ERR_INVALID_RECORDER.
When the container application is launched from a remote desktop connection the multimedia engine could cause a GPF.
The following methods may generate a bitmap of the waveform not perfectly accurate when dealing with very large sound files: Waveform.BitmapViewSaveToFile, Waveform.BitmapViewSaveToMemory and Waveform.BitmapViewDrawToHdc.
After completing a shuffled playlist, set to be executed in loop, the next execution order remains the same without the needed automatic re-shuffle.
Playing in loop FLAC files may cause a deadlock at the end of the song.
An exception may be raised when enabling a VST effect attached to the output of a custom stream mixer.
A regression introduced inside version 9,2,2,3 may cause the embedded fader to generate an exception when calling the Fader.StartManualFading method.
When a playlist not having the loop mode set to "true" has been completed, calling the Fader.StartManualFading method will have no effect so a restart of the playlist results impossible.
A player could sometime miss executing items inside the loaded playlist.
After a ResetEngine the components may fail loading sound files in AAC, MP4, AC3, ALAC, WavPack, MPC, SPX and APE formats.
A regression introduced inside version 9,2,2,3 may cause certain audio formats (like FLAC, CAF and W64) to be played in loop.
The CoreAudioDeviceDefaultChange event is not raised when an USB device is inserted and automatically promoted by Windows as the system default device.
When a sound is played in loop, the normalization effect may stop being applied after the first loop.
An exception may be generated when trying to extract the audio stream from a RealMedia video clip.
The audio track extracted inside a memory buffer from a video clip having a mono audio track (not stereo) may result half its real duration.
The extraction of the audio track from a video clip doesn't work when invoked the second time from a component instanced on a secondary form that is being closed and reopened.
The VUMeter.Resize, Spectrum.Resize and Oscilloscope.Resize always return the error code ERR_FEEDBACK_ALREADY_AVAILABLE (-29).
the VU-meter object doesn't work as expected when the VUMeter.BandType property is set to VU_BAND_MIXED.
When calling the VST.ProgramParamGetDefaultValue method an error message may appear stating that there was an overflow error.

PRODUCT HISTORY

Full product history available inside the online documentation.