# I3 select button and release issues

**URL:** <https://vistaforum.chroma-q.com/t/i3-select-button-and-release-issues/397>\
**Category:** Vista 3 Releases\
**Created:** [October 13, 2018, 5:38pm UTC](https://vistaforum.chroma-q.com/t/i3-select-button-and-release-issues/397 "2018-10-13T17:38:16Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mattb](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@mattb](https://vistaforum.chroma-q.com/u/mattb)\
**Post date:** [October 13, 2018, 5:38pm UTC](https://vistaforum.chroma-q.com/t/i3-select-button-and-release-issues/397/1 "2018-10-13T17:38:16Z")

</div>

Just installed the Vista 3 software on our i3. Here are the glitches we’re seeing:

1. The select button plays the first cue live but doesn’t show it as playing on the playback window.
2. Hitting release from this condition initially releases it, then plays it live again.
3. Sometimes the cuelest will release at the end with play, sometimes it won’t.

Cuelest properties are setup with:  
play at end option - release  
fader auto play - none

Has anyone else seen this behavior with the new software?

---

<div class="post-metadata">

**Author:** ![jack.moorhouse](https://sea2.discourse-cdn.com/flex016/user_avatar/vistaforum.chroma-q.com/jack.moorhouse/32/439_2.png) [@jack.moorhouse](https://vistaforum.chroma-q.com/u/jack.moorhouse)\
**Post date:** [October 15, 2018, 8:55am UTC](https://vistaforum.chroma-q.com/t/i3-select-button-and-release-issues/397/2 "2018-10-15T08:55:43Z")

</div>

Hi Matt,

I think all of your points might be related to a single bug.

Do you have the superplayback in cuelist mode (not intensity poistion colour gobo beam etc) ?  
If you put the crossfader to 0% does this solve the problem of the select button playing the cue?

Remember, the forum isn’t the best place for reporting these sorts of issues. Please submit an official [support request](http://www.vistabychromaq.com/vista-by-chroma-q-support-request/) and attach a copy of your showfile that exhibits the problem.

---

<div class="post-metadata">

**Author:** ![mattb](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@mattb](https://vistaforum.chroma-q.com/u/mattb)\
**Post date:** [October 15, 2018, 12:00pm UTC](https://vistaforum.chroma-q.com/t/i3-select-button-and-release-issues/397/3 "2018-10-15T12:00:02Z")

</div>

Jack,

You are spot on with your analysis. It was indeed the crossfader that had been pushed up. Very embarrasing.

Thanks,

Matt

---

<div class="post-metadata">

**Author:** ![jack.moorhouse](https://sea2.discourse-cdn.com/flex016/user_avatar/vistaforum.chroma-q.com/jack.moorhouse/32/439_2.png) [@jack.moorhouse](https://vistaforum.chroma-q.com/u/jack.moorhouse)\
**Post date:** [October 23, 2018, 10:47am UTC](https://vistaforum.chroma-q.com/t/i3-select-button-and-release-issues/397/4 "2018-10-23T10:47:07Z")

</div>

Don’t be embarrassed, that behavior shouldn’t happen. It is a bug.

We have fixed it and the fix will be rolled out within the next update.

---

<div class="post-metadata">

**Author:** ![Theisbr](https://avatars.discourse-cdn.com/v4/letter/t/e9bcb4/32.png) [@Theisbr](https://vistaforum.chroma-q.com/u/Theisbr)\
**Post date:** [November 12, 2018, 3:59am UTC](https://vistaforum.chroma-q.com/t/i3-select-button-and-release-issues/397/5 "2018-11-12T03:59:44Z")

</div>

When will this new update occur? We are having the same issue on our L5.

---

<div class="post-metadata">

**Author:** ![jack.moorhouse](https://sea2.discourse-cdn.com/flex016/user_avatar/vistaforum.chroma-q.com/jack.moorhouse/32/439_2.png) [@jack.moorhouse](https://vistaforum.chroma-q.com/u/jack.moorhouse)\
**Post date:** [November 12, 2018, 10:07am UTC](https://vistaforum.chroma-q.com/t/i3-select-button-and-release-issues/397/6 "2018-11-12T10:07:32Z")

</div>

There is no time frame that I can currently commit to . We have added some small new features and are continuing to add improvements to the existing feature set, because of this we need to ensure the software is appropriately alpha and beta tested before releasing. We are however making great progress.

As mentioned in the other thread …If you set the crossfader to 0% (or disable it if you are not using it) you will not encounter the problem discussed.
