Thanks for the link!
I’m not that familiar with numba, but it seems in audio.py you are using the jit annotation from it. Could it be that numba initializes a CUDA context, thus raising this issue?
Could you try to remove the jit for the sake of debugging and try it again?
I’m not sure, what might have broken the code in the latest release, but it would be interesting, if numba has a role in it.