Fix ringbuffer calloc count

[finnvoor]

Previously the ring buffer calloc call was allocating kDevice_RingBufferSize * kBytes_Per_Channel * kNumber_Of_Channels * sizeof(Float32) bytes, resulting in gRingBuffer being 4 times larger than necessary (kBytes_Per_Channel and sizeof(Float32) are redundant).

The calloc call now uses the correct kDevice_RingBufferSize * kNumber_Of_Channels count. This no longer takes kLatency_Frame_Size into account, but kLatency_Frame_Size is 0 and unused.

[devinroth]

Actually in thinking about it more, it’s an artifact of an early version. As long as the kDevice_RingBufferSize is large enough there shouldn’t be any problems. Sorry. I think I got a little confused for a second. Devin Roth

…

On Feb 11, 2022, 9:53 AM -0800, Finn Voorhees ***@***.***>, wrote: Previously the ring buffer calloc call was allocating kDevice_RingBufferSize * kBytes_Per_Channel * kNumber_Of_Channels * sizeof(Float32) bytes, resulting in gRingBuffer being 4 times larger than necessary (kBytes_Per_Channel and sizeof(Float32) are redundant). The calloc call now uses the correct kDevice_RingBufferSize * kNumber_Of_Channels count. This no longer takes kLatency_Frame_Size into account, but kLatency_Frame_Size is 0 and unused. You can view, comment on, or merge this pull request online at: #536 Commit Summary • c1ee4c2 Fix ringbuffer calloc count File Changes (1 file) • M BlackHole/BlackHole.c (2) Patch Links: • https://github.com/ExistentialAudio/BlackHole/pull/536.patch • https://github.com/ExistentialAudio/BlackHole/pull/536.diff — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>