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 - VST install

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.

VidPlayVST32.vst is provided for backward compatibility with 32 BIT HOSTS ONLY. Do not try to use this with modern DAW hosts which, in most cases, are 64-bit applications.

Apple OSX/macOS - Audio Unit (AU) install

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 VidPlayAU32.component and VidPlayAU64.component.

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

VidPlayAU32.component is provided for backward compatibility with 32 BIT HOSTS ONLY. Do not try to use this with modern DAW hosts which, in most cases, are 64-bit applications.

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.

For problems with installation in Propellerhead Reason, please refer to the specific topic at the bottom of this page.
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 'MIDI: 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, MOTU Digital Performer and Bitwig Studio 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.

In Sonar, Digital Performer and GarageBand you can change this behaviour by setting the 'SYNC: Follow Tempo Changes' option.
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, Zynewave Podium and Cantabile 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.
Yes. It is included with the OSX/macOS distribution available on the downloads page.
Not at the moment. A good option is to use a wrapper plugin such as DDMF Metaplugin Synth. VidPlayVST can then be loaded in Avid Pro Tools, which does not normally support VSTi plugins. There is a demo of how to use Metaplugin in Pro Tools, presented by Production Expert. Skip forward to 3:15 to see how a VSTi instrument is configured.
VidPlayVST has a special optimization feature for handling a long video. Before opening the video, select the 'OPTIMIZE: Cache File Analysis' option. Open the video and the plug-in will save away to disk the important file analysis data. Next time the video is opened it will load very quickly using the cached data.

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 the plug-in will simply re-create them next time the video is opened.
There is a test video available DAW-Seek-Test.mp4. This is a short 25 fps video which has the 'performance time stamp' (pts) displayed on every frame (the frames are 40 milliseconds apart). You can compare the pts against the time displayed in your DAW transport. These two values should normally be within 40 milliseconds of each other (unless you are using the 'MIDI: Cue with any C note' option).
No, this does not work in OSX/macOS, although it may be OK in some Windows hosts. Please do not try to 'bridge' from 32-bit to 64-bit. Always install the 64-bit version of VidPlayVST for a 64-bit host.

Sorry, I don't have the resources to run a system to register licenses and issue automatic software updates.

The plug-in version number is shown in the About window (click on the logo). Current version numbers are as follows:
Windows - 1.3.3, download file date is 06-03-2018
OSX/macOS - 1.2.2, download file date is 20-10-2017
If you have an earlier version that you want to upgrade, please email me at the address shown below. I will send you the latest version as an email attachment.

As of March 2018 the plug-in has been on sale for a year. It is known to be running reliably with many different DAWs and there are no plans to add any extra functionality.

It appears that Reason does not always scan for new plug-ins when the application is started. To force a re-scan of the plug-in folders it is necessary to close the app and delete the plug-in cache data file, which is located here...
OSX: /Users/'Your-Name'/Library/Caches/Reason/PluginCache.dat
Windows: C:/Users/'Your-Name'/AppData/Local/Propellerhead Software/Reason/PluginCache.dat
Open Reason again and check that VidPlayVST is listed in the 'Manage Plugins' window.

Please rename the file using characters from a US or European keyboard ANSI character set.