Morgan Harris

+1 Pretty much unusable without it.

Personally, I think it shouldn't mess with `AVAudioSession` at all - or if it does, it should very much be optional. This is considered to be an application-level setting, specific...

I cloned the repo and hacked at it until it worked. https://github.com/gormster/python-sounddevice/tree/api-mode-experimental Note that this replaces ABI mode completely with API mode. I'm sure there's a graceful way to handle...

Ok so… I've done a thing where it does (I think) handle this gracefully. (Well, sort of; [it uses an environment variable at runtime to select which mode to use](https://github.com/gormster/python-sounddevice/tree/env-api-mode-experimental)....

@ealpha In case you missed it in that wall of text, here's a potential workaround: 1. Create a fresh `conda` environment. Do not install `python-sounddevice`. (You can install `numpy` or...

Seems to me like the sensible thing would be to just drop any specific graphics technology stack, and work with IOSurfaces directly. Metal and GL both support it natively, so...

Hmm. Prefixing the *native* methods wouldn't be a breaking change, right? As long as it only prefixes when there's a clash. (In fact, you don't even need to worry about...

Is this being worked on actively? I've got a draft implementation here, if you're interested: https://github.com/gormster/userscripts/tree/issue/230

Ah, didn't realise that, but I did think about it when I noticed there were no other JS variables being used in the background script… Storing the data entirely in...

done! that was actually fairly straightforward, and got rid of a ton of complexity. hooray!