-
Notifications
You must be signed in to change notification settings - Fork 22
PCM #497 #502
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
base: main
Are you sure you want to change the base?
Conversation
dpwe
left a comment
There was a problem hiding this 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.
|
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. |
Does all the stuff in #497. With tests! And documentation !