Skip to content

feat: configurable mixer input buffer frames, public ringbuf - #20

Merged
anunaym14 merged 3 commits into
mainfrom
feat/mixer-p2
Sep 18, 2025
Merged

feat: configurable mixer input buffer frames, public ringbuf#20
anunaym14 merged 3 commits into
mainfrom
feat/mixer-p2

Conversation

@anunaym14

Copy link
Copy Markdown
Member

No description provided.

@anunaym14
anunaym14 requested review from a team as code owners September 18, 2025 12:00
@kuba--

kuba-- commented Sep 18, 2025

Copy link
Copy Markdown

If you ask me, I would name the package ring and constructor NewBuffer, so we may have access like: ring.Buffer (instead of ringbuf.Buffer).

Just out of curiosity - why a new implementation of ring buffer (instead of using this one from go's std. library or from backend-commons)?

@dennwc

dennwc commented Sep 18, 2025

Copy link
Copy Markdown
Collaborator

Agree @kuba-- , good point regarding the naming.

@dennwc

dennwc commented Sep 18, 2025

Copy link
Copy Markdown
Collaborator

As for "why", I think both implementation had some assumptions that were not true for SIP. It either assumes large object pointers instead of arrays of samples or doesn't have the methods we need. I can recall specifics later if you want. There should be an old PR to SIP which has exactly the same question answered.

@anunaym14
anunaym14 merged commit 11d305e into main Sep 18, 2025
2 checks passed
@anunaym14
anunaym14 deleted the feat/mixer-p2 branch September 18, 2025 17:54
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.

4 participants