-
The WaveformAnalyzer.BitmapViewGetWidth method doesn't work.
-
After failing to load a large sound file in memory, that sound file may result locked until closing the container application.
-
A call to the PlaySound method may return error -100 when called immediately after completing a previous playback.
-
Sound files added to an append or mixing automation session will stay locked until the application is closed.
-
Adding a sound file to a mixing automation session will not report an error when the file is invalid or unsupported.
-
The OutputVolumeSet method doesn't change the volume and returns error code ERR_INVALID_PLAYER.
-
After performing one or more append or mixing automation sessions, with many sound files invloved, closing the container application may require several seconds to complete.
-
Starting playback with the PlaySoundRange method, having the nFromPosition parameter set to 0, may cause playback to fail without reporting any kind of error.
-
A GPF may occur when loading a WAV file encoded with CCITT uLaw format on a PC not having a sound card or having a sound card driver not supporting floating point quality.
-
The waveform scroller may generate a GPF during a waveform analysis.
-
While editing a WAV file encoded with CCITT uLaw, when a special effect is applied on a range of the sound, the final resulting sound could be truncated.
-
DeNoise filter adds a small silent portion at the beginning of the file and cuts a corresponding portion of sound at the end.
-
On Windows Vista and higher versions, AAC/MP4 sound files may report a wrong duration.
-
When the SetStoreMode method has been invoked with parameter STORE_MODE_TEMP_FILE, each time a new sound is loaded the temporary file for the previous editing session may remain on disk until the application is not closed.
-
Vertical lines are not automatically rendered by default on the waveform scroller.
-
When the waveform analyzer is used in conjunction with the waveform scroller, moving/accesing vertical or horizontal lines through the mouse could result disabled.
-
The usage of the FromMsToFormattedTime method could cause the raise of strange exceptions apparently unrelated with the code being executed.
-
When the waveform analyzer is used in conjunction with the waveform scroller, moving/accesing vertical or horizontal lines through the mouse could result disabled.
-
The nWaveLineIntensityFactor field of the WSCROLLER_SETTINGS structure is ignored when the WaveformScroller.SettingsSet method is invoked.
-
If the WaveformScroller.Create method fails returning 0, no error is reported inside the LastError property.
-
When the nSelectionMode field of the WANALYZER_WAVEFORM_SETTINGS has been set to WAVE_SEL_CUSTOM_COLORS, calling the WaveformAnalyzer.SetSelection method correctly displays the selection handles but colors of the selected portion don't change.
-
When a vertical line is added to the waveform analyzer at position 0, there is no way to move it through the mouse.
-
The attempt to load an audio file stored inside a data CD could report back an error.
-
When a new sound is loaded, existing graphic items added to the waveform analyzer are discarded.
-
The loading range set through the SetLoadingRange method may sometime be ignored or result in a loading range larger than expected.
-
When the nSelectionMode field of the WANALYZER_WAVEFORM_SETTINGS structure has been set to WAVE_SEL_CUSTOM_COLORS and a selection with the mouse is being performed backward, the rendered waveform won't have the correct colors until the mouse button is not released.
-
Existing tags are ignored if the filename passed to the TagsEditor.ALL_AnalyzeSoundOnEditor and TagsEditor.ALL_AnalyzeSoundFile methods has an unknown extension.
-
When the EnableSoundPreloadForPlayback method has been invoked with parameter "true", the output volume may be reset to 0 after the first call to the PlaySoundRange method.
-
On x64 systems the usage of the WaveformAnalyzer object may cause unexpected exceptions.
-
After enabling through the EnableAutoWaveAnalysisOnLoad method the auto-analysis of loaded sound files, the waveform of CCITT a-Law sound files could result wrong.
-
When the EnableAutoWaveAnalysisOnLoad method has been invoked with parameter "true", loading a sound file while a previous one is still loading may cause an exception.
-
When the EnableAutoWaveAnalysisOnLoad method has been invoked with parameter "true" and the loading of a sound file is cancelled through the LoadSoundCancel method, the memory of the waveform analyzer is not cleaned.
-
When a selection with the mouse is being performed backward, the selection itself is lost when the mouse goes outside of the waveform area.
-
Inside the waveform analyzer, when the possibility to select a portion of waveform through the mouse has been disabled through the WaveformAnalyzer.MouseSelectionEnable method, dragging the mouse outside of the waveform area will cause the whole visible range to be selected in error.
-
An exception may be generated when the LoadSoundCancel is invoked.
-
When the EnableAutoWaveAnalysisOnLoad method has been invoked and the waveform scroller is enabled, loading a sound file may cause an exception.
-
When the EnableAutoWaveAnalysisOnLoad method has been invoked, trying to load a sound file in CCITT u-Law or a-Law format may cause an exception.
-
When the font's height of time rulers has been set to a value higher respect to the default one, the text on the top ruler may be covered by the waveform's display.
-
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.
-
When copying into the system clipboard a portion of the loaded sound through the CopyRangeToClipboard method, the stored sound may result damaged when the loaded sound file is in CCITT a-Law or u-Law format.
-
An exception may be raised when analyzing chunks of a corrupted WAV file.
-
During playback of the loaded sound, eventual selection or vertical and horizontal lines cannot be moved through the mouse.
-
The Effects.VSTFree method doesn't free the loaded VST and always returns error -102.
- Loading a wav file having a BEXT chunk whose size is smaller than 602 bytes may cause the application to crash.
- An exception may be generated when playing a sound range through the PlaySoundRange method.
- The ConvertFile, ConvertFileRaw, ConvertFileRange and ConvertFileRawRange methods will not work when processing a file whose filename contains UNICODE characters and the source sound file to convert may finally result damaged.
- The ConvertAutomationAddFile doesn't work correctly when passing a filename containing UNICODE characters.
