Skip to content
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

Reuse GstBuffer as much as possible #127

Open
fengalin opened this issue Aug 28, 2018 · 2 comments
Open

Reuse GstBuffer as much as possible #127

fengalin opened this issue Aug 28, 2018 · 2 comments

Comments

@fengalin
Copy link
Owner

The AudioBuffer / WaveformBuffer design is now pretty close to the point where it would no longer be necessary to keep up to 30s of samples in AudioBuffer. When a seek back is performed, a mechanism allows holding WaveImage rendering until enough samples are available. This means that we could also remove the code that deals with merging existing samples with incoming ones.

Considering that, current design could transition to this:

  • When a new segment is received outside of currently rendered boundaries (or if nothing is rendered yet), clear the AudioBuffer and the WaveformBuffers / WaveformImages. Add the incoming GstBuffer to the AudioBuffer's VecDeque with flags indicating which WaveformBuffer has already handled the buffer.
  • When a new segment is contained within currently rendered boundaries (e.g. in window seek), set the new segment reference, but drop the buffer.
  • When a new buffer inside current segment is received and the buffer is contained within currently rendered boundaries update the cumulative offset, but drop the buffer.
  • When a new buffer inside current segment is received and and the buffer is not contained within currently rendered boundaries update the cumulative offset, add the buffer to the VecDeque and mark it has not handled yet.

On the DoubleAudioBuffer could select whether or not to swap the WaveformBuffers depending on the last buffer handling status. Current working buffer could be filled (converting samples to pixels on the fly) until the exposed buffer window range becomes too short, marking the buffer as handled by the working buffer, then the WaveformBuffers would be swapped. When a buffer has been handled by both WaveformBuffers the buffer is dropped.

This would avoid copying samples in the AudioBuffer (we would just get a reference on the GstBuffer) saving CPU cycles and memory. The only new cost would be induced by the double conversion samples -> pixels. It should be possible to use SIMD to handle multiple samples at once (either several channels or several consecutive samples at once).

@fengalin
Copy link
Owner Author

Instead of using flags indicating whether the WaveformBuffer has already been handled, it should be possible to use dedicated Buffer queues for each WaveformBuffer. Buffers memory would not be duplicated and each buffer would pop buffers from the queue and the reference counting mechanism would take care of releasing memory when possible.

@fengalin
Copy link
Owner Author

fengalin commented Nov 3, 2018

While it should be possible to avoid copying the gst::Buffers, we are bound to keeping the history mechanism as we need it to render with new sample steps after a zoom in / out.

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

No branches or pull requests

1 participant