Hello ArrayFire team,
I am the developer of ZBF (Zero Bad Frames), a 17-year planetary imaging pipeline using ArrayFire for GPU-accelerated image processing.
My current setup uses ArrayFire with the oneAPI backend on Intel Arc A750 (OCuLink eGPU). The compute part works well, but I am missing graphics/Forge window support for the oneAPI backend — currently I cannot use af::Window and visualization functions natively with oneAPI/Intel Arc.
This is critical for my turbu1 acquisition module, which displays real-time camera frames at 200fps using ArrayFire's 2-window display.
Could you provide:
- Current status of Forge/graphics support for the oneAPI backend
- Estimated timeline for full graphics support
- Any workaround available in the meantime (e.g. mixed oneAPI compute + OpenGL display)
Thank you for this excellent library — the oneAPI backend is a key enabler for Intel Arc users in the scientific computing community.
Michel Szlosser
Developer, ZBF Pipeline — gpu-vision.fr
Hello ArrayFire team,
I am the developer of ZBF (Zero Bad Frames), a 17-year planetary imaging pipeline using ArrayFire for GPU-accelerated image processing.
My current setup uses ArrayFire with the oneAPI backend on Intel Arc A750 (OCuLink eGPU). The compute part works well, but I am missing graphics/Forge window support for the oneAPI backend — currently I cannot use af::Window and visualization functions natively with oneAPI/Intel Arc.
This is critical for my
turbu1acquisition module, which displays real-time camera frames at 200fps using ArrayFire's 2-window display.Could you provide:
Thank you for this excellent library — the oneAPI backend is a key enabler for Intel Arc users in the scientific computing community.
Michel Szlosser
Developer, ZBF Pipeline — gpu-vision.fr