Skip to content

Conversation

@bwhitman
Copy link
Collaborator

@bwhitman bwhitman commented Dec 21, 2025

Does all the stuff in #497. With tests! And documentation !

Copy link
Collaborator

@dpwe dpwe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed the code. I was kind of assuming I was reviewing AI-written code which definitely colored my patience. Then I saw the thing where you had summarily rejected the need to scan for largest amplitude in a block, which I guess is not AI. Anyway, I think the code tends to be a bit prolix. It's OK, but it's getting harder to understand - we should simplify to a single pcm_preset_t rather than having separate memorypcm and (ROM) pcm_map_t. But I'm OK with checking this in as long as you make an issue for the tech debt.

@bwhitman
Copy link
Collaborator Author

How about the setting max_value to 1 in PCM. Is that correct and that was just normal snark, or something to fix? The issue was samples with blocks of silence stopping too early.

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.

3 participants