# Max: Procesing buffer~ with MSP objects (hacking)

**URL:** https://discourse.flucoma.org/t/max-procesing-buffer-with-msp-objects-hacking/644
**Category:** New Ideas
**Created:** [July 10, 2020, 8:27am UTC](https://discourse.flucoma.org/t/max-procesing-buffer-with-msp-objects-hacking/644 "2020-07-10T08:27:23Z")
**Posts on this page:** 1
**Showing post:** 46

<div class="post-metadata">

### Author: ![a.harker](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/a.harker/32/18_2.png) [@a.harker](https://discourse.flucoma.org/u/a.harker)
#### Post date: [August 26, 2020, 11:33pm UTC](https://discourse.flucoma.org/t/max-procesing-buffer-with-msp-objects-hacking/644/46 "2020-08-26T23:33:40Z")

</div>

It’s also in the MaxAPI doc about newobject\_sprintf … Anyway

- you’ll need to start thinking about multiple inputs and outputs.
- as you don’t care where the objects are in the patch newobject\_fromboxtext might be easier than newobject\_sprintf
- as far as I’m aware there’s no way to make an object in a patch (or about any of box attributes) with typed arguments, and reconverting to text is not nice. The wrapper for framelib demos how to grab the text of your object box (which you’d then need to remove the attributes from and the first bit) - that’s probably the nastiest part of this task.
- Also gets more complex if your hosted object takes attributes…

---

_[View the full topic](https://discourse.flucoma.org/t/max-procesing-buffer-with-msp-objects-hacking/644)._