Known Issues for Catalyst

Current Issues

• Incorrect frames served on a clip that was split or resized (most versions)
  Catalyst is not working correctly if you apply Neat Video to a clip that is split or resized by Catalyst tools. In such a situation, Catalyst may send incorrect input frames to the window of the Neat Video plug-in: frames from a different part of the clip may be sent by Catalyst. You can then see that in Neat Video window. This is a limitation of Catalyst itself. It affects the frames sent to Neat Video window at the time of building a noise profile and adjusting filter settings. This does not affect the render results: at render time, Catalyst serves the correct frames and render results show no abnormalities.

• Modified frames served on a clip with another effect applied (most versions)
  Catalyst is not working correctly if you apply Neat Video to a clip with another effect applied. Catalyst may send modified (by another effect) frames to Neat Video (both at the time of setting up a noise profile and at the time of the final render) even if that other effect is disabled or deleted. To avoid that problem please place Neat Video to the top of the effects list.

• Catalyst render process hangs in specific conditions (most versions)
  Catalyst render hangs if (1) the project contains a transition between clips with Neat Video applied and (2) the frame rates of those clips are different. To avoid hanging please ensure that all clips in the project have the same frame rate.

• Neat Video applied to a section of the video only (most versions)
  Catalyst's render process supplies Neat Video plug-in with wrong information about the duration of the effect when:

  1. Neat Video is applied to a Track or Timeline and
  2. The frame rate of the exported video file does not match the frame rate of the Timeline.

  As a result, Neat Video is applied to a section of the video only, not to the whole duration of the video. To work around this issue please ensure that the frame rate of the exported clip is equal to the frame rate of the Timeline. Another solution would be applying Neat Video to a clip rather than to a Track or Timeline.

Older Issues

    No known issues