Workaround: Rename the segments to only use 7-bit ASCII characters.įile 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.Īudio 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. 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.Īppended 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. 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 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. A workaround is to add a dummy job that sets the audio mode to None or Source. 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. There is no workaround other than to disable proxy mode using proxyoff.reg. Workaround: Don't do that.įrameclient 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. ![]() There is no problem once a video file has been opened.Ĭrash when changing priority while render is completing Changing the priority while a render job is flushing out the final frames can cause a crash. Switching the desktop to 24-bit, disabling DirectX display support in Options/Preferences/Display, and using 24-bit source images are workarounds.Ĭrash 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. This affects both display code and image sequence reads. 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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |