ActiveX version (amp3dj.ocx)
220.127.116.11 (September 12, 2014)
Multimedia engine version (AdjMmsEng.dll) 10.7.0.1 ( December 12, 2014)
Full product history is 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)
- When calling the VST.ProgramParamGetDefaultValue method an error message may appear stating that there was an overflow error.
- When calling the PlaySoundDisableLoop method, the control will raise an error message stating that a wrong number of parameters was specified.
- After loading a sound file in formats like PVF, SVX, AU, VOC, CAF, W64, NIST, IRCAM and PAF, when closing it through the CloseSound method the sound file could remain locked.
- The call to the RequestSoundExportToWav method may generate an expception when dealing with input sound files whose duration is longer than 30 minutes.
- When the output of the stream mixer is set to -1, attaching an instance of the recorder will only produce an empty output file.
- Playing a 8 bits per sample sound file may generate an exception.
- If the audio stream volume of a video clip has been set to a value lower than 100 (0 dB), after calling the VideoPlayer.Seek method the stream volume will be automatically reset to 100.
- With a video clip loaded but still not playing, after seeking the current position through the VideoPlayer.Seek method, an eventual call to the VideoPlayer.Play method will start playback from the beginning of the video clip..
- With a video clip loaded but still not playing, an eventual call to the VideoPlayer.Seek method may cause the application to hang..
- Starting playback of a WMA Internet stream may fail.
- The CloseSound method doesn't interrupt the connection to an Internet stream.
- When starting direct playback through an Active DJ Studio player of an input channel recorded through Active Sound Recorder, through the PlaySoundFromRecorder or PlaySoundFromRecorderEx methods, the resulting sound may contain static noise or some stuttering..
- When dealing with DirectShow codecs which don't report the correct size of video frames, frames grabbing could report a successful result while no grame was effectively grabbed.
- When the EnableMixingFeatures properties is set to False, smoothing volume doesn't work anymore.
- In certain situations, loading a MP3 file which only contains an ID3V2 tag but doesn't contain any sound frame will fail without reporting any error code.
- When resuming playback of a paused video clip, in certain situation no sound is heard also if the volume of the stream was set to the maximum.
- Certain FLAC files may cause strange situations with the impossibility to play the file and returning a wrong duration.
- When the PlaySoundRangeLoop method is called with the nToPosition parameter set to -1, the loop could not occurr and playback could result stopped.
- The BeatsDetectRequest method doesn't work.
- The waveform scroller may generate a GPF during a waveform analysis.
- If a custom stream mixer has been created using the StreaMixerCreate method having the nOutput parameter set to -1, there will be a CPU overload until the moment in which the stream mixer is connected to a recording session or to a casting session.
- In absence of a sound card, also if the nOutput parameter of the InitDJSystem/InitSoundSystem has been set to -1, the loading of a file will fail with error ERR_CANNOT_LOAD_FOR_MIXING and the silence analysis will fail with error ERR_NOT_LOADED_FOR_MIXING.
- On Windows Vista and higher versions, AAC/MP4 sound files may report a wrong duration.
- If the CustomDSP.UseFloatSamples method has been invoked with parameter "true" and a video clip has been loaded on a player whose audio rendering mode for video files has been set to AUDIO_RENDERER_MODE_CUSTOM_2 through the VideoPlayer.AudioRendererModeSet method, the call to the VideoPlayer.Seek method during playback will cause a short noise on the audio output.
- The GetSoundFileDuration method may return an inconsistent value instead of an error code when the sound file fails to load.
- When the VideoPlayer.AudioRendererModeSet method has been invoked with AUDIO_RENDERER_MODE_CUSTOM_2, an exception may be raised when the audio stream is set to work with samples made of integers 24 or 32 bits. Can be reproduced when the audio stream is managed through the LAV Audio decoder.
- When the VideoPlayer.AudioRendererModeSet method has been invoked with AUDIO_RENDERER_MODE_CUSTOM_2, visual feedbacks may report wrong values when the audio stream is set to work with samples made of integers 8 or 16 bits. Can be reproduced when the audio stream is managed through the LAV Audio decode.
- If a MIDI input device has already been started through the MIDI.InputDevicesStart or MIDI.InputDevicesStartOnPlayer methods, a new call to the MIDI.InputDevicesEnum method, without a previous stopping of started devices through the MIDI.InputDevicesStop method, may cause the failure of a new device starting and the application could hang on exit.
- When a volume automation session is set to perform a linear volume slide (nCurveType parameter set to VOLUME_CURVE_LINEAR), the sliding doesn't occur and the volume goes to the final level only at the end of the established time.
- The StreamVolumeSlide and StreamVolumeSlideEx methods don't work as expected when the nScaleType parameter is set to SCALE_LOG.
- Calling the SeekSound method while a volume sliding, started through the StreamVolumeSlide and StreamVolumeSlideEx methods, is occurring may cause unpredictable results.
- When the nSlideDuration parameter of the StreamVolumeSlide and StreamVolumeSlideEx methods is set to 0, the volume will start at a very high and wrong level.
- When the nSlideDuration parameter of the StreamVolumeSlide and StreamVolumeSlideEx methods is set to a value smaller than 200 ms and is immediately followed by a call to the SeekSound method and by another call to the StreamVolumeSlide and StreamVolumeSlideEx methods, an eventual call to the StreamVolumeIsSliding method will return "false" also if the sliding is still occurring.
- When the embedded fader object is initialized from different instances of the component, meaning that there will be more than one working fader, the call to the Fader.StartManualFading method may return an ERR_GENERIC error.
- When the program of a VST effect is changed through the editor of the VST itself, the VstParamChangedValue event is not fired and, in case a new sound file should be loaded, parameters of the program would be reset to the previous value.
- The attempt to load an audio file stored inside a data CD could report back an error.
- The usage of the PlayListItemVolAutomPointRemove and of the PlayListItemCuePointRemove methods could sometime give wrong result and in some case could cause an exception.
- More calls to the StartManualFading method during a volume automation with an occurring volume sliding may cause a dead-lock.
- The final volume level applied with the StreamVolumeDirectSoundBufferSet method is not the same applied by the StreamVolumeLevelSet method.
- At the end and at the beginning of volume sliding operations, the FadingVolumeChanged event may report several times the same volume.
- The SetSmoothingTimeOnSeekOps method is hidden to the Intellisense.
- When a volume sliding needs to bring the final volume level to 100 (maximum volume), the sliding may stop at volume level 99.
- When invoking the SeekSound method on a playing sound, a loud click could be heard.
- After invoking the StreamVolumeDirectSoundBufferSet method, a call to the SeekSound method may apply an unwanted change to the volume level.
- When the level of a spectrum bar comes to its maximum limit it will suddenly drop to 0.
- When the selected audio rendering mode for video files has been set to AUDIO_RENDERER_MODE_CUSTOM or AUDIO_RENDERER_MODE_CUSTOM_RESAMPLE_STEREO or AUDIO_RENDERER_MODE_CUSTOM_NO_SURROUND through the VideoPlayer.AudioRendererModeSet method, seeking the current position through the VideoPlayer.Seek method may cause the volume level to drop to 0.
- The VideoPlayer.PlayRange method could not predispose the correct playback range when the initial and/or final positions exceed 7 minutes.
- When a volume smoothing on playback start has been predisposed through the StreamVolumeSmoothingSet method, the VideoPlayer.PlayRange method may start playback without any volume fade-in.
- The embedded VU-Meter doesn't report correct volume levels.
- An exception may be generated when the VideoMixer.Move method is invoked with the nWidth and/or nHeight parameters set to 0.
- When a video player has been added to the video mixer through the VideoPlayer.AttachToVideoMixer method, the related video preview window will not route mouse events to the container hosting form or control.
- When a video player has been added to the video mixer through the VideoPlayer.AttachToVideoMixer method, calls to the VideoPlayer.AudioTrackExtract method
- During the download session of a huge sized file, started through the Downloader.SessionStartToFile or Downloader.SessionStartToPlayer methods, the value of the nProgressPerc parameter of the DownloaderSessionProgress event may suddenly drop to 0.
- If a volume automation should be programmed for performing a fade whose duration would require an excessive amount of minutes, the application could hang.
- Existing tags are ignored if the filename passed to the TagsReader.ALL_AnalyzeSoundOnPlayer and TagsReader.ALL_AnalyzeSoundFile methods has an unknown extension.
- An exception may be generated when removing a volume automation point throught the VolumeAutomation.PointRemove method while the player is already in playback status.
- In absence of a sound card installed inside the system, if a custom stream mixer has been created using the StreaMixerCreate method having the nOutput parameter set to -1, and if the nOutput parameter of the InitDJSystem has been set to -1, an eventual casting session will success in establishing the connection with the server but will not send any sound data in output.
- For loaded video clips the GetSampleRate method returns 0.
- When more than one instance of Active DJ Studio and/or Active Sound Recorder controls are instanced within the same applications, values of CoreAudio VU meters may not be notified to all of the instanced controls.
- The possibility to scroll the waveform for its full length inside the waveform scroller is not updated after loading a new sound file having a longer duration.
- The WaveformScroller.Create method could reference the wrong player when more than one instance of the control has been initialized.
- The StreamVolumeIsSliding and VolumeAutomation.IsSliding methods may sometime return TRUE also if the sound is stopped.
- When executing a volume automation based playlist (PDJ format) the FadeInStarted, FadeOutStarted, FadeInCompleted and FadeOutCompleted events are not fired.
- The VST.EffectFree method doesn't free the loaded VST and always returns error -102.
- When the Fader.Init method has been invoked with the nFadeType parameter set to FADE_SINGLE, the Fader.StartManualFading method will fail fading if involved players have loaded an Internet stream.
- When the Waveform.PeaksLoad method is invoked, when starting playback of the loaded sound an eventual waveform scroller will not move as expected.
- Loading a wav file having a BEXT chunk whose size is smaller than 602 bytes may cause the application to crash.
- The PlayListItemVolAutomPointModify method may sometime cause unpredictable behaviours of the volume automation when playlist is already being executed.
- When the EnableMixingFeature property is set to False, the embedded fader may stop raising events related to start/end of volume fade-in and fade-out.
- The SoundStopped event may be fired in error immediately after invoking the the PlaySoundFromRecorderEx method and also when the PauseSound method is invoked during playback of sound incoming from an instance of the recorder.