since its a documented limitation and the error matches the documentation, the approach I would recommend is to file a bug, asking for stream capture to be supported with VPI.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| vpiStreamCreateWrapperCUDA with cuda kernels | 0 | 100 | August 8, 2024 | |
| VPI <=> CUDA stream and event interop | 1 | 814 | December 9, 2020 | |
| CUDA stream & VPI stream synchronization | 8 | 394 | November 22, 2024 | |
| Cuda Engine with VPI | 3 | 923 | June 30, 2022 | |
| Does vpiStreamSync on wrapped CUDA stream synchronize underlyng CUDA stream? | 3 | 994 | January 20, 2022 | |
| VPI 3.2 scheduling CUDA kernels/API calls on a VPI stream | 2 | 47 | June 8, 2026 | |
| VPI CUDA interop with managed memory | 15 | 2127 | December 18, 2020 | |
| Capturing a graph launch | 0 | 399 | July 11, 2023 | |
| vpiStreamCreateWrapperCUDA Leaks? | 0 | 54 | May 11, 2026 | |
| VPI efficiency issues | 1 | 435 | October 12, 2023 |