Marking glitch when looping still in 2.1.2

Hi there,

Sorry for the issues. Can you post a showfile where you're seeing this?

Thanks!

Hans

Steps to recreate the problem

Using 2.1.2 start a new show.

In Patch:

Chan 1 Type Wybron CXI Scroller Mix @ 1
Chan 1 Part 2 Type Generic Dimmer @ 3

In Live Table mode:

Chan 1 @ 0 <enter>

Record Cues 1, 2, and 3.

Chan 1 @ FL <enter>
Chan 1 Color 5/26 <enter>

Chan 1 Mark Cue 2 <enter>

Record Q 4.

Cue 4 Link to Cue 3

Press Go.

You should see Channel 1 fade to zero, then the scroller moves to its home (cue 1) position.
Hiting Go again shows the scroller parameters in dull green indicating live movement.

Compare this to Go to Q 3 and Backing into Cue 3.

This problem wasn't in version 2.0.1.

So apparently using Go To Cue Mark and Load Cue are also affected when jumping to a previous cue.  It seems the Mark option has been applied as a default for Link to Cue and Load Cue, even though it fails to play the cues properly.  Since it is in all 2.1 versions I can't tell if ETC engineers are oblivious to this or proud of it.  By the weak response my post has gotten I expect the issue will quietly appear on the never-shrinking Known Issues list.

Hi there,

I was able to reproduce this behavior in version 2.1.2, but I wasn't able to reproduce this in version 2.2.0 using the steps to reproduce (I do appreciate that greatly -- it helped get to the root of the issue quickly). Before posting back that this was fixed in the next version, however, I was working to confirm that this was an intentional change. I didn't want to post back until I had confirmation one way or another. I agree with you that it definitely appears to be a bug in 2.1.2.

I understand your frustration. Rest assured, we take bug reports seriously and we want to minimize the amount of time that a bug is in the field, but it needs to get prioritized against other known issues and feature work. We work hard on this-- as an example of bug fixes, take a look at the v2.0.0 release note -- we did a significant amount of bug fixing in addition to a large volume of feature work.

As soon as I know more about the state of the issue, I'll post back and let you know. I apologize for the delay in replying.

Thanks!

Hans

I think I would rather see a version 2.1.3 ( ie the current feature set fully patched ), before a new set of features (and issues) arise.   As a linux user, I am used to the idea of backporting fixes to prior releases, giving users the choice of adding (or avoiding) new features.  I know of users who refuse to go beyond 2.0.1 because they have become wary of updates that take on too much.  I only upgraded to 2.1.0 to get rid of the Undo bug that was affecting me.  I never had used the Go To Cue # Mark feature, yet it came around to bite me in a cue link while using 2.1.0.

i don't think those users refusing to go past 2.0.1 because of big steps will be really helpful. after all if they decide after let's say three updates that they like one of the new features too much to resist, they have so many more changes to cope with. it's like some people didn't go past the shift-key update (1.9.8 i think) and after 2.0 was released they wanted magic sheets, needed to update and thus had to cope with all shift-key changes as well as everything else that happened in 1.9.10, .11, .12 and 2.0 ...

Well I think that making users wait for ETC to get kinks out of magic sheets ( or any other new features that they didn't want anyway), before fixing the current list of bugs is foolish and short sighted, attempting to dazzle new customers while blowing off complaints from previous buyers.

I remember reporting a bug in Expression 2.1.8 (I believe) that got fixed a year later in the very next version ...3.0 (seriously), that came with a bunch or new bugs and behaviour changes.  In fact, while checking out 3.0 beta version, we found the system clock was not running the whole time.  Don't get me started with obessions I & II.  That's why in some circles ETC is known for breaking one thing for every two things they fix, or is it the other way round.

To revise my earlier point.  There should not be a 2.2 unitl after versions  2.1.3 thru 2.1.9  and all of those dealing with current issues. Or in other words..Don't bundle patches with features.

33boardop said:

I think I would rather see a version 2.1.3 ( ie the current feature set fully patched ), before a new set of features (and issues) arise.   As a linux user, I am used to the idea of backporting fixes to prior releases, giving users the choice of adding (or avoiding) new features.  I know of users who refuse to go beyond 2.0.1 because they have become wary of updates that take on too much.  I only upgraded to 2.1.0 to get rid of the Undo bug that was affecting me.  I never had used the Go To Cue # Mark feature, yet it came around to bite me in a cue link while using 2.1.0.

Despite the fact that 2.0.1 had come out, I made the decision to wait six months for my off season to update the console.  In the past, I have never had an issue upgrading the software, but choose to wait, just in case.  Now that 2.1.X is out, there have been several bug fixes that I would like to take advantage of.  But will wait for another 2 months.

@33boardop   If you are unsatisfied with any bugs found in the 2.1.X series software, there is nothing stopping you from downgrading the console software.  

And now I am curious as to what this "Undo" bug you are talking about is.  I frequently use Undo and haven't had problems.  Guess I should read the release notes more carefully.

Hi there,

The out-of-sequence marking issue that we discussed is indeed fixed in version 2.2.0 (currently in beta). This was definitely a bug -- SCR 26118, and was found in version 2.1.0 of software. Version 2.0.1 did not exhibit this issue. 

As a workaround in version 2.1.0 through 2.1.2, I was able to do a playback assert on the cue, which put the fixture back in the correct location. The process for doing this would be to press [Fader Controls], then press and hold the {Assert} button and press the [Load] button on the fader. 

Thanks!

Hans