# Input buffer 0x600004a7d040: not enough frames
**URL:** https://discourse.flucoma.org/t/input-buffer-0x600004a7d040-not-enough-frames/208
**Category:** Bug Reports and Issues
**Created:** [May 26, 2019, 6:00pm UTC](https://discourse.flucoma.org/t/input-buffer-0x600004a7d040-not-enough-frames/208 "2019-05-26T18:00:11Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)
#### Post date: [May 26, 2019, 6:00pm UTC](https://discourse.flucoma.org/t/input-buffer-0x600004a7d040-not-enough-frames/208/1 "2019-05-26T18:00:11Z")
At the moment I’m getting an error message complaining about the input buffer not having enough frames.
I don’t think that’s happening in the patch itself (but I could be wrong about that), but the purpose of this bug report is how it reports the name of the buffer.
Double-clicking the error message takes me back to the object which is great, but it would be better if it reported the actual name of the buffer.
`fluid.bufspectralshape~: Input buffer 0x600004a7d040: not enough frames`
`fluid.bufpitch~: Input buffer 0x600004a7dc80: not enough frames`
`fluid.bufloudness~: Input buffer 0x600004a7d640: not enough frames`
---
### Author:  [@tremblap](https://discourse.flucoma.org/u/tremblap)
#### Post date: [May 27, 2019, 7:11am UTC](https://discourse.flucoma.org/t/input-buffer-0x600004a7d040-not-enough-frames/208/2 "2019-05-27T07:11:44Z")
this happens when you define the end of calculation after the end of buffer (instead of crashing) so you can check your address your sending to the objects, and you are likely to overflow at times.
As for user feedback, at one point I’m told by @weefuzzy that the cryptic buffer name will be translated to the actual buffer name 😉
---
### Author:  [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [May 28, 2019, 10:11am UTC](https://discourse.flucoma.org/t/input-buffer-0x600004a7d040-not-enough-frames/208/3 "2019-05-28T10:11:52Z")
Yup, this is on the radar