-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
No. The standard DirectML path is intended for broader Windows GPU compatibility.
TensorRT is optional and NVIDIA RTX-specific.
Yes, depending on the filter chain. Heavy filters can exceed the practical performance or memory budget, so adjust model weight and capture resolution to the GPU.
Compatible models can be added, but not every ONNX model has a graph/interface Neo understands.
Yes. Neo supports user-addable mpv-compatible GLSL shaders.
No. Neo currently targets SDR processing and output.
Yes. RIFE is available for smooth interpolation, while DRBA is aimed at preserving anime-style held-frame timing more naturally.
The interpolation multiplier defines how many frames Neo attempts to generate; it does not guarantee the GPU can process and present them in real time.
The Beam simulation is intended for high-refresh displays. A higher physical monitor refresh rate than the simulated/source rate is required for the intended temporal effect. For 60 fps content, 120 Hz is a practical starting point.
The external Beam design allows the compatible filter to be installed separately. Put it at:
shaders/CRT/CRT Beam Simulator-Neo.glsl
No. It is a different temporal effect and can be combined with spatial CRT appearance shaders if desired.
Yes. The normal distribution is designed for portable use. Keep the package folder structure intact.