Frequently Asked Questions

Microsoft Windows

The download file is a compressed archive .zip folder. That folder contains executable files for either 32-bit or 64-bit DAW hosts.

For Microsoft Windows the executable files are called VidPlayVST32.dll and VidPlayVST64.dll.

To install, copy the relevant executable file into the VST plug-in folder used by your host DAW. Instruct your DAW to re-scan the plug-in folder.

Apple OSX/macOS

The download file is a compressed archive .zip folder. That folder contains executable files for either 32-bit or 64-bit DAW hosts.

For Apple OSX/macOS the executable files are called VidPlayVST32.vst and VidPlayVST64.vst.

To install, copy the relevant executable file into the VST plug-in folder used by your host DAW. Instruct your DAW to re-scan the plug-in folder.

Linux
The Linux version is distributed as a self-extracting archive. Please refer to the Linux Page.
VidPlayVST is a VSTi instrument plug-in. It is listed with 'synth' plug-ins in the host DAW. It is not an 'effect' plug-in and should not normally be dropped into an effect slot.

The manufacturer name for VidPlayVST is 'AnthonySJaques'. If you are having trouble finding the plug-in in your DAW try looking for that name. Some hosts (e.g. Brainspawn Forte) organise their plug-in lists by manufacturer name.
Please check that the plug-in is not bypassed in your DAW. For VidPlayVST to work it must be enabled like any other VSTi instrument.

Also check the 'Cue with any C note' option. If this is set then the plug-in will not start playback until a MIDI C note is received.
The audio project is probably running at 90% or more CPU usage. VidPlayVST is losing synchronisation because there is not enough CPU time available to the plug-in. Check the CPU load in Task Manager/Resource Monitor (Windows) or Activity Monitor (OSX). 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. This allows more CPU time for the DAW to do its main job of processing your audio project.

There are tools available online to re-encode a video down to a smaller frame size. 426*240 is the default size of the VidPlayVST 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.
Open the file in VidPlayVST and click on the logo. This displays various statistics, including the video and audio codecs, and the frame size.
This happens in Cakewalk Sonar, Bitwig Studio and MOTU Digital Performer because of the way in which they implement the Steinberg VSTi plug-in interface. These DAWs report the timeline location to plug-ins only when the transport is actually running. If you move the timeline by clicking or dragging then VidPlayVST does not know the new song position until the transport is restarted.
Hold down the Ctrl Key while dragging the slider. You are then able to set the time to within 30ms so a specific video frame can be selected.
This happens in Acoustica Mixcraft and Zynewave Podium because of the way in which they implement the Steinberg VSTi plug-in interface. In these DAWs the current sample timestamp increments constantly, regardless of the host transport status. The solution is to use the VidPlayVST 'SYNC: Follow Tempo Changes' option.
VidPlayVST supports the video and audio codecs that were licensed to FFmpeg, for decoding, as of August 2016.
Microsoft Windows and Apple OSX/macOS
Yes, but keep in mind that you also need sufficient CPU power to run the audio processing for your project. The plug-in will skip frames if there is not sufficient CPU time available for it to keep synchronisation with the host.
Linux
No.
Not at the moment. There is a workaround using a wrapper plug-in such as DDMF Metaplug-inSynth. With this you can use VidPlayVST in a DAW such as Logic, which does not support VSTi plug-ins.