# Confusing sync/cue behavior

**URL:** <https://in-thread.sonic-pi.net/t/confusing-sync-cue-behavior/7155>\
**Category:** Support, Help & Resources\
**Created:** [October 2, 2022, 11:06pm UTC](https://in-thread.sonic-pi.net/t/confusing-sync-cue-behavior/7155 "2022-10-02T23:06:23Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Hussein](https://dub1.discourse-cdn.com/flex017/user_avatar/in-thread.sonic-pi.net/hussein/32/1972_2.png) [@Hussein](https://in-thread.sonic-pi.net/u/Hussein)\
**Post date:** [October 4, 2022, 7:05am UTC](https://in-thread.sonic-pi.net/t/confusing-sync-cue-behavior/7155/6 "2022-10-04T07:05:45Z")

</div>

@decode but this is only true if both live\_loops play patterns that use the same sleep value (resolution), otherwise they still require separate sleep patterns. Even with the suggested workaround there will still be the extra beat. The live\_loop must play at least once for the others to sync to it, hence the extra foo.

There are threads and examples that discuss how to overcome this issue, and various proposed fixes, including this one that perhaps gets closest (closer) to a solution: [http://in-thread.sonic-pi.net/t/live-loops-sync-questions/1172/18](http://in-thread.sonic-pi.net/t/live-loops-sync-questions/1172/18)

There’s a bit more here: [https://in-thread.sonic-pi.net/t/using-sync-with-live-loops/172/2](https://in-thread.sonic-pi.net/t/using-sync-with-live-loops/172/2)

Do have a look and see if these help to resolve the issue.

---

_[View the full topic](https://in-thread.sonic-pi.net/t/confusing-sync-cue-behavior/7155)._