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.

Sign up for GitHub

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

Jump to bottom

Multiple audio objects behave incorrectly with NULL input #465

Open
h4yn0nnym0u5e opened this issue Jun 28, 2023 · 0 comments
Open

Multiple audio objects behave incorrectly with NULL input #465

h4yn0nnym0u5e opened this issue Jun 28, 2023 · 0 comments

Comments

@h4yn0nnym0u5e
Copy link
Contributor

h4yn0nnym0u5e commented Jun 28, 2023 •
edited
Loading

For examples see fixes for AudioRecordQueue (PR#403), AudioEffectEnvelope (PR#444), AudioEffectFade (PR#464). Typically this is where the object contains time-dependent state internally, which is not updated as it should be when there is no received audio block (e.g. receiveReadOnly() returns NULL). Silence does not necessarily mean inactivity.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@h4yn0nnym0u5e