Assembly version (AudioSoundRecorder.dll) 220.127.116.11 (July 29 , 2009)
Multimedia engine version (AdjMmsEng.dll) 18.104.22.168 (January 5 , 2010)
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 3.0)
- During a recording session started through the StartFromFile method, if the EncodeFormats.ResampleMode property is set to RESAMPLE_MODE_NATIVE_FORMAT and the EncodeFormats.ResampleNativeFormat property is set to -1, the final recorded sound is always based upon a 8 bits per sample format.
- After completing a recording session in native format (EncodeFormats.ResampleMode property set to RESAMPLE_MODE_NATIVE_FORMAT), an exporting session in MP3, OGG Vorbis or AAC format won't apply correct settings.
- The append of two recording sessions from a memory buffer, whose output is generated inside a memory buffer, doesn't work.
- A recording session in append mode, whose output is sent to a memory buffer in MP3 format, doesn't work.
- A move of the waveform analyzer could cause the missing rendering of the vertical line indicating the playback position.
- Calling the WaveformAnalyzer.Create method twice could cause a bad behaviour of the analyzer instead of returning an error.
- Under Vista the playback of a previously recorded sound could fail.
- Canceling a CD ripping session locks the output file till the container application is closed.
- Occasionally a mouse click over the waveform analyzer surface can generate a GPF.
- Recording sessions in append and insert mode can sometime cause issues.
- Recording sessions in append, insert, mix and overwrite mode can cause issues if the output format is WAV PCM with 8 bits per sample.
- Setting the bAppearance3d member of the WAVEFORM_ANALYZER_SETTINGS class to "false" will cause the resizing handles of the waveform analyzer to be rendered without the usual black border.
- The RecordedSound.PlayRange method doesn't work under Vista.
- Passing an invalid set of parameters to the WMA encoder will cause the encoder to return a ERR_CD_IDENTIF_UNAVAIL error code instead of a ERR_ENCODER_ERROR error code.
- After enabling the splitting in chunks of a recording session, through a previous call to the SplitWavRecordingEnable method, chunks are not generated at all if the original destination of the recording session is a file.
- A fast resize of the waveform analyzer containing custom vertical lines could cause the mentioned lines to be displayed at wrong positions.
- An exporting session performed using a 8 bits per sample format could create a damaged output file whose dimension in bytes is double respect to the expected one.
- A recording session from a memory file could create a damaged output file whose dimension in bytes is double respect to the expected one.
- A direct saving to a file in WAV PCM, performed through the RecordedSound.SaveToFile method, can generate a distorted sound if the recording session has been performed using 8 bits per sample.
- Under Vista it's not possible starting two recording sessions at the same time on the same input device.
- Covering or moving outside of the visible area the form containing the Waveform embedded feedback can cause a cleaning of the Waveform area itself.
- Passing -1 as nInputDevice to the InitRecorder method will cause a wrong initialization.
- Inserting or appending to the recording session a file having different resolution in terms of sample rate and channels can cause a wrong output.
- Trying to record from a file using its native resolution will fail.
- Recording from a file whose original number of bits per sample is 16 or higher and performing a resampling to 8 bits per sample will cause a wrong output.
- The Pause method will be ignored under certain conditions when the Sound Activation System is enabled.
- Enumeration of ACM codecs or a recording session performed using the Audio Compression Manager can cause a GPF if the EncodeFormats.ACM.InitCodecs method has not been previously called.
- The editing of a recording session can fail on Windows Vista when using a half-duplex device (like the SpeechMike).
- Performing an editing session while a waveform analysis is underway could cause a GPF.
- Recording from an Internet URL doesn't work.
- The exporting session of a huge recording session can fail due to a "not enough memory error".
- A recording session performed into a destination file cannot be exported into the same destination file.
- Recording sessions in insert, mixing, append and overwrite modes will generate a wrong output if the existing session has a different resolution in terms of frequency and bits per sample.
- Lame versions higher than 3.96.1 generate distorted MP3 files.
- The Automatic Gain Control (AGC) doesn't wok if enabled before starting the recording session.
- Recording session generates a GPF when the system runs out of memory.
- The merging of two huge recording sessions can generate a GPF.
- Resizing of trackers of the waveform analyzer is not interrupted when the left mouse button is released.
- The waveform analysis can generate a GPF when started during the merging of two recording sessions.
- Editing of files in WMA format doesn't work.
- Recording, CD ripping and exporting sessions in ACM could fail if the WAVEFORMATEX structure has been passed through the EncodeFormats.ACM.SetCodecFormatWavData method.
- The RecordedSound.GetDuration method could return 0 in error with certain audio formats.
- The insertion of a new recording session at position 0 of an existing recording session could generate a GPF.
- A new recording session in overwrite mode at the end of an existing recording session could result in an empty session.
- In rare cases the waveform analysis can generate a GPF.
- The call to the Stop method during a recording session from an Internet URL is not immediate.
- The insertion of a new recording session inside an existing one ,whose duration is longer than 30 minutes, can cause a GPF.
- Methods KeepRange, DeleteRange and InsertSilence don't work as expected with very long sessions.
- The merging of two recording sessions whose destination is a file on disk doesn't work correctly.
- Methods KeepRange and DeleteRange are not reliable in terms of positioning.
- The nWidth parameter of the WaveformAnalyzer.VerticalLineAdd method is ignored.
- If a recording session fails and its destination is a WAV file, the destination file remains locked.
- The RecordedSound.SaveToFile method has been called RecordedSound.SaveToDisk in error.
- The ConnectionToUrlDone event doesn't report the correct result.
- If the recorder is instanced inside a secondary form, it will not work correctly starting from the second time the form is opened.
- In presence of a faulty sound card or of a faulty sound card driver the initialization of the component could fail and the container application could hang at startup.
- If the EncodeFormats.ResampleMode property is set to RESAMPLE_MODE_NATIVE_FORMAT and the EncodeFormats.ResampleNativeFormat property is set to -1, it's not possible recording when the EncodeFormats.ForRecording property is set to ENCODING_FORMAT_ACM.
- When both the DJ Studio and the Sound Recorder are instanced inside the same application, if the DJ Studio had one of the players whose output was set to -1 through the InitSoundSystem method, if the recorder calls EnableOutputDevice (x, true) (where 'x' indicates the index of any of the available output devices) an exception will be raised.
- Files in G723 format generated by the Vivo codec are not always opened correctly.
- When exporting a file the SoundExportPerc event is not generated correctly.
- If you set the playback position using the RecordedSound.SeekPlayPosition method while the sound is stopped, a subsequent call to the RecordedSound.GetPlaybackPosition method will return 99 instead of the real position.
- If inside the same form there are both DJ Studio and Sound Recorder instanced, the DJ Studio won't be able to enumerate speakers available for each output device also if the EnableSpeakers property is set to true.
- If the call to the StartFromInputDevice method should be performed twice, the second one would not be blocked with return code ERR_RECORDER_BUSY and the resulting recording session would be damaged.
- The background bitmap set into the waveform analyzer is lost when the loaded sound is discarded from memory.
- If the container application is started without any disk inside available CD drives and then a CD is inserted inside one of the CD drives, Windows Explorer will not have the possibility to access it.
- If the start of a recording session in memory in WAV format should fail, an exception could be generated.
- When using a half-duplex device, during playback of the recorded sound the RecordedSound.GetPlaybackPosition method could return back error code -52 instead of the current position.
- The call to the RecordedSound.PlayRange method doesn't update the Status property to RECORD_STATUS_PLAYING.
- Closing the container form could sometime raise an exception.
- After a ResetEngine call, system mixers are no more accessible.
- When the RecordedSound.PlayRange method is called, a SoundPlaybackStopped event is raised in error.
- Requests about CD covers from Amazon catalogue could cause an exception.
- A regression inside the code doesn't allow recording from an Internet URL.
- If a call to the RecordedSound.PlayRange method seeks the playback position to a percentage higher than 90% of the total file duration, playback could be stopped before reaching the 100%.
- If a CD track is loaded from a CD drive different from the first one listed by the system, the CD tracks is anyway loaded from the first one.
- If a recording session from a device is immediately stopped in less than 100 ms, a duplication of an esisting previous session could occur.
- A regression inserted inside version 22.214.171.124 of AdjMmsEng.dll caused the control to miss generating the SoundPlaybackStopped event after a call to the RecordedSound.Stop method.
- Multiple subsequent requests to CddbRequestServersList or CddbRequestAlbumInfo methods could cause a GPF.
- A call to the RecordedSound.Stop method doesn't generate the SoundPlaybackStopped event.
- Due to an internal delay, the RecordingDuration event could return a wrong value.
- During intensive graphical operations, the position selection on the waveform analyzer could disappear or not being displayed at all.
- If the control is instanced on a secondary form and a VU Meter displaying volume level of the recorder itself is created inside the same form, when the form is closed and opened again the VU Meter creation will return an error stating that the VU Meter alredy exists.
- If the control is instanced on a secondary form and custom lines are added to the waveform analyzer of the editor/recorder itself, when the form is closed and opened again custom lines creation will return an error stating that the custom line alredy exists.
- After seeking the playback position through the RecordedSound.SeekPlayPosition, using a percentage-based position, the RecordedSound.GetPlaybackPosition returns -1.
- There are positioning problems when trying to seek during a playback of a range.
Full product history available inside the online documentation.