Frequently Asked Questions
This will occur if the AudaVid install location is changed. The solution is to delete 2 files pluginregistry.cfg and pluginsettings.cfg in folder C:\Users\'Your Name'\AppData\Roaming\AudaVid. Restart AudaVid and the application will re-scan for plug-in locations. In option 'Effect, Add / Remove Plug-ins...' check that AudaVidVST is now shown 'Enabled'.
The PC may be running at 90% or more CPU usage. AudaVid will lose synchronisation if there is not enough CPU time available. Check the CPU load in Task Manager. Refer to the next question for a solution.
The best way to optimise the required resources (CPU time and memory) is to reduce the video frame size. If you halve the width and height then each frame will decode and render four times faster, thus reducing CPU load.
There are tools available online to re-encode a video down to a smaller frame size. 426*240 is the default size of the AudaVidVST window, so that would be a good minimum size to choose.
Close down all other applications (including your internet browser) and disconnect from the internet.
The cache files are created in the same folder as the video. They are named with "_acache.vdp" and "_vcache.vdp" appended to the video path name. The 'OPTIMIZE: Cache File Analysis' option must remain set, otherwise the cache files are ignored. You may delete the cache files at any time, and AudaVidVST will simply re-create them next time the video is opened.
Please rename the file using characters from a US or European keyboard ANSI character set.
The video probably has very long key frame intervals. Click on the help button to open the About window. Video statistics are displayed here, including 'Average key frame interval'. If this exceeds 5000 msecs then seek time will be noticeable as a delay in synchronization when the timeline is moved.
A video may have been encoded with long key frame intervals in order to get maximum compression. For a video to be quickly 'seekable' it needs to have key frame intervals of 1000 msecs or less. The fix for this problem is to re-encode the video.
The video has probably been encoded without any key frames. Click on the help button to open the About window. Video statistics are displayed here, including 'Final key frame'. If this is zero it indicates that AudaVid was not able to find any key frames in the file.
As an example, the GIF format encodes video without key frames, and also without a video length parameter in the file header. In AudaVid synchronization takes a long time when the timeline is moved because the video plug-in has to decode all the frames from zero to the sync position. The fix for this problem is to make the video 'seekable' by re-encoding with key frames, preferably at an interval of 1000 msecs or less.