On Sat, Jun 1, 2024 at 11:27 PM IOhannes m zmölnig <zmoel...@iem.at> wrote: > if you know how to use `git bisect`, you could try to narrow down the > commit that introduced the slowdown.
this is new to me, i admit - but hoping that i did it correctly, i now get: 2fe920f88abb814fc89719a617ce48d63a3eae3a is the first bad commit cheers, ben _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
