Knowledge base

Version 1.5.10 (18160)

• 16-bit to 32-bit conversion crash The integer SSE RGB16-to-RGB32 converter routine crashes if the input is not a multiple of 4 pixels. This affects both display code and image sequence reads. Switching the desktop to 24-bit, disabling DirectX display support in Options/Preferences/Display, and using 24-bit source images are workarounds.

• Crash when starting with output pane disabled Disabling the output pane before opening any video file can result in a crash, because critical CPU detection code is bypassed. There is no problem once a video file has been opened.

• Crash when changing priority while render is completing Changing the priority while a render job is flushing out the final frames can cause a crash. Workaround: Don't do that.

• Frameclient proxy mode leaks file handles Enabling the "proxy" mode of the frameclient driver by using the proxyon.reg registry patch can result in file handles being leaked from applications that use AVIFile, most notably Windows XP Explorer. This leads to "file is in use" errors. There is no workaround other than to disable proxy mode using proxyoff.reg.

• Jobs using WAV files don't close WAV file Running a job that splices in a WAV file for audio leaves the WAV file selected in VirtualDub after the job has completed, preventing it from being modified, moved, or deleted when automation is used. A workaround is to add a dummy job that sets the audio mode to None or Source. Note that the bug is that VirtualDub doesn't write a line to close the WAV file, not that the WAV file persists between jobs, so this bug may exist in third-party programs that generate job scripts as well.

• Scan for Errors is vulnerable to error concealment The error mode for the video stream must be set to "report all errors" for the Scan for Errors command to work. Note that this option also relies on the video codec correctly detecting corruption and reporting an error back safely; this is not always implemented or possible depending on the error.

• Appended files with foreign characters in name don't load properly VirtualDub doesn't write out job scripts correctly when a video segment has been appended that has foreign characters in its name — it writes it out as ANSI encoded and then tries to read it back in as UTF-8. Workaround: Rename the segments to only use 7-bit ASCII characters.

• File Information reports wrong audio statistics for AVI files The "File Information" dialog for AVI files mixes up audio and video streams and reports incorrect size statistics for audio streams.

• Audio disappears when audio stream exceeds several hours Parts of VirtualDub are not 64-bit clean and mess up when audio streams exceed a certain length, typically 1-2 billion samples or bytes. Some of these bugs will be fixed for 1.6.0.

• Audio sync drift after using "center cut" audio filter The "center cut" audio filter has an uncorrected 3072 sample delay.

Version 1.5.9 (18121)

1.5.9 had a couple of bugs that caused application instability, particularly under Windows 95/98. The update to 1.5.10 is considered mandatory.

• Memory corruption error The MPEG-1 parser in 1.5.9 corrupts memory and causes random failures. The upgrade to 1.5.10 is considered a mandatory fix for this reason.

• Windows 98 shutdown bluescreen An uninitialized window handle could cause blue-screens under Windows 95/98 when exiting the application.