Usage Notes and 'Gotchas'

System Requirements - Microsoft Windows

Windows version 7 or later is required. VidPlayVST will not run in Windows XP or Vista.

System Requirements - Apple OSX/macOS

OSX/macOS 10.8 or later is required. VidPlayVST will not run in OSX Tiger, Leopard, Snow Leopard or Lion.

System Requirements - Linux

Please refer to the Linux Page.

Audio Render - using the plug-in to extract audio:

Most DAWs have a 'Fast Render' option and many also have track 'Freeze'. These options will not work with VidPlayVST. Please render audio at the normal playback speed. Use a plug-in such as MeldaProduction MRecorder, if necessary, to record to file in a mixer bus.

Synchronisation in Cakewalk Sonar and MOTU Digital Performer:

In these DAWs it is recommended that you use the 'SYNC: Follow Tempo Changes' option. With this option the plug-in will synchronise when the timeline is moved by clicking or dragging within the project.

Synchronisation in Bitwig Studio and SoundBridge:

In these DAWs VidPlayVST synchronises to the host timeline ONLY WHEN THE TRANSPORT IS RUNNING (i.e. the user has hit 'play'). When the transport is stopped the plug-in window does not refresh if the timeline is moved by clicking or dragging within the project. This is a limitation of the plug-in interface provided by these particular DAWs.

Acoustica Mixcraft, Zynewave Podium, Cantabile and LMMS:

In these hosts the VidPlayVST option 'SYNC: Follow Tempo Changes' MUST BE SET. Without this setting video playback runs free and does not synchronise to the transport timeline. 'MIDI: Cue with any C note' cannot be used with these hosts. LMMS also requires 'Sync VST plugins to host playback'.

Tempo changes in Ableton Live:

VidPlayVST will not work correctly in Ableton Live when there are tempo changes in the project. A fixed tempo must be used due to a limitation of the plug-in interface provided by this DAW.

VidPlayVST is configured as an 'Instrument' (VSTi v2.4):

VidPlayVST will not work with Steinberg Wavelab, Adobe Audition, Audacity® or Wavosaur. These audio editor applications do not support VSTi 'Instrument' plug-ins.

Key Frames, Key Frames!!:

Most videos are encoded with frequent key frames, and these are required for VidPlayVST to work correctly. A key frame interval of 1 second or less is ideal. Click on the plug-in logo to open the About window, where video statistics are displayed, to confirm the 'Average key frame interval, msecs'. If this exceeds 5000 msecs then there will be noticeable delays in synchronisation when the DAW timeline is moved around.

DRM - Digital Rights Management:

VidPlayVST will not open videos that are encrypted with DRM.

How to configure as a video server using Vienna Ensemble Pro:

Using VidPlayVST with VEPro