Zero out auxiliary output buffers
We used to do this, but this got lost in the migration to the new buffer management system.
This commit is contained in:
parent
9d45cbf1d9
commit
cc5980e215
|
@ -10,6 +10,13 @@ Since there is no stable release yet, the changes are organized per day in
|
|||
reverse chronological order. The main purpose of this document in its current
|
||||
state is to list breaking changes.
|
||||
|
||||
## [2023-04-01]
|
||||
|
||||
### Fixed
|
||||
|
||||
- Auxiliary output buffers are now always zeroed out in case the host didn't do
|
||||
this for us. This was a regression from before 2023-03-31.
|
||||
|
||||
## [2023-03-31]
|
||||
|
||||
### Changed
|
||||
|
|
|
@ -338,6 +338,10 @@ impl BufferManager {
|
|||
*output_channel_pointer,
|
||||
num_samples,
|
||||
);
|
||||
|
||||
// The host may not zero out the buffers, and assume the plugin always
|
||||
// write something there
|
||||
output_slice.fill(0.0);
|
||||
}
|
||||
|
||||
// If the caller/host should have provided buffer pointers but didn't then
|
||||
|
|
Loading…
Reference in a new issue