-
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.
-
Recording sessions based upon external encoders (like MP3, OGG and AAC) don't handle the closure of the external encoder correctly so the recorded sound file stays locked also after freeing the recorder's memory through the RecordedSound.FreeMemory method.
-
The RecordedSound.GetPlaybackPosition may return a wrong value if the ScaleUnits property of Active/Audio DJ Studio has been set to a value different from SCALE_MILLISECONDS.
-
If a recording session has been previously performed by loading from a sound file encoded with an ACM encoder, the result of an appending / mixing / overwriting / inserting session of another sound having different frequency or number of channels respect to the previous one, will cause the final sound to result damaged.
-
If a recorded session is in playback, an eventual call to the RecordedSound.FreeMemory method will not automatically stop playback and the component could go into an undetermined state.
-
After calling the EnableOutputDevice method, an eventual player instanced by Audio DJ Studio and loaded with a sound file stored inside a memory buffer may result empty.
-
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".
-
A GPF may be raised when pasting a large amount of sound from the clipboard.
-
When the recorder component and the editor component are instanced and initialized together, the application could generate an error box stating "Cannot create engine VX".
-
When performing a Paste operation of a sound stored inside the clipboard the application may suffer a GPF.
-
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 SwitchOutputFile method doesn't work correctly when used in conjunction with the Sound Activation System.
-
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 OutputDeviceGet method may return a wrong value when the selected current output device is of type DirectSound.
-
During a recording session from an ASIO input device, with the Sound Activation System enabled, there may be an abnormal memory consumption.
-
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 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: WaveformAnalyzer.BitmapViewSaveToFile, WaveformAnalyzer.BitmapViewSaveToMemory and WaveformAnalyzer.BitmapViewDrawToHdc
-
After a ResetEngine the components may fail loading sound files in AAC, MP4, AC3, ALAC, WavPack, MPC, SPX and APE formats.
-
An exception may be generated when trying to extract the audio stream from a RealMedia video clip.
-
No error is generated when trying to extract the audio track from an invalid video file.
-
An audio file containing noise or audio at wrong speed could be generated when extracting the audio track from a multichannel video clip or from a video clip containing a 8 bits per sample audio track.
-
If inside the system there is a CD drive mapped on letter "F", when recording a file stored inside a ftp site, the control returns the error code -37 (ERR_CD_INVALID_TRACK).
-
The VUMeter.Resize, Spectrum.Resize and Oscilloscope.Resize methods 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.
