New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GStreamer sink buffer questions #1687

Closed
lazka opened this Issue Sep 17, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@lazka
Member

lazka commented Sep 17, 2015

Now that we control the volume of GStreamer sinks directly we can increase buffering without adding much volume adjustment delay and save some CPU time as a result.

Some open questions:

  • Increasing the buffering and segment size decreases CPU notably, but increasing them too far makes PA go crazy and using 20% CPU..? What is a good max value?
  • Increasing too far also introduces a slight volume change delay. Maybe we can decrease the buffer size during volume changes and reset them back after 2 seconds of no volume change or so?

@lazka lazka added the enhancement label Sep 17, 2015

lazka added a commit that referenced this issue Sep 17, 2015

gstbe: double buffer size if we control the sink volume. See #1687
reduces CPU usage for both QL/PA; adds a bit of volume change delay
@lazka

This comment has been minimized.

Member

lazka commented Sep 17, 2015

  • Changing the buffer size while running isn't possible (according to #gstreamer).
  • Changing the PA write size (latency-time) didn't change the CPU usage much and as stated above behaves weird in same cases.
  • Doubled the buffer size (buffer-time) for now..
@lazka

This comment has been minimized.

Member

lazka commented Jul 8, 2017

No problems so far, and increasing the buffer size even more doesn't help much with CPU here, so closing.

@lazka lazka closed this Jul 8, 2017

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