# fl.chain~

**URL:** <https://framelib.discourse.group/t/fl-chain/52>\
**Category:** Usage Questions\
**Created:** [12 November 2019 12:47 UTC](https://framelib.discourse.group/t/fl-chain/52 "2019-11-12T12:47:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![o.green](https://yyz2.discourse-cdn.com/free1/user_avatar/framelib.discourse.group/o.green/32/29_2.png) [@o.green](https://framelib.discourse.group/u/o.green)\
**Post date:** [12 November 2019 12:47 UTC](https://framelib.discourse.group/t/fl-chain/52/1 "2019-11-12T12:47:57Z")

</div>

Pending a help file, I wonder if some help understanding this object could be mustered. I thought it might offer part of a solution to evening out the processing load for a granulator, by being able to break up buffer reads into predictable chunks.

Q’s:

- What’s the behaviour with new input? If it’s working through a list of times, is the idea that it a) replaces the old list; b) ignores the new list; c) merges the lists? [seems like it ignores the new list?]
- I’m not grasping the absolute / relative behaviour. Does ‘relative’ mean that [0 1 2 4 8] is interpreted as  
`now, now+1, now+1+2, now+1+2+4, now+1+2+4+8`  
and absolute  
`now, now+1, now+2, now+4, now+8`

---

<div class="post-metadata">

**Author:** ![james.bradbury](https://yyz2.discourse-cdn.com/free1/user_avatar/framelib.discourse.group/james.bradbury/32/15_2.png) [@james.bradbury](https://framelib.discourse.group/u/james.bradbury)\
**Post date:** [14 November 2019 21:35 UTC](https://framelib.discourse.group/t/fl-chain/52/2 "2019-11-14T21:35:29Z")

</div>

I may have answered the question in the other thread but `relative` mode is relative to the trigger frame (and actually sorted IIRC), while `absolute` mode is perhaps more easily conceived as an accumulation of the times in their frame order.