# @startframe/@numframes attributes for fluild.bufnmfcross~

**URL:** <https://discourse.flucoma.org/t/startframe-numframes-attributes-for-fluild-bufnmfcross/526>\
**Category:** Pre-Release Toolbox2 New Ideas\
**Created:** [June 21, 2020, 5:21pm UTC](https://discourse.flucoma.org/t/startframe-numframes-attributes-for-fluild-bufnmfcross/526 "2020-06-21T17:21:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rodrigo.constanzo](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/rodrigo.constanzo/32/12_2.png) [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)\
**Post date:** [June 21, 2020, 5:21pm UTC](https://discourse.flucoma.org/t/startframe-numframes-attributes-for-fluild-bufnmfcross/526/1 "2020-06-21T17:21:22Z")

</div>

From what @tremblap said at the last FluCoMaChaT, `fluild.bufnmfcross~` has changed a bunch already from what we “accidentally” got in alpha03, so this may already be the case, but it would be great to be able to specify `@startframe` & `@numframes` (ideally for both `@source` and `@target`).

Granted, one could `fluid.bufcompose~` what they want first, but most(all?) of the other `buf`-based `fluid.objects~` have some kind of specificity with regards to the desired frames to analyze.