Category:Support
Support Portal
For information on Digital Vision support availability, including contact details and contracts, please see the support area of the main web site.
NotesContentsCompatibility with Previous ReleasesProjects and notes from the previous release of the application are normally compatible and supported in the (major) release after i.e. 2014.1 is compatible with the previous release 2013.3. However, projects and notes from releases prior to the version previous are not supported and might result in application instability and project damage. Projects and notes from the current release are not compatible in previous versions. Once opened in the latest release, you should not open a project in any older release (even the last) or project damage might result. Memory SettingsThis release is 64 bit and can use all available system memory. Application memory usage is controlled using the preference setting memoryImagePoolMaxMB (in megabytes). New installations will set this parameter to half system RAM by default but you may want to change this. You can change this through editing the preference file or in the GUI Preferences / Rendering : Image memory :
Examples :
You may need to experiment to determine best settings for your workload. Note that this discussion assumes no other application is running at the same time as ours. In particular, any external helper applications such as Apple Quicktime or Avid will also allocate and require their own memory areas. Thread SettingsThere are two thread preference settings available. The recommended settings are :
These recommendations are set automatically on fresh new installs of the latest version where a preference file does not exist. If the preferences exist, the settings inside will be used. It is best to let the application create a brand new preference file by moving any existing one out of the way. The renderFrameThreads and renderTileThreads parameters are available in the preference file and via the GUI Preferences / Rendering section. If the application starts running out of memory for rendering, one way to mitigate this is to try reducing the number of Frame threads. Optimising Performance and ThreadingThese thread settings may not be optimal for your specific workflow. For best performance, you should analyse and benchmark your workflow using a variety of thread settings and select the settings that work best for you. Optimising threads can have a big impact on render speed so it is a good idea to undertake some tests before starting a job. To determine the number of cores and an optimal value for renderFrameThreads, see the FAQ. DPX CompatibilityThere are some DPX specific compatibility settings you can add to the Clip.prefs file (in your ROOT folder) : DPX { luma10PadLines BOOLEAN luma10MSBFirst BOOLEAN RGB12as2011 BOOLEAN } Where BOOLEAN can be "true" or "false" (without the quotes).
{{M-Note|Compatibility with 2011.2 For complete compatibility with version 2011.2 and earlier, you should set : DPX { luma10PadLines false luma10MSBFirst true RGB12as2011 true } GPU DirectGPU Direct is disabled by default in current releases and should only be enabled for testing purposes (and feedback). GPU Direct is an NVIDIA mechanism that allows a more efficient use of system resources when using an SDI video board with an NVIDIA graphics card. This feature is considered beta currently and we have disabled it by default. To enable and test, see below. Feedback is welcome but please see the Known Issues section in the release notes post install. To enable GPU Direct, set the following option in your preferences (inside the IOCard section) : IOCard { enableGpuDirect true } GPU Direct is supported by all DVS video boards except the Centaurus2. |
Pages in category ‘Support’
The following 12 pages are in this category, out of 12 total.