Skip to content

Conversation

@StefanBruens
Copy link

Most processing happens as a result of an incoming DBus event. The only case when a timed processing
is needed is due to an pending save.

Instead of implementing a full event loop just run the timed loop while a save is pending, and use an
infinite timeout otherwise.

Fixes: #962

Most processing happens as a result of an incoming
DBus event. The only case when a timed processing
is needed is due to an pending save.

Instead of implementing a full event loop just run the
timed loop while a save is pending, and use an
infinite timeout otherwise.

Fixes: jackaudio#962
@falkTX
Copy link
Member

falkTX commented Dec 13, 2023

The PR changes seem fine, but if one is using jack the idea of saving battery is non-sensical.
JACK will keep the audio device active at all times on a very quick / small buffer size, this will save very little

@StefanBruens
Copy link
Author

The PR changes seem fine, but if one is using jack the idea of saving battery is non-sensical. JACK will keep the audio device active at all times on a very quick / small buffer size, this will save very little

Running jackdbus does not equal running jack. People will have jackdbus running in the background continously, even if they use jack just sometimes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Jackdbus wakes up every 200ms

2 participants