Mike Kazantsev
Mike Kazantsev
Not sure which "crashes before" do you mean there. If you mean PulseOperationError stuff fixed recently - nope, different unrelated issue to loop itself.
Wrt this issue though: - pjsua has its own event-loop running in a separate thread, which is how that python2 module is written. - Pulse client has its glib event...
As mentioned in an earlier email, I'd suggest that it might be more cost-effective to rewrite this from scratch, maybe using proper python3/asyncio eventloop hooking into libpulse fds in place...
Note that when rewriting the script, you'd probably be using different bindings entirely (pjsua2.so swig module, not old python2 pjsua code), which will probably work differently. But even if not,...
> The error this issue is about seems to happen inconsistently based on my testing, sometimes I can call many times without issue. Yeah, it's almost certainly some trivial race...
Sorry for the delay. Don't think it'd remove the dependency, as volume-setting is needed all over the place there iirc, and maybe there's some other stuff like moving streams between...
Continuing from comment on #4... And as this issue seem to be very much related to #4 - "scheduling" should probably be done in some WebUI - I think these...
I fixed this in the git version, as mentioned to you on multiple occasions in the long chat we had few days ago, don't you remember? Now you're trying to...
Double-checked for whether I maybe forgot to push it, specific fix is this one: https://github.com/AccelerateNetworks/PagingServer/commit/080ca3fe27944972404b0a9b398a3f251ff57c77#diff-c6353a73b3f5034b1f9661701ec297bfR625 Bundled it with other fix for error imports, so maybe that makes it less obvious,...
"mute" in paging.py is implemented via JACK, and I don't see any good reason to have it done through mpd itself at the moment (even fade-in/fade-out should probably be done...